You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
pipelines are designed to trigger and run on every commit to specified branches/tags.
I'm curious to know more about your workflow, why do you want to avoid running multiple pipelines?
We have code deployed to our staging servers upon every commit to develop branch.
In situation when two commits are put into develop quickly one after another, two deployment processed are started almost simulateously and interfere with each other.
I have overcome this problem by setting up a lock mechanism in our deployment script using flock command.
I found this one because I am having the same issue.
@SebC the new pipeline should wait the current one to finish before being triggered. The reasons are very simple (pre setup) and this behaviour is pretty much standard across the tools which provide CI/CD as service.
I am sure this matter will be given the right attention.