[JIRA] (JENKINS-60516) Jenkins pipeline triggered for all branches on code commit in Develop branch

17 views
Skip to first unread message

monali.chaudhary@capgemini.com (JIRA)

unread,
Dec 17, 2019, 8:46:02 AM12/17/19
to jenkinsc...@googlegroups.com
Monali Chaudhary created an issue
 
Jenkins / Bug JENKINS-60516
Jenkins pipeline triggered for all branches on code commit in Develop branch
Issue Type: Bug Bug
Assignee: Mark Waite
Components: git-plugin
Created: 2019-12-17 13:45
Priority: Major Major
Reporter: Monali Chaudhary

My developer is pushing the code in Dev branch of Bitbucket but in Jenkins it triggers Dev, Test, Stage and Prod pipeline though there is no changes deployed in Other branches and it simply redeploys the last commit in Test, Stage and Prod. But then why should any code push to DEV branch should trigger another pipelines.

Please note that every env pipeline is only checking out respective env branch for deployment. I had raised this issue with Bitbucket community as well but they confirmed that no issues seen from Bitbucket end and suggested to check from Jenkins end.

In my jenkins every pipeline is triggered based on "Build whenever a change is pushed to Bitbucket"

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

monali.chaudhary@capgemini.com (JIRA)

unread,
Dec 18, 2019, 4:29:05 AM12/18/19
to jenkinsc...@googlegroups.com
Monali Chaudhary commented on Bug JENKINS-60516
 
Re: Jenkins pipeline triggered for all branches on code commit in Develop branch

Hi Mark,

Can you please provide help for this issue as my production pipelines are getting triggered  and have disabled it until I get some workaround or solution for the same.

 

mark.earl.waite@gmail.com (JIRA)

unread,
Dec 18, 2019, 4:35:02 AM12/18/19
to jenkinsc...@googlegroups.com

mark.earl.waite@gmail.com (JIRA)

unread,
Dec 18, 2019, 4:43:02 AM12/18/19
to jenkinsc...@googlegroups.com
Mark Waite commented on Bug JENKINS-60516
 
Re: Jenkins pipeline triggered for all branches on code commit in Develop branch

You'll need to provide significantly more information so that others can duplicate the problem you're describing. Refer to "How to report an issue" for the guidelines.

When maintainers choose which bug reports they will investigate, their choice is strongly influenced by the content and clarity of the bug report.

If I spent several hours making guesses about the details of the configuration you are using, I could then describe what works and what doesn't work in my experiments. However, it is very likely that my guesses will be different from your configuration in important ways. Those differences could be the root of the problem. It probably won't help you or me if I make guesses about the configuration you are using.

Describe the issue in a way that someone like me can duplicate the problem based on your description of the problem. Which plugins are you using? What versions? What is the detailed job configuration of the job that is showing the problem? How are the webhooks configured on Bitbucket? Which type of Bitbucket are you running, cloud or server? Are there cases where the system behaves the way you want in this use case, or do you always have the poor behavior?

mark.earl.waite@gmail.com (JIRA)

unread,
Dec 18, 2019, 4:53:04 AM12/18/19
to jenkinsc...@googlegroups.com
Mark Waite edited a comment on Bug JENKINS-60516
You'll need to provide significantly more information so that others can duplicate the problem you're describing.  Refer to "[How to report an issue|https://wiki.jenkins.io/display/JENKINS/How+to+report+an+issue#Howtoreportanissue-WhatinformationtoprovideforEnvironmentandDescription]" for the guidelines.


When maintainers choose which bug reports they will investigate, their choice is strongly influenced by the content and clarity of the bug report.

If I spent several hours making guesses about the details of the configuration you are using, I could then describe what works and what doesn't work in my experiments.  However, it is very likely that my guesses will be different from your configuration in important ways.  Those differences could be the root of the problem.  It probably won't help you or me if I make guesses about the configuration you are using.

Describe the issue in a way that someone like me can duplicate the problem based on your description of the problem.  Which plugins are you using?  What versions?  What is the detailed job configuration of the job that is showing the problem?  How are the webhooks configured on Bitbucket?  Which type of Bitbucket are you running, cloud or server?  Are there cases where the system behaves the way you want in this use case, or do you always have the poor behavior?   Are you using webhooks to notify Jenkins?   What arguments are included in the Bitbucket webhook call to Jenkins?  If you poll for changes, does it behave the same way, or does it only build on the branch that changed?

monali.chaudhary@capgemini.com (JIRA)

unread,
Dec 20, 2019, 5:09:02 AM12/20/19
to jenkinsc...@googlegroups.com

monali.chaudhary@capgemini.com (JIRA)

unread,
Dec 20, 2019, 5:10:02 AM12/20/19
to jenkinsc...@googlegroups.com

monali.chaudhary@capgemini.com (JIRA)

unread,
Dec 20, 2019, 5:11:02 AM12/20/19
to jenkinsc...@googlegroups.com
Monali Chaudhary commented on Bug JENKINS-60516
 
Re: Jenkins pipeline triggered for all branches on code commit in Develop branch

Hi Mark,

 

Apologies for not providing detailed information. Please find the details in the attached document. Do let me know if you need any other information.

Jenkins_Issue_Details.docx

Regards,

Monali

mark.earl.waite@gmail.com (JIRA)

unread,
Dec 20, 2019, 11:18:03 AM12/20/19
to jenkinsc...@googlegroups.com

Monali Chaudhary since you only see the problem once a month and the creation of a new job is not enough to show the problem, I won't be able to help. I don't have any ideas to suggest for diagnosing a problem that occurs once a month.

mark.earl.waite@gmail.com (JIRA)

unread,
Dec 20, 2019, 7:11:02 PM12/20/19
to jenkinsc...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages