-
Bug
-
Resolution: Unresolved
-
Minor
-
Jenkins: 2.17
Local mercurial version: 3.1.2
Mercurial plugin: 1.56
Pipeline plugin: 2.2
Pipeline Multibranch plugin: 2.8
I've created a pipeline multibranch project with mercurial repo as a source, build configuration set in Jenkinsfile in repo and set to build periodically to poll the repo every two minutes (H/2). The first step inside Jenkinsfile is checkout scm.
It seems that for newly created branches (that have only one commit) the changes view is totally empty. On the other hand, when there are more commits it seems that they are logged twice (see screenshot below).
This looks like a similar issue to JENKINS-30491 or JENKINS-31079 yet this time it happens with mercurial instead of git.
- is related to
-
-
- Resolved
-
- relates to
-
-
- Reopened
-
- links to
[JENKINS-37384] Changes view issues using Mercurial with Multibranch pipeline
Bartlomiej Beton
created issue -
Bartlomiej Beton
made changes -
| Description |
Original:
I've created a pipeline multibranch project with mercurial repo as a source, build configuration set in Jenkinsfile in repo and set to build periodically to poll the repo every two minutes (H/2). The first step inside Jenkinsfile is `checkout scm`. It seems that for newly created branches (that have only one commit) the changes view is totally empty. On the other hand, when there are more commits it seems that they are logged twice (see !Zrzut ekranu z 2016-08-12 o 21.48.08.png|thumbnail! ). This looks like a similar issue to https://issues.jenkins-ci.org/browse/JENKINS-30491 or https://issues.jenkins-ci.org/browse/JENKINS-31079 yet this time it happens with mercurial instead of git. |
New:
I've created a pipeline multibranch project with mercurial repo as a source, build configuration set in Jenkinsfile in repo and set to build periodically to poll the repo every two minutes (H/2). The first step inside Jenkinsfile is _checkout scm_. It seems that for newly created branches (that have only one commit) the changes view is totally empty. On the other hand, when there are more commits it seems that they are logged twice (see screenshot below). !Zrzut ekranu z 2016-08-12 o 21.48.08.png|thumbnail! This looks like a similar issue to https://issues.jenkins-ci.org/browse/JENKINS-30491 or https://issues.jenkins-ci.org/browse/JENKINS-31079 yet this time it happens with mercurial instead of git. |
| Component/s | Original: workflow-multibranch-plugin [ 21465 ] |
| Labels | New: multibranch pipeline |
| Description |
Original:
I've created a pipeline multibranch project with mercurial repo as a source, build configuration set in Jenkinsfile in repo and set to build periodically to poll the repo every two minutes (H/2). The first step inside Jenkinsfile is _checkout scm_. It seems that for newly created branches (that have only one commit) the changes view is totally empty. On the other hand, when there are more commits it seems that they are logged twice (see screenshot below). !Zrzut ekranu z 2016-08-12 o 21.48.08.png|thumbnail! This looks like a similar issue to https://issues.jenkins-ci.org/browse/JENKINS-30491 or https://issues.jenkins-ci.org/browse/JENKINS-31079 yet this time it happens with mercurial instead of git. |
New:
I've created a pipeline multibranch project with mercurial repo as a source, build configuration set in {{Jenkinsfile}} in repo and set to build periodically to poll the repo every two minutes (H/2). The first step inside {{Jenkinsfile}} is {{checkout scm}}. It seems that for newly created branches (that have only one commit) the changes view is totally empty. On the other hand, when there are more commits it seems that they are logged twice (see screenshot below). !Zrzut ekranu z 2016-08-12 o 21.48.08.png|thumbnail! This looks like a similar issue to |
| Link | New: This issue relates to JENKINS-29326 [ JENKINS-29326 ] |
| Link |
New:
This issue is related to |
| Labels | Original: multibranch pipeline | New: multibranch pipeline scm-api-tidy-scrub |
JENKINS-33274