[JIRA] [parameterized-trigger] (JENKINS-25192) Trigger are always run after finalize
William Bernardet created JENKINS-25192 Trigger are always run after finalize Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger Created: 17/Oct/14 12:35 PM Description: We are currently trying to trigger a build as post action using parameters from a property file generated in the workspace during the build. As last post action the job uses the workspace cleanup plugin. The issue is that the cleanup is done before the triggering. Which leads to never trigger the sub build... So the following setting is the plugin doesn't make sense with the "Parameters from a property" option. https://github.com/jenkinsci/parameterized-trigger-plugin/blob/master/src/main/java/hudson/plugins/parameterizedtrigger/BuildTrigger.java#L41 Would it be possible to change the returned value to false to the notifier gets executed in correct order... Project: Jenkins Priority: Critical Reporter: William Bernardet 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.
[JIRA] [parameterized-trigger] (JENKINS-25192) Trigger are always run after finalize
Daniel Beck updated JENKINS-25192 Trigger are always run after finalize AFAIU the problem is that only after finalization, the build result is unmodifiable (which is a requirement of "Trigger when build is:"). Reducing priority due to straightforward workaround: Do not delete the file with the parameters. Workspace Cleanup is extremely configurable. Change By: Daniel Beck (17/Oct/14 1:08 PM) Priority: Critical Minor 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.
[JIRA] [parameterized-trigger] (JENKINS-25192) Trigger are always run after finalize
Daniel Beck updated JENKINS-25192 Trigger are always run after finalize Appears to not be a bug, but deliberate. Change By: Daniel Beck (17/Oct/14 1:09 PM) Issue Type: Bug Improvement 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.
[JIRA] [parameterized-trigger] (JENKINS-25192) Trigger are always run after finalize
William Bernardet commented on JENKINS-25192 Trigger are always run after finalize I guess it is deliberate, but one thing that annoys me is that we define some order of execution for the publisher/notifier in job config, and this runAfterFinilized affects it. From an end user prospective it is pretty difficult to find it out as it does not reflect from ui. So one option is also to raise a bug on the workspace cleanup to run after finalize, so if it is the last one in the list, then it really gets executed as the last one 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.
