Bitbucket allows you to run multiple pipelines by triggering them manually or by scheduling the trigger at a given time.
Overview
Run pipelines steps manually
Set a manual pipeline
Setup
Run a pipeline manually from the Branches view
Run a pipeline manually from the Commits view
Run a pipeline manually from the Pipelines page
On schedule
Setup
Create a schedule for your pipeline
Remove a schedule
Run pipelines steps manually
Manual steps allow you to customize your CI/CD pipeline by making some steps run only if they are manually triggered. This is useful for items such as deployment steps, where manual testing or checks are required before the step runs.
Configure a manual step by adding trigger: manual to the step in yourbitbucket-pipelines.ymlfile.
Since a pipeline is triggered on a commit, you can't make the first step manual. If you'd like a pipeline toonlyrun manually, you can set up acustompipeline instead. Another advantage of a custom pipeline is that you cantemporarily add or update values for your variables, for example, to add a version number, or supply a single-use value.
Set a manual pipeline
Any existing pipeline can also be manually run against a specific commit, or as ascheduled build.
If you want a pipeline toonlyrun manually then use a custom pipeline. Custom pipelinesdonotrun automatically on a commit to a branch. To define a custom pipeline, add the pipeline configuration in thecustomsection of yourbitbucket-pipelines.ymlfile. Pipelines which are not defined as a custom pipeline will also run automatically when a push to the branch occurs.
You'll needwritepermission on the repository to run a pipeline manually, and you can trigger it from the Bitbucket Cloud UI.
Setup
Add a pipeline to the bitbucket-pipelines.yml file. You can manually trigger a build for any pipeline build configuration included inyourbitbucket-pipelines.ymlfile
Example:123456789101112131415pipelines: custom: # Pipelines that can only be triggered manually sonar: - step: script: - echo "Manual triggers for Sonar are awesome!" deployment-to-prod: - step: script: - echo "Manual triggers for deployments are awesome!" branches: # Pipelines that run automatically on a commit to a branch can also be triggered manually staging: - step: script: - echo "Automated pipelines are cool too."Trigger the pipeline from Bitbucket Cloud. Pipelinescan be triggered manually from either the Branches view or the Commits view in the Bitbucket Cloud interface.
Run a pipeline manually from the Branches view
In Bitbucket, choose a repo and go toBranches.
Choose the branch you want to run a pipeline for.
Click (...) , and selectRun pipeline for a branch.
Choose a pipeline and clickRun:
Run a pipeline manually from the Commits view
In Bitbucket, choose a repo and go toCommits.
Go to the Commits' view for a commit.
Select a commit hash.
SelectRun pipeline.
Choose a pipeline, then clickRun:
Run a pipeline manually from the Pipelines page
In Bitbucket, choose a repo and go toPipelines.
ClickRun pipeline
Choose branch, a pipeline, and clickRun
Additionally, you can run custom pipelines manually parsing variables to the pipeline.
To enable the variables, define them under the custom pipeline that you want to enter when you run the pipeline.
Example:
12345678910pipelines: custom: custom-name-and-region: #name of this pipeline - variables: #list variable names under here - name: Username - name: Region - step: script: - echo "User name is $Username" - echo "and they are in $Region"
Then, when you run a custom pipeline by going to Branches>⋯>Run pipeline for a branch>Custom.
On schedule
Scheduled pipelines allow you to run a pipeline at hourly, daily or weekly intervals.
Scheduled pipelines run in addition to any builds triggered by commits, or triggered manually.
You can create a schedule for anypipeline defined in yourbitbucket-pipelines.ymlfile.
If you make a custom pipeline it will only run when scheduled or manually triggered.
Setup
Create a pipeline. Here's a simple example showing how you would define a custom pipelinein thebitbucket-pipelines.ymlfile.
Example:
123456pipelines: custom: # defines that this can only be triggered manually or by a schedule staging: # The name that is displayed in the list in the Bitbucket Cloud GUI - step: script: - echo "Scheduled builds in Pipelines are awesome!"
Read more aboutcustom pipelines.
Create a schedule for your pipeline
Go to the repository in Bitbucket.
ClickPipelinesthenSchedules(at the top right), and then clickNew schedule.
Choose theBranchandPipelinethat you want to schedule:
The schedule will run the HEAD commit of the branch.
The pipeline must be defined in the bitbucket-pipelines.yml on the branch you selected.
Set theSchedule:
Select how often you would like the pipeline to run (hourly, daily or weekly)
Select the time (in your local time). However, your pipeline will be scheduled in UTC time (unaffected by daylight savings hours)
The scheduled pipeline can run at any time in the selected time period. This is to distribute all schedules in Pipelines triggering across the hour.
Remove a schedule
Go toPipelines>Schedules(at the top right-hand side of the screen)to see all the schedules for a repository.
Remove a schedule by using the 'trash' icon at the right of the schedule.
Note that schedules created using the API are displayed as a Cron expression (such as0 10 15 * *).
