Using Azure Storage with a Hudson Continuous Integration solution


The following information shows how to use Blob storage as a repository of build artifacts created by a Hudson Continuous Integration (CI) solution, or as a source of downloadable files to be used in a build process. One of the scenarios where you would find this useful is when you're coding in an agile development environment (using Java or other languages), builds are running based on continuous integration, and you need a repository for your build artifacts, so that you could, for example, share them with other organization members, your customers, or maintain an archive. Another scenario is when your build job itself requires other files, for example, dependencies to download as part of the build input.

In this tutorial, you will be using the Azure Storage plugin for Hudson CI made available by Microsoft.

Introduction to Hudson

Hudson enables continuous integration of a software project by allowing developers to easily integrate their code changes and have builds produced automatically and frequently, thereby increasing the productivity of the developers. Builds are versioned, and build artifacts can be uploaded to various repositories. This article will show how to use Azure Blob storage as the repository of the build artifacts. It will also show how to download dependencies from Azure Blob storage.

More information about Hudson can be found at Meet Hudson.

Benefits of using the Blob service

Benefits of using the Blob service to host your agile development build artifacts include:

  • High availability of your build artifacts and/or downloadable dependencies.
  • Performance when your Hudson CI solution uploads your build artifacts.
  • Performance when your customers and partners download your build artifacts.
  • Control over user access policies, with a choice between anonymous access, expiration-based shared access signature access, private access, etc.


You will need the following to use the Blob service with your Hudson CI solution:

  • A Hudson Continuous Integration solution.

    If you currently don't have a Hudson CI solution, you can run a Hudson CI solution using the following technique:

    1. On a Java-enabled machine, download the Hudson WAR from

    2. At a command prompt that is opened to the folder that contains the Hudson WAR, run the Hudson WAR. For example, if you have downloaded version 3.1.2:

      java -jar hudson-3.1.2.war

    3. In your browser, open http://localhost:8080/. This will open the Hudson dashboard.

    4. Upon first use of Hudson, complete the initial setup at http://localhost:8080/.

    5. After you complete the initial setup, cancel the running instance of the Hudson WAR, start the Hudson WAR again, and reopen the Hudson dashboard, http://localhost:8080/, which you will use to install and configure the Azure Storage plugin.

      While a typical Hudson CI solution would be set up to run as a service, running the Hudson war at the command line will be sufficient for this tutorial.

  • An Azure account. You can sign up for an Azure account at

  • An Azure storage account. If you don't already have a storage account, you can create one using the steps at Create a Storage Account.

  • Familiarity with the Hudson CI solution is recommended but not required, as the following content will use a basic example to show you the steps needed when using the Blob service as a repository for Hudson CI build artifacts.

How to use the Blob service with Hudson CI

To use the Blob service with Hudson, you'll need to install the Azure Storage plugin, configure the plugin to use your storage account, and then create a post-build action that uploads your build artifacts to your storage account. These steps are described in the following sections.

How to install the Azure Storage plugin

  1. Within the Hudson dashboard, click Manage Hudson.
  2. On the Manage Hudson page, click Manage Plugins.
  3. Click the Available tab.
  4. Click Others.
  5. In the Artifact Uploaders section, select Microsoft Azure Storage plugin.
  6. Click Install.
  7. After the installation is complete, restart Hudson.

How to configure the Azure Storage plugin to use your storage account

  1. Within the Hudson dashboard, click Manage Hudson.

  2. On the Manage Hudson page, click Configure System.

  3. In the Microsoft Azure Storage Account Configuration section:

    a. Enter your storage account name, which you can obtain from the Azure portal.

    b. Enter your storage account key, also obtainable from the Azure portal.

    c. Use the default value for Blob Service Endpoint URL if you are using the global Azure cloud. If you are using a different Azure cloud, use the endpoint as specified in the Azure portal for your storage account.

    d. Click Validate storage credentials to validate your storage account.

    e. [Optional] If you have additional storage accounts that you want made available to your Hudson CI, click Add more storage accounts.

    f. Click Save to save your settings.

How to create a post-build action that uploads your build artifacts to your storage account

For instruction purposes, first we'll need to create a job that will create several files, and then add in the post-build action to upload the files to your storage account.

  1. Within the Hudson dashboard, click New Job.

  2. Name the job MyJob, click Build a free-style software job, and then click OK.

  3. In the Build section of the job configuration, click Add build step and choose Execute Windows batch command.

  4. In Command, use the following commands:

         md text
         cd text
         echo Hello Azure Storage from Hudson > hello.txt
         date /t > date.txt
         time /t >> date.txt
  5. In the Post-build Actions section of the job configuration, click Upload artifacts to Microsoft Azure Blob storage.

  6. For Storage Account Name, select the storage account to use.

  7. For Container Name, specify the container name. (The container will be created if it does not already exist when the build artifacts are uploaded.) You can use environment variables, so for this example enter ${JOB_NAME} as the container name.


    Below the Command section where you entered a script for Execute Windows batch command is a link to the environment variables recognized by Hudson. Click that link to learn the environment variable names and descriptions. Environment variables that contain special characters, such as the BUILD_URL environment variable, are not allowed as a container name or common virtual path.

  8. Click Make new container public by default for this example. (If you want to use a private container, you'll need to create a shared access signature to allow access. That is beyond the scope of this article. You can learn more about shared access signatures at Using Shared Access Signatures (SAS).)

  9. [Optional] Click Clean container before uploading if you want the container to be cleared of contents before build artifacts are uploaded (leave it unchecked if you do not want to clean the contents of the container).

  10. For List of Artifacts to upload, enter text/*.txt.

  11. For Common virtual path for uploaded artifacts, enter ${BUILD_ID}/${BUILD_NUMBER}.

  12. Click Save to save your settings.

  13. In the Hudson dashboard, click Build Now to run MyJob. Examine the console output for status. Status messages for Azure Storage will be included in the console output when the post-build action starts to upload build artifacts.

  14. Upon successful completion of the job, you can examine the build artifacts by opening the public blob.

    a. Sign in to the Azure portal.

    b. Click Storage.

    c. Click the storage account name that you used for Hudson.

    d. Click Containers.

    e. Click the container named myjob, which is the lowercase version of the job name that you assigned when you created the Hudson job. Container names and blob names are lowercase (and case-sensitive) in Azure Storage. Within the list of blobs for the container named myjob you should see hello.txt and date.txt. Copy the URL for either of these items and open it in your browser. You will see the text file that was uploaded as a build artifact.

Only one post-build action that uploads artifacts to Azure Blob storage can be created per job. The single post-build action to upload artifacts to Azure Blob storage can specify different files (including wildcards) and paths to files within List of Artifacts to upload using a semi-colon as a separator. For example, if your Hudson build produces JAR files and TXT files in your workspace's build folder, and you want to upload both to Azure Blob storage, use the following for the List of Artifacts to upload value: build/*.jar;build/*.txt. You can also use double-colon syntax to specify a path to use within the blob name. For example, if you want the JARs to get uploaded using binaries in the blob path and the TXT files to get uploaded using notices in the blob path, use the following for the List of Artifacts to upload value: build/*.jar::binaries;build/*.txt::notices.

How to create a build step that downloads from Azure Blob storage

The following steps show how to configure a build step to download items from Azure Blob storage. This would be useful if you want to include items in your build, for example, JARs that you keep in Azure Blob storage.

  1. In the Build section of the job configuration, click Add build step and choose Download from Azure Blob storage.
  2. For Storage account name, select the storage account to use.
  3. For Container name, specify the name of the container that has the blobs you want to download. You can use environment variables.
  4. For Blob name, specify the blob name. You can use environment variables. Also, you can use an asterisk, as a wildcard after you specify the initial letter(s) of the blob name. For example, project\* would specify all blobs whose names start with project.
  5. [Optional] For Download path, specify the path on the Hudson machine where you want to download files from Azure Blob storage. Environment variables can also be used. (If you do not provide a value for Download path, the files from Azure Blob storage will be downloaded to the job's workspace.)

If you have additional items you want to download from Azure Blob storage, you can create additional build steps.

After you run a build, you can check the build history console output, or look at your download location, to see whether the blobs you expected were successfully downloaded.

Components used by the Blob service

The following provides an overview of the Blob service components.

  • Storage account: All access to Azure Storage is done through a storage account. This is the highest level of the namespace for accessing blobs. An account can contain an unlimited number of containers, as long as their total size is under 100 TB.

  • Container: A container provides a grouping of a set of blobs. All blobs must be in a container. An account can contain an unlimited number of containers. A container can store an unlimited number of blobs.

  • Blob: A file of any type and size. There are two types of blobs that can be stored in Azure Storage: block and page blobs. Most files are block blobs. A single block blob can be up to 200 GB in size. This tutorial uses block blobs. Page blobs, another blob type, can be up to 1 TB in size, and are more efficient when ranges of bytes in a file are modified frequently. For more information about blobs, see Understanding Block Blobs, Append Blobs, and Page Blobs.

  • URL format: Blobs are addressable using the following URL format:

    (The format above applies to the global Azure cloud. If you are using a different Azure cloud, use the endpoint within the Azure portal to determine your URL endpoint.)

    In the format above, storageaccount represents the name of your storage account, container_name represents the name of your container, and blob_name represents the name of your blob, respectively. Within the container name, you can have multiple paths, separated by a forward slash, /. The example container name in this tutorial was MyJob, and ${BUILD_ID}/${BUILD_NUMBER} was used for the common virtual path, resulting in the blob having a URL of the following form:

Next steps

For more information, visit Azure for Java developers.