[JIRA] (JENKINS-43219) join plugin job dsl incomplete
Title: Message Title mdonohue commented on JENKINS-43219 Re: join plugin job dsl incomplete I'm not familiar with the job-dsl plugin. Does the change here need to be in the Join plugin or the job-dsl plugin? 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.
[JIRA] (JENKINS-23476) git-client plugin timeout default is not configurable in a standard manner
Title: Message Title mdonohue assigned an issue to Mikael Gaunin Jenkins / JENKINS-23476 git-client plugin timeout default is not configurable in a standard manner Change By: mdonohue Assignee: mdonohue Mikael Gaunin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-37775) Add support for logstash plugin
Title: Message Title mdonohue resolved as Fixed Jenkins / JENKINS-37775 Add support for logstash plugin Change By: mdonohue Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-37775) Add support for logstash plugin
Title: Message Title mdonohue commented on JENKINS-37775 Re: Add support for logstash plugin Now in configurationslicing-1.47 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-31043) SAML plugin can't auth with CSRF protection enabled
Title: Message Title mdonohue closed an issue as Fixed Jenkins / JENKINS-31043 SAML plugin can't auth with CSRF protection enabled Change By: mdonohue Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-31043) SAML plugin can't auth with CSRF protection enabled
Title: Message Title mdonohue commented on JENKINS-31043 Re: SAML plugin can't auth with CSRF protection enabled Patch was merged, and plugin released back in February. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-31043) SAML plugin can't auth with CSRF protection enabled
Title: Message Title mdonohue assigned an issue to mdonohue Jenkins / JENKINS-31043 SAML plugin can't auth with CSRF protection enabled Change By: mdonohue Assignee: mdonohue Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-38581) Jenkins auto linkification for Bugzilla is broken on the build page
Title: Message Title mdonohue commented on JENKINS-38581 Re: Jenkins auto linkification for Bugzilla is broken on the build page Sorry, I'm volunteering here - you'll need to do the legwork to get this one fixed. it's almost certainly not the bugzilla plugin at fault. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-38581) Jenkins auto linkification for Bugzilla is broken on the build page
Title: Message Title mdonohue commented on JENKINS-38581 Re: Jenkins auto linkification for Bugzilla is broken on the build page I am still not able to reproduce with the subversion plugin, alongside Fisheye integration. It's very difficult to guess what the root cause is without a way to reproduce the problem. Can you try building a test Jenkins setup, and add one plugin at a time, until the problem reproduces there? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-38581) Jenkins auto linkification for Bugzilla is broken on the build page
Title: Message Title mdonohue commented on JENKINS-38581 Re: Jenkins auto linkification for Bugzilla is broken on the build page Ok, the git plugin provides 'fisheye' links. I tried a Git repo, with fisheye enabled. Still can't repro your problem. Are you able to make a test install of Jenkins with just the git + bugzilla plugins, and reproduce this problem? I think it's some other plugin interacting. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-38581) Jenkins auto linkification for Bugzilla is broken on the build page
Title: Message Title mdonohue updated an issue Jenkins / JENKINS-38581 Jenkins auto linkification for Bugzilla is broken on the build page Change By: mdonohue On the job's main page, Recent Changes correctly link to Bugzilla bugs. However, if we go to specific builds' Recent Changes, links are broken. On a build's page, something like the following is shownBug 1234 - $COMMIT_MESSAGEwhich should have been like $LINK_TO_BUG1234 $COMMIT_MESSAGEFrom the page's source, it looks like all leading angled brackets are missing from the beginning of the Bugzilla URL's. For example& amp; lt;a href=''>Bug 1234& amp; lt;/a>& amp; lt;br>$COMMIT_MESSAGE Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-38581) Jenkins auto linkification for Bugzilla is broken on the build page
Title: Message Title mdonohue commented on JENKINS-38581 Re: Jenkins auto linkification for Bugzilla is broken on the build page What plugin is causing those 'fisheye' links? I think another plugin is processing the text and changing the angle brackets. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-38581) Jenkins auto linkification for Bugzilla is broken on the build page
Title: Message Title mdonohue commented on JENKINS-38581 Re: Jenkins auto linkification for Bugzilla is broken on the build page I tested just now with the 'ocaml' repo: http://caml.inria.fr/svn/ocaml/trunk The hyperlinks work fine from both the main page and the specific build page, so I am not able to reproduce. Can you provide more details? Or do you have a public repo that reproduces this? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-29547) "master" value is silently ignored and empty value is set for "Restrict where..." in Tied Label Slicer section
Title: Message Title mdonohue commented on JENKINS-29547 Re: "master" value is silently ignored and empty value is set for "Restrict where..." in Tied Label Slicer section I don't know how to get any more attention for this one. I just added a comment to the pull request. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-28979) Trigger if a failed dependency is retried and succeeds
Title: Message Title mdonohue resolved as Fixed JENKINS-29652 has a couple of patches attached and is largely the same issue, so closing this one. Jenkins / JENKINS-28979 Trigger if a failed dependency is retried and succeeds Change By: mdonohue Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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
[JIRA] (JENKINS-29652) Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin
Title: Message Title mdonohue commented on JENKINS-29652 Re: Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin I'm looking at both patches that are attached here - it seems the test cases that break as a result of these changes are just commented out. Can you explain why they are no longer needed? Also, can you add a test case to exercise the path this is creating? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-35665) NPE in Join plugin for Jenkins 2.8
Title: Message Title mdonohue resolved as Fixed Jenkins / JENKINS-35665 NPE in Join plugin for Jenkins 2.8 Change By: mdonohue Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-35665) NPE in Join plugin for Jenkins 2.8
Title: Message Title mdonohue commented on JENKINS-35665 Re: NPE in Join plugin for Jenkins 2.8 1.21 is out with the fix. let me know how it goes. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-35665) NPE in Join plugin for Jenkins 2.8
Title: Message Title mdonohue commented on JENKINS-35665 Re: NPE in Join plugin for Jenkins 2.8 I believe that's caused by upgrading an existing job - I will apply a fix. In the short term, going to the job config page and saving it again should make this go away. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] [join-plugin] (JENKINS-29652) Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin
Title: Message Title mdonohue commented on JENKINS-29652 Re: Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin When you say "rerun" is that distinguishable from just clicking "Build Now" on the job that failed? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-35008) hudson.tasks.Mailer cannot be used in a composable manner
Title: Message Title mdonohue closed an issue as Fixed Jenkins / JENKINS-35008 hudson.tasks.Mailer cannot be used in a composable manner Change By: mdonohue Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-35008) hudson.tasks.Mailer cannot be used in a composable manner
Title: Message Title mdonohue commented on JENKINS-35008 Re: hudson.tasks.Mailer cannot be used in a composable manner Okay, I finally got the pom updated, and now that I tested against 1.635, i see this was already fixed. Sorry for the noise. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-35008) hudson.tasks.Mailer cannot be used in a composable manner
Title: Message Title mdonohue updated an issue Jenkins / JENKINS-35008 hudson.tasks.Mailer cannot be used in a composable manner Change By: mdonohue The join plugin includes select post-build actions as 'join' actions. This requires a certain amount of composability in the configuration screen to work - the email trigger doesn't work here, for example. The problem is that the join trigger post-build actions appear first, and consume the form keys before the main action. Using the JSON format data submission should fix this, and would provide a better example for future plugin creators. See JENKINS-7529 for the motivation for this change Tested with Jenkins 1.424 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-35008) hudson.tasks.Mailer cannot be used in a composable manner
Title: Message Title mdonohue updated an issue Jenkins / JENKINS-35008 hudson.tasks.Mailer cannot be used in a composable manner Change By: mdonohue The join plugin includes select post-build actions as 'join' actions. This requires a certain amount of composability in the configuration screen to work - the email trigger doesn't work here, for example. The problem is that the join trigger post-build actions appear first, and consume the form keys before the main action. Using the JSON format data submission should fix this, and would provide a better example for future plugin creators. See JENKINS-7529 for the motivation for this change Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-35008) hudson.tasks.Mailer cannot be used in a composable manner
Title: Message Title mdonohue created an issue Jenkins / JENKINS-35008 hudson.tasks.Mailer cannot be used in a composable manner Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/May/22 1:03 AM Priority: Minor Reporter: mdonohue The join plugin includes select post-build actions as 'join' actions. This requires a certain amount of composability in the configuration screen to work - the email trigger doesn't work here, for example. The problem is that the join trigger post-build actions appear first, and consume the form keys before the main action. Using the JSON format data submission should fix this, and would provide a better example for future plugin creators. Add Comment
[JIRA] [join-plugin] (JENKINS-7529) Allow an email to be sent following a successful join activation
Title: Message Title mdonohue commented on JENKINS-7529 Re: Allow an email to be sent following a successful join activation The problem is still present in Jenkins 1.424. So this is a bug in core jenkins - it's easy to add the email post-build action to the join trigger, but it breaks the email functionality for non-join cases, so it is left out intentionally. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [join-plugin] (JENKINS-7529) Allow an email to be sent following a successful join activation
Title: Message Title mdonohue commented on JENKINS-7529 Re: Allow an email to be sent following a successful join activation This was removed because the email trigger wasn't able to be used in multiple places on the same form: see JENKINS-4384 I'll see if it behaves better in 2016, compared to 2009. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [join-plugin] (JENKINS-9946) join should be able to wait for all downstream jobs
Title: Message Title mdonohue closed an issue as Duplicate Jenkins / JENKINS-9946 join should be able to wait for all downstream jobs Change By: mdonohue Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [join-plugin] (JENKINS-9946) join should be able to wait for all downstream jobs
Title: Message Title mdonohue commented on JENKINS-9946 Re: join should be able to wait for all downstream jobs JENKINS-11274 appears better thought out. Closing this as a duplicate. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [join-plugin] (JENKINS-16212) Exception thrown from join plugin as it can't find BuildTrigger class in Parameterized Trigger plugin
Title: Message Title mdonohue commented on JENKINS-16212 Re: Exception thrown from join plugin as it can't find BuildTrigger class in Parameterized Trigger plugin "Latest everything as of now..." I'm glad you were up to date in 2012, but following up on this bug 4 years later, this description is very hard to follow. This is why software has version numbers - please use them. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [join-plugin] (JENKINS-25290) Join configuration not updated when job is renamed
Title: Message Title mdonohue resolved as Fixed I didn't write the code, but this was fixed by join-1.15-4-g4f4922b Jenkins / JENKINS-25290 Join configuration not updated when job is renamed Change By: mdonohue Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [join-plugin] (JENKINS-25290) Join configuration not updated when job is renamed
Title: Message Title mdonohue commented on JENKINS-25290 Re: Join configuration not updated when job is renamed Reviewing the commit history, it looks like Nicolas De Loof fixed this after the 1.15 release of the join plugin. Since this is reported against 1.15, I see that it was fixed later. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [join-plugin] (JENKINS-25290) Join configuration not updated when job is renamed
Title: Message Title mdonohue commented on JENKINS-25290 Re: Join configuration not updated when job is renamed I just tested this with freestyle projects - i have start, left, right, finish. I have left and right triggered by 'start' and finish is the join-trigger post build action. Jenkins 1.424, with a fresh build of the join plugin, but it should be functionally the same as join 1.19 I renamed left to left2, and that was picked up, as expected. I also renamed 'finish' to 'finish3' and the 'start' project now triggers 'finish3' as the join-trigger post build action. So it seems everything works correctly. Can you give me more specifics to reproduce the problem you are seeing? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [join-plugin] (JENKINS-28709) Join Plugin ignores dependencies wrapped with flexible-publish
Title: Message Title mdonohue commented on JENKINS-28709 Re: Join Plugin ignores dependencies wrapped with flexible-publish I commented on the pull request - it looks like whitespace was changed as part of the commit, making the diff difficult to read. It is recommended practice on any project to separate whitespace changes from content changes, so I can't accept this as-is. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [configurationslicing-plugin] (JENKINS-9478) NullPointerException while submitting config slicer logrotationbuilds or logrotationdays
Title: Message Title mdonohue closed an issue as Cannot Reproduce Jenkins / JENKINS-9478 NullPointerException while submitting config slicer logrotationbuilds or logrotationdays Change By: mdonohue Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [configurationslicing-plugin] (JENKINS-33368) Making changes through configuration slicing plugin is also changing other untouched configuration
Title: Message Title mdonohue commented on JENKINS-33368 Re: Making changes through configuration slicing plugin is also changing other untouched configuration Each slicer is a distinct piece of code, so it doesn't make sense to include this all in one bug report. Also, can you provide some more steps to reproduce. Such as the XML config files from before and after running the slicer. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [configurationslicing-plugin] (JENKINS-25123) Configuration Slicing plugin 1.39 does not support build timeout plugin 1.12+
Title: Message Title mdonohue resolved as Fixed the newly released 1.45 version of configuration slicing now uses XStream to show the built timeout config. This is less user friendly, but should work better with the current build timeout design. Jenkins / JENKINS-25123 Configuration Slicing plugin 1.39 does not support build timeout plugin 1.12+ Change By: mdonohue Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [configurationslicing-plugin] (JENKINS-30775) Please add support for the "Abort build if stuck" fields of Build-timeout plugin
Title: Message Title mdonohue resolved as Fixed I went with XStream and XML - you should be able to configure any build timeout field now. This should appear in the 1.45 release of the configuration slicing plugin which just went out. Jenkins / JENKINS-30775 Please add support for the "Abort build if stuck" fields of Build-timeout plugin Change By: mdonohue Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [configurationslicing-plugin] (JENKINS-32647) Support the incremental build option for Maven Jobs
Title: Message Title mdonohue resolved as Fixed This should appear in the 1.45 release of the configuration slicing plugin which just went out. Jenkins / JENKINS-32647 Support the incremental build option for Maven Jobs Change By: mdonohue Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [configurationslicing-plugin] (JENKINS-30775) Please add support for the "Abort build if stuck" fields of Build-timeout plugin
Title: Message Title mdonohue commented on JENKINS-30775 Re: Please add support for the "Abort build if stuck" fields of Build-timeout plugin Yes, there is now an object hierarchy around the BuildTimeOutStrategy, which doesn't lend itself well to a simple string representation. Using a JSON or XML format may work though. We can serialize the strategy object to JSON, then use the databinding mechanism to read it back in from the slice configuration. I don't think this use-case was intended with Jenkins though, so it might hit some rough spots. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [configurationslicing-plugin] (JENKINS-9478) NullPointerException while submitting config slicer logrotationbuilds or logrotationdays
Title: Message Title mdonohue commented on JENKINS-9478 Re: NullPointerException while submitting config slicer logrotationbuilds or logrotationdays ok. thanks. I tried it just now with 1.580.1, and both slicers worked fine - # builds and days to keep. I'm inclined to close this as cannot reproduce, unless more information is provided. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [configurationslicing-plugin] (JENKINS-9478) NullPointerException while submitting config slicer logrotationbuilds or logrotationdays
Title: Message Title mdonohue commented on JENKINS-9478 Re: NullPointerException while submitting config slicer logrotationbuilds or logrotationdays i am not aware of any log-rotations slicers. The artifact and old build slicers come to mind, but they are not about logs in particular. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [configurationslicing-plugin] (JENKINS-25320) UnsupportedOperationException when updating "Max # of builds to keep"
Title: Message Title mdonohue resolved as Cannot Reproduce Jenkins / JENKINS-25320 UnsupportedOperationException when updating "Max # of builds to keep" Change By: mdonohue Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [configurationslicing-plugin] (JENKINS-31666) Create configuration slicing based on builders from another project
Title: Message Title mdonohue commented on JENKINS-31666 Re: Create configuration slicing based on builders from another project I'm having trouble matching the title with the body of this issue. Do you want a slicer that shows the inheritance information? i.e. it would slice all jobs showing what job they inherit from. Or do you something more precise than that? The title mentions 'builders' but the body mentions templates. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [join-plugin] (JENKINS-32604) join-pluging missing licensing information
Title: Message Title mdonohue reopened an issue Jenkins / JENKINS-32604 join-pluging missing licensing information Change By: mdonohue Resolution: Won't Fix Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [join-plugin] (JENKINS-32604) join-pluging missing licensing information
Title: Message Title mdonohue resolved as Fixed Jenkins / JENKINS-32604 join-pluging missing licensing information Change By: mdonohue Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [join-plugin] (JENKINS-32604) join-pluging missing licensing information
Title: Message Title mdonohue commented on JENKINS-32604 Re: join-pluging missing licensing information Saying something is "unusable" is a bit extreme. I added an explicit MIT license to the pom.xml file just now. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [join-plugin] (JENKINS-22348) Join Plugin: intermittent NullPointerException in child project when all downstream projects complete
Title: Message Title mdonohue resolved as Fixed Jenkins / JENKINS-22348 Join Plugin: intermittent NullPointerException in child project when all downstream projects complete Change By: mdonohue Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [join-plugin] (JENKINS-22348) Join Plugin: intermittent NullPointerException in child project when all downstream projects complete
Title: Message Title mdonohue commented on JENKINS-22348 Re: Join Plugin: intermittent NullPointerException in child project when all downstream projects complete the suggested fix is in the 1.19 release of the join plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [join-plugin] (JENKINS-32604) join-pluging missing licensing information
Title: Message Title mdonohue commented on JENKINS-32604 Re: join-pluging missing licensing information Guess you'll have to make the risk decision here. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [join-plugin] (JENKINS-32604) join-pluging missing licensing information
Title: Message Title mdonohue resolved as Won't Fix Jenkins / JENKINS-32604 join-pluging missing licensing information Change By: mdonohue Status: Reopened Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [join-plugin] (JENKINS-32604) join-pluging missing licensing information
Title: Message Title mdonohue resolved as Won't Fix Jenkins / JENKINS-32604 join-pluging missing licensing information Change By: mdonohue Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [join-plugin] (JENKINS-32604) join-pluging missing licensing information
Title: Message Title mdonohue commented on JENKINS-32604 Re: join-pluging missing licensing information https://wiki.jenkins-ci.org/display/JENKINS/Before+starting+a+new+plugin "If nothing is defined, your code will be assumed to fall under the MIT license terms." Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [join-plugin] (JENKINS-32604) join-pluging missing licensing information
Title: Message Title mdonohue commented on JENKINS-32604 Re: join-pluging missing licensing information Please consult with the overall project on this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [join-plugin] (JENKINS-29652) Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin
Title: Message Title mdonohue commented on JENKINS-29652 Re: Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin I'm having a hard time reducing your expectation to reasonable semantics. By what logic does the join plugin avoid the double build situation I described? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [join-plugin] (JENKINS-29652) Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin
Title: Message Title mdonohue commented on JENKINS-29652 Re: Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin What do you mean by a "retry" build? If you mean manually triggering a build of a project that also is named as a join project, this will result in a lot of ambiguity. Using kolos's bug description setup: What if jobA is triggered again after jobC failed the first time, and jobA then causes jobC to succeed. Should this then trigger the previous execution of jobA to continue with the join, as well as the current execution? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [configurationslicing-plugin] (JENKINS-26933) Saving change in 'Configure Slicing Plugin' page causing Form too large exception
Title: Message Title mdonohue commented on JENKINS-26933 Re: Saving change in 'Configure Slicing Plugin' page causing Form too large exception Jenkins 1.639 picks up the fix Jesse Glick mentions. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [configurationslicing-plugin] (JENKINS-26933) Saving change in 'Configure Slicing Plugin' page causing Form too large exception
Title: Message Title mdonohue resolved as Fixed Jenkins / JENKINS-26933 Saving change in 'Configure Slicing Plugin' page causing Form too large exception Change By: mdonohue Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [configurationslicing-plugin] (JENKINS-26933) Saving change in 'Configure Slicing Plugin' page causing Form too large exception
Title: Message Title mdonohue commented on JENKINS-26933 Re: Saving change in 'Configure Slicing Plugin' page causing Form too large exception Yeah, I saw that discussion. It's hard to say there's obviously a problem here without knowing how many jobs are being configured. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [configurationslicing-plugin] (JENKINS-29547) "master" value is silently ignored and empty value is set for "Restrict where..." in Tied Label Slicer section
Title: Message Title mdonohue commented on JENKINS-29547 Re: "master" value is silently ignored and empty value is set for "Restrict where..." in Tied Label Slicer section And here is the pull request: https://github.com/jenkinsci/jenkins/pull/1881 I'm still working on getting it accepted. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-20327) “Form too large” errors submitting view configurations with many jobs
Title: Message Title mdonohue commented on JENKINS-20327 Re: “Form too large” errors submitting view configurations with many jobs What version of Jenkins picked up the jetty change to accept the whole submission? I see Stephen Connolly's patch was applied to winstone, but there hasn't been a deploy of winstone with that patch based on the tags I see, and core/war/pom.xml points at winstone-2.8, which doesn't have the patch. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [join-plugin] (JENKINS-30335) join plugin doens't work with maven snapshot triggering
Title: Message Title mdonohue commented on JENKINS-30335 Re: join plugin doens't work with maven snapshot triggering I don't use maven much - can you give a simple example that triggers this? Can it be reproduced entirely in Jenkins, or do I need a certain maven pom file as well? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [saml-plugin] (JENKINS-31043) SAML plugin can't auth with CSRF protection enabled
Title: Message Title mdonohue created an issue Jenkins / JENKINS-31043 SAML plugin can't auth with CSRF protection enabled Issue Type: Bug Assignee: Ben McCann Components: saml-plugin Created: 20/Oct/15 6:22 AM Priority: Critical Reporter: mdonohue I have SAML configured to auth users. We recently decided to turn on CSRF protection, but discovered it prevents anyone from authenticating via SAML. The securityRealm/loginFinished page produces a "missing CSRF crumb" error. Add Comment
[JIRA] [saml-plugin] (JENKINS-31043) SAML plugin can't auth with CSRF protection enabled
Title: Message Title mdonohue commented on JENKINS-31043 Re: SAML plugin can't auth with CSRF protection enabled The CSRF protection can be disabled in some circumstances - I wrote a patch against the saml plugin to exclude the loginFinished endpoint from CSRF protection. This gets rid of the missing crumb error, but login does not complete either. This is the patch: https://github.com/mdonohue/saml-plugin/commit/717fd8cb75b5f8ab65a48fcafded25c1f802f7ac Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [configurationslicing-plugin] (JENKINS-30775) Please add support for the "Abort build if stuck" fields of Build-timeout plugin
Title: Message Title mdonohue commented on JENKINS-30775 Re: Please add support for the "Abort build if stuck" fields of Build-timeout plugin configurationslicing is built against the 1.8 version of the build timeout plugin, which is from 2011, so it has no notion of the new strategies. These strategies sound more general purpose, so may not lend themselves to slicing - i haven't looked at the build timeout plugin source yet to confirm that though. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [configurationslicing-plugin] (JENKINS-29547) "master" value is silently ignored and empty value is set for "Restrict where..." in Tied Label Slicer section
Title: Message Title mdonohue commented on JENKINS-29547 Re: "master" value is silently ignored and empty value is set for "Restrict where..." in Tied Label Slicer section JDK7 didn't fare any better. Does Jenkins-core build on windows cleanly? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [configurationslicing-plugin] (JENKINS-29547) "master" value is silently ignored and empty value is set for "Restrict where..." in Tied Label Slicer section
Title: Message Title mdonohue commented on JENKINS-29547 Re: "master" value is silently ignored and empty value is set for "Restrict where..." in Tied Label Slicer section My proposed fix to Jenkins core is here: https://github.com/mdonohue/jenkins/commit/2cb89d3e269318644fabd1acb4861690e662aef9 I am having difficulty testing this code right now - JDK8 on Windows 10 results in several unit test failures doing a 'mvn install' on jenkins. I think JDK7 will do better, but I couldn't find any documentation of that on the jenkins wiki. JDK7 testing will happen another day. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [configurationslicing-plugin] (JENKINS-19651) Config Slicing "Gradle version per project" yields stack trace output
Title: Message Title mdonohue resolved as Fixed Jenkins / JENKINS-19651 Config Slicing "Gradle version per project" yields stack trace output Change By: mdonohue Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [configurationslicing-plugin] (JENKINS-19651) Config Slicing "Gradle version per project" yields stack trace output
Title: Message Title mdonohue commented on JENKINS-19651 Re: Config Slicing "Gradle version per project" yields stack trace output Fixed in configurationslicing-1.41-2-g6c6f04b Code appears in the 1.44 release of the plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [configurationslicing-plugin] (JENKINS-29093) POM location is deleted when changing Maven top-level target
Title: Message Title mdonohue resolved as Fixed Released in the 1.44 version of configurationslicing Jenkins / JENKINS-29093 POM location is deleted when changing Maven top-level target Change By: mdonohue Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [configurationslicing-plugin] (JENKINS-29941) Using Configuration Slicer unsets the "Ignore post-commit hooks" checkbox for polled builds
Title: Message Title mdonohue resolved as Fixed Released in the 1.44 version of configurationslicing Jenkins / JENKINS-29941 Using Configuration Slicer unsets the "Ignore post-commit hooks" checkbox for polled builds Change By: mdonohue Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [configurationslicing-plugin] (JENKINS-22551) Changes Saved on Execution Slicer not Saved in config.xml
Title: Message Title mdonohue commented on JENKINS-22551 Re: Changes Saved on Execution Slicer not Saved in config.xml i hadn't heard of the inheritance-plugin before. it seems at odds with the design of the configuration slicing plugin. If anything, I would just put in a warning on the configuration slicing screen explaining that they don't play nice together. Pick one strategy, rather than trying to mix them. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [configurationslicing-plugin] (JENKINS-25320) UnsupportedOperationException when updating "Max # of builds to keep"
Title: Message Title mdonohue commented on JENKINS-25320 Re: UnsupportedOperationException when updating "Max # of builds to keep" Following up on Ninian's comment: Does this still reproduce with the 1.40 release of configurationslicing? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [configurationslicing-plugin] (JENKINS-26044) "Ant version per project" fails to change via Configuration Slicing (AntSlicer)
Title: Message Title mdonohue commented on JENKINS-26044 Re: "Ant version per project" fails to change via Configuration Slicing (AntSlicer) I am not able to reproduce this problem right now - Jenkins 1.580.1 and a dev build of configuration slicing. git describe is: configurationslicing-1.41-12-g7e87159. If I switch a project's ant version from default to one on the list, everything works correctly. Even tried an ant version with a space in the name. It looks like making a typo isn't handled well - if you're off by one character, no change is made, but also no error is reported. Having better error reporting, along with an auto-complete facility, would be very useful. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [configurationslicing-plugin] (JENKINS-26933) Saving change in 'Configure Slicing Plugin' page causing Form too large exception
Title: Message Title mdonohue commented on JENKINS-26933 Re: Saving change in 'Configure Slicing Plugin' page causing Form too large exception Which slicers does this affect? Also, how many jobs or items are being sliced when it happens? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [configurationslicing-plugin] (JENKINS-29547) "master" value is silently ignored and empty value is set for "Restrict where..." in Tied Label Slicer section
Title: Message Title
mdonohue commented on JENKINS-29547
Re: "master" value is silently ignored and empty value is set for "Restrict where..." in Tied Label Slicer section
Yes, getAssignedNode and setAssignedNode are consistent about converting 'master' to/from a null value in the field. The problem is that the configuration section for AbstractProject does not follow that convention.
see getAssignedLabelString and AbstractProject.submit. Here are the relevant lines of code, where you can see no attempt is made to convert 'master' into a null value for assignedNode. You can also verify this by looking at config.xml for a project after setting the label to 'master', where you will see master in the file.
if(req.getParameter("hasSlaveAffinity")!=null) {
assignedNode = Util.fixEmptyAndTrim(req.getParameter("_.assignedLabelString"));
} else {
assignedNode = null;
}
canRoam = assignedNode==null;
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [configurationslicing-plugin] (JENKINS-29547) "master" value is silently ignored and empty value is set for "Restrict where..." in Tied Label Slicer section
Title: Message Title mdonohue edited a comment on JENKINS-29547 Re: "master" value is silently ignored and empty value is set for "Restrict where..." in Tied Label Slicer section I've been looking at the code, comparing the configuration of a freestyle project manually, and via the label slicer. I think this is a bug in Jenkins, since using the configuration screen sets the 'assignedNode' private field directly based on what was typed in the HTML form. In this case the 'master' string goes directly into the field. But any other plugin that wants to modify the 'assignedNode' field needs to call 'setAssignedNode', and that function does extra checking. If you set the assigned node to "master" it switches that to 'null'.There are other comments indicating that 'null' is the preferred representation for the master node, but the AbstractProject configuration code doesn't maintain that invariant. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [configurationslicing-plugin] (JENKINS-29547) "master" value is silently ignored and empty value is set for "Restrict where..." in Tied Label Slicer section
Title: Message Title mdonohue commented on JENKINS-29547 Re: "master" value is silently ignored and empty value is set for "Restrict where..." in Tied Label Slicer section I've been looking at the code, comparing the configuration of a freestyle project manually, and via the label slicer. I think this is a bug in Jenkins, since using the configuration screen sets the 'assignedNode' private field directly based on what was typed in the HTML form. In this case the 'master' string goes directly into the field. But any other plugin that wants to modify the 'assignedNode' field needs to call 'setAssignedNode', and that function does extra checking. If you set the assigned node to "master" it switches that to 'null'. There are other comments indicating that 'null' is the preferred representation for the master node, but the AbstractProject configuration code doesn't maintain that invariant. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [configurationslicing-plugin] (JENKINS-19651) Config Slicing "Gradle version per project" yields stack trace output
Title: Message Title mdonohue commented on JENKINS-19651 Re: Config Slicing "Gradle version per project" yields stack trace output Yeah, the Gradle plugin constructor changed since version 1.12, and didn't leave a compatibility constructor behind. I have some code written to fix that in the configuration slicing plugin. Will get it packaged up tonight. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [configurationslicing-plugin] (JENKINS-25536) Adding some parameters
Title: Message Title mdonohue commented on JENKINS-25536 Re: Adding some parameters There's no specific documentation besides looking at the source code of the configuration slicing plugin itself. I had originally hoped that other plugin makers might adopt slicing implementations within their plugins, but that seems unlikely given the complexity of stacked plugin dependencies. The alternative would be to move the slicing functionality into Jenkins core, so other plugin implementors would be more likely to see it. A number of other contributors have picked up work on the slicing plugin in the last few years. As I look at the UI of slices, it seems a little overwhelming right now. So I think taming the UI complexity of selecting a slice would be the next big step for this plugin. Perhaps it could be moved closer to the configuration page for individual projects, instead of listing everything at once. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [configurationslicing-plugin] (JENKINS-29941) Using Configuration Slicer unsets the Ignore post-commit hooks checkbox for polled builds
Title: Message Title mdonohue commented on JENKINS-29941 Re: Using Configuration Slicer unsets the Ignore post-commit hooks checkbox for polled builds Yes, SCMTrigger now has two constructors. Configuration slicing uses the older one, which defaults the Ignore post-comits hooks value to 'false'. To fix this, we will need to include the post-commit hooks option in the configuration slice spec. I played around with some ideas here last night, but didn't get something that worked well. The current design doesn't handle this well, so I think the slicing logic will need more parameterization to make this work. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [bitkeeper-plugin] (JENKINS-29788) Bk configuration removed on project change
Title: Message Title mdonohue resolved as Fixed bitkeeper-plugin 1.8 should work well with the multiple-scm plugin. databound constructors were the trick Jenkins / JENKINS-29788 Bk configuration removed on project change Change By: mdonohue Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [bitkeeper-plugin] (JENKINS-29788) Bk configuration removed on project change
Title: Message Title mdonohue commented on JENKINS-29788 Re: Bk configuration removed on project change plugin version 1.8 should be released now. let me know how it goes. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [bitkeeper-plugin] (JENKINS-29788) Bk configuration removed on project change
Title: Message Title mdonohue commented on JENKINS-29788 Re: Bk configuration removed on project change I switched the BitKeeper plugin to use databinding for the job configuration, instead of looking for explicit form values. This is more modular, and my testing shows that it now works properly with the multiple SCM plugin. I am currently working on getting it released. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [bitkeeper-plugin] (JENKINS-29788) Bk configuration removed on project change
Title: Message Title mdonohue commented on JENKINS-29788 Re: Bk configuration removed on project change Thanks - yes, the multiple SCMs plugin introduces a number of corner cases that don't appear normally. I will see if I can reproduce with that plugin. Do you have other SCM plugins installed beside those three - BitKeeper, Mercurial, Multiple SCM? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [bitkeeper-plugin] (JENKINS-29788) Bk configuration removed on project change
Title: Message Title mdonohue commented on JENKINS-29788 Re: Bk configuration removed on project change I have a test environment setup with Jenkins 1.613 and the BitKeeper 1.7 plugin. I created a job, entered some values for the parent URL and local repo, and noted that those values were saved correctly. Then I went to make some changes to the job - the polling schedule was updated and I added a build step, and saved the config change. When viewing the job again, the parent URL and local repo strings are unchanged. Is there anything else you can tell me about how to get this to reproduce? Are you able to make it happen with a small test Jenkins setup? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [urlscm] (JENKINS-17479) URL SCM always marks URL as changed with Poll SCM option
mdonohue commented on JENKINS-17479 URL SCM always marks URL as changed with Poll SCM option URLSCM checks the last-modified time returned by the web server. If the web server always returns a different last-modified time, then you will see the behavior described. 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] (JENKINS-16670) Join trigger not kicking off end jobs after update to latest set of plugins.
mdonohue resolved JENKINS-16670 as Duplicate Join trigger not kicking off end jobs after update to latest set of plugins. Change By: mdonohue (10/Feb/13 10:45 PM) Status: Open Resolved 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/groups/opt_out.
