[
https://issues.jenkins-ci.org/browse/JENKINS-12986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159942#comment-159942
]
gbois commented on JENKINS-12986:
---------------------------------
FSTrigger and its typology XTRigger is not aware about upstream/downstream.
XTrigger plugins is aimed at excluding the usage of job dependencies.
Could you just upload your job configuration files? I'll try to reproduce it.
> "Block build when downstream project is building" and fstrigger problem
> -----------------------------------------------------------------------
>
> Key: JENKINS-12986
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12986
> Project: Jenkins
> Issue Type: Bug
> Components: fstrigger
> Affects Versions: current
> Environment: fstrigger 0.27
> jenkins 1.451
> Reporter: Trevor Baker
> Assignee: gbois
>
> It seems that when you enable "Block build when downstream project is
> building" that scheduled polling still occurs. If you use fstrigger and a
> poll sees a file change when builds are blocked due to running downstream
> jobs, the timestamp or "fingerprint" or the file/folder watched still gets
> updated. This means that once the downstream job completes and the block is
> removed a new job should be triggered. Currently builds are NOT triggered as
> the plugin is comparing the contents observed during the blockout to current
> which are the same.
> When builds are blocked fstrigger should not update its "state" used for
> comparisons.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
