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

bitbucket notifier not configurable under pipeline

XMLWordPrintable

      Issue JENKINS-33841 was supposed to add support to pipeline for build status notifier. However, there is no way for a project to set it's local oauth credentials. Neither in the pipeline nor as a pipeline configuraiton option. Documentation says you have to set credentials in Bitbucket notify build status post build action, but there is no such thing as "post build action" in a pipeline.

          [JENKINS-39779] bitbucket notifier not configurable under pipeline

          Antonio Mansilla added a comment -

          Hi ddelbecq sorry for my late answer. For working with the pipeline there is no way to add the credentials in "Bickbucket notifiy build status post action" so the properly way is to add that credentials globally as explained in the documentation: See "Add OAuth Credentials to Jenkins" -> "Global".

          Please let me know, whether this solves your problem.

          Antonio Mansilla added a comment - Hi ddelbecq sorry for my late answer. For working with the pipeline there is no way to add the credentials in "Bickbucket notifiy build status post action" so the properly way is to add that credentials globally as explained in the documentation: See "Add OAuth Credentials to Jenkins" -> "Global". Please let me know, whether this solves your problem.

          David Delbecq added a comment -

          Hello Antonio,

          We have moved away from pipeline and went back to regular builds where we could select credentials to use. Having a single jenkins credentials for bitbucket notfify was not an option here as each team sharing that jenkins are clearly separated at bitbucket level and tool credentials would be different for each project. Having a global bitbucket "jenkins" account was not an option.

          David Delbecq added a comment - Hello Antonio, We have moved away from pipeline and went back to regular builds where we could select credentials to use. Having a single jenkins credentials for bitbucket notfify was not an option here as each team sharing that jenkins are clearly separated at bitbucket level and tool credentials would be different for each project. Having a global bitbucket "jenkins" account was not an option.

            flagbit Antonio Mansilla
            ddelbecq David Delbecq
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: