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

Support for pipeline builds

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      It would be great if Bitbucket Build Status Notifier would support pipeline builds. There don't seem to be any way to use the Bitbucket Build Status Notifier plugin with the pipeline build that was added in Jenkins 2.0.

        Attachments

          Activity

          Hide
          itaisanders Itai Sanders added a comment -

          Yevhenii Kurtov I think you are gettin mixed up.
          you need to provide credentials to your repository in order to access it.

          you can either:
          1. provide them in the job configurations (and place the Jenkinsfile inside the scm), in which case you can simply call on 'scm checkout' to checkout the entire code. Jenkins then will use the credentials you used to access the Jenkinsfile in order to checkout that same repo.
          2. provide them inside the checkout call, as you first did, in case you are writing your pipeline code inside Jenkins (so you never configured the scm in the job configurations) or in case you wish to checkout a different repo than the one you used to store the Jenkinsfile.

          either way, you will still need to provide the notifier plugin with the credentials to mark the build status. you configure it inside the Jenkins Configure System (inside Manage Jenkins, not in the specific job). you will need to produce a dedicated OAuth credentials.

          this and more you can find in the very good README in github: https://github.com/jenkinsci/bitbucket-build-status-notifier-plugin

          and again - this is getting much more general than the discussed issue. you should raise those questions in Slack, or if you want you can Telegram me and I wouldn't mind helping you out as far as I can.

          Show
          itaisanders Itai Sanders added a comment - Yevhenii Kurtov I think you are gettin mixed up. you need to provide credentials to your repository in order to access it. you can either: 1. provide them in the job configurations (and place the Jenkinsfile inside the scm), in which case you can simply call on 'scm checkout' to checkout the entire code. Jenkins then will use the credentials you used to access the Jenkinsfile in order to checkout that same repo. 2. provide them inside the checkout call, as you first did, in case you are writing your pipeline code inside Jenkins (so you never configured the scm in the job configurations) or in case you wish to checkout a different repo than the one you used to store the Jenkinsfile. either way, you will still need to provide the notifier plugin with the credentials to mark the build status. you configure it inside the Jenkins Configure System (inside Manage Jenkins, not in the specific job). you will need to produce a dedicated OAuth credentials. this and more you can find in the very good README in github: https://github.com/jenkinsci/bitbucket-build-status-notifier-plugin and again - this is getting much more general than the discussed issue. you should raise those questions in Slack, or if you want you can Telegram me and I wouldn't mind helping you out as far as I can.
          Hide
          allan_burdajewicz Allan BURDAJEWICZ added a comment -

          Could we merge the pull request of Itai Sanders for Pipeline Multibranch Support: https://github.com/jenkinsci/bitbucket-build-status-notifier-plugin/pull/30?

          Show
          allan_burdajewicz Allan BURDAJEWICZ added a comment - Could we merge the pull request of Itai Sanders for Pipeline Multibranch Support: https://github.com/jenkinsci/bitbucket-build-status-notifier-plugin/pull/30?
          Hide
          itaisanders Itai Sanders added a comment -

          that would be great Allan BURDAJEWICZ!

          btw, I didn't get to test it myself (since I am using my locally compiled merged version), but I think if you don't use the default parameters of the plugin and define your own legal parameters manually, you would work around this bug (along with the "key per job and not per build" sort-of-a-bug).

          Show
          itaisanders Itai Sanders added a comment - that would be great Allan BURDAJEWICZ ! btw, I didn't get to test it myself (since I am using my locally compiled merged version), but I think if you don't use the default parameters of the plugin and define your own legal parameters manually, you would work around this bug (along with the "key per job and not per build" sort-of-a-bug).
          Hide
          chessracer Jonathan Baker added a comment -

          Is there a way, in a pipeline build, to override the global oauth credentials?

          Show
          chessracer Jonathan Baker added a comment - Is there a way, in a pipeline build, to override the global oauth credentials?
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Jesse Glick
          Path:
          COMPATIBILITY.md
          http://jenkins-ci.org/commit/pipeline-plugin/c84a9af380854dbafd66e265b63cd05969ad7c47
          Log:
          Merge pull request #439 from alexbrjo/alexbrjo-compat-update

          JENKINS-32263 JENKINS-32650 JENKINS-33841 JENKINS-33310 JENKINS-26591 JENKINS-30522 Updated support status for several plugins

          Compare: https://github.com/jenkinsci/pipeline-plugin/compare/23d473486c8e...c84a9af38085

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/pipeline-plugin/c84a9af380854dbafd66e265b63cd05969ad7c47 Log: Merge pull request #439 from alexbrjo/alexbrjo-compat-update JENKINS-32263 JENKINS-32650 JENKINS-33841 JENKINS-33310 JENKINS-26591 JENKINS-30522 Updated support status for several plugins Compare: https://github.com/jenkinsci/pipeline-plugin/compare/23d473486c8e...c84a9af38085

            People

            • Assignee:
              flagbit Antonio Mansilla
              Reporter:
              sajfer Anton Bretting
            • Votes:
              8 Vote for this issue
              Watchers:
              18 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: