![]() ![]() For more information, see schedules.cron definition - variable This variable is only set if the pipeline run is triggered by a YAML scheduled trigger. The displayName of the cron schedule that triggered the pipeline run. When you upload an artifact in your pipeline, it's added to a container that is specific for that particular artifact. The ID of the container for your artifact. You can define your build to clean it up on the Repository tab. The local path on the agent you can use as an output folder for compiled binaries.īy default, new build pipelines aren't set up to clean this directory. ![]() Note: This value can contain whitespace or other invalid label characters. You can specify what is included in this value.Ī typical use of this variable is to make it part of the label format, which you specify on the repository tab. The name of the completed build, also known as the run number. The ID of the record for the completed build. This variable is agent-scoped, and can be used as an environment variable in a script and as a parameter in a build task, but not as part of the build number or as a version control tag. This directory is purged before each new build, so you don't have to clean it up yourself. Note: Build.ArtifactStagingDirectory and Build.StagingDirectory are interchangeable. For example: c:\agent_work\1\aĪ typical way to use this folder is to publish your build artifacts with the Copy files and Publish build artifacts tasks. The local path on the agent where any artifacts are copied to before being pushed to their destination. Note: This directory isn't guaranteed to be writable by pipeline tasks (for example, when mapped into a container) Learn about managing this directory on a self-hosted agent. These tasks add tools from this directory to PATH so that subsequent build steps can use them. The directory used by tasks such as Node Tool Installer and Use Python Version to switch between multiple versions of a tool. NET Core CLI task to hold temporary items like test results before they're published.įor example: /home/vsts/work/_temp for Ubuntu Valid values are:Ī temporary folder that is cleaned after each pipeline job. The operating system processor architecture of the agent host. If you're running in a container, the agent host and container may be running different operating systems. If you're using a self-hosted agent, then this name is specified by you. The name of the agent that is registered with the pool. The name of the machine on which the agent is installed. The older agent.jobstatus is available for backwards compatibility. The environment variable should be referenced as AGENT_JOBSTATUS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |