[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title Jonathan Baker commented on JENKINS-33841 Re: Support for pipeline builds Is there a way, in a pipeline build, to override the global oauth credentials? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title Itai Sanders commented on JENKINS-33841 Re: Support for pipeline builds 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). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-33841 Re: Support for pipeline builds Could we merge the pull request of Itai Sanders for Pipeline Multibranch Support: https://github.com/jenkinsci/bitbucket-build-status-notifier-plugin/pull/30? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title Itai Sanders commented on JENKINS-33841 Re: Support for pipeline builds 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. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title Yevhenii Kurtov commented on JENKINS-33841 Re: Support for pipeline builds Before I used generated snippet to checkout the repository, checkout([$class: 'GitSCM', branches: [[name: 'master']], doGenerateSubmoduleConfigurations: false, extensions: [], submoduleCfg: [], userRemoteConfigs: [[credentialsId: 'c6bcc00a-8dea-4671-bdd3-8335a959d610', url: 'g...@bitbucket.org:org/proj.git']]]) but changed it to the `checkout scm` to fully reproduce your snippet. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title Itai Sanders commented on JENKINS-33841 Re: Support for pipeline builds Yevhenii Kurtov now you have a Credentials not Found exception. did you set them in the Jenkins Global Configurations? if you want some general help with Jenkins maybe it will be better to move to a more general platform e.g. https://devopsengineers.slack.com/archives/jenkins-ci (once there, feel free to pm me if you'd like. although I do follow the jenkins-ci channel anyway) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title
Yevhenii Kurtov edited a comment on JENKINS-33841
Re: Support for pipeline builds
Hi [~itaisanders]thank you for the tip, this is my first experience with Jenkins, so pretty frustrated atm due to the setup complexity. I tried to `checkout scm` before setting status, but change.Here is the script itself: {code:java}node {deleteDir()checkout scmbitbucketStatusNotify(buildState: 'INPROGRESS')sleep 10 bitbucketStatusNotify (buildState: 'SUCCESSFUL')}{code}and console output{code:java}Started by user lesslessReplayed #2Setting origin to g...@bitbucket.org:team/proj.gitFetching origin...[Pipeline] nodeRunning on master in /var/lib/jenkins/workspace/ ave88-g proj /feature%2Fadd-jenkinsfile[Pipeline] {[Pipeline] deleteDir[Pipeline] checkoutCloning the remote Git repositoryCloning repository g...@bitbucket.org:team/proj.git > git init /var/lib/jenkins/workspace/proj -g /feature%2Fadd-jenkinsfile # timeout=10Fetching upstream changes from g...@bitbucket.org:team/proj.git > git --version # timeout=10using GIT_SSH to set credentials > git -c core.askpass=true fetch --tags --progress g...@bitbucket.org:team/proj.git +refs/heads/*:refs/remotes/origin/* > git config remote.origin.url g...@bitbucket.org:team/proj.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url g...@bitbucket.org:team/proj.git # timeout=10Fetching upstream changes from g...@bitbucket.org:team/proj.gitusing GIT_SSH to set credentials > git -c core.askpass=true fetch --tags --progress g...@bitbucket.org:team/proj.git +refs/heads/*:refs/remotes/origin/*Checking out Revision 7911cc863d326253d1333cc899a837883dced255 (feature/add-jenkinsfile) > git config core.sparsecheckout # timeout=10 > git checkout -f 7911cc863d326253d1333cc899a837883dced255 > git rev-list 7911cc863d326253d1333cc899a837883dced255 # timeout=10[Pipeline] bitbucketStatusNotify[Pipeline] }[Pipeline] // node[Pipeline] End of Pipelinejava.lang.Exception: Credentials could not be found! at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusHelper.sendBuildStatusNotification(BitbucketBuildStatusHelper.java:262) at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusHelper.notifyBuildStatus(BitbucketBuildStatusHelper.java:252) at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifierStep$Execution.run(BitbucketBuildStatusNotifierStep.java:189) at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifierStep$Execution.run(BitbucketBuildStatusNotifierStep.java:140) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:52) at hudson.security.ACL.impersonate(ACL.java:213) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:49) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)Finished: FAILURE{code}
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title
Yevhenii Kurtov commented on JENKINS-33841
Re: Support for pipeline builds
Hi Itai Sanders thank you for the tip, this is my first experience with Jenkins, so pretty frustrated atm due to the setup complexity. I tried to `checkout scm` before setting status, but change. Here is the script itself:
node {
deleteDir()
checkout scm
bitbucketStatusNotify(buildState: 'INPROGRESS')
sleep 10
bitbucketStatusNotify (buildState: 'SUCCESSFUL')
}
and console output
Started by user lessless
Replayed #2
Setting origin to g...@bitbucket.org:team/proj.git
Fetching origin...
[Pipeline] node
Running on master in /var/lib/jenkins/workspace/ave88-g/feature%2Fadd-jenkinsfile
[Pipeline] {
[Pipeline] deleteDir
[Pipeline] checkout
Cloning the remote Git repository
Cloning repository g...@bitbucket.org:team/proj.git
> git init /var/lib/jenkins/workspace/proj-g/feature%2Fadd-jenkinsfile # timeout=10
Fetching upstream changes from g...@bitbucket.org:team/proj.git
> git --version # timeout=10
using GIT_SSH to set credentials
> git -c core.askpass=true fetch --tags --progress g...@bitbucket.org:team/proj.git +refs/heads/*:refs/remotes/origin/*
> git config remote.origin.url g...@bitbucket.org:team/proj.git # timeout=10
> git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url g...@bitbucket.org:team/proj.git # timeout=10
Fetching upstream changes from g...@bitbucket.org:team/proj.git
using GIT_SSH to set credentials
> git -c core.askpass=true fetch --tags --progress g...@bitbucket.org:team/proj.git +refs/heads/*:refs/remotes/origin/*
Checking out Revision 7911cc863d326253d1333cc899a837883dced255 (feature/add-jenkinsfile)
> git config core.sparsecheckout # timeout=10
> git checkout -f 7911cc863d326253d1333cc899a837883dced255
> git rev-list 7911cc863d326253d1333cc899a837883dced255 # timeout=10
[Pipeline] bitbucketStatusNotify
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
java.lang.Exception: Credentials could not be found!
at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusHelper.sendBuildStatusNotification(BitbucketBuildStatusHelper.java:262)
at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusHelper.notifyBuildStatus(BitbucketBuildStatusHelper.java:252)
at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifierStep$Execution.run(BitbucketBuildStatusNotifierStep.java:189)
at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifierStep$Execution.run(BitbucketBuildStatusNotifierStep.java:140)
at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:52)
at hudson.security.ACL.impersonate(ACL.java:213)
at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:49)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title Itai Sanders commented on JENKINS-33841 Re: Support for pipeline builds Yevhenii Kurtov: I need to see the pipeline code to be certain, but from the snippet you posted it seems like you activated the bitbucketnotifier before the checkout stage. Proceeding [Pipeline] bitbucketStatusNotify [Pipeline] stage (Checkout) the notifier is looking for the scm object instance, which in pipelines (unlike the freestyle jobs) is only initiated when you go through the scm checkout step, so basically you are calling for bitbucketnotifier with an uninitiated (null) scm object. it might be best if the plugin catches this and posts a more friendly exception message. maybe I'll look into it and post another pull request later if no one gets to it. let me know if placing the scm checkout before the bitbucketnotifier step worked or it's something else entirely. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title Yevhenii Kurtov commented on JENKINS-33841 Re: Support for pipeline builds Hello Itai Sanders I notice that you have a status notification message in the logs Sending build status INPROGRESS for commit 4e7eb185a08b8b5cb1775c31d26f3f05cbaa8bbc to BitBucket is done! Sending build status SUCCESSFUL for commit 4e7eb185a08b8b5cb1775c31d26f3f05cbaa8bbc to BitBucket is done! what looks really good, but my build doesn't issue even anything close to that, I have just: Proceeding [Pipeline] bitbucketStatusNotify [Pipeline] stage (Checkout) and even more strange - error in the end [Pipeline] bitbucketStatusNotify [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline java.lang.NullPointerException at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifierStep$Execution.run(BitbucketBuildStatusNotifierStep.java:191) at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifierStep$Execution.run(BitbucketBuildStatusNotifierStep.java:140) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:52) at hudson.security.ACL.impersonate(ACL.java:213) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:49) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Finished: FAILURE Can you please suggest what I might be missing? The only difference I can see between my and sample config is that I'm fetching code with credentials: checkout([$class: 'GitSCM', branches: [[name: env.BRANCH_NAME]], doGenerateSubmoduleConfigurations: false, extensions: [], submoduleCfg: [], userRemoteConfigs: [[credentialsId: 'c6bcc00a-8dea-4671-bdd3-8335a959d610', url: 'g...@bitbucket.xxx/xxx.git']]])
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title Thomas VIAL commented on JENKINS-33841 Re: Support for pipeline builds Works great, thanks guys! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title Itai Sanders commented on JENKINS-33841 Re: Support for pipeline builds no problem. I am using my own locally compiled version with both my pull requests here, since I needed those fixes. I'm sorry about the versions mixup. tbh, this is the first time I am doing an actual pull request to a Jenkins plugin and I just changed the code as needed without taking notice of the metadata that came with it. I guess you can just commit whatever needs to be changed in the versions, or give me the pointers and I'll be glad to add them to the pull request. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title Thomas VIAL commented on JENKINS-33841 Re: Support for pipeline builds Thanks for this work guys. I'm gonna test it. Just a feedback, I'm using Jenkins 2.14 and the latest version of the plugin is 1.2.2 and not 1.3.0 in the web interface. I'm gonna install it manually. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title
Itai Sanders edited a comment on JENKINS-33841
Re: Support for pipeline builds
[~flagbit] - sure:{code}Jul 18, 2016 11:43:00 AM INFO hudson.model.Queue maintainBuildableItem devops.tests.allsorts: pending -> buildable as the assigned executor disappearedJul 18, 2016 11:43:46 AM WARNING org.jenkinsci.plugins.workflow.support.steps.input.InputAction loadExecutionsno flow execution found for devops.tests.allsorts/notifier #7Jul 18, 2016 11:45:33 AM INFO org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusHelper sendBuildStatusNotificationThis request was sent: { "state": "INPROGRESS", "key": "[some key]", "url": "[jenkins url]/job/devops.tests.allsorts/job/notifier/8/", "name": "devops.tests.allsorts » notifier #8"}Jul 18, 2016 11:45:33 AM INFO org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusHelper sendBuildStatusNotificationThis response was received: Bad RequestJul 18, 2016 11:45:59 AM INFO org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusHelper sendBuildStatusNotificationThis request was sent: { "state": "SUCCESSFUL", "key": "[same key as previous request]", "url": "[jenkins url]job/devops.tests.allsorts/job/notifier/8/", "name": "devops.tests.allsorts » notifier #8"}Jul 18, 2016 11:45:59 AM INFO org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusHelper sendBuildStatusNotificationThis response was received: Bad RequestJul 18, 2016 11:45:59 AM INFO org.jenkinsci.plugins.workflow.job.WorkflowRun finishdevops.tests.allsorts/notifier #8 completed: SUCCESS{code}maybe it's the » sign that comes from the folder plugin.as an afterthought, I decided to check this out on a job outside any foldered structure (such as in a multibranch job) and there it worked (same repo so same Jenkinsfile). moved that job into a folder, and again I get the same results as the multibranch job.so whatever it is - it happens only when ran inside a folder. EDIT: I took the liberty of forking the code and look into it myself. it wasn't such a huge fix. created a [pull request|https://github.com/jenkinsci/bitbucket-build-status-notifier-plugin/pull/30] for you.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title Itai Sanders commented on JENKINS-33841 Re: Support for pipeline builds btw, I also noticed that if I notify about an INPROGRESS status and the build fails or aborted, then there's no automatic status update in Bitbucket so it freezes on INPROGRESS. not a show stopper, but something to think about for a future release. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title
Itai Sanders commented on JENKINS-33841
Re: Support for pipeline builds
Antonio Mansilla - sure:
Jul 18, 2016 11:43:00 AM INFO hudson.model.Queue maintain
BuildableItem devops.tests.allsorts: pending -> buildable as the assigned executor disappeared
Jul 18, 2016 11:43:46 AM WARNING org.jenkinsci.plugins.workflow.support.steps.input.InputAction loadExecutions
no flow execution found for devops.tests.allsorts/notifier #7
Jul 18, 2016 11:45:33 AM INFO org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusHelper sendBuildStatusNotification
This request was sent: {
"state": "INPROGRESS",
"key": "[some key]",
"url": "[jenkins url]/job/devops.tests.allsorts/job/notifier/8/",
"name": "devops.tests.allsorts » notifier #8"
}
Jul 18, 2016 11:45:33 AM INFO org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusHelper sendBuildStatusNotification
This response was received: Bad Request
Jul 18, 2016 11:45:59 AM INFO org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusHelper sendBuildStatusNotification
This request was sent: {
"state": "SUCCESSFUL",
"key": "[same key as previous request]",
"url": "[jenkins url]job/devops.tests.allsorts/job/notifier/8/",
"name": "devops.tests.allsorts » notifier #8"
}
Jul 18, 2016 11:45:59 AM INFO org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusHelper sendBuildStatusNotification
This response was received: Bad Request
Jul 18, 2016 11:45:59 AM INFO org.jenkinsci.plugins.workflow.job.WorkflowRun finish
devops.tests.allsorts/notifier #8 completed: SUCCESS
maybe it's the » sign that comes from the folder plugin. as an afterthought, I decided to check this out on a job outside any foldered structure (such as in a multibranch job) and there it worked (same repo so same Jenkinsfile). moved that job into a folder, and again I get the same results as the multibranch job. so whatever it is - it happens only when ran inside a folder.
Add Comment
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title Antonio Mansilla commented on JENKINS-33841 Re: Support for pipeline builds Hi Itai Sanders, can you please provide the jenkins log info during the execution of the job? Probably there we can guess what going on. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title
Itai Sanders edited a comment on JENKINS-33841
Re: Support for pipeline builds
[~amansilla] - thanks for the update!I updated the plugin and ran a small test in a multibranch job using the following Jenkinsfile:{code}node {stage 'checkout'checkout scmbitbucketStatusNotify ( buildState: 'INPROGRESS' )}stage 'pause'input 'waiting...'stage 'complete'bitbucketStatusNotify ( buildState: 'SUCCESSFUL' ){code}the console output in Jenkins seems promising:{code}Branch indexing[Pipeline] nodeRunning on master...[Pipeline] {[Pipeline] stage (checkout)Entering stage checkoutProceeding[Pipeline] checkout...[Pipeline] bitbucketStatusNotifySending build status INPROGRESS for commit 4e7eb185a08b8b5cb1775c31d26f3f05cbaa8bbc to BitBucket is done![Pipeline] }[Pipeline] // node[Pipeline] stage (pause)Entering stage pauseProceeding[Pipeline] inputwaiting...Proceed or AbortApproved by Itai Sanders[Pipeline] stage (complete)Entering stage completeProceeding[Pipeline] bitbucketStatusNotifySending build status SUCCESSFUL for commit 4e7eb185a08b8b5cb1775c31d26f3f05cbaa8bbc to BitBucket is done![Pipeline] End of Pipeline[Bitbucket] Notifying commit build result[Bitbucket] Build result notifiedFinished: SUCCESS{code}but when I go to the Bitbucket web interface I can't see any sign of the build status: !screenshot-1.png|thumbnail! am I doing it wrong? just for some more details: I tested this with both a consumer under my own account and a consumer under my team's account. both had the same result.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title
Itai Sanders commented on JENKINS-33841
Re: Support for pipeline builds
Antonio Mansilla - thanks for the update! I updated the plugin and ran a small test in a multibranch job using the following Jenkinsfile:
node {
stage 'checkout'
checkout scm
bitbucketStatusNotify ( buildState: 'INPROGRESS' )
}
stage 'pause'
input 'waiting...'
stage 'complete'
bitbucketStatusNotify ( buildState: 'SUCCESSFUL' )
the console output in Jenkins seems promising:
Branch indexing
[Pipeline] node
Running on master...
[Pipeline] {
[Pipeline] stage (checkout)
Entering stage checkout
Proceeding
[Pipeline] checkout
...
[Pipeline] bitbucketStatusNotify
Sending build status INPROGRESS for commit 4e7eb185a08b8b5cb1775c31d26f3f05cbaa8bbc to BitBucket is done!
[Pipeline] }
[Pipeline] // node
[Pipeline] stage (pause)
Entering stage pause
Proceeding
[Pipeline] input
waiting...
Proceed or Abort
Approved by Itai Sanders
[Pipeline] stage (complete)
Entering stage complete
Proceeding
[Pipeline] bitbucketStatusNotify
Sending build status SUCCESSFUL for commit 4e7eb185a08b8b5cb1775c31d26f3f05cbaa8bbc to BitBucket is done!
[Pipeline] End of Pipeline
[Bitbucket] Notifying commit build result
[Bitbucket] Build result notified
Finished: SUCCESS
but when I go to the Bitbucket web interface I can't see any sign of the build status: am I doing it wrong?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title Itai Sanders updated an issue Jenkins / JENKINS-33841 Support for pipeline builds Change By: Itai Sanders Attachment: screenshot-1.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title Antonio Mansilla resolved as Fixed Jenkins / JENKINS-33841 Support for pipeline builds Change By: Antonio Mansilla Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title Antonio Mansilla started work on JENKINS-33841 Change By: Antonio Mansilla Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title Antonio Mansilla commented on JENKINS-33841 Re: Support for pipeline builds Support for pipeline build was added and will be available on next release. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title Itai Sanders edited a comment on JENKINS-33841 Re: Support for pipeline builds I tried this plugin for the first time. I defined the OAuth in the Jenkins Global Configurations and it seems like it applied itself by default to my pipelines, which is good.what is strange is that instead of updating the build status in BitBucket, it posts a comment on that commit saying whether it looks good or failed with a link to that build. the build status icon stays empty. EDIT: it seems like the comments don't come from this plugin, but from the BitBucket Source plugin. and they too have an issue requesting for it to become a status update: [JENKINS-33507|https://issues.jenkins-ci.org/browse/JENKINS-33507] Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33841) Support for pipeline builds
Title: Message Title Itai Sanders commented on JENKINS-33841 Re: Support for pipeline builds I tried this plugin for the first time. I defined the OAuth in the Jenkins Global Configurations and it seems like it applied itself by default to my pipelines, which is good. what is strange is that instead of updating the build status in BitBucket, it posts a comment on that commit saying whether it looks good or failed with a link to that build. the build status icon stays empty. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
