web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :

Make use of predefined variables in your upload asset task

mhdshb1 Profile Picture mhdshb1 1,250

Hi everyone,

This is a very simple post that you can make use of when maintaining the asset library in the LCS with the help of Dynamics Lifecycle Services (LCS) Asset Upload.

Sustaining asset library with all the new deployable package releases and rolling back to a correct one is hectic in a busy environment.

As such, I am going to share with you some of the predefined build variables that help in achieving this. 

In your upload asset task in the release pipeline, you can add the Release or the Build predefined variables. 

For example i used,

  • $(Build.SourceBranch) to identify which branch the release is uploading and what is the branch of the triggering repo the build was queued for.
  • $(Release.ReleaseName) to get the name of the current release.
  • $(Build.BuildNumber) to identify the build number from the build pipeline.
  • $(Build.SourceVersion) to get the latest commit id for this build.
  • $(Release.Reason) to identify the reason of this release (Manual, Continuous Integration,Scheduled,None).

blog3.PNG

blog2.PNG

There are many other predefined variables you can make use of, and make your life easier. 

You can check these link for Predefined variables and Classic release and artifacts variables.

I hope this helps

Regards,

M

Comments

*This post is locked for comments