[JIRA] (JENKINS-1877) Explanatory message at prepare for shutdown
Title: Message Title Steffen Breitbach edited a comment on JENKINS-1877 Re: Explanatory message at prepare for shutdown Seconded.The worst part of the message is the "shutdown" part. I also got calls from users "why the Jenkins is shutting down" when this absolutely wasn't true...To me the best solution would be a default message (maybe the shutdown one) being displayed as long as not specified otherwise and the ability to override this somehow. Maybe the menu item shouldn't even read "Prepare for shutdown" but "Cease all operation" instead? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-1877) Explanatory message at prepare for shutdown
Title: Message Title Steffen Breitbach commented on JENKINS-1877 Re: Explanatory message at prepare for shutdown Seconded. The worst part of the message is the "shutdown" part. I also got calls from users "why the Jenkins is shutting down" when this absolutely wasn't true... To me the best solution would be a default message (maybe the shutdown one) being displayed as long as not specified otherwise and the ability to override this somehow. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-1877) Explanatory message at prepare for shutdown
Title: Message Title Steffen Breitbach reopened an issue Well, this is not a "Bug", it's an "Improvement". The lenient shutdown plugin has other caveats and I still feel this should find its way into Jenkins sooner or later, so I'm reopening this. Jenkins / JENKINS-1877 Explanatory message at prepare for shutdown Change By: Steffen Breitbach Resolution: Done Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-30458) [Maven settings] "Replace All" does not work
Title: Message Title Steffen Breitbach commented on JENKINS-30458 Re: [Maven settings] "Replace All" does not work Well, that seems to be what I meant by saying: Either the mechanism is broken or the help text is wrong. So. This particular setting will not replace "even ones not found in the provided list of credentials" but rather remove all server credentials and then replace those stated explicitly. The help text in the corresponding help-isReplaceAll.html should be replaced, maybe to something like: Replace all servers in the Maven settings.xml file. If a server is not in the provided list of credentials, this servers credentials will be empty. Cheers Steffen Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33975) On demand slave shows misleading offline cause message
Title: Message Title Steffen Breitbach created an issue Jenkins / JENKINS-33975 On demand slave shows misleading offline cause message Issue Type: Bug Assignee: Unassigned Components: core, slave-utilization Created: 2016/Apr/01 10:23 AM Environment: Jenkins 1.642.2 inside Tomcat 7, master and slaves on Debian (7), manual install Priority: Minor Reporter: Steffen Breitbach We have configured our slaves to "Take this slave on-line when in demand and off-line when idle". When a slave goes offline, the slave page ($Jenkins_URL/computer/$slavename/) reports "Ping response time is too long or timed out." This is misleading. Instead, something like "This slave is offline because of the idle timeout." (or maybe nothing at all) should be displayed.
[JIRA] [stashnotifier-plugin] (JENKINS-32817) stashnotifier-plugin credentials are broken
Title: Message Title Steffen Breitbach commented on JENKINS-32817 Re: stashnotifier-plugin credentials are broken Just a quick note: this affects the global _configuration. The _per job configuration still works. 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] [maven-plugin] (JENKINS-26048) Jenkins no longer cleaning up child processes when build stopped - as of 1.587
Title: Message Title Steffen Breitbach commented on JENKINS-26048 Re: Jenkins no longer cleaning up child processes when build stopped - as of 1.587 After a bit of investigation, we found out that all of the processes that stay after a job has been terminated "abnormally" will have INIT as their parent process. So if you kill the process(tree) that starts with a java process which has INIT as parent, you should be safe (and in my opinion safer as grepping for strings). You could for example create a cronjob for this task. 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] [config-file-provider-plugin] (JENKINS-30458) [Maven settings] "Replace All" does not work
Title: Message Title Steffen Breitbach commented on JENKINS-30458 Re: [Maven settings] "Replace All" does not work It seems that 2.10.0 is affected as well. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29902) Unexpected executor death - java.lang.IllegalStateException: already existed
Title: Message Title Steffen Breitbach edited a comment on JENKINS-29902 Re: Unexpected executor death - java.lang.IllegalStateException: already existed This could be true. We have a job that reloads the configuration (scripted) but also triggers a downstream job. The downstream job ended in a dead executor the last time it ran Would using a quiet period help? Are the build numbers determined/created _before_ or _after_ the quiet period? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29902) Unexpected executor death - java.lang.IllegalStateException: already existed
Title: Message Title Steffen Breitbach commented on JENKINS-29902 Re: Unexpected executor death - java.lang.IllegalStateException: already existed This could be true. We have a job that reloads the configuration (scripted) but also triggers a downstream job. The downstream job ended in a dead executor the last time it ran Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27595) Empty plugin list hides update information
Title: Message Title Steffen Breitbach commented on JENKINS-27595 Re: Empty plugin list hides update information Still an issue in both 1.609.3 LTS and 1.632 As a workaround, the button in "Available" can be used. 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] [maven-plugin] (JENKINS-22252) Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap
Title: Message Title Steffen Breitbach commented on JENKINS-22252 Re: Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap I can confirm that it works again for us in 2.12.1 Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-1877) Explanatory message at prepare for shutdown
Title: Message Title Steffen Breitbach commented on JENKINS-1877 Re: Explanatory message at prepare for shutdown Thanks Kumar Mani, nice find! 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] [config-file-provider-plugin] (JENKINS-30458) [Maven settings] "Replace All" does not work
Title: Message Title Steffen Breitbach created an issue Jenkins / JENKINS-30458 [Maven settings] "Replace All" does not work Issue Type: Bug Assignee: Dominik Bartholdi Components: config-file-provider-plugin Created: 15/Sep/15 8:45 AM Environment: Jenkins 1.609.3 LTS Config File Provider Plugin 2.9.3 Maven 3.0.5 Priority: Major Reporter: Steffen Breitbach The help text to the "Replace All" checkbox says Replace all servers in the Maven settings.xml file, even ones not found in the provided list of credentials . In the Config File Provider Plugin version 2.9.3 this does not seem to work. Artifacts can not be resolved from a server if its credentials have not been specified explicitly trough a credential setting. After adding a credential for each server id everything works as expected. Either the mechanism is broken or the help text is wrong.
[JIRA] [core] (JENKINS-30399) [LTS] Update link to LTS war and changelog wrong
Title: Message Title Steffen Breitbach created an issue Jenkins / JENKINS-30399 [LTS] Update link to LTS war and changelog wrong Issue Type: Bug Assignee: Unassigned Components: core Created: 11/Sep/15 8:29 AM Labels: lts Priority: Minor Reporter: Steffen Breitbach When there's a new LTS version to download, an info will be displayed on the $jenkins_url/manage page: New version of Jenkins (1.609.3) is available for download (changelog). In the case of this example (1.609.3), download is a link that points to http://updates.jenkins-ci.org/download/war/1.609.3/jenkins.war while changelog points to http://jenkins-ci.org/changelog.html Expected behaviour The changelog should point to the LTS changelog instead of the regular changelog (http://jenkins-ci.org/changelog-stable)
[JIRA] [core] (JENKINS-29268) Unexpected executor death
Title: Message Title Steffen Breitbach commented on JENKINS-29268 Re: Unexpected executor death We encounter this issue on freestyle builds that are triggered by a cron _expression_ and an upstream job. When those triggers both happen close to each other it seams to "kill" the executor due to the IllegalStateException 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] [maven-plugin] (JENKINS-30249) Jenkins 1.580.1 with jdk 5 build fails
Title: Message Title Steffen Breitbach commented on JENKINS-30249 Re: Jenkins 1.580.1 with jdk 5 build fails Have you tried Maven Project Plugin 2.11? 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] [maven-plugin] (JENKINS-22252) Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap
Title: Message Title Steffen Breitbach commented on JENKINS-22252 Re: Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap Same here. Downgrade of the Maven Integration plugin from 2.12 to 2.10 fixed the problem. 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] [maven-plugin] (JENKINS-25272) remoting-2.46.jar breaks JDK 5 Maven builds
Title: Message Title Steffen Breitbach commented on JENKINS-25272 Re: remoting-2.46.jar breaks JDK 5 Maven builds Will that PR be merged into the LTS branch very soon? Pretty please? 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-node-stalker-plugin] (JENKINS-29774) [NODE STALKER] The job $jobname has no traceable runs!
Title: Message Title Steffen Breitbach created an issue Jenkins / JENKINS-29774 [NODE STALKER] The job $jobname has no traceable runs! Issue Type: Bug Assignee: Unassigned Components: job-node-stalker-plugin Created: 04/Aug/15 9:17 AM Environment: Jenkins 1.609.1 LTS Node Stalker Plugin 1.0.3 Priority: Minor Reporter: Steffen Breitbach Node Stalker does not seem to be able to determine the last slave a job ran on: [NODE STALKER] The job $jobname has no traceable runs! There is no evidence of the error in Jenkins' log file. Add Comment
[JIRA] [artifactory-plugin] (JENKINS-27949) off switch for Bintray feature
Steffen Breitbach created JENKINS-27949 off switch for Bintray feature Issue Type: Improvement Assignee: yossis Components: artifactory-plugin Created: 15/Apr/15 8:19 AM Description: Please add a checkbox that allows the administrator to disable the Bintray feature globally. Project: Jenkins Priority: Minor Reporter: Steffen Breitbach 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] [chucknorris-plugin] (JENKINS-25084) Chuck is no longer since Jenkins update
Steffen Breitbach assigned JENKINS-25084 to Steffen Breitbach Chuck is no longer since Jenkins update Change By: Steffen Breitbach (06/Mar/15 12:48 PM) Assignee: SteffenBreitbach 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] [chucknorris-plugin] (JENKINS-25084) Chuck is no longer since Jenkins update
Steffen Breitbach assigned JENKINS-25084 to Unassigned Chuck is no longer since Jenkins update Change By: Steffen Breitbach (06/Mar/15 12:53 PM) Assignee: SteffenBreitbach 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] [jobconfighistory-plugin] (JENKINS-18900) [JobConfigurationHistory] Wrong history being displayed
Steffen Breitbach resolved JENKINS-18900 as Wont Fix [JobConfigurationHistory] Wrong history being displayed Change By: Steffen Breitbach (06/Feb/15 8:53 AM) Status: Open Resolved Resolution: WontFix 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] [cluster-stats-plugin] (JENKINS-25861) ClusterStats plugin page title shows Disk Usage
Steffen Breitbach created JENKINS-25861 ClusterStats plugin page title shows Disk Usage Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: cluster-stats-plugin Created: 02/Dec/14 8:42 AM Description: When Jenkins is installed behind a reverse proxy, the hostname/port it uses internally may be different than what users see. The plugin should generate URLs relative to the 'Jenkins URL' set in the configuration page, rather than something detected internally. For example, given http://build.example.com/jenkins, other plugins correctly show their urls as build.example.com/jenkins/plugin/... but the cluster stats plugin shows it at jenkins:8080/jenkins/plugin/..., which is the cluster-internal-only name/URL. Project: Jenkins Priority: Major Reporter: Steffen Breitbach 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] [cluster-stats-plugin] (JENKINS-25861) ClusterStats plugin page title shows Disk Usage
Steffen Breitbach
updated JENKINS-25861
ClusterStats plugin page title shows Disk Usage
Change By:
Steffen Breitbach
(02/Dec/14 8:46 AM)
Issue Type:
Bug
Improvement
Description:
WhenJenkinsisinstalledbehindareverseproxy,thehostname/portit
TheClusterStatsPlugin
uses
internallymaybedifferentthanwhatuserssee
DiskUsageasitstitle
.
ThepluginshouldgenerateURLsrelativetothe
{code}titleDiskUsage[
Jenkins
URLsetintheconfigurationpage,ratherthansomethingdetectedinternally.
]/title{code}
Forexample,givenhttp
TherehasbeenapullrequestinGitHubsinceJune2013thatwouldfixthisissue
:
https:
//
build
github
.
example.
com/
jenkins,otherpluginscorrectlyshowtheirurlsasbuild.example.com
jenkinsci
/
jenkins/plugin/...butthe
cluster
-
stats
pluginshowsitatjenkins:8080
/
jenkins
pull
/
plugin/...
1Also
,
which
Ifinditabitirritatingthattheplugin
is
calledClusterStatsPluginwhile
the
cluster-internal-onlyname/URL
headeronthepageisJenkinsClusterStatistics
.
MaybethatcouldbechangedtoClusterStatsaswell.
Priority:
Major
Minor
Labels:
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-23333) Label display wrong when using operators in expression
Steffen Breitbach commented on JENKINS-2 Label display wrong when using operators in _expression_ I'm super busy at the moment. I managed to install it but didn't have the time yet to restart Jenkins and have a closer look. Sorry. I'll look at this as soon as possible. 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-23333) Label display wrong when using operators in expression
Steffen Breitbach commented on JENKINS-2 Label display wrong when using operators in _expression_ Great job guys, looks really nice! Thanks a lot so far. Quick question: will the plug in be compatible to the latest LTS version? 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-23333) Label display wrong when using operators in expression
Steffen Breitbach created JENKINS-2 Label display wrong when using operators in _expression_ Issue Type: Bug Assignee: Unassigned Components: core Created: 05/Jun/14 1:13 PM Description: Behaviour: go to job configuration enable "Restrict where this project can be run" enter _expression_ with operator, e.g. "label1label2" go to slave that is configured to run label1 and label2 klick on label1 (link next to "Labels:") URL $your_jenkins/label/label1/? will open Project using "label1label2" won't be displayed, only projects that use "label1" and nothing else will be displayed Workaround: enter $your_jenkins/label/label1label2/ as URL Expected behaviour: Klicking on a label (i.e. navigating to $your_jenkins/label/label1/?) should display all jobs that actually make use of this label regardless of using it alone or in combination with other labels (via an operator). Environment: Jenkins ver. 1.532.2 LTS Project: Jenkins Priority: Major Reporter: Steffen Breitbach 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-19134) Disallow Users to set a custom workspace
Steffen Breitbach commented on JENKINS-19134 Disallow Users to set a custom workspace My goal would be to provide a "child-proof UI" as you put it I reckon that the Template plugin would work with the CloudBees Jenkins only? 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-19134) Disallow Users to set a custom workspace
Steffen Breitbach commented on JENKINS-19134 Disallow Users to set a custom workspace I agree with you in terms of "users can do what they want anyway", so let's give the issue an other name: I'd like to have a choice about what to show to users in terms of configuration and what not. For example, I'd like to hide "Build when job nodes start" from non-admin users or allow usage of certain plugins for certain user groups only and so on... But still, I agree that this is something worth discussing and not a "hard" request. 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] [subversion] (JENKINS-19133) [SVN] Credentials shouldn't be changed by users
Steffen Breitbach commented on JENKINS-19133 [SVN] Credentials shouldnt be changed by users Very nice, 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/groups/opt_out.
[JIRA] [jobconfighistory] (JENKINS-18900) [JobConfigurationHistory] Wrong history being displayed
Steffen Breitbach assigned JENKINS-18900 to Steffen Breitbach [JobConfigurationHistory] Wrong history being displayed Change By: Steffen Breitbach (10/Feb/14 12:28 PM) Assignee: StefanBrausch SteffenBreitbach 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] [jobconfighistory] (JENKINS-18900) [JobConfigurationHistory] Wrong history being displayed
Steffen Breitbach commented on JENKINS-18900 [JobConfigurationHistory] Wrong history being displayed Hi Stefan, no problem. I've opened this issue when we were running 1.509.2 LTS and Job Configuration History 2.4 We're running 1.532.1 and Job Configuration History 2.5 and I can't reproduce the issue any more. As far as I am concerned the issue may be closed. Regards Steffen 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] [mailer] (JENKINS-20954) Cannot save email recipients
Steffen Breitbach commented on JENKINS-20954 Cannot save email recipients +1 Breaks in version 1.6 and 1.509.4 LTS Rollback to 1.5 fixed the issue for 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/groups/opt_out.
[JIRA] [core] (JENKINS-16012) Allow users to be able to specify a reason why Jenkins is in shutdown
Steffen Breitbach resolved JENKINS-16012 as Duplicate Allow users to be able to specify a reason why Jenkins is in shutdown I think this is a duplicate of JENKINS-1877. Let's all vote there Change By: Steffen Breitbach (13/Dec/13 2:19 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15269) Jenkins is preparing for shutdown - add a comment
Steffen Breitbach resolved JENKINS-15269 as Duplicate Jenkins is preparing for shutdown - add a comment I think this is a duplicate of JENKINS-1877. Let's all vote there Change By: Steffen Breitbach (13/Dec/13 2:20 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gui] (JENKINS-1877) Explanatory message at prepare for shutdown
Steffen Breitbach commented on JENKINS-1877 Explanatory message at prepare for shutdown I somewhat disagree. In my opinion, the shutdown message is semantically incorrect. It says "Jenkins is going to shut down." when really just the flag that prevents new jobs from being executed is set. If you un-set the flag, nothing will happen in terms of shutdown. Maybe you don't see any benefit in a shutdown message. If we don't get the ability to set one at least the message should be set. I use the shutdown flag from time to time just to prevent Jenkins from doing anything while working on other tools (e.g. Sonar). 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] [gui] (JENKINS-1877) Explanatory message at prepare for shutdown
Steffen Breitbach commented on JENKINS-1877 Explanatory message at prepare for shutdown Okay, so tell me just one of those MILLION better ways: how to stop the build queue AND let users know what's happening? 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] [gui] (JENKINS-1877) Explanatory message at prepare for shutdown
Steffen Breitbach commented on JENKINS-1877 Explanatory message at prepare for shutdown How exactly do I stop all Jobs on Jenkins with EmailExt 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/groups/opt_out.
[JIRA] [gui] (JENKINS-1877) Explanatory message at prepare for shutdown
Steffen Breitbach commented on JENKINS-1877 Explanatory message at prepare for shutdown I just realised that we do exactly have the "Explanatory message at (prepare for) shutdown" functionality already. You can enter a comment when taking offline a slave. So why not have the same functionality when taking the master offline?! 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-19142) Don't add jobs to a view
Steffen Breitbach commented on JENKINS-19142 Dont add jobs to a view In ListView, regular _expression_ and manual selection can be used together. So I think it is difficult to determine whether to add automatically. That's exactly the reason why I wanted to have the "don't add job to view on creation"-Flag (on each view). To explain my particulat need for this: I administrate our Jenkins installation. Our Jenkins does have 16 main views with 4 nested views each (so 64 in total) in order to structure our roughly 1200 jobs. We have round about 100-150 Users that use Jenkins. The problem is that they tend to create their jobs "anywhere" and not in the particular view the are supposed to. So I don't want to have that job being displayed in the view they created it in (we manage this by regular expressions). 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-19142) Don't add jobs to a view
Steffen Breitbach commented on JENKINS-19142 Dont add jobs to a view Hi Yoichi, looks good from a first glance, thanks For my clarification: what is "root" in this context? Is it the "Default view" as configured in the Jenkins main configuration? Regards Steffen 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] [fingerprint] (JENKINS-18615) Fingerprints being created always
Steffen Breitbach commented on JENKINS-18615 Fingerprints being created always Most of our jobs are Maven jobs. What's the link between Maven jobs and fingerprints? 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] [jobconfighistory] (JENKINS-18920) [JobConfigurationHistory] Keep history only for
Steffen Breitbach created JENKINS-18920 [JobConfigurationHistory] Keep history only for Issue Type: New Feature Affects Versions: current Assignee: Mirko Friedenhagen Components: jobconfighistory Created: 25/Jul/13 7:00 AM Description: As of today, the maximum number of history entries can be limited by numbers or "days to keep". It would be nice if there was an option to keep only the configurations that jobs exist for (plus maybe one older configuration). If there are builds being discarded in Jenkins because of "max # of builds to keep", the job configurations should be discarded as well. Environment: Jenkins 1.509.2 LTS Job Configuration History 2.4 Tomcat 6.0.36 Java 1.7.0 u25-b15 Project: Jenkins Labels: plugin plugins Priority: Major Reporter: Steffen Breitbach 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] [jobconfighistory] (JENKINS-18920) [JobConfigurationHistory] Keep history only for existing builds
Steffen Breitbach updated JENKINS-18920 [JobConfigurationHistory] Keep history only for existing builds Change By: Steffen Breitbach (25/Jul/13 7:17 AM) Summary: [JobConfigurationHistory]Keephistoryonlyfor existingbuilds 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] [jobconfighistory] (JENKINS-18900) [JobConfigurationHistory] Wrong history being displayed
Steffen Breitbach created JENKINS-18900 [JobConfigurationHistory] Wrong history being displayed Issue Type: Bug Affects Versions: current Assignee: Mirko Friedenhagen Attachments: Job Configuration History Jenkins.png Components: jobconfighistory Created: 24/Jul/13 7:23 AM Description: When clicking on "Job Config History" from within a job, it seems that all (global) recent job changes are being displayed rather than the job changes of the job itself. On the other hand, the actual configuration changes of the job itself are missing (see the screenshot). Clicking on the "View as XML" link however will display the correct xml that belongs to the job as it seems. config-history directory listing drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-04-27_11-42-23 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-04-27_11-54-08 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-04-27_11-54-12 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-04-27_12-50-06 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-04-27_13-02-23 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-04-27_13-02-24 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-04-27_13-21-05 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-04-27_14-26-12 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-04-27_14-28-01 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-04-27_14-42-55 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-05-16_09-40-55 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-06-06_09-16-45 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-06-19_15-09-11 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-06-19_15-09-14 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-06-19_15-10-19 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-06-28_09-24-09 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-02_11-52-25 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-02_11-57-28 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-06_12-05-38 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-06_12-06-40 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-06_12-11-04 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-06_12-26-12 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-06_14-47-51 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-06_14-57-27 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-06_15-09-25 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-06_15-16-25 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-07_01-02-23 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-10_17-32-07 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-10_17-32-09 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-15_16-18-29 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-15_16-19-11 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-16_08-09-36 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-16_08-09-37 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-27_17-22-28 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-09-12_13-58-03 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-09-24_16-51-05 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-09-24_16-52-07 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-09-24_16-52-08 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-11-22_10-32-46 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-11-22_10-32-47 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-11-22_10-32-49 Environment: Jenkins 1.509.2 LTS Job Configuration History 2.4 Tomcat 6.0.36 Java 1.7.0 u25-b15 Project: Jenkins Labels: plugin plugins job Priority: Major Reporter: Steffen Breitbach
[JIRA] [slave-status] (JENKINS-18877) [Slaves] Node Monitoring frequently fails
Steffen Breitbach created JENKINS-18877 [Slaves] Node Monitoring frequently fails Issue Type: Bug Assignee: Unassigned Attachments: exceptions.txt Components: slave-status Created: 23/Jul/13 6:40 AM Description: Monitoring the slaves will frequently fail with java.lang.InterruptedException. Environment: Jenkins 1.509.2 LTS Tomcat 6.0.36 Java 1.7.0_25-b15 Project: Jenkins Labels: exception slave Priority: Major Reporter: Steffen Breitbach 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] [ldap] (JENKINS-17281) Please add a config option for groupSearchFilter
Steffen Breitbach commented on JENKINS-17281 Please add a config option for groupSearchFilter +1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16272) LTS 1.480.2 breaks launching slaves via jnlp
Steffen Breitbach commented on JENKINS-16272 LTS 1.480.2 breaks launching slaves via jnlp This is why I've posted a link and set this issue to resolved aready. 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
[JIRA] (JENKINS-16272) LTS 1.480.2 breaks launching slaves via jnlp
Steffen Breitbach reopened JENKINS-16272 LTS 1.480.2 breaks launching slaves via jnlp Change By: Steffen Breitbach (09/Jan/13 4:58 PM) Resolution: Fixed Status: Resolved Reopened 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
[JIRA] (JENKINS-16272) LTS 1.480.2 breaks launching slaves via jnlp
Steffen Breitbach resolved JENKINS-16272 as Not A Defect LTS 1.480.2 breaks launching slaves via jnlp Change By: Steffen Breitbach (09/Jan/13 4:58 PM) Status: Reopened Resolved Resolution: NotADefect 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
[JIRA] (JENKINS-16272) LTS 1.480.2 breaks launching slaves via jnlp
Steffen Breitbach closed JENKINS-16272 as Not A Defect LTS 1.480.2 breaks launching slaves via jnlp Change By: Steffen Breitbach (09/Jan/13 4:58 PM) Status: Resolved Closed 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
[JIRA] (JENKINS-16272) LTS 1.480.2 breaks launching slaves via jnlp
Steffen Breitbach resolved JENKINS-16272 as Fixed LTS 1.480.2 breaks launching slaves via jnlp Kohsuke provided a fix in https://groups.google.com/forum/?fromgroups=#!topic/jenkinsci-users/YbxqaMWMNs0 resp. https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-01-04 Change By: Steffen Breitbach (08/Jan/13 8:21 AM) 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
[JIRA] (JENKINS-16272) LTS 1.480.2 breaks launching slaves via jnlp
Steffen Breitbach created JENKINS-16272 LTS 1.480.2 breaks launching slaves via jnlp Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: slave-prerequisites Created: 07/Jan/13 2:28 PM Description: Jenkins is running within a Tomcat 6.0.36 / Java 7u9 1.480.1 works as expected with 1.480.2, if trying to start a slave via JNLP, I get an error 403 from the server. http://$JENKINS/computer/$SLAVE/slave-agent.jnlp = HTTP request sent, awaiting response... 403 Forbidden 2013-01-07 15:17:43 ERROR 403: Forbidden. Environment: Linux/Tomcat Project: Jenkins Labels: jenkins slave Priority: Major Reporter: Steffen Breitbach 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
[JIRA] (JENKINS-16272) LTS 1.480.2 breaks launching slaves via jnlp
Steffen Breitbach commented on JENKINS-16272 LTS 1.480.2 breaks launching slaves via jnlp Maybe this is of importance: Coming from 1.480.1 I just exchanged the jenkins.war with 1.480.2 Anonymous read access is granted. 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
