Open jgmsb opened 2 years ago
+1 The problem is caused by not propagating revision(but branch name is propagated) of the source branch revision. Can be checked with this code in Jenkinsfile, based on the way bitbucket-branch-source-plugin determinate commit to notify:
import jenkins.scm.api.SCMSource
import jenkins.scm.api.SCMRevision
import jenkins.scm.api.SCMRevisionAction
SCMSource s = SCMSource.SourceByItem.findSource(currentBuild.rawBuild.getParent())
SCMRevision r = SCMRevisionAction.getRevision(s, currentBuild.rawBuild)
println("Repo: ${s.getRepository()} Revision: ${r}")
Same is happening with GitLab Branch Source plugin - no job statuses returned. Is there any workaround for this issue?
Any solutions to this issue?
Describe the bug Hi. I've detected that when using the Remote Jenkinsfile plugin with a bitbucket repository, the default bitbucket notification that comes with multibranch pipelines stops working. Even using the Bitbucket Build Status Notifier to force the notification doesn't work either.
To Reproduce Steps to reproduce the behavior:
Expected behavior The bitbucket notifications should work with the Remote Jenkinsfile Plugin
Jenkins Version
Remote Jenkinsfile Plugin Version