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

[raphael.uni...@stef.com (JIRA)]

Title: Message Title

Raphaël UNIQUE created an issue   Jenkins / JENKINS-51357 conflict between poolscm trigger and repository re-index Issue Type: Bug Assignee: Unassigned Attachments: image-2018-05-16-11-21-50-866.png, image-2018-05-16-11-26-51-102.png, image-2018-05-16-11-36-24-001.png, image-2018-05-16-11-37-40-355.png, image-2018-05-16-11-46-37-793.png, image-2018-05-16-11-48-56-424.png Components: workflow-multibranch-plugin Created: 2018-05-16 10:01 Labels: multibranch Priority: Major Reporter: Raphaël UNIQUE 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   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):     Add Comment   This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.