-
Bug
-
Resolution: Unresolved
-
Major
-
None
I'm using this plugin with a Multibranch Pipeline for reporting the status of a build to Bitbucket. The issue I'm seeing is that the first time a branch is built, the status is not being sent. I can see in the log that it does call the plugin, but the log that says that posting the status succeeded does not show up. Each time a build is run after the first run works as expected.
[JENKINS-40456] First time builds are not reporting to Bitbucket
Ethan Rogers
created issue -
Antonio Mansilla
made changes -
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Ryan Feather
made changes -
| Attachment | New: screenshot-1.png [ 35952 ] |
Ryan Feather
made changes -
| Attachment | New: screenshot-2.png [ 35953 ] |
Same issue here. Using mutlibranch and calling bitbucketstatusnotify within the pipeline. Plugin version 1.3.1, jenkins version 2.39. It seems to be failing silently as far as I can tell.
First build
Second build
Ryan Feather
added a comment - - edited Same issue here. Using mutlibranch and calling bitbucketstatusnotify within the pipeline. Plugin version 1.3.1, jenkins version 2.39. It seems to be failing silently as far as I can tell.
First build
Second build
Antonio Mansilla
added a comment - Hi ethanfrogers, that a weird behaviour, since I'm as well using multibranch pipeline jobs and the build status is being reported to Bitbucket properly. Can you please post here the part relative to this plugin of your current Jenkinsfile, so I can find better the problem?
I'll close this issue since I guess the problem is a misconfiguration o error on the Jenkinsfile and will reopen in case the error is still persisting.
Antonio Mansilla
added a comment - Hi ethanfrogers , that a weird behaviour, since I'm as well using multibranch pipeline jobs and the build status is being reported to Bitbucket properly. Can you please post here the part relative to this plugin of your current Jenkinsfile, so I can find better the problem?
I'll close this issue since I guess the problem is a misconfiguration o error on the Jenkinsfile and will reopen in case the error is still persisting. Antonio Mansilla
made changes -
| Status | Original: In Progress [ 3 ] | New: Open [ 1 ] |
Antonio Mansilla
made changes -
| Resolution | New: Cannot Reproduce [ 5 ] | |
| Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Paweł Szczekutowicz
added a comment - Hi amansilla
I have same issue. I'm using multibranch pipeline projects with latest plugins. Notifications are sent inside node block but not in any stage block. INPROGRESS is sent after checkout stage with checkout scm step. SUCCESSFUL and FAILED are sent inside node but outside stage blocks too. All notifications are sent with same buildKey. First build is not notified with any state, second and next ones are notified.
Paweł Szczekutowicz
added a comment - Hi amansilla
I have same issue. I'm using multibranch pipeline projects with latest plugins. Notifications are sent inside node block but not in any stage block. INPROGRESS is sent after checkout stage with checkout scm step. SUCCESSFUL and FAILED are sent inside node but outside stage blocks too. All notifications are sent with same buildKey. First build is not notified with any state, second and next ones are notified. 
Could you please add what is logged in case of error as you described and which version of the plugin are you using, so I'll be able to reproduce easily the error.
Thanks and best regards