[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
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.
[JIRA] [credentials-binding] (JENKINS-24910) Username/password to support separate env variables
William Bernardet created JENKINS-24910 Username/password to support separate env variables Issue Type: Improvement Assignee: Jesse Glick Components: credentials-binding Created: 29/Sep/14 12:16 PM Description: Currently the plugin will generate a single environment variable based on the name give set as this: NAME=username:password Would it be possible to have an option to split it into two distinct environment variables: NAME_USERNAME=username NAME_PASSWORD=password This would ease the usage of the plugin as most of the tool requiring a username password would ask them separatly. Project: Jenkins Priority: Minor 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] [template-project] (JENKINS-21787) use all the publishers from this project is not triggering a new build
William Bernardet commented on JENKINS-21787 use all the publishers from this project is not triggering a new build The fix for JENKINS-23710 will also covert this issue. 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] [template-project] (JENKINS-23710) The plugin does not support plugins implementing the DependencyDeclarer interface
William Bernardet created JENKINS-23710 The plugin does not support plugins implementing the DependencyDeclarer interface Issue Type: Bug Affects Versions: current Assignee: huybrechts Components: template-project Created: 08/Jul/14 9:33 AM Description: At the moment the ProxyBuilder and ProxyPublisher do not support the DependencyDeclarer interface, which means plugin implementing it will not behave properly when used from a template, like the parametrized build trigger plugin. 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] [template-project] (JENKINS-23710) The plugin does not support plugins implementing the DependencyDeclarer interface
William Bernardet commented on JENKINS-23710 The plugin does not support plugins implementing the DependencyDeclarer interface Fix proposal https://github.com/jenkinsci/template-project-plugin/pull/9 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] [rebuild] (JENKINS-20288) The rebuild plugin doesn't support custom parameter types
William Bernardet commented on JENKINS-20288 The rebuild plugin doesnt support custom parameter types Would it be possible to release the plugin with that fix? 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] [rebuild] (JENKINS-20288) The rebuild plugin doesn't support custom parameter types
William Bernardet closed JENKINS-20288 as Fixed The rebuild plugin doesnt support custom parameter types I've tried the plugin with latest git content and it works ok. Change By: William Bernardet (16/Jun/14 7:42 PM) Status: Open Closed Fix Version/s: current Resolution: Fixed 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] [template-project] (JENKINS-22381) The plugin do not fail the build if a template is removed
William Bernardet created JENKINS-22381 The plugin do not fail the build if a template is removed Issue Type: Bug Assignee: huybrechts Components: template-project Created: 27/Mar/14 11:56 AM Description: In case the template job is removed the ProxyBuilder keeps going without notifying the end user about the issue. The builder should fail and report the issue to the user, rather than just hiding the issue. The problems come from the getProjectBuilders, if the returned project is null then it should throw an exception to signal that template doesn't exists anymore. And if Case the project type is not handled, it should throw an exception as well indicating the plugin do not support this type of project... Project: Jenkins Priority: Major 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] [template-project] (JENKINS-22399) The template-project ignore unexisting project
William Bernardet created JENKINS-22399 The template-project ignore unexisting project Issue Type: Bug Assignee: huybrechts Components: template-project Created: 28/Mar/14 5:45 AM Description: The template project currently ignore if a template project has been deleted or renamed. I would expect it to fail the build and report an error rather than swallowing it. This mainly comes from the getProjectBuilders method from the ProxyBuilder class where if the getItem returns null then an empty collection is returned rather than throwing/reporting an error. Similarly if the type of template project is not supported, nothing happen. Project: Jenkins Labels: plugin Priority: Major 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] [template-project] (JENKINS-22399) The template-project ignore unexisting project
William Bernardet closed JENKINS-22399 as Duplicate The template-project ignore unexisting project Sorry I created it again, as I was not able to find previous one... Change By: William Bernardet (28/Mar/14 5:47 AM) Status: Open Closed Resolution: Duplicate 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] [ws-cleanup] (JENKINS-18345) Current implementation forces the wait of previous build to complete
William Bernardet commented on JENKINS-18345 Current implementation forces the wait of previous build to complete I've created a pull request for a fix proposal. https://github.com/vjuranek/ws-cleanup/pull/1 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/groups/opt_out.
[JIRA] [ws-cleanup] (JENKINS-18345) Current implementation forces the wait of previous build to complete
William Bernardet edited a comment on JENKINS-18345 Current implementation forces the wait of previous build to complete I've created a pull request for a fix proposal. https://github.com/jenkinsci/ws-cleanup-plugin/pull/9 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/groups/opt_out.
[JIRA] [ws-cleanup] (JENKINS-18345) Current implementation forces wait of previous build to complete
William Bernardet created JENKINS-18345 Current implementation forces wait of previous build to complete Issue Type: Bug Affects Versions: current Assignee: vjuranek Components: ws-cleanup Created: 14/Jun/13 5:58 AM Description: The current implementation of the WsCleanup publisher is using BuildStepMonitor.STEP as value for the getRequiredMonitorService method. This forces Jenkins to wait previous build to complete this step before running it in latest build. As this plugin does not seem to rely on any Action from previous builds adviced value is BuildStepMonitor.NONE (http://javadoc.jenkins-ci.org/hudson/tasks/BuildStep.html#getRequiredMonitorService()). This bug is pretty annoying as it serializes a large set of our builds, which should complete independently. 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/groups/opt_out.
[JIRA] [ws-cleanup] (JENKINS-18345) Current implementation forces the wait of previous build to complete
William Bernardet updated JENKINS-18345 Current implementation forces the wait of previous build to complete Change By: William Bernardet (14/Jun/13 5:58 AM) Summary: Currentimplementationforces the waitofpreviousbuildtocomplete 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/groups/opt_out.
[JIRA] [template-project] (JENKINS-16800) When including publishers from another job, the link to the report is not added
William Bernardet commented on JENKINS-16800 When including publishers from another job, the link to the report is not added I've been currently facing similar issue with the warnings plugin, which is not showing the trend graph when called from a template. The issue is that ProxyBuilder and ProxyPublisher are not implementing getProjectActions, which is used to contribute transient action to the project. I have just submitted a fix request to the github repo: https://github.com/jenkinsci/template-project-plugin/pull/5 Please feel free to test it. 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/groups/opt_out.
