A plugin for uploading build artifacts to, or downloading build dependencies from, Microsoft Azure Blob storage. (For a more detailed tutorial see http://go.microsoft.com/fwlink/?LinkId=280058)
This plugin is available in the Jenkins plugin manager. To install in Jenkins, go to Manage Jenkins | Manage Plugins | Available | Windows Azure Storage Plugin | Install. Then restart Jenkins to complete the installation.
At least one Azure storage account must be configured in the global configuration before the plugin can be used in build steps. To add a storage account, go to Manage Jenkins | Configure System | Microsoft Azure Storage Account Configuration and fill out the needed information.
For a more detailed tutorial see: http://go.microsoft.com/fwlink/?LinkId=280058.
The Upload artifacts to Azure
post-build step uploads a build artifact generated by your build to Azure Blob storage.
- Select the storage account name to use from the dropdown control
- Enter a name for the container. A new container will be created if it does not exist. Environment variables can also be referenced. For example: ${JOB_NAME}
- Enter the list of artifacts to upload, following the Ant glob syntax. You may create mappings between groups of artifacts and the virtual directory structure for them to be put under in the blob storage using the "::" notation.
- Optionally, specify the common virtual path under the container that the artifacts will be placed under. This string (followed by a slash '/' character) will follow the container name (after a slash) in the URL for each artifact. Any combination of characters can be used, but reserved URL characters must be properly escaped. Environment variables can also be referenced. For example: "${BUILD_ID}/${BUILD_NUMBER}/"
The `Download from Azure blob storage’ build step downloads blob contents from Azure blob storage.
- Select the storage account name to use from the dropdown control
- Select 'Download From Container' or 'Download artifact from build'.
- 'Download From Container' >> Enter the name of the container to download from. Environment variables can also be referenced. For example: ${JOB_NAME}
- 'Download artifact from build' >> Enter Project Name and select the build from the drop-down for 'Build to download' . For example: 'Latest successful build'.
- Enter the name of the blob to download. You may also use the wild card "" at the end to select multiple blob downloads sharing the same prefix, for example: project
- Optionally, enter the target download path. If not specified, the files will be downloaded into the job's workspace. Environment variables can also be referenced, for example: ${JOB_NAME}
For a tutorial, see http://go.microsoft.com/fwlink/?LinkId=280058.
- storage account key has become a hidden field.
- added the capability to use managed artifacts, a use case for artifacts can be downloading a known good build or an artifact from an upstream build.
- artifacts can be downloaded from previous builds.
- links on the project page (to download) has been fixed. This now allows easier access to download artifacts from Jenkins.
- downloads are now faster, plugin doesn't need to search the entire container for the correct blobs when using managed artifacts.
- changes are made inline with Jenkins API, updated Azure Java SDK to provide better output to Jenkins REST API.
- Added easily accessible links for azure artifacts uploaded to blob storage.
- changed the logic of the "make container public" checkbox to apply to newly created containers only
- added a "download from blob" build action
- added a "clean container" option to the artifact uploader post-build action
- some renamings due to branding changes in Azure (Windows Azure changing to Microsoft Azure)
- Initial release