...
Select the <Project Name> Build Service from the user/group drop-down and set the role as contributor (contributor will have both read and write access).
...
Update Azure DevOps Build
...
Pipeline
Our Build pipeline downloads the code from the Git Codebase and uses ant plugin to create a jar file. We want to publish the created artifact to Azure Artifact.
...
Click on the Pipelines to navigate to the Pipeline Definition
Select the desired Build Pipeline and select Edit option as shown below.
Next, we shall will create the variables $packageName , and $packageVersion under pipeline definition.
...
Create another variable for $packageVersion by clicking on the '+' icon. As mentioned in previous step create the variable with name ( packageVersion ) and check on the ‘Let users override this value when running this pipeline’ checkbox.
...
Next, we shall can use Universal Package task to publish the generated artifact to Azure Artifacts feed.
On the right-hand pane, on the search box filter for Universal Package.
Click on the Universal Package to add the task to the existing YAML script.
...
Next, we shall will configure the Universal package task.
...
Build Workflow
Navigate to the Workflows tab and create a Build build workflow using the “+”(Click to create new Workflow) button. The Workflow Type field defines the type of workflow.
Build Workflow
Navigate to the Workflows tab
Select the “+” button from the left-hand pane to create a new workflow with type as Build.
...
The Workflow Group and Subgroup define the folder hierarchy. Once the workflow is created, it should look like the below. No constraint on workflow or folder naming convention.
...
The steps of the workflow execution can be configured through the Definition section.
Navigate through the plugin operations and find the desired one.
In our workflow execution, 2 plugin operations being used to achieve our goal.
...
Below given is the detailed explanation of our workflow operations.
...
Build Workflow Properties
We'll start by creating a Workflow Property for the Feed button as highlighted below.
...
Below are the steps of our workflow.
...
Build Workflow Properties
We'll start by creating a Workflow Property for the Feed Name, Package Name, Package Version, Project Name, Build Definition Name and Variables List.
Go back to the Main Properties tab of the Workflow
Under Workflow Properties, use Add option to add the properties.
From the Add menu, we We can add an existing property , or create a new one. Select New Property Create
Properties must each have a unique code, give a meaningful code for the new property.
A property Display Name does not have to be unique and can contain spaces. This is the name that will be displayed on the properties association screen.
Select the property scope, this defines where the property will be configured. We're using Project because this property can be overridden at project level.
Info |
---|
...
The properties scope can be Target as well. In case any property value is environment specific (e.g. Project Name is different for each environment), then the scope should be set as Target. This will |
...
change based on |
...
requirements. |
...
We are using multiple Project properties, not all of them are mandatory.
...
Input Name | Mandatory | Description |
---|---|---|
Feed Name | Yes | The Name of the Feed. |
Package Name | Yes | The Name of the Package. |
Project Name | Yes | The Name of the Project. |
Package Version | No | The Version of the package. |
Package Path | No | Absolute directory path to place the artifacts. If not specified, then it will place the files in the FD_ARTIFACTS_DIR. |
Additional Parameters | No | Add any additional parameters not listed above, which will be concatenated to the download artifacts command. |
...
. |
...
Topology
For detailed steps on how to configure the topology and target properties, please refer to Target Groups
Target Properties
Selecting the DEV environment mapped to the Target Group will display the configurable properties/Endpoint and allows to the configure the properties.
...