jenkinsci / jenkinsci/workflow-multibranch-plugin

[JENKINS-51357] conflict between poolscm trigger and repository re-index

Open
#494 1 comment 0 reactions 0 assignees View on GitHub
component:workflow-multibranch-plugin imported-jira-issue priority:major resolution:unresolved
Dominant language
Java
Stars
87
Forks
131
PR merge metrics
No merged PRs in 30d

Description

hi,

 

we try to use:



  • re-index option on the workflow multibranch project to detect new branches (delay 1 day)

  • poolscm trigger in the jenkinsfiles to trigger build 15 min after commit (svn)

 

but there is a conflict:

if i commit code in a branch, the corresponding job is triggered correctly.

i have done a commit in the trunk (rev 4149):

 

but the next execution of the re-indexing detect a change, but trigger a build of all branches and trunk:

Démarré par l'utilisateur Raphaël Unique

[mer. mai 16 11:41:19 CEST 2018] Starting branch indexing...
Opening conection to https://svn.xxxx
Checking directory /fr.agrostar.posteprepa@​HEAD
Checking directory /fr.agrostar.posteprepa/branches@​HEAD
...
Checking candidate branch /fr.agrostar.posteprepa/trunk@​HEAD
‘Jenkinsfile’ found
Met criteria
Changes detected: trunk (4148 → 4149)
Scheduled build for branch: trunk
[mer. mai 16 11:41:22 CEST 2018] Finished branch indexing. Indexing took 2,7 s
Finished: SUCCESS

a build (29) is triggered for the trunk (not necessary):

 

 

---
Originally reported by raphael_unique, imported from: conflict between poolscm trigger and repository re-index


  • status: In Progress
  • priority: Major
  • component(s): workflow-multibranch-plugin
  • label(s): multibranch, triaged-2018-11
  • resolution: Unresolved
  • votes: 0
  • watchers: 2
  • imported: 20251212-090250

Raw content of original issue

hi,

 

we try to use:



  • re-index option on the workflow multibranch project to detect new branches (delay 1 day)

  • poolscm trigger in the jenkinsfiles to trigger build 15 min after commit (svn)

 

but there is a conflict:

if i commit code in a branch, the corresponding job is triggered correctly.

i have done a commit in the trunk (rev 4149):

 

but the next execution of the re-indexing detect a change, but trigger a build of all branches and trunk:



Démarré par l'utilisateur Raphaël Unique

[mer. mai 16 11:41:19 CEST 2018] Starting branch indexing...
Opening conection to https://svn.xxxx
Checking directory /fr.agrostar.posteprepa@HEAD
Checking directory /fr.agrostar.posteprepa/branches@HEAD
...
Checking candidate branch /fr.agrostar.posteprepa/trunk@HEAD
‘Jenkinsfile’ found
Met criteria
Changes detected: trunk (4148 → 4149)
Scheduled build for branch: trunk
[mer. mai 16 11:41:22 CEST 2018] Finished branch indexing. Indexing took 2,7 s
Finished: SUCCESS


a build (29) is triggered for the trunk (not necessary):

 

 

6 attachments

- [image-2018-05-16-11-21-50-866.png](https://issues.jenkins.io/secure/attachment/42607/image-2018-05-16-11-21-50-866.png)
> ![image-2018-05-16-11-21-50-866.png](https://issues.jenkins.io/secure/attachment/42607/image-2018-05-16-11-21-50-866.png)
- [image-2018-05-16-11-26-51-102.png](https://issues.jenkins.io/secure/attachment/42606/image-2018-05-16-11-26-51-102.png)
> ![image-2018-05-16-11-26-51-102.png](https://issues.jenkins.io/secure/attachment/42606/image-2018-05-16-11-26-51-102.png)
- [image-2018-05-16-11-36-24-001.png](https://issues.jenkins.io/secure/attachment/42605/image-2018-05-16-11-36-24-001.png)
> ![image-2018-05-16-11-36-24-001.png](https://issues.jenkins.io/secure/attachment/42605/image-2018-05-16-11-36-24-001.png)
- [image-2018-05-16-11-37-40-355.png](https://issues.jenkins.io/secure/attachment/42604/image-2018-05-16-11-37-40-355.png)
> ![image-2018-05-16-11-37-40-355.png](https://issues.jenkins.io/secure/attachment/42604/image-2018-05-16-11-37-40-355.png)
- [image-2018-05-16-11-46-37-793.png](https://issues.jenkins.io/secure/attachment/42603/image-2018-05-16-11-46-37-793.png)
> ![image-2018-05-16-11-46-37-793.png](https://issues.jenkins.io/secure/attachment/42603/image-2018-05-16-11-46-37-793.png)
- [image-2018-05-16-11-48-56-424.png](https://issues.jenkins.io/secure/attachment/42602/image-2018-05-16-11-48-56-424.png)
> ![image-2018-05-16-11-48-56-424.png](https://issues.jenkins.io/secure/attachment/42602/image-2018-05-16-11-48-56-424.png)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.