The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
× Create
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Community resources
Community resources
Community resources
Parameterized Builds for Jenkins
Srinivasan Gunasekaran
September 12, 2017 edited
We have a setup in bitbucket for any checkins to trigger a job in jenkins.
It is working fine. For every checkin, trigerring a job and it will be in queue for previous job to complete.
Now, we have a issue like if they do multiple checkins in short time, lets take 5 checkins for example and if the first jenkins job is completed only after the 5th checkin, then the second job will take the source code of 5th (latest checkin) checkin instead of the 2nd one.
Please guide is there any way to overcome this.
0 answers
Comments for this post are closed
Community moderators have prevented the ability to post new answers.
Copyright © 2026 Atlassian