nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Bitbucket Pipeline Paused the pipeline

venkatcss

Hi Team,

I have setup the Bit bucket pipeline in my environment .

When multiple users commits one by one .. Second commit pipeline is going to pause mode.

first commit pipeline is only running.. But here I want to run the latest commit pipeline need to run..

I hope you got it my problem.. Please help me on this issue.

Bitbucket-pipeline.yml

---
image: "node:10.15.0"
pipelines:
branches:
development:
-
step:
deployment: test
name: "install and build"
caches:
- node
script:
- "apt-get update -y"
- "apt-get install -y zip"
- "cd admin/front-end"
- "npm install"
- CI=false
- "npm run build"
- "zip -r /tmp/artifact.zip *"
trigger: automatic
artifacts:
- admin/front-end/build/**
-
step:
image: "python:3.5.7"
name: test
caches:
- pip
script:
- "apt-get update -y"
- "pip install boto3==1.9.197"
- "apt-get install -y zip"
- "zip -r /tmp/artifact.zip *"
- "python codedeploy_deploy.py"

Thanks & regards,

venkat

Accepted answers

All comments

Rafael Pinto Sperafico_35quns

Hi @venkatcss ,

Pipelines will automatically check if there is a deployment in progress before starting a new one to the same environment. If there is already a deployment in progress, later pipelines deploying to the same environment will be paused.

More information can be found on Deployment concurrency control.

Kind regards,
Rafael

venkatcss

Hi rsperafico,

Thanks for your reply Yes I agreed it's happening for me.. But if it's happens like this my

It will causes problems for my all code.. so I want to run latest commit pipeline .

is it possible or not?

But as per your information after paused the pipeline do i need to resume the pipeline manually?

Regards,

Venkat

Rafael Pinto Sperafico_35quns

Hi @venkatcss ,

As the documentation suggests (Deployment concurrency control), you can manually:

Rerun the whole pipeline from the beginning
Resume the paused pipeline at the step it became paused

When setting up bitbucket-pipelines.yml, you can define if the build will get trigger automatically or manually. Based on your YAML, builds will be triggered automatically getting the latest commit from your development branch.

The build is based on a commit, so in the screenshot you have provided the build will be executed against commit 3ff2c6f regardless if there are new commit.

Perhaps you should consider making use of tags, running builds only when a tag is created or updated. In this way, you will define what should run and what should not.

Please, refer to the following documentation for further information:

Kind regards,
Rafael

Shawn Hempel

@Rafael Pinto Sperafico wouldn't it make sense to automatically resume after the current deployment completes?

In a Continuous Integration model, our expectation is that every commit will eventually make it to the integration environment without any manual intervention.

It should not be necessary to use tags or manually resume the pipeline. The logic we (and I suspect most people) would want is for concurrency to automatically resume the pipeline after the deployment completes.