[JIRA] [job-dsl-plugin] (JENKINS-29502) add support for publisher of Debian Package Plugin
Title: Message Title Marc Gnther commented on JENKINS-29502 Re: add support for publisher of Debian Package Plugin Pull Request: [JENKINS-29502] added support debian package publisher #542 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] [job-dsl-plugin] (JENKINS-29501) add support for Crittercism dSYM Plugin
Title: Message Title Marc Gnther commented on JENKINS-29501 Re: add support for Crittercism dSYM Plugin Pull Request: [JENKINS-29501] added support for crittercism plugin #541 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] [job-dsl-plugin] (JENKINS-29503) add support for filesMatch condition of Run Condition Plugin
Title: Message Title Marc Gnther commented on JENKINS-29503 Re: add support for filesMatch condition of Run Condition Plugin Pull Request: [JENKINS-29503] added filesMatch to Run Condition plugin #538 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] [job-dsl-plugin] (JENKINS-29504) add support for Xcode Plugin
Title: Message Title Marc Gnther commented on JENKINS-29504 Re: add support for Xcode Plugin Pull Request: [JENKINS-29504] added support for Xcode plugin #545 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] [job-dsl-plugin] (JENKINS-29500) add support for sandboxed groovy postbuild sripts
Title: Message Title Marc Gnther commented on JENKINS-29500 Re: add support for sandboxed groovy postbuild sripts Pull Request: [JENKINS-29500] added sandbox option to groovyPostbuild #539 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] [job-dsl-plugin] (JENKINS-29499) add support for Heavy Job Plugin
Title: Message Title Marc Gnther updated an issue Jenkins / JENKINS-29499 add support for Heavy Job Plugin Change By: Marc Gnther Addsupportforthe[Heavy Weight Job Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Heavy+Job+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] [job-dsl-plugin] (JENKINS-29499) add support for Heavy Weight Plugin
Title: Message Title Marc Gnther commented on JENKINS-29499 Re: add support for Heavy Weight Plugin Pull Request: [JENKINS-29499] added weight option for Heavy Job Plugin #540 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] [job-dsl-plugin] (JENKINS-29499) add support for Heavy Job Plugin
Title: Message Title Marc Gnther updated an issue Jenkins / JENKINS-29499 add support for Heavy Job Plugin Change By: Marc Gnther Summary: addsupportforHeavy Weight Job 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] [job-dsl-plugin] (JENKINS-29498) add support for primaryView of Folders plugin
Title: Message Title Marc Gnther commented on JENKINS-29498 Re: add support for primaryView of Folders plugin Pull Request: [JENKINS-29498] added the primaryView option to Folders #544 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] [job-dsl-plugin] (JENKINS-29505) add support for Clang Scan Build Plugin
Title: Message Title Marc Gnther commented on JENKINS-29505 Re: add support for Clang Scan Build Plugin Pull Request: [JENKINS-29505] added support for Clang Scan-Build plugin #543 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] [job-dsl-plugin] (JENKINS-29500) add support for sandboxed groovy postbuild sripts
Title: Message Title Marc Gnther created an issue Jenkins / JENKINS-29500 add support for sandboxed groovy postbuild sripts Issue Type: Bug Assignee: Marc Gnther Components: job-dsl-plugin Created: 20/Jul/15 9:51 AM Priority: Minor Reporter: Marc Gnther Add support for the sandbox option (Use Groovy Sandbox) of Groovy Postbuild Plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [job-dsl-plugin] (JENKINS-29501) Add support for Crittercism dSYM Plugin
Title: Message Title Marc Gnther created an issue Jenkins / JENKINS-29501 Add support for Crittercism dSYM Plugin Issue Type: Bug Assignee: Marc Gnther Components: job-dsl-plugin Created: 20/Jul/15 9:52 AM Priority: Minor Reporter: Marc Gnther Add support for Crittercism dSYM Plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [job-dsl-plugin] (JENKINS-29504) Add support for Xcode Plugin
Title: Message Title Marc Gnther created an issue Jenkins / JENKINS-29504 Add support for Xcode Plugin Issue Type: Improvement Assignee: Marc Gnther Components: job-dsl-plugin Created: 20/Jul/15 9:58 AM Priority: Minor Reporter: Marc Gnther Add support for the Xcode Plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [job-dsl-plugin] (JENKINS-29502) add support for publisher of Debian Package Plugin
Title: Message Title Marc Gnther created an issue Jenkins / JENKINS-29502 add support for publisher of Debian Package Plugin Issue Type: Bug Assignee: Marc Gnther Components: job-dsl-plugin Created: 20/Jul/15 9:54 AM Priority: Minor Reporter: Marc Gnther Add support for the publisher part of the Debian Package Builder. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [job-dsl-plugin] (JENKINS-29498) add support for primaryView of Folders plugin
Title: Message Title Marc Gnther created an issue Jenkins / JENKINS-29498 add support for primaryView of Folders plugin Issue Type: Bug Assignee: Marc Gnther Components: job-dsl-plugin Created: 20/Jul/15 9:45 AM Priority: Minor Reporter: Marc Gnther The Folders Plugin allows to set one of the views in the folder as the default view (called primaryView). Currently, Job-Dsl-Plugin hardcodes this to the All view. Add Comment
[JIRA] [job-dsl-plugin] (JENKINS-29505) add support for Clang Scan Build Plugin
Title: Message Title Marc Gnther created an issue Jenkins / JENKINS-29505 add support for Clang Scan Build Plugin Issue Type: Improvement Assignee: Marc Gnther Components: job-dsl-plugin Created: 20/Jul/15 9:59 AM Priority: Minor Reporter: Marc Gnther Add support for the Clang Scan Build Plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [job-dsl-plugin] (JENKINS-29499) add support for Heavy Weight Plugin
Title: Message Title Marc Gnther created an issue Jenkins / JENKINS-29499 add support for Heavy Weight Plugin Issue Type: Bug Assignee: Marc Gnther Components: job-dsl-plugin Created: 20/Jul/15 9:49 AM Priority: Minor Reporter: Marc Gnther Add support for the Heavy Weight Plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [job-dsl-plugin] (JENKINS-29498) add support for primaryView of Folders plugin
Title: Message Title Marc Gnther updated an issue Jenkins / JENKINS-29498 add support for primaryView of Folders plugin Change By: Marc Gnther Issue Type: Bug Improvement 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] [job-dsl-plugin] (JENKINS-29500) add support for sandboxed groovy postbuild sripts
Title: Message Title Marc Gnther updated an issue Jenkins / JENKINS-29500 add support for sandboxed groovy postbuild sripts Change By: Marc Gnther Issue Type: Bug Improvement 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] [job-dsl-plugin] (JENKINS-29499) add support for Heavy Weight Plugin
Title: Message Title Marc Gnther updated an issue Jenkins / JENKINS-29499 add support for Heavy Weight Plugin Change By: Marc Gnther Issue Type: Bug Improvement 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] [job-dsl-plugin] (JENKINS-29503) add support for filesMatch condition of Run Condition Plugin
Title: Message Title Marc Gnther updated an issue Jenkins / JENKINS-29503 add support for filesMatch condition of Run Condition Plugin Change By: Marc Gnther Issue Type: NewFeature Improvement 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] [job-dsl-plugin] (JENKINS-29501) Add support for Crittercism dSYM Plugin
Title: Message Title Marc Gnther updated an issue Jenkins / JENKINS-29501 Add support for Crittercism dSYM Plugin Change By: Marc Gnther Issue Type: Bug Improvement 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] [job-dsl-plugin] (JENKINS-29502) add support for publisher of Debian Package Plugin
Title: Message Title Marc Gnther updated an issue Jenkins / JENKINS-29502 add support for publisher of Debian Package Plugin Change By: Marc Gnther Issue Type: Bug Improvement 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] [job-dsl-plugin] (JENKINS-29503) add support for filesMatch condition of Run Condition Plugin
Title: Message Title Marc Gnther created an issue Jenkins / JENKINS-29503 add support for filesMatch condition of Run Condition Plugin Issue Type: New Feature Assignee: Marc Gnther Components: job-dsl-plugin Created: 20/Jul/15 9:56 AM Priority: Minor Reporter: Marc Gnther Add support for the filesMatch condition from the Run Condition Plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [job-dsl-plugin] (JENKINS-29501) add support for Crittercism dSYM Plugin
Title: Message Title Marc Gnther updated an issue Jenkins / JENKINS-29501 add support for Crittercism dSYM Plugin Change By: Marc Gnther Summary: Add add supportforCrittercismdSYMPlugin 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] [job-dsl-plugin] (JENKINS-29508) add support for Extra Columns Plugin
Title: Message Title Marc Gnther created an issue Jenkins / JENKINS-29508 add support for Extra Columns Plugin Issue Type: Improvement Assignee: Marc Gnther Components: job-dsl-plugin Created: 20/Jul/15 12:54 PM Priority: Minor Reporter: Marc Gnther Currently, only lastBuildConsole and configureProject columns are supported, but Extra Columns Plugin plugin provides many more. Add Comment This message was sent by Atlassian JIRA
[JIRA] [job-dsl-plugin] (JENKINS-29509) add support for Console Column Plugin
Title: Message Title Marc Gnther created an issue Jenkins / JENKINS-29509 add support for Console Column Plugin Issue Type: Improvement Assignee: Marc Gnther Components: job-dsl-plugin Created: 20/Jul/15 12:56 PM Priority: Minor Reporter: Marc Gnther Add support for the Console Column Plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [job-dsl-plugin] (JENKINS-29510) add support for Compact Columns
Title: Message Title Marc Gnther created an issue Jenkins / JENKINS-29510 add support for Compact Columns Issue Type: Improvement Assignee: Marc Gnther Components: job-dsl-plugin Created: 20/Jul/15 12:57 PM Priority: Minor Reporter: Marc Gnther Add support for Compact Columns. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [job-dsl-plugin] (JENKINS-29504) add support for Xcode Plugin
Title: Message Title Marc Gnther updated an issue Jenkins / JENKINS-29504 add support for Xcode Plugin Change By: Marc Gnther Summary: Add add supportforXcodePlugin 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] [job-dsl-plugin] (JENKINS-29504) Add support for Xcode Plugin
Title: Message Title Marc Gnther updated an issue Jenkins / JENKINS-29504 Add support for Xcode Plugin Change By: Marc Gnther Add add supportforthe[XcodePlugin|https://wiki.jenkins-ci.org/display/JENKINS/Xcode+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] [job-dsl-plugin] (JENKINS-29504) Add support for Xcode Plugin
Title: Message Title Marc Gnther updated an issue Jenkins / JENKINS-29504 Add support for Xcode Plugin Change By: Marc Gnther add Add supportforthe[XcodePlugin|https://wiki.jenkins-ci.org/display/JENKINS/Xcode+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] [crowd-plugin] (JENKINS-17288) Packaging of spring-context-support causes crowd plugin to prevent Jenkins starting properly
Marc Günther commented on JENKINS-17288 Packaging of spring-context-support causes crowd plugin to prevent Jenkins starting properly Any news on this one? We still have to remove that spring-context jar file manually, every time we do an upgrade of Jenkins... 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] [docker-plugin] (JENKINS-27325) Docker plugin messes up Configure page
Marc Günther commented on JENKINS-27325 Docker plugin messes up Configure page I feared as much... On the other hand, I have never ever seen this problem before in all the years I use Jenkins. And now it came up in Docker and Slack Plugin. So this is more a general issue in core, and not a plugin problem? 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] [docker-plugin] (JENKINS-27325) Docker plugin messes up Configure page
Marc Günther edited a comment on JENKINS-27325 Docker plugin messes up Configure page Oh, yeah, another quite confusing example. Is there already a ticket for this more general issue? So, is the order in which plugins appear on the page completely arbitrary, or can the plugin control this? (sorry, I know absolutely nothing about this) If I understand this correctly, we have two kinds of plugins here: plugins with lots of options, that introduce their section with a visible separator (heading) plugins with very few options, with no visible separator Wouldn't it be a quick fix to at least bubble the plugins that to NOT have a visible separator to the top? Then at least none of the above scenarios could happen. 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] [docker-plugin] (JENKINS-27325) Docker plugin messes up Configure page
Marc Günther commented on JENKINS-27325 Docker plugin messes up Configure page Oh, yeah, another quite confusing example. So, is the order in which plugins appear on the page completely arbitrary, or can the plugin control this? (sorry, I know absolutely nothing about this) If I understand this correctly, we have two kinds of plugins here: plugins with lots of options, that introduce their section with a visible separator (heading) plugins with very few options, with no visible separator Wouldn't it be a quick fix to at least bubble the plugins that to NOT have a visible separator to the top? Then at least none of the above scenarios could happen. 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] [slack-plugin] (JENKINS-27326) Slack plugin messes up Configure page
Marc Günther created JENKINS-27326 Slack plugin messes up Configure page Issue Type: Bug Assignee: Unassigned Components: slack-plugin Created: 10/Mar/15 8:39 PM Description: Slack Plugin simply inserts its configuration options somewhere in the middle of the top section of the Jenkins Configure page. There is no visible separator at the end of its section, making it quite difficult to find out which options belong to the plugin and which don't. Project: Jenkins Priority: Minor Reporter: Marc Günther 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] [docker-plugin] (JENKINS-27325) Docker plugin messes up Configure page
Marc Günther created JENKINS-27325 Docker plugin messes up Configure page Issue Type: Bug Assignee: Unassigned Components: docker-plugin Created: 10/Mar/15 8:39 PM Description: Docker Plugin simply inserts its configuration options somewhere in the middle of the top section of the Jenkins Configure page. There is no visible separator at the end of its section, making it quite difficult to find out which options belong to the plugin and which don't. (see JENKINS-25713 for the confusion this causes) Project: Jenkins Priority: Minor Reporter: Marc Günther 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] [disk-usage-plugin] (JENKINS-22224) one job configuration change results in three Job Config History entries
Marc Günther commented on JENKINS-4 one job configuration change results in three Job Config History entries +1 We are not using disk-usage plugin anymore, cause it's so slow, but I still see this behaviour. So it's definitely not restricted to disk-usage plugin alone 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] [github-plugin] (JENKINS-23662) Github Plugin 1.9 broke webhook trigger
Marc Günther commented on JENKINS-23662 Github Plugin 1.9 broke webhook trigger So this issue has been 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] [github-plugin] (JENKINS-10391) GitHub plugin fails to add webhook on an organization's repository
Marc Günther commented on JENKINS-10391 GitHub plugin fails to add webhook on an organizations repository FWIW, it works for me on a Github Enterprise instance, where the repos are owned by an organization, and the jenkins user is an owner in that organization. Github Plugin 1.9.1, Github API Plugin 1.58 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] [github-plugin] (JENKINS-23662) Github Plugin 1.9 broke webhook trigger
Marc Günther commented on JENKINS-23662 Github Plugin 1.9 broke webhook trigger Thanks 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] [github-plugin] (JENKINS-24193) Github Pull Request Builder plugin uses github account email instead of the custom route email
Marc Günther commented on JENKINS-24193 Github Pull Request Builder plugin uses github account email instead of the custom route email wrong component! - ghprb-plugin 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] [github-plugin] (JENKINS-19804) Automatic Github push creation would be awesome if the setup allowed me to select HTTPS instead of HTTP
Marc Günther commented on JENKINS-19804 Automatic Github push creation would be awesome if the setup allowed me to select HTTPS instead of HTTP FWIW, Github Plugin 1.9.1 is creating https hooks for me just fine... 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] [ghprb-plugin] (JENKINS-24193) Github Pull Request Builder plugin uses github account email instead of the custom route email
Marc Günther commented on JENKINS-24193 Github Pull Request Builder plugin uses github account email instead of the custom route email Yes, definitely. Took me a little bit to find it under that name, and I guess most people simply do not take the time to search for 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/d/optout.
[JIRA] [credentials] (JENKINS-22338) Safari silently overwrites various username or password fields
Marc Günther commented on JENKINS-22338 Safari silently overwrites various username or password fields I don't understand how Safari decides which fields to overwrite. For example on the page Manage Jenkins - Configure Global Security I use the Project-based Matrix Authorization Strategy and it detects the "User/group to add" text field at the end as the one to put my login name. The html looks like this: td colspan="3" User/group to add: input id="id1826282text" type="text" span class="yui-button yui-push-button " id="id1826282button" name="" span class="first-child" button type="button" tabindex="0" id="id1826282button-button"Add/button /span /span /td So it seems the only indication is, that there is a text containing the string "user" in front of an otherwise completely unusual textfield. BTW, Safari only does that if it also detects a password field on the same page, which in my case is way above on that page in the "Security Realm - Crowd" setting. The html here looks like this: tr nameref="radio-block-0" style="" td class="setting-leftspace"nbsp;/td td class="setting-name"Application Password/td td class="setting-main" input name="crowd.applicationPassword" value="secret" class="setting-input " type="password" /td td class="setting-help"a class="help-button" href="" class="code-quote">"#" helpurl="/jenkins/plugin/crowd/help-global-apppassword.html" tabindex=""img height="16" alt="Help for feature: Application Password" width="16" src="" class="code-quote">"/jenkins/static/83dac1d3/images/16x16/help.png"/a/td /tr Here, at least, the field is of type password, it contains "password" in its name, and it has "password" in the string before it... I'm confused... Anyway, the problem is, that the "Configure Global Security" page is completely unusable in Safari, as it will overwrite the Crowd password every time. And, the layout being as broken as it is, you don't even notice, as the password field is somewhere outside the page on the far right... 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] (JENKINS-22338) Safari silently overwrites various username or password fields
Marc Günther commented on JENKINS-22338 Safari silently overwrites various username or password fields Yea, I know, just trying to find out what we can actually do to prevent this thing from happening... As it seems that simply using autocomplete="off" does not work for Safari: http://stackoverflow.com/questions/22661977/disabling-safari-autofill-on-usernames-and-passwords nor for Chrome: https://code.google.com/p/chromium/issues/detail?id=370363#makechanges 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-24017) Rebuild Last can trigger the wrong build
Marc Günther created JENKINS-24017 Rebuild Last can trigger the wrong build Issue Type: Bug Assignee: ragesh_nair Components: rebuild Created: 29/Jul/14 2:48 PM Description: When you click on the "Rebuild Last" link in the main menu, it will trigger the build which was the last one when the page was loaded. If there have been other builds in the mean time, they will be skipped. This is especially annoying for parameterized jobs, of course. The reason for this is because the link contains the fixed build number in its URL, eg. ../jenkins/job/my-job/6139/rebuild. A simple solution would be to simply use lastCompletedBuild instead of the build number in the link. It will then always use the last build that is not currently running. Project: Jenkins Priority: Minor Reporter: Marc Günther 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-24017) Rebuild Last can trigger the wrong build
Marc Günther edited a comment on JENKINS-24017 Rebuild Last can trigger the wrong build One more comment, I was first thinking of using lastBuild, but that gave me a NullPointerException if (and only if) the job was currently running. The NPE involved Naginator, though Caused by: java.lang.NullPointerException at com.chikli.hudson.plugin.naginator.NaginatorActionFactory.createFor(NaginatorActionFactory.java:20) at hudson.model.Run.getTransientActions(Run.java:351) ... So, using lastCompletedBuild would still give you "wrong" results if a job is currently running, but it's still better than the current behaviour, and seems to be a trivial change. 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] [maven] (JENKINS-11864) Renaming a JDK/Maven Installation does not adjust Jobs which use it
Marc Günther updated JENKINS-11864 Renaming a JDK/Maven Installation does not adjust Jobs which use it Change By: Marc Günther (08/Jul/14 12:51 PM) Summary: Renaminga JDK/ MavenInstallationdoesnotadjustJobswhichuseit Description: WehaveseveralMaveninstallations,whicharedefinedintheJenkinsGlobalSettings.WhenIrenameoneoftheinstallations,thejobsthathadbeenconfiguredtouseitarenotupdated,andswitchtothe(Default)Maveninstallation,causingthosebuildstofaillateron. EDIT:sameistrueforJDKInstallations.IrenamedourJDK8installation,andnowtonsofjobsfailedbecausetheyusedthedefaultJDK6. 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] [core] (JENKINS-18131) Pressing Return when adding users switches to different page
Marc Günther commented on JENKINS-18131 Pressing Return when adding users switches to different page Sorry, I do not understand why this is "Not a Defect". This is a usability issue. I know quite well how a standard html form behaves. That is completely besides the point. Other websites manage to handle this case quite fine. So this is a genuine bug. 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] [core] (JENKINS-19393) global search should not jump to exact result if more than one result is found
Marc Günther commented on JENKINS-19393 global search should not jump to exact result if more than one result is found The dropdown only shows the first 10 results. We have for example lots of jobs (80) that contain the string 'sonar'. I used to be able to enter 'sonar' into the search box, and see all those jobs (after clicking on the annoying "see 20 more" link for four times, but that's another issue). Now someone was so entirely clever to name his job "sonar", and now the search jumps directly to that job, which is entirely not whoat I would expect. Jumping directly to a specific result should (if at all) happen ONLY, when there is EXACTLY ONE result. NOT when there are 80 results... I don't see how this can not be a bug. 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] [disk-usage] (JENKINS-22224) one job configuration change results in three Job Config History entries
Marc Günther commented on JENKINS-4 one job configuration change results in three Job Config History entries It is a problem, cause it is convoluting your job config history. If every plugin did something like this, the history would be completely useless. Disappearing publisher configs are of course an even bigger problem... 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] [core] (JENKINS-17578) target attribute get's removed from a tags in job descriptions
Marc Günther commented on JENKINS-17578 target attribute gets removed from a tags in job descriptions "Anything Goes Formatter" plugin sounds interesting, but still, I guess my original questions was more like, why is the target attribute considered unsafe? Beause I don't think it is, and then this would be a bug, no? I don't understand the "Jira is not a support site" part of your comment. 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] [core] (JENKINS-19136) concurrent edit of configurations overwrite each other
Marc Günther commented on JENKINS-19136 concurrent edit of configurations overwrite each other Uh, wow, really? I luckily have never encountered that (the reload thingy). It sounds quite dangerous... 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] [core] (JENKINS-17459) Little red/yellow/green icons should get you to Console everywhere
Marc Günther commented on JENKINS-17459 Little red/yellow/green icons should get you to Console everywhere Unfortunately, given the treatment of several of my reported issues (most of which are usability problems), I don't get the feeling that inconsistent usability is considered a bug, or even a missing feature 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] [core] (JENKINS-22340) Cannot configure colums of 'All' view
Marc Günther commented on JENKINS-22340 Cannot configure colums of All view You probably mean, that you install a buggy column, which breaks your personal views, so you can't open them anymore? I fail to see how the All View is going to help you in that case, especially when you have already set a different view as the default one, as you describe later. So to me, the All View is mostly useless and broken by design. 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] [plugin] (JENKINS-17480) Copying a job should disable the copy while editing it
Marc Günther resolved JENKINS-17480 as Fixed Copying a job should disable the copy while editing it Oleg, I get the impression that you completely misunderstood my report. I have no other explanation for your replies. Anyway, I just noticed that this has been fixed in the mean time, so resolving this as Fixed. Don't know which version, of if there was a different ticket for this, though. Change By: Marc Günther (07/Jul/14 3:06 PM) Status: Open Resolved 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] [core] (JENKINS-21930) Jobs fail due to node went offline during the build
Marc Günther
commented on JENKINS-21930
Jobs fail due to node went offline during the build
I didn't try that, but I just looked at the source code, and found this:
https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/AbstractBuild.java#L538
public Result run(@Nonnull BuildListener listener) throws Exception {
Computer c = node.toComputer();
if (c==null || c.isOffline()) {
// As can be seen in HUDSON-5073, when a build fails because of the slave connectivity problem,
// error message doesn't point users to the slave. So let's do it here.
listener.hyperlink("/computer/"+builtOn+"/log","Looks like the node went offline during the build. Check the slave log for the details.");
...
And the isOffline() method also checks for the temporarilyOffline status:
https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Computer.java#L507
public boolean isOffline() {
return temporarilyOffline || getChannel()==null;
}
So, you are correct, the connection is not broken, but the check in this case is wrong. It should check only for the channel, and not the temporarilyOffline status.
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] [envinject] (JENKINS-23274) Do not output the Evaluated Groovy script to console
Marc Günther updated JENKINS-23274 Do not output the Evaluated Groovy script to console Change By: Marc Günther (02/Jun/14 4:04 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] [envinject] (JENKINS-23274) Do not output the Evaluated Groovy script to console
Marc Günther created JENKINS-23274 Do not output the Evaluated Groovy script to console Issue Type: Bug Assignee: Gregory Boissinot Components: envinject Created: 02/Jun/14 4:03 PM Description: The contents of the "Evaluated Groovy script" are printed to the Console of every build. This only clutters the Console output and is very confusing for our users. Can it be disabled? Project: Jenkins Priority: Trivial Reporter: Marc Günther 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] [core] (JENKINS-19074) Why More than 1 builds are needed for the trend report?
Marc Günther commented on JENKINS-19074 Why More than 1 builds are needed for the trend report? What about consistency? I always click on the "trend" link, when I want to see the build times. There is absolutely no reason whatsoever to not display it. The fact that the information is displayed somewhere else is besides the point. 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] [core] (JENKINS-17471) Maven Buildstep and Maven project are completely different
Marc Günther commented on JENKINS-17471 Maven Buildstep and Maven project are completely different Having two completely independent implementations for doing the same thing does not really sound like a good design decision to me 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] [core] (JENKINS-18869) list-view with lots of tabs renders a very wide job table
Marc Günther commented on JENKINS-18869 list-view with lots of tabs renders a very wide job table I just tried this on Safari, Chrome and Firefox (all MacOSX). When I have a page with for example 30 tabs that don't fit horizontally inside the window anymore, then the table with the list of jobs below it also gets expanded to fit the entire width of the page. What I would expect is that the table takes only as much horizontal space as it needs to display everything without wrapping, and not grow to fit the entire tab bar above 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/d/optout.
[JIRA] [core] (JENKINS-21930) Jobs fail due to node went offline during the build
Marc Günther commented on JENKINS-21930 Jobs fail due to node went offline during the build We have mostly Swarm slaves, and I usually use the jenkins-cli offline-node command, although I might have used the "Mart this node temporarily offline" button once in a while. I am not sure if it also happens on ssh slaves. 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] [core] (JENKINS-22490) weather icon also for test failures, not only build failures
Marc Günther commented on JENKINS-22490 weather icon also for test failures, not only build failures Not really a helpful behaviour, as usually we have maybe a couple of failing unit tests, but definitely never 20%. How could that even happen? 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] [plugin] (JENKINS-17480) Copying a job should disable the copy while editing it
Marc Günther commented on JENKINS-17480 Copying a job should disable the copy while editing it Why a plugin? "Copy existing job" is a core functionality, and should do the right thing. The current behaviour is simply broken. 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] [core] (JENKINS-18869) list-view with lots of tabs renders a very wide job table
Marc Günther commented on JENKINS-18869 list-view with lots of tabs renders a very wide job table Ah, lol, now I understand We are currently using Nested Views plugin and have a couple of views where this is happening. I might try the DropDown ViewsTabBar you mentioned. Thanks. 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] [core] (JENKINS-22490) weather icon also for test failures, not only build failures
Marc Günther commented on JENKINS-22490 weather icon also for test failures, not only build failures We have more like 8000 tests. 20% is definitely not going to happen Yea, I know how the weather icon works, I was merely questioning its usefulness in this particular case. As for plugins, nothing special, just the normal "Publish junit test result" thingy. 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] [plugin] (JENKINS-17480) Copying a job should disable the copy while editing it
Marc Günther commented on JENKINS-17480 Copying a job should disable the copy while editing it I would still maintain that this is a bug in the existing implementation, and not a feature. And as such it doesn't belong into a plugin. 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] [core] (JENKINS-19566) Confusing Delete Project and Wipe Workspace
Marc Günther updated JENKINS-19566 Confusing Delete Project and Wipe Workspace Change By: Marc Günther (08/Apr/14 3:16 PM) Description: Severaltimesnow,Ihaveaccidentally * deleted * aproject,whenIwantedtowipe titse its workspace.Obvioususabilityrules:-menuentriesfordangerousactionsshould*NOTbenear*everydayactions-confirmationmessagesfordangerousactionsshould*NOTlooksimilar*tomoreharmlessactionsJenkinsfailsboth:-theDeleteProjectentryissittingbetweenBuildNowandConfigure-thewarningmessageforwipingouttheworkspacelooksandworksalmostidenticaltothedeleteprojectwarning.Infact,thewipeworkspacewarningeven*looksmorescary*,asitisinabigboldfont,whereasthedeleteprojectwarningisinasmallnormalfont. EDIT:Sincesomeversions,insteadofaseparatepage,Jenkinsnowopensaconfirmationdialog,which*lookscompletelyidentical*forbothoperations. 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] [git] (JENKINS-22064) Git Repository Browser URL not saved anymore
Marc Günther commented on JENKINS-22064 Git Repository Browser URL not saved anymore I would have really liked to post a groovy script here, that fixes all the now empty URLs, but it is not possible to set the url or the browser programmatically So how do I fix the 670 jobs with a browser but no url, that I now have? 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] [core] (JENKINS-22338) Safari silently overwrites various username or password fields
Marc Günther
updated JENKINS-22338
Safari silently overwrites various username or password fields
Change By:
Marc Günther
(03/Apr/14 6:09 PM)
Summary:
Safari
siltenly
silently
overwritesvarioususernameorpasswordfields
Description:
IamusingSafarionMac,andhaveitsetituptoremembermyusername/passwordfortheloginscreen.Nowinvariousother(non-login)pagesinJenkins,thereisausernameorpasswordfield,andSafarioverwritesthosefieldswithmystoreduserinfooneachpageload,eveniftheyalreadycontainothervalues.The
onlyindicationisthatthe
fieldsareshownwithayellowbackground.Thishappensforexample:-IntheproxyconfigurationofPluginManager-Advanced-WhenaddingorEDITING(!)acredential-WhenaddingacredentialofkindCertificate:the{{filename}}fieldisfilledwithmyusername,butthepasswordfieldisnottouched.-WhengoingtoManageCredentialspage,IhaveaSSHusernamewithprivatekeyandaUsernamewithpasswordcredential,anditreplacesthe{{username}}ofthefirst,andthe{{password}}fieldofthesecondentryItdoesNOThappeninsomeotherplaces,forexampletheJiraSetup.
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] [core] (JENKINS-22490) weather icon also for test failures, not only build failures
Marc Günther created JENKINS-22490 weather icon also for test failures, not only build failures Issue Type: Bug Assignee: Unassigned Components: core Created: 03/Apr/14 6:13 PM Description: The current weather status icon only takes failed (red) builds into account, but ignores instable (yellow) ones. We almost never have failing builds, but we have test failures, so the weather icon is very useless to us. It would still be nice to have though, if it would take instable builds into account. Project: Jenkins Priority: Trivial Reporter: Marc Günther 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] [core] (JENKINS-17288) Packaging of spring-context-support causes crowd plugin to prevent Jenkins starting properly
Marc Günther commented on JENKINS-17288 Packaging of spring-context-support causes crowd plugin to prevent Jenkins starting properly We use the standalone jar with embedded winstone, and it works when we delete the spring-context-support-2.5.6.SEC03.jar from the jenkins.war. 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] [crowd2] (JENKINS-13547) Jenkins runs extremely slow with remote crowd server
Marc Günther commented on JENKINS-13547 Jenkins runs extremely slow with remote crowd server Has this really been fixed or is this simply JENKINS-16703 ??? 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] [core] (JENKINS-22338) Safari siltenly overwrites various username or password fields
Marc Günther created JENKINS-22338 Safari siltenly overwrites various username or password fields Issue Type: Bug Assignee: stephenconnolly Components: core, credentials Created: 25/Mar/14 1:51 PM Description: I am using Safari on Mac, and have it set it up to remember my username/password for the login screen. Now in various other (non-login) pages in Jenkins, there is a username or password field, and Safari overwrites those fields with my stored user info on each page load, even if they already contain other values. The fields are shown with a yellow background. This happens for example: In the proxy configuration of Plugin Manager - Advanced When adding or EDITING a credential When adding a credential of kind Certificate: the filename field is filled with my username, but the password field is not touched. When going to Manage Credentials page, I have a "SSH username with private key" and a "Username with password" credential, and it replaces the username of the first, and the password field of the second entry It does NOT happen in some other places, for example the Jira Setup. Environment: Safari 6.1.1, MacOSX 10.8.5 Project: Jenkins Priority: Trivial Reporter: Marc Günther 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] [core] (JENKINS-22340) Cannot configure colums of 'All' view
Marc Günther created JENKINS-22340 Cannot configure colums of All view Issue Type: Bug Assignee: Unassigned Components: core Created: 25/Mar/14 3:56 PM Description: The 'All' view in Jenkins has no 'Edit View' menu, so you cannot edit it's columns, making it rather useless (unless you happen to like the default columns) Project: Jenkins Priority: Trivial Reporter: Marc Günther 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] [core] (JENKINS-17288) Packaging of spring-context-support causes crowd plugin to prevent Jenkins starting properly
Marc Günther commented on JENKINS-17288 Packaging of spring-context-support causes crowd plugin to prevent Jenkins starting properly And Crowd2-Plugin has severe perfomance issues (we tried it), so it's not an option either: JENKINS-16703 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] [disk-usage] (JENKINS-22345) disk-usage-plugin causes jobs to hang at the end for 5min
Marc Günther created JENKINS-22345 disk-usage-plugin causes jobs to hang at the end for 5min Issue Type: Bug Assignee: Lucie Votypkova Components: disk-usage Created: 25/Mar/14 7:37 PM Description: We noticed the following strange behaviour on quite a lot of our jobs. After all build steps and post build steps finished, the build is in some quite inconsistent state for up to exactly 5min: the Console is still spinning with no output the big ball of the job is still blinking starting the job again results in "current job is already building" ALTHOUGH the build is shown as finished in the build history of the job it has disappeared from the slave it was running on I especially liked the build history, when you start a new build #128, it says, build #127 is still in progress, and right below you see a quite finished build #127 We double checked enabling and disabling the disk-usage-plugin, and it was clearly causing this issue. The 5min are probably some kind of timeout somewhere. Project: Jenkins Priority: Major Reporter: Marc Günther 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] [crowd2] (JENKINS-16703) Too many periodic requests to Crowd server
Marc Günther commented on JENKINS-16703 Too many periodic requests to Crowd server This renders the crowd2-plugin completely unusable. We had page load times of around 20sec, compared to ~1sec with the old crowd-plugin. We switched back to that one now. 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] [git-client] (JENKINS-21124) Use proxy to access git repository
Marc Günther commented on JENKINS-21124 Use proxy to access git repository Some context would be very helpful! What do the proxy settings in plugin manager have to do with cloning a git repository? Where in Jenkins is there a "validate Proxy" button? 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] [disk-usage] (JENKINS-22224) one job configuration change results in three Job Config History entries
Marc Günther
updated JENKINS-4
one job configuration change results in three Job Config History entries
Change By:
Marc Günther
(18/Mar/14 6:37 PM)
Description:
EverytimeImakeaconfigurationchangetoajob,IgetthreeentriesintheJobConfigHistoryview:#removaloftheconfigfor{{disk-usage}}plugin#actualchangeImade#additionoftheconfigof{{disk-usage}}againTheremovedandre-addedlinelookslikethis:{code}hudson.plugins.disk__usage.DiskUsagePropertyplugin=disk-usage@0.23/{code}Expected:1.and3.shouldnothappen..
EDIT:Ihavenowalsoseenacasewhere1.and2.arecombinedintoonechange,and3.isthesecondchange.
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] [nodejs] (JENKINS-22102) NodeJS plugin does not remember the saved NodeJS Installation
Marc Günther commented on JENKINS-22102 NodeJS plugin does not remember the saved NodeJS Installation BTW, the popup in the "Provide Node npm bin/ folder to PATH" works perfectly fine. 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] [build-pipeline] (JENKINS-16961) memory leak in Build Pipeline plugin (BuildForm)
Marc Günther commented on JENKINS-16961 memory leak in Build Pipeline plugin (BuildForm) Any progress on this? 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] [disk-usage] (JENKINS-22224) one job configuration change results in three Job Config History entries
Marc Günther created JENKINS-4 one job configuration change results in three Job Config History entries Issue Type: Bug Assignee: Lucie Votypkova Components: disk-usage, jobconfighistory Created: 17/Mar/14 1:42 PM Description: Every time I make a configuration change to a job, I get three entries in the Job Config History view: removal of the config for disk-usage plugin actual change I made add of the config of disk-usage again The removed and re-added line looks like this: hudson.plugins.disk__usage.DiskUsageProperty plugin="disk-usage@0.23"/ Expected: 1. and 3. should not happen.. Project: Jenkins Priority: Minor Reporter: Marc Günther 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] [disk-usage] (JENKINS-22224) one job configuration change results in three Job Config History entries
Marc Günther
updated JENKINS-4
one job configuration change results in three Job Config History entries
Change By:
Marc Günther
(17/Mar/14 2:17 PM)
Description:
EverytimeImakeaconfigurationchangetoajob,IgetthreeentriesintheJobConfigHistoryview:#removaloftheconfigfor{{disk-usage}}plugin#actualchangeImade#
add
addition
oftheconfigof{{disk-usage}}againTheremovedandre-addedlinelookslikethis:{code}hudson.plugins.disk__usage.DiskUsagePropertyplugin=disk-usage@0.23/{code}Expected:1.and3.shouldnothappen..
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] [git] (JENKINS-22064) Git Repository Browser URL not saved anymore
Marc Günther commented on JENKINS-22064 Git Repository Browser URL not saved anymore I guess you need to "Reload Configuration" after editing the file. I never use "Reload Configuration" myself, though, as it has been a constant source of problems in the past. Another workaround might be to switch back to "(Auto)", as long as you have at least one untouched project with the same repository left. Yet another solution would be a small Groovy script, which calculates the correct browser URL based on the repo URL. 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] [nodejs] (JENKINS-22102) NodeJS plugin does not remember the saved NodeJS Installation
Marc Günther created JENKINS-22102 NodeJS plugin does not remember the saved NodeJS Installation Issue Type: Bug Assignee: Unassigned Components: nodejs Created: 10/Mar/14 2:35 PM Description: In my job, I added an "Execute NodeJS script" build step. There I can choose between my three installed NodeJS Installation (as configured in the global Jenkins configuration). When I choose one installation from the popup, and save the job, it is saved fine, but as soon as I open the configuration page of the job again, the popup always shows the first NodeJS installation (and then if I save without changing anything, it will also save that wrong selection) Expected: The configured NodeJS installation should show in the popup, not the first one Project: Jenkins Priority: Minor Reporter: Marc Günther 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] [nodejs] (JENKINS-22103) NodeJS buildstep succeeds, although installation failed
Marc Günther created JENKINS-22103 NodeJS buildstep succeeds, although installation failed Issue Type: Bug Assignee: Unassigned Components: nodejs Created: 10/Mar/14 2:56 PM Description: I have configured a NodeJS 0.10.26 Installation in the global Jenkins configuration (as "install automatically from nodejs.org"), and added grunt to the "Global npm packages to install". I also have a very simple hello world job that uses that installation. Now, due to firewall restrictions, the Jenkins slave cannot connect to the internet, so the NodeJS installation first fails, but then seems to succeed anyway as it is somehow downloading it from the master (this part confuses me). Then it tries to install grunt, and that one also fails (for real this time). Anyway, the point of this bugreport is, that the NodeJS buildstep succeeds, and the job is green. If NodeJS installation could not succeed completely, I would expect it so fail ?!? Project: Jenkins Priority: Trivial Reporter: Marc Günther 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] [git] (JENKINS-22064) Git Repository Browser URL not saved anymore
Marc Günther commented on JENKINS-22064 Git Repository Browser URL not saved anymore I don't think it's a problem during the upgrade. Old projects still have the setting, and even show it in the Configure screen. It is only during a save that the setting vanishes. I also just tried to create a new Freestyle project, and there the same thing happens. This is with git-client-plugin 1.6.4 and git-plugin 2.0.4 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] [git] (JENKINS-22064) Git Repository Browser URL not saved anymore
Marc Günther commented on JENKINS-22064 Git Repository Browser URL not saved anymore yep, that are exactly the same steps I have done 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] [git] (JENKINS-22064) Git Repository Browser URL not saved anymore
Marc Günther created JENKINS-22064 Git Repository Browser URL not saved anymore Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 06/Mar/14 1:33 PM Description: The "Repository Browser" URL is not saved anymore. The value of the popup itself (githubweb, gitoriousweb, etc) is saved, though. We just upgraded Jenkins from 1.501 and git-plugin 1.1.26. Furthermore, with existing jobs that still have the URL, when you configure and save them without any change, the URL gets removed. Looking at the Job Config History, it shows that the refspec was removed (but that was empty), and also the url inside of the browser class="hudson.plugins.git.browser.GitoriousWeb" tag Project: Jenkins Priority: Minor Reporter: Marc Günther 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] [core] (JENKINS-21930) Jobs fail due to node went offline during the build
Marc Günther created JENKINS-21930 Jobs fail due to node went offline during the build Issue Type: Bug Assignee: Unassigned Components: core Created: 24/Feb/14 8:47 AM Description: I keep getting failures on random jobs (see example below), when I take a slave offline. I thought the purpose of "take slave offline" (versus disconnecting a slave) is that running jobs can continue to run, but no new jobs are started, and I can then disconnect the slave when all jobs are finished (we have a small script which does exactly that, to take a slave out of the cluster). With the current behaviour, it is impossible to cleanly shutdown a slave. Expected: Taking a slave offline should NEVER have any impact on any of the jobs running on that slave. They should not even be aware of the fact. Looks like the node went offline during the build. Check the slave log for the details.FATAL: /var/lib/jenkins/logs/slaves/null/slave.log (No such file or directory) java.io.FileNotFoundException: /var/lib/jenkins/logs/slaves/null/slave.log (No such file or directory) at java.io.RandomAccessFile.open(Native Method) at java.io.RandomAccessFile.init(RandomAccessFile.java:212) at org.kohsuke.stapler.framework.io.LargeText$FileSession.init(LargeText.java:397) at org.kohsuke.stapler.framework.io.LargeText$2.open(LargeText.java:120) at org.kohsuke.stapler.framework.io.LargeText.writeLogTo(LargeText.java:210) at hudson.console.AnnotatedLargeText.writeHtmlTo(AnnotatedLargeText.java:159) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:605) at hudson.model.Run.execute(Run.java:1568) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Project: Jenkins Priority: Major Reporter: Marc Günther 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] [core] (JENKINS-19074) Why More than 1 builds are needed for the trend report?
Marc Günther commented on JENKINS-19074 Why More than 1 builds are needed for the trend report? This is in Core. It is simply the "(trend)" link, which appears in the upper right of the "Build History" section of every job. 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] [core] (JENKINS-17288) Packaging of spring-context-support causes crowd plugin to prevent Jenkins starting properly
Marc Günther commented on JENKINS-17288 Packaging of spring-context-support causes crowd plugin to prevent Jenkins starting properly Still not fixed in Jenkins LTS 1.532.2 and Crowd Plugin 1.2 This essentially means that we cannot even upgrade to LTS. We are on 1.501 currently... 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] [nested-view] (JENKINS-18128) Filtering build queue/executors does not work in nested view
Marc Günther updated JENKINS-18128 Filtering build queue/executors does not work in nested view Change By: Marc Günther (11/Nov/13 11:26 AM) Description: ThecheckboxesFilterbuildqueueandFilterbuildexecutorsdonotreallymakesenseatthemomentina nexted nested view.Asanestedviewcontainsnojobsatall,thecheckboxessimplycompletelyremovethebuildqueue/executorlist.Suggestions:-RemovethecheckboxesfromtheEditViewpagefornestedviews-Ormakethemworkbyrecursivelylookingforthejobsinsidethenestedview 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] [git] (JENKINS-19063) Failed to instantiate class BuildChooser from stapler-class:hudson.tasks.Maven
Marc Günther
created JENKINS-19063
Failed to instantiate class BuildChooser from stapler-class:hudson.tasks.Maven
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
git
Created:
05/Aug/13 1:09 PM
Description:
Sometimes (about once out of 10 times), when I do this:
click Configure of a job,
change something (not GitSCM related),
click on Save,
I get the exception below.
The workaround is to simply click Configure again, make the same change again and Save, and then it succeeds.
Status Code: 500
Exception:
Stacktrace:
java.lang.RuntimeException: Failed to instantiate class hudson.plugins.git.GitSCM from {"":["hudson.plugins.git.util.DefaultBuildChooser","6"],"authorOrCommitter":false,"branches":{"name":"master"},"browser":{"stapler-class":"hudson.plugins.git.browser.GitoriousWeb","url":"http://git.host.domain/my-project/my-repo/"},"buildChooser":{"stapler-class":"hudson.tasks.Maven"},"clean":false,"disableSubmodules":false,"excludedRegions":"","excludedUsers":"","gitConfigEmail":"","gitConfigName":"","gitTool":"Default","ignoreNotifyCommit":false,"includedRegions":"","localBranch":"master","pruneBranches":true,"recursiveSubmodules":true,"reference":"/home/jenkins/reference_repositories/my-project/my-repo","relativeTargetDir":"","remotePoll":true,"scmName":"","skipTag":false,"useShallowClone":false,"userRemoteConfigs":{"name":"origin","refspec":"+refs/heads/*:refs/remotes/origin/*","url":"g...@git.host.domain:my-project/my-repo.git"},"value":"2","wipeOutWorkspace":false}
at hudson.model.Descriptor.newInstance(Descriptor.java:602)
at hudson.plugins.git.GitSCM$DescriptorImpl.newInstance(GitSCM.java:1484)
at hudson.plugins.git.GitSCM$DescriptorImpl.newInstance(GitSCM.java:1405)
at hudson.scm.SCMS.parseSCM(SCMS.java:63)
at hudson.model.AbstractProject.submit(AbstractProject.java:1878)
at hudson.model.Project.submit(Project.java:195)
at hudson.model.Job.doConfigSubmit(Job.java:1045)
at hudson.model.AbstractProject.doConfigSubmit(AbstractProject.java:729)
at sun.reflect.GeneratedMethodAccessor1439.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151)
at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487)
[JIRA] [core] (JENKINS-18893) Show stderr output in red color in Console
Marc Günther created JENKINS-18893 Show stderr output in red color in Console Issue Type: New Feature Assignee: Unassigned Components: core Created: 23/Jul/13 7:03 PM Description: The output of a job should be displayed differently in the Job's Console, depending whether it came through stdout or stderr. Given that stderr seems more likely to indicate some error messages, I would suggest to mark all stderr text as red, and leave the stdout text black. Project: Jenkins Priority: Minor Reporter: Marc Günther 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] [core] (JENKINS-18869) list-view with lots of tabs renders a very wide job table
Marc Günther created JENKINS-18869 list-view with lots of tabs renders a very wide job table Issue Type: Bug Assignee: Unassigned Components: core Created: 22/Jul/13 2:16 PM Description: If you have a list view with lots of tabs (so you have to scroll horizontally), the table with the jobs becomes as wide as the tabs. This leaves very much space between the columns, and makes the table very much unusable. Expected: make the table es wide as necessary to display it's contents, and not wider. Project: Jenkins Priority: Trivial Reporter: Marc Günther 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] [timestamper] (JENKINS-16778) Timestamper makes the build fail if the slave if put offline during the build.
Marc Günther commented on JENKINS-16778 Timestamper makes the build fail if the slave if put offline during the build. Thanks Steven. I just tested thsis, and it works now. I still get a "Looks like the slave went offline..." message in the Console, but no more exception and it doesn't fail the build. 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.
