Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-67065

Cannot select anything related to BitBucket in Conditional Build Step

      I am attempting to make one of my jobs "smarter" by using conditional build steps to trigger different build actions. The most obvious choice for me is to use a "Build Cause" then trigger based on the different things that might cause this job to run. The issue I am encountering is that none of the available "Build Cause" options appears to apply to build triggered by the "Build when a change is pushed to BitBucket" trigger.

      Ideally, I would be able to select a BuildCause that aligns with the "Build when a change is pushed to BitBucket" option.

          [JENKINS-67065] Cannot select anything related to BitBucket in Conditional Build Step

          I'm not maintaining the plugin anymore, but just as a reference: it seems what you need to do is to extend the run condition plugin to know about the build causes you wish to be supported:

          Dominik Bartholdi added a comment - I'm not maintaining the plugin anymore, but just as a reference: it seems what you need to do is to extend the run condition plugin to know about the build causes you wish to be supported: https://plugins.jenkins.io/run-condition/ https://github.com/jenkinsci/run-condition-plugin/blob/master/src/main/java/org/jenkins_ci/plugins/run_condition/core/CauseCondition.java#L50-L115

          Mike Jones added a comment -

          imod My assumption is that Jenkins has some "known" triggers that Run Condition can see and that the Bitbucket plugin should be "triggering" one of those.

          Not sure how/why this was assigned to you, unless this system looks at the tagged plugins and picks the "best" maintainer.

          Mike Jones added a comment - imod My assumption is that Jenkins has some "known" triggers that Run Condition can see and that the Bitbucket plugin should be "triggering" one of those. Not sure how/why this was assigned to you, unless this system looks at the tagged plugins and picks the "best" maintainer.

          I'm just the default assignee because I used to maintain the conditional-build-step plugin, the run-condition plugin and a couple of other plugins and the default assignee has not yet been changed  ...but you are free to adopt the plugins...

          your assumption is correct, just follow the links I provided - the known triggers are easy to identify in the source: https://github.com/jenkinsci/run-condition-plugin/blob/master/src/main/java/org/jenkins_ci/plugins/run_condition/core/CauseCondition.java#L50-L115

           

          Dominik Bartholdi added a comment - I'm just the default assignee because I used to maintain the conditional-build-step plugin, the run-condition plugin and a couple of other plugins and the default assignee has not yet been changed  ...but you are free to adopt the plugins... your assumption is correct, just follow the links I provided - the known triggers are easy to identify in the source:  https://github.com/jenkinsci/run-condition-plugin/blob/master/src/main/java/org/jenkins_ci/plugins/run_condition/core/CauseCondition.java#L50-L115  

          Tzach Solomon added a comment -

          Hi mkdjns ,

          1. Is this still relevant?
          2. If answer to #1 is yes, than this is not related to bitbucket-plugin but to run-condition plugin. Please change to that plugin

          Tzach Solomon added a comment - Hi mkdjns , 1. Is this still relevant? 2. If answer to #1 is yes, than this is not related to bitbucket-plugin but to run-condition plugin. Please change to that plugin

            Unassigned Unassigned
            mkdjns Mike Jones
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: