Artifact
Last updated
Last updated
The integrated artifacts like GitHub, GitLab, GitRepo, and Bitbucket can be used in multiple stages of the Pipelines. The integrated accounts can be used to automate triggers by providing access to artifacts which are used in the pipeline execution process.
GitHub is a platform and cloud based service for software development and version control using Git. Refer to GitHub for more information.
To know how to add a GitHub Integration Refer to this page.
To Add GitHub Repo in the Pipeline Stages
The following steps provide details on how to access your GitHub repo and use it in the pipeline stages.
Create a pipeline by following the steps provided in Create Pipelines.
Click Configure and select the pipeline to which you want to add your GitHub repo.
Click Automated Triggers from the options provided on the left.
Click Add Trigger and select Git from the Type dropdown.
Select GitHub from the Repo Type dropdown.
In the Organization or User field, enter the organization name or your GitHub repo username
In the Project field, enter your GitHub project name.
In the Branch field, enter the branch name in the given format.
If branch name is specified, it pushes to the branches that match this Java Regular Expression and only that branch is triggered. Leave the branch name empty to trigger builds for every branch.
Enter the secret branch name (this is an optional field)
If specified, it verifies GitHub as the sender of this trigger. See GitHub docs for more information.
In the Artifact Constraints, by default deploy is displayed. To add your artifact, from the dropdown select Define a new artifact. Artifacts are required for the trigger to execute. Only one of the artifacts needs to be present for the trigger to execute.
Enter a Display Name for the artifact.
In the Account dropdown, select your account.
In the File path field enter the filepath of your github project that you want to integrate.
Check the Use prior execution, if you want to match against an artifact in the prior pipeline execution's context. This ensures that you will always be using the most recently supplied artifact to this pipeline, and is generally a safe choice.
Check the Use default artifact checkbox, if your artifact is not supplied from a trigger, or it wasn't found in a prior execution. See the reference for more information.
Click Save Artifact to save the changes.
Check the Trigger Enabled checkbox to trigger this.
Click Save Changes to save the changes or Revert to discard the changes.
Your GitHub repo is added in the pipeline stage and can be triggered from here.
GitLab is a DevOps software package which can develop, secure, and operate software. Refer to GitLab for more information.
To know how to add a GitLab Integration Refer to this page.
To Add GitLab in the Pipeline Stages
The following steps provide details on how to access your GitLab repo and use it in the pipeline stages.
Create a pipeline by following the steps provided in Create Pipelines.
Click Configure and select the pipeline to which you want to add your GitLab repo.
Click Automated Triggers from the options provided on the left.
Click Add Trigger and select Git from the Type dropdown.
Select GitLab from the Repo Type dropdown.
In the Organization or User field, enter the organization name or your GitLab repo username
In the Project field, enter your GitLab project name.
In the Branch field, enter the branch name in the given format.
If branch name is specified, it pushes to the branches that match this Java Regular Expression and only that branch is triggered. Leave the branch name empty to trigger builds for every branch.
Enter the secret branch name (this is an optional field)
In the Artifact Constraints, by default deploy is displayed. To add your artifact, from the dropdown select Define a new artifact. Artifacts are required for the trigger to execute. Only one of the artifacts needs to be present for the trigger to execute.
Enter a Display Name for the artifact.
In the Account dropdown, select your account.
In the File path field enter the filepath of your gitlab project that you want to integrate.
Check the Use prior execution, if you want to match against an artifact in the prior pipeline execution's context. This ensures that you will always be using the most recently supplied artifact to this pipeline, and is generally a safe choice.
Check the Use default artifact checkbox, if your artifact is not supplied from a trigger, or it wasn't found in a prior execution. See the reference for more information.
Click Save Artifact to save the changes.
Check the Trigger Enabled checkbox to trigger this.
Click Save Changes to save the changes or Revert to discard the changes.
Your GitLab repo is added in the pipeline stage and can be triggered from here.
Bitbucket cloud is a Git-based code and CI/CD tool optimized for teams using Jira. Refer to Bitbucket for more information.
To know how to add a Bitbucket Integration Refer to this page.
To Add Bitbucket in the Pipeline Stages
The following steps provide details on how to access your GitLab repo and use it in the pipeline stages.
Create a pipeline by following the steps provided in Create Pipelines.
Click Configure and select the pipeline to which you want to add your BitBucket repo.
Click Automated Triggers from the options provided on the left.
Click Add Trigger and select Git from the Type dropdown.
Select BitBucket from the Repo Type dropdown.
In the Team or User field, enter the team or user name.
In the Branch field, enter the branch name in the given format.
If branch name is specified, it pushes to the branches that match this Java Regular Expression and only that branch is triggered. Leave the branch name empty to trigger builds for every branch.
Enter the secret branch name (this is an optional field)
In the Artifact Constraints, by default deploy is displayed. To add your artifact, from the dropdown select Define a new artifact. Artifacts are required for the trigger to execute. Only one of the artifacts needs to be present for the trigger to execute.
Enter a Display Name for the artifact.
In the Account dropdown, select your account.
In the File path field enter the filepath of your bitbucket project that you want to integrate.
Check the Use prior execution, if you want to match against an artifact in the prior pipeline execution's context. This ensures that you will always be using the most recently supplied artifact to this pipeline, and is generally a safe choice.
Check the Use default artifact checkbox, if your artifact is not supplied from a trigger, or it wasn't found in a prior execution. See the reference for more information.
Click Save Artifact to save the changes.
Check the Trigger Enabled checkbox to trigger this.
Click Save Changes to save the changes or Revert to discard the changes.
Your Bitbucket account is added in the pipeline stage and can be triggered from here.
