See Gitlab documentation for webhooks and webhook events. ID of the trigger that received the event Value will be empty string if the pipeline is triggered by other sources. The unique id of the schedule if it is a scheduled pipeline. The name of the schedule if it is a scheduled pipeline. The source that triggers the pipeline, current values are webhook, api, scheduled_pipeline. True if the pipeline is in the setup phase, for example, running a setup workflow. In addition, if the build was triggered via the API, the variable will not be present. When the build is the first build for a branch, the variable will not be present. Note: While in most cases _revision will be the SHA of the pipeline that ran before your currently running pipeline, there are some caveats. The long (40-character) git SHA of the build prior to the one being built. The long (40-character) git SHA that is being built. The name of the git branch that was pushed to trigger the pipeline. If the pipeline was not triggered by a tag, then this is the empty string. The name of the git tag that was pushed to trigger the pipeline. The lower-case name of the VCS provider, for example, “github”, “bitbucket”. The URL where the current project is hosted. VariableĪ globally unique id representing for the pipeline.Ī project unique integer id for the pipeline. They are interpolated at compilation time, not workflow/job runtime. Pipeline values are scoped at the pipeline level. Pipeline values are available to all pipeline configurations and can be used without previous declaration. We do not document the contents of this directory the data schema is subject to change. A directory where internal data related to the job is stored. The value of the working_directory key of the current job. This identifier is the same for every job in a given workflow. This identifier is the same for every job in a given workflow instance.Īn identifier for the workspace of the current job. The GitHub or Bitbucket username of the user who triggered the pipeline (only if the user has a CircleCI account).Ī unique identifier for the workflow instance of the current job. For more information, see the Git Tag Job Execution section of the Workflows page. The name of the git tag, if the current build is tagged. The SHA1 hash of the last commit of the current build. The URL of your GitHub or Bitbucket repository. If there are multiple associated pull requests, one URL is randomly chosen.Ĭomma-separated list of URLs of the current build’s associated pull requests. The GitHub or Bitbucket username of the current project. The name of the repository of the current project. This variable is likely to be deprecated, and CircleCI recommends users to avoid using it. Note: The variable is not always set, and is not deterministic. The largest job number in a given branch that is less than the current job number. The GitHub or Bitbucket username of the user who created the pull request. The name of the GitHub or Bitbucket repository where the pull request was created. The number of the associated GitHub or Bitbucket pull request. This is equivalent to the value of parallelism in your config file.Īn OpenID Connect token signed by CircleCI which includes details about the current job. The value ranges from 0 to ( CIRCLE_NODE_TOTAL - 1)įor jobs that run with parallelism enabled, this is the number of parallel runs. Job numbers are unique for each job.įor jobs that run with parallelism enabled, this is the index of the current parallel run. The name of the Git branch currently being built. True (represents whether the current environment is a CircleCI environment) True (represents whether the current environment is a CI environment)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |