[JIRA] [core] (JENKINS-23191) ReverseBuildTrigger.threshold not consistently saved

[dan...@beckweb.net (JIRA)]

Daniel Beck edited a comment on JENKINS-23191 ReverseBuildTrigger.threshold not consistently saved Christian: This is a deliberate, documented change. Quoting the changelog for 1.560: The “upstream pseudo trigger” was also removed in favor of a true trigger configured on the downstream project; you may use either the post-build action or the trigger according to where you want this configuration stored, and who is authorized to change it. Actually the settings in job C have no effect, ie. when no PBA is configured in B, job C is never triggered, whatever it's configuration is. This could be a legitimate bug. Could you provide complete and detailed steps to reproduce this on a test instance with default plugins?

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira

--
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.