-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins 2.19.2, Bitbucket Branch Source 1.8
Presently this plugin creates duplicate INPROGRESS notifications. It notifies once for the first checkout (without much information) and one on the actual node (with proper information), as seen in this output:
Branch indexing Cloning the remote Git repository Cloning repository https://example.git > git checkout -f fdd9a31ec4c3b20125db3771b760109202826688 [Bitbucket] Notifying commit build result // <== FIRST INPROGRESS (BAD) [Pipeline] node Running on linux2 in /home/example [Pipeline] { [Pipeline] timestamps [Pipeline] { [Pipeline] stage [Pipeline] { (Checkout SCM) [Pipeline] checkout 12:15:05 Cloning the remote Git repository 12:15:05 Cloning repository https://example.git 12:15:05 > git init /home/example 12:17:12 > git checkout -f fdd9a31ec4c3b20125db3771b760109202826688 12:17:13 [Bitbucket] Notifying commit build result // <== SECOND INPROGRESS (GOOD)
and here's the example pipeline:
node() {
timestamps {
stage('Checkout SCM') {
checkout scm
}
stage('Build & Test') {
sh 'sleep 60'
}
}
}
The first notification (labeled BAD) results in a generic number and "The tests have started..." in Bitbucket, and the second one (GOOD) actually shows the job name and Jenkins link. Attached is a screenshot at the end of the build showing the duplicate notifications, one generic from the first notification and one that looks good.
