[JIRA] [nested-view] (JENKINS-23283) nested view plugin get list of jobs in a sub view ?
Manoj Thakkar created JENKINS-23283 nested view plugin get list of jobs in a sub view ? Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: nested-view Created: 03/Jun/14 6:00 AM Description: i am trying to get list of jobs in a subview of a nested view. I could not get it programatically, hudson.instance.getView or hudson.instance.getViews does not help in this case, Please advise on how to get that information, if its not already there then please add the necessary changes Due Date: 03/Jun/14 12:00 AM Project: Jenkins Priority: Major Reporter: Manoj Thakkar 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-failure-analyzer] (JENKINS-23284) Get value of all parameters in the database
Manoj Thakkar created JENKINS-23284 Get value of all parameters in the database Issue Type: Improvement Assignee: Tomas Westling Components: build-failure-analyzer Created: 03/Jun/14 6:03 AM Description: Hi, I was looking at the mongodb for results stored from the build failure , it doe snot list the values of all the parameters specified in a given job, It will be really helpful and nice to store value of all parameters passed to a job. Due Date: 10/Jun/14 12:00 AM Project: Jenkins Priority: Major Reporter: Manoj Thakkar 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-20327) javax.servlet.ServletException: java.lang.IllegalStateException: Form too large 241320200000
Jason W
commented on JENKINS-20327
javax.servlet.ServletException: java.lang.IllegalStateException: Form too large 24132020
For all those that the -Dorg.eclipse.jetty.server.Request.maxFormContentSize=500 doesn't work, add it straight after the java command and before the -jar
Example: java -Dorg.eclipse.jetty.server.Request.maxFormContentSize=500 -jar ${JENKINS_HOME}/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] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
michael oullion commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 +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/d/optout.
[JIRA] [core] (JENKINS-23120) FATAL: hudson.remoting.RequestAbortedException on Windows Slaves
Mads Nielsen commented on JENKINS-23120 FATAL: hudson.remoting.RequestAbortedException on Windows Slaves We're experiencing a similar issue the stacktrace is different, but the symptoms are the same, aborted builds in the middle of job execution. Problems started after an upgrade from 1.556 to 1.564. I Think this could be a blocker. Console.out FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.IOException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:739) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:168) at com.sun.proxy.$Proxy45.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:951) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:745) at hudson.model.Build$BuildExecution.build(Build.java:198) at hudson.model.Build$BuildExecution.doRun(Build.java:159) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:518) at hudson.model.Run.execute(Run.java:1706) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:802) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.io.IOException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond at sun.nio.ch.SocketDispatcher.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(Unknown Source) at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source) at sun.nio.ch.IOUtil.read(Unknown Source) at sun.nio.ch.SocketChannelImpl.read(Unknown Source) at hudson.remoting.SocketChannelStream$1.read(SocketChannelStream.java:33) at sun.nio.ch.ChannelInputStream.read(Unknown Source) at sun.nio.ch.ChannelInputStream.read(Unknown Source) at sun.nio.ch.ChannelInputStream.read(Unknown Source) at java.io.InputStream.read(Unknown Source) at sun.nio.ch.ChannelInputStream.read(Unknown Source) at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:82) at java.io.ObjectInputStream$PeekInputStream.peek(Unknown Source) at java.io.ObjectInputStream$BlockDataInputStream.peek(Unknown Source) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.readObject(Unknown Source) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:70) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) 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:
[JIRA] [crowd2] (JENKINS-11912) SSO not working
Martin Alig commented on JENKINS-11912 SSO not working Thanks for your help. I was able to figure it out inspecting the logs on both sides. As Jenkins is running on an internal machine, I had to configure the trusted Proxies in Crowd correctly. 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] [violations] (JENKINS-3529) StyleCop support in Violations plugin can't deal with absolute paths.
Fernando Borrego Polo commented on JENKINS-3529 StyleCop support in Violations plugin cant deal with absolute paths. Hi, I know this issue is old but I think I'm having a similar if not the same issue. The source paths reported by the Violations plugin make the files not accessible from the Jenkins UI. They are relative to the root of the volume :S. So, if my .cs file is in C:\SourceCodeFolder\MySolution\MyProject\Namespace\SourceCode.cs, then the link in Jenkins is: http://jenkins_server/job/job_name/violations/file/SourceCodeFolder/MySolution/Namespace/SourceCode.cs/ This happens even after setting the faux project path to "C:\SourceCodeFolder\MySolution", and no matter what I try to set in the source code patterns. 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-23193) UI blocked frequently
Saulo Alvarado Mateos commented on JENKINS-23193 UI blocked frequently Hi, K.P. Sure, we assumed that was the cause and change it some time ago (in March, if my memory serves me). Currently we use the next configuration in our jenkins.xml config file: executable%BASE%\jre\bin\java/executable arguments-Xrs -XX:PermSize=100m -Xmx768m -Dhudson.slaves.WorkspaceList="_" -Djava.rmi.server.hostname=10.0.100.90 -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port= -Dcom.sun.management.jmxremote.local._only_=false -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -jar "%BASE%\jenkins.war" --httpPort=80 -Xloggc:D:\Jenkins\loggcjenkins.txt/arguments For four weeks we also add parameters for monitoring Jenkins with jconsole. Assuming that these parameters are correct, we have never seen that used memory exceeds 200 MB of occupation. And PermGem has never exceeded 66 MB of occupation. 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.
PTC integrity plugin: version 1.18, download from MKS only folders without any file
Hi, I have problem about PTC Integrity Plugin, it created in workspace only directories (make it clear: directory structure is correct) without any files. Hereafter console output: Preparing to execute si projectinfo for #/NisSoft#ClassicESigner/dev/src/Toolkit Preparing to execute si viewproject for #/NisSoft#ClassicESigner/dev/src/Toolkit Checkout directory is C:\cmo\jenkins\jobs\test_6.3\workspace A clean copy is requested; deleting contents of C:\cmo\jenkins\jobs\test_6.3\workspace Populating clean workspace... Successfully checked out 304 files! Saving current Integrity Project configuration... Writing build change log... Change log successfully generated: C:\cmo\jenkins\jobs\test_6.3\builds\2014-06-03_10-33-14\changelog.xml Finished: SUCCESS but there is still no any file in workspace and it's size in bytes 0. Seems to be a regression because working fine some weeks ago ! Partial extrat of LOG file: juin 03, 2014 10:33:24 AM [DEBUG] IntegritySCM - API open file handles: 1 juin 03, 2014 10:33:24 AM [DEBUG] IntegritySCM - Checkout on API thread: hudson.scm.APISession@38bd81 juin 03, 2014 10:33:24 AM org.apache.commons.httpclient.HttpMethodBase readResponseBody WARNING: Unsupported transfer encoding: juin 03, 2014 10:33:24 AM org.apache.commons.httpclient.HttpMethodBase readResponseBody INFO: Response content is not chunk-encoded juin 03, 2014 10:33:24 AM [DEBUG] IntegritySCM - API open file handles: 1 juin 03, 2014 10:33:24 AM [DEBUG] IntegritySCM - Checkout on API thread: hudson.scm.APISession@4f713d juin 03, 2014 10:33:24 AM org.apache.commons.httpclient.HttpMethodBase readResponseBody WARNING: Unsupported transfer encoding: juin 03, 2014 10:33:24 AM org.apache.commons.httpclient.HttpMethodBase readResponseBody INFO: Response content is not chunk-encoded juin 03, 2014 10:33:24 AM org.apache.commons.httpclient.HttpMethodBase readResponseBody WARNING: Unsupported transfer encoding: juin 03, 2014 10:33:24 AM org.apache.commons.httpclient.HttpMethodBase readResponseBody INFO: Response content is not chunk-encoded juin 03, 2014 10:33:26 AM [DEBUG] IntegritySCM - Checkout process: 304 of 304 juin 03, 2014 10:33:28 AM [DEBUG] IntegritySCM - Successfully disconnected connection jfba...@francium.gemalto.com:18000 juin 03, 2014 10:33:28 AM [DEBUG] IntegritySCM - Successfully disconnected connection jfba...@francium.gemalto.com:18000 juin 03, 2014 10:33:28 AM [DEBUG] IntegritySCM - Attempting to shut down database: C:\cmo\jenkins\jobs\test_6.3\builds\2014-06-03_10-33-14\IntegritySCM juin 03, 2014 10:33:28 AM [INFO] IntegritySCM - Failed to shutdown database connection! juin 03, 2014 10:33:28 AM [INFO] IntegritySCM - Database 'C:/cmo/jenkins/jobs/test_6.3/builds/2014-06-03_10-33-14/IntegritySCM' shutdown. juin 03, 2014 10:33:28 AM [INFO] IntegritySCM - java.sql.SQLNonTransientConnectionException: Database 'C:/cmo/jenkins/jobs/test_6.3/builds/2014-06-03_10-33-14/IntegritySCM' shutdown. juin 03, 2014 10:33:28 AM org.apache.commons.httpclient.HttpMethodBase readResponseBody WARNING: Unsupported transfer encoding: juin 03, 2014 10:33:28 AM org.apache.commons.httpclient.HttpMethodBase readResponseBody INFO: Response content is not chunk-encoded juin 03, 2014 10:33:28 AM [DEBUG] IntegritySCM - Successfully disconnected connection jfba...@francium.gemalto.com:18000 juin 03, 2014 10:33:28 AM [DEBUG] IntegritySCM - calcRevisionsFromBuild() invoked...! juin 03, 2014 10:33:28 AM [DEBUG] IntegritySCM - createChangeLogParser() invoked...! juin 03, 2014 10:33:29 AM hudson.model.Run execute INFO: test_6.3 #27 main build action completed: SUCCESS Jenkins version = 1.565 (running as a service) PTC plugin version = 1.18 Windows Seven 32 bits -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/PTC-integrity-plugin-version-1-18-download-from-MKS-only-folders-without-any-file-tp4705011.html Sent from the Jenkins issues mailing list archive at Nabble.com. -- 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-11912) SSO not working
Kanstantsin Shautsou resolved JENKINS-11912 as Not A Defect SSO not working Change By: Kanstantsin Shautsou (03/Jun/14 9:30 AM) 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 -- 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] [nodeofflinenotification] (JENKINS-23197) When entering offline reason for a node, it should be prefixed with a date+time stamp
Yaniv Kaul
commented on JENKINS-23197
When entering offline reason for a node, it should be prefixed with a date+time stamp
I assume the change is under /core/src/main/java/hudson/model/Node.java :
void setTemporaryOfflineCause(OfflineCause cause) {
try {
if (temporaryOfflineCause != cause) {
temporaryOfflineCause = cause; // Add date here.
Jenkins.getInstance().save(); // Gotta be a better way to do this
}
} catch (java.io.IOException e) {
LOGGER.warning("Unable to complete save, temporary offline status will not be persisted: " + e.getMessage());
}
}
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] [gui] (JENKINS-23285) All links on trend graph map are wrong on testngreports subpage
Hubert Grzeskowiak created JENKINS-23285 All links on trend graph map are wrong on testngreports subpage Issue Type: Bug Assignee: Nalin Makar Components: gui, testng Created: 03/Jun/14 10:26 AM Description: The TestNG Plugin for Jenkins adds a new menu entrry to all projects called "TestNG Results" which, when clicked, leads to a page called "TestNG Results Trends" with the URL "/job/projectname/testngreports/". On that page a HTML image map shows the trend and offers links to the single builds. However, the anchors in the imagemap are all like "BUILDNUMBER/testngreports/". What they should point to instead is "../BUILDNUMBER/testngreports" - note the "../". I guess the devs simply reused code from the project overview widget, where the URLs work together nicely. As it is now, however, the testng report page contains links to non-existent pages, leading to 404. Project: Jenkins Labels: plugin testng Priority: Major Reporter: Hubert Grzeskowiak 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-19454) Move DecoratedLauncher from the custom-tools plugin to the Jenkins Core
SCM/JIRA link daemon resolved JENKINS-19454 as Fixed Move DecoratedLauncher from the custom-tools plugin to the Jenkins Core Change By: SCM/JIRA link daemon (03/Jun/14 11:10 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 -- 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-20559) hudson.Launcher:ProcStarter::envs() may throw NPE
SCM/JIRA link daemon commented on JENKINS-20559 hudson.Launcher:ProcStarter::envs() may throw NPE Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/Launcher.java http://jenkins-ci.org/commit/jenkins/ef943a3ee69529a9f41353f134043ed3363f12e0 Log: FIXED JENKINS-20559 - ProcStarter: Check for null before cloning of environment variables list Resolves https://issues.jenkins-ci.org/browse/JENKINS-20559 BTW, I also need to add some tests to "Test Harness" in order to improve coverage of nested operations. These test require a fix for https://issues.jenkins-ci.org/browse/JENKINS-19454 Signed-off-by: Oleg Nenashev nenas...@synopsys.com 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-19454) Move DecoratedLauncher from the custom-tools plugin to the Jenkins Core
SCM/JIRA link daemon commented on JENKINS-19454 Move DecoratedLauncher from the custom-tools plugin to the Jenkins Core Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/Launcher.java test/src/test/java/hudson/ProcStarterTest.java http://jenkins-ci.org/commit/jenkins/4d4ca20a241aac64d000cc29bc27e7f1c1920f94 Log: Merge pull request #1013 from synopsys-arc-oss/launcher_fixes FIXED JENKINS-20559 and JENKINS-19454 - hudson.Launcher bugfix and additional wrapper Compare: https://github.com/jenkinsci/jenkins/compare/4f41d2aa28d6...4d4ca20a241a 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-20559) hudson.Launcher:ProcStarter::envs() may throw NPE
SCM/JIRA link daemon commented on JENKINS-20559 hudson.Launcher:ProcStarter::envs() may throw NPE Code changed in jenkins User: Oleg Nenashev Path: test/src/test/java/hudson/ProcStarterTest.java http://jenkins-ci.org/commit/jenkins/c5d01b0645a12e64e2a256641b18989c2f68eeea Log: JENKINS-20559 - A direct test for the bug Signed-off-by: Oleg Nenashev o.v.nenas...@gmail.com 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-19454) Move DecoratedLauncher from the custom-tools plugin to the Jenkins Core
SCM/JIRA link daemon commented on JENKINS-19454 Move DecoratedLauncher from the custom-tools plugin to the Jenkins Core Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/Launcher.java http://jenkins-ci.org/commit/jenkins/a865a52562a7f29ff065e3c86e67013cf606f9d5 Log: FIXED JENKINS-19454 - Added DecoratedLauncher implementation to the core. This launcher Allows subclasses to only implement methods they want to override. Originally, this launcher has been implemented in Custom Tools Plugin, but there are many duplicates in other plugins = it would be useful to have it in Jenkins core. Resolves https://issues.jenkins-ci.org/browse/JENKINS-19454 Signed-off-by: Oleg Nenashev nenas...@synopsys.com 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-19454) Move DecoratedLauncher from the custom-tools plugin to the Jenkins Core
SCM/JIRA link daemon commented on JENKINS-19454 Move DecoratedLauncher from the custom-tools plugin to the Jenkins Core Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/Launcher.java http://jenkins-ci.org/commit/jenkins/ef943a3ee69529a9f41353f134043ed3363f12e0 Log: FIXED JENKINS-20559 - ProcStarter: Check for null before cloning of environment variables list Resolves https://issues.jenkins-ci.org/browse/JENKINS-20559 BTW, I also need to add some tests to "Test Harness" in order to improve coverage of nested operations. These test require a fix for https://issues.jenkins-ci.org/browse/JENKINS-19454 Signed-off-by: Oleg Nenashev nenas...@synopsys.com 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-20559) hudson.Launcher:ProcStarter::envs() may throw NPE
SCM/JIRA link daemon commented on JENKINS-20559 hudson.Launcher:ProcStarter::envs() may throw NPE Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/Launcher.java test/src/test/java/hudson/ProcStarterTest.java http://jenkins-ci.org/commit/jenkins/4d4ca20a241aac64d000cc29bc27e7f1c1920f94 Log: Merge pull request #1013 from synopsys-arc-oss/launcher_fixes FIXED JENKINS-20559 and JENKINS-19454 - hudson.Launcher bugfix and additional wrapper Compare: https://github.com/jenkinsci/jenkins/compare/4f41d2aa28d6...4d4ca20a241a 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-20559) hudson.Launcher:ProcStarter::envs() may throw NPE
Oleg Nenashev resolved JENKINS-20559 as Fixed hudson.Launcher:ProcStarter::envs() may throw NPE The issue will be fixed in 1.567 Change By: Oleg Nenashev (03/Jun/14 11:16 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 -- 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-23287) GIT_BRANCH not set when 'Merge before build' is used
T.B. Anton created JENKINS-23287 GIT_BRANCH not set when Merge before build is used Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git Created: 03/Jun/14 11:30 AM Description: We have a shell script driven build, that uses the value of GIT_BRANCH to figure out what branch we are building. This works fine for a simple configuration with one branch configured. Recently, I added a 'Merge before build' step to the configuration, so a specific topic branch is merged into master before building. This results in GIT_BRANCH being unset. I was expecting it to be set to the branch, that is being merged into (e.g. master), since that is still the branch that should be tracked for changes. How can I pass branch information into a shell script when using 'Merge before build'? Project: Jenkins Priority: Major Reporter: T.B. Anton 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] [job-dsl-plugin] (JENKINS-23289) ClassCastException in JobDSL whith removed Folder
Romain Chalumeau created JENKINS-23289 ClassCastException in JobDSL whith removed Folder Issue Type: Bug Assignee: Justin Ryan Components: job-dsl-plugin Created: 03/Jun/14 11:48 AM Description: Hi, When a folder is in the list of "Removing items" at the end of the execution, it triggers the following exception : FATAL: com.cloudbees.hudson.plugins.folder.Folder cannot be cast to hudson.model.AbstractProject java.lang.ClassCastException: com.cloudbees.hudson.plugins.folder.Folder cannot be cast to hudson.model.AbstractProject at javaposse.jobdsl.plugin.ExecuteDslScripts.updateGeneratedJobs(ExecuteDslScripts.java:278) at javaposse.jobdsl.plugin.ExecuteDslScripts.perform(ExecuteDslScripts.java:177) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.Build$BuildExecution.build(Build.java:198) at hudson.model.Build$BuildExecution.doRun(Build.java:159) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:523) at hudson.model.Run.execute(Run.java:1700) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Rgds/Romain Environment: Ubuntu Precise 12.4 Project: Jenkins Priority: Major Reporter: Romain Chalumeau 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] [xunit] (JENKINS-23288) xUnit converts the cppunit xml report file but it does not display them
Vladimir Zak created JENKINS-23288 xUnit converts the cppunit xml report file but it does not display them Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: xunit Created: 03/Jun/14 11:47 AM Description: xUnit converts the cppunit xml report file but it does not display them Old version - cpp unit test xml reports were correctly parsed and displayed. Now in the log there are message about parsing (was not there but no problem is visible) but tests are not visible in the job page. In the log I did not find anything related to this problem. Environment: - Jenkins ver. 1.554.2 xUnit - 1.89 Project: Jenkins Priority: Critical Reporter: Vladimir Zak 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-23270) After migrating to another IP hyperlink in Slaves in label still refers to old value.
Oleg Nenashev resolved JENKINS-23270 as Fixed After migrating to another IP hyperlink in Slaves in label still refers to old value. The built-in help provides the detailed explanation, why Jenkins needs the explicit configuration of "Jenkins URL" Change By: Oleg Nenashev (03/Jun/14 12:01 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-23273) RPM post-install should not do a chown -R jenkins:jenkins /var/lib/jenkins
Oleg Nenashev commented on JENKINS-23273 RPM post-install should not do a chown -R jenkins:jenkins /var/lib/jenkins Introduced by https://github.com/jenkinsci/jenkins/commit/4335bd435f9e5258831c5631bfab2fd837fd7719 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-20559) hudson.Launcher:ProcStarter::envs() may throw NPE
dogfood commented on JENKINS-20559 hudson.Launcher:ProcStarter::envs() may throw NPE Integrated in jenkins_main_trunk #3432 FIXED JENKINS-20559 - ProcStarter: Check for null before cloning of environment variables list (Revision ef943a3ee69529a9f41353f134043ed3363f12e0) JENKINS-20559 - A direct test for the bug (Revision c5d01b0645a12e64e2a256641b18989c2f68eeea) Result = SUCCESS o.v.nenashev : ef943a3ee69529a9f41353f134043ed3363f12e0 Files : core/src/main/java/hudson/Launcher.java o.v.nenashev : c5d01b0645a12e64e2a256641b18989c2f68eeea Files : test/src/test/java/hudson/ProcStarterTest.java 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-19454) Move DecoratedLauncher from the custom-tools plugin to the Jenkins Core
dogfood commented on JENKINS-19454 Move DecoratedLauncher from the custom-tools plugin to the Jenkins Core Integrated in jenkins_main_trunk #3432 FIXED JENKINS-19454 - Added DecoratedLauncher implementation to the core. (Revision a865a52562a7f29ff065e3c86e67013cf606f9d5) Result = SUCCESS o.v.nenashev : a865a52562a7f29ff065e3c86e67013cf606f9d5 Files : core/src/main/java/hudson/Launcher.java 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-23273) RPM post-install should not do a chown -R jenkins:jenkins /var/lib/jenkins
Oleg Nenashev assigned JENKINS-23273 to Nicolas De Loof RPM post-install should not do a chown -R jenkins:jenkins /var/lib/jenkins Change By: Oleg Nenashev (03/Jun/14 12:07 PM) Assignee: NicolasDeLoof 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] [other] (JENKINS-13480) Http HEAD request returns body
Oleg Nenashev resolved JENKINS-13480 as Fixed Http HEAD request returns body The issue seems to be resolved Change By: Oleg Nenashev (03/Jun/14 12:17 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] [nunit] (JENKINS-23290) unit plugins put result into same grahp
Jes Struck created JENKINS-23290 unit plugins put result into same grahp Issue Type: Bug Affects Versions: current Assignee: redsolo Components: nunit, xunit Created: 03/Jun/14 12:25 PM Description: if i set xUnit to cellect some Nunit results, and afterwards set the Nunit plugin to collect a different set of Nunit test i get two identical graph's is that intentional. Im trying to collect the result files from a job that has run x64 and x84 bit C# NUnit test (which is possible with C#, given youre running on a x64 os) I'd exspected to get two different graph's one with the status of the x64 result and one with x84 result's I have tested that it's not because we have the exactly same result in both, i have tesed with a setup 100:1. Please help is it possible to fix? Environment: Jenkins 1.554.2 NUnit 0.15 xunit 1.89 Windows 7 x64 Project: Jenkins Priority: Major Reporter: Jes Struck 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-23273) RPM post-install should not do a chown -R jenkins:jenkins /var/lib/jenkins
Chris Burroughs commented on JENKINS-23273 RPM post-install should not do a chown -R jenkins:jenkins /var/lib/jenkins This isn't just a performance problem. We have the workspace owned by a different group and this rpm tries to undo that. 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] [parameters] (JENKINS-23291) Cannot remove job parameters via config.xml POST
Diogo Campos
created JENKINS-23291
Cannot remove job parameters via config.xml POST
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
new_without_parameters.xml, old_with_parameters.xml
Components:
parameters
Created:
03/Jun/14 12:56 PM
Description:
If I have a job that is parameterized, and I try to remove parameters from its config.xml via HTTP post to JOB_URL/config.xml, nothing happens.
The correct config.xml is uploaded (this can be seen in the JOB_URL/config.xml page), but there seems to be no effect on the interface.
Manually reloading configuration from disk in Jenkins Management after uploading the new XML will put the correct options there.
I've only tested this using python_jenkins, but it really only does an HTTP post:
def reconfig_job(self, name, config_xml):
self.get_job_info(name)
headers = {'Content-Type': 'text/xml'}
reconfig_url = self.server + CONFIG_JOB % locals()
self.jenkins_open(urllib2.Request(reconfig_url, config_xml, headers))
XML files attached.
Reproduced in 1.528 and 1.565.
Project:
Jenkins
Priority:
Major
Reporter:
Diogo Campos
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] [fitnesse] (JENKINS-20174) Corrupt FitNesse plugin XML report generated
David JL edited a comment on JENKINS-20174 Corrupt FitNesse plugin XML report generated I managed to install groovy and get the scripts to execute correctly via Jenkins. However I now have the following issue: Xml results saved as windows-1252 to C:\Users\Administrator\.jenkins\workspace\FITNESSE_ECRAN_EXPLOIT_3\fitnesse_tmp_result.xml FITNESSE_ECRAN_EXPLOIT_3 $ "C:\Program Files (x86)\Groovy\Groovy-2.3.2\bin\groovy.exe" C:\Users\Administrator\.jenkins\workspace\FITNESSE_ECRAN_EXPLOIT_3\hudson7296783988754375979.groovy Reading results as windows-1252 from C:\Users\Administrator\.jenkins\workspace\FITNESSE_ECRAN_EXPLOIT_3\fitnesse_result.xml Parsing results... javax.xml.transform.TransformerException: javax.xml.transform.TransformerException: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: Invalid byte 2 of 3-byte UTF-8 sequence. It would appear the file produced by the groovy script has some sort of encoding issue. Still trying to figure this one out. 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] [fitnesse] (JENKINS-20174) Corrupt FitNesse plugin XML report generated
David JL commented on JENKINS-20174 Corrupt FitNesse plugin XML report generated I managed to install groovy and get the scripts to execute correctly via Jenkins. However I now have the following issue: Xml results saved as windows-1252 to C:\Users\Administrator\.jenkins\workspace\FITNESSE_ECRAN_EXPLOIT_3\fitnesse_tmp_result.xml FITNESSE_ECRAN_EXPLOIT_3 $ "C:\Program Files (x86)\Groovy\Groovy-2.3.2\bin\groovy.exe" C:\Users\Administrator\.jenkins\workspace\FITNESSE_ECRAN_EXPLOIT_3\hudson7296783988754375979.groovy Reading results as windows-1252 from C:\Users\Administrator\.jenkins\workspace\FITNESSE_ECRAN_EXPLOIT_3\fitnesse_result.xml Parsing results... javax.xml.transform.TransformerException: javax.xml.transform.TransformerException: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: Invalid byte 2 of 3-byte UTF-8 sequence. It would appear the file produced by the groovy script has some sort of encoding issue. Still trying to figure this one out. 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] [fitnesse] (JENKINS-20174) Corrupt FitNesse plugin XML report generated
David JL edited a comment on JENKINS-20174 Corrupt FitNesse plugin XML report generated I managed to install groovy and get the scripts to execute correctly via Jenkins. However I now have the following issue: Xml results saved as windows-1252 to C:\Users\Administrator\.jenkins\workspace[JOB]\fitnesse_tmp_result.xml FITNESSE_ECRAN_EXPLOIT_3 $ "C:\Program Files (x86)\Groovy\Groovy-2.3.2\bin\groovy.exe" C:\Users\Administrator\.jenkins\workspace\FITNESSE_ECRAN_EXPLOIT_3\hudson7296783988754375979.groovy Reading results as windows-1252 from C:\Users\Administrator\.jenkins\workspace[JOB]\fitnesse_result.xml Parsing results... javax.xml.transform.TransformerException: javax.xml.transform.TransformerException: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: Invalid byte 2 of 3-byte UTF-8 sequence. It would appear the file produced by the groovy script has some sort of encoding issue. Still trying to figure this one out. 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] [fitnesse] (JENKINS-20174) Corrupt FitNesse plugin XML report generated
David JL edited a comment on JENKINS-20174 Corrupt FitNesse plugin XML report generated I managed to install groovy and get the scripts to execute correctly via Jenkins. However I now have the following issue: Xml results saved as windows-1252 to C:\Users\Administrator\.jenkins\workspace[JOB]\fitnesse_tmp_result.xml [JOB] $ "C:\Program Files (x86)\Groovy\Groovy-2.3.2\bin\groovy.exe" C:\Users\Administrator\.jenkins\workspace\FITNESSE_ECRAN_EXPLOIT_3\hudson7296783988754375979.groovy Reading results as windows-1252 from C:\Users\Administrator\.jenkins\workspace[JOB]\fitnesse_result.xml Parsing results... javax.xml.transform.TransformerException: javax.xml.transform.TransformerException: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: Invalid byte 2 of 3-byte UTF-8 sequence. It would appear the file produced by the groovy script has some sort of encoding issue. Still trying to figure this one out. 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] [fitnesse] (JENKINS-20174) Corrupt FitNesse plugin XML report generated
David JL edited a comment on JENKINS-20174 Corrupt FitNesse plugin XML report generated I managed to install groovy and get the scripts to execute correctly via Jenkins. However I now have the following issue: Xml results saved as windows-1252 to C:\Users\Administrator\.jenkins\workspace[JOB]\fitnesse_tmp_result.xml [JOB] $ "C:\Program Files (x86)\Groovy\Groovy-2.3.2\bin\groovy.exe" C:\Users\Administrator\.jenkins\workspace[JOB]\hudson7296783988754375979.groovy Reading results as windows-1252 from C:\Users\Administrator\.jenkins\workspace[JOB]\fitnesse_result.xml Parsing results... javax.xml.transform.TransformerException: javax.xml.transform.TransformerException: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: Invalid byte 2 of 3-byte UTF-8 sequence. It would appear the file produced by the groovy script has some sort of encoding issue. Still trying to figure this one out. 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] [ssh-slaves] (JENKINS-23217) Prefix/Suffix Start Slave Command does not automatically append/prepend
Fred G commented on JENKINS-23217 Prefix/Suffix Start Slave Command does not automatically append/prepend OK. I wasn't aware of that. So the current shell needs to be detected as well. 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] [tfs] (JENKINS-3002) TFS Support to get labels
sly ge commented on JENKINS-3002 TFS Support to get labels Hi, What about this issue? Can we now use labels in TFS plugin? I can't find anything in release 3.1.1 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-21335) Forward slashes in a File Parameter's file location cause parameter download links to break
Eric Anker commented on JENKINS-21335 Forward slashes in a File Parameters file location cause parameter download links to break I don't believe so. it's a single server and the issue is present on localhost. How else can I help diagnose? 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] [delivery-pipeline] (JENKINS-23282) Delivery Pipeline view renders a blank page when set as the default system view in Jenkins
Patrik Boström resolved JENKINS-23282 as Fixed Delivery Pipeline view renders a blank page when set as the default system view in Jenkins Thanks for the PR! Great work! Merged to master, will go out in next release. Change By: Patrik Boström (03/Jun/14 1:39 PM) Status: Open Resolved Assignee: PatrikBoström 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] [leastload] (JENKINS-23293) Load balancing does not work when many jobs are launched simultaneously
Sampo Niskanen created JENKINS-23293 Load balancing does not work when many jobs are launched simultaneously Issue Type: Bug Assignee: Unassigned Components: leastload Created: 03/Jun/14 1:51 PM Description: We have a master job (using the Multijob plugin) which launches eight sub-jobs in our CI pipeline. We have installed the least load plugin to evenly distribute the load on our (currently two) Jenkins slaves. However, we often see that seven jobs are launched on one slave and only one on the other. My guess is that since the jobs are launched at exactly the same time, the least load plugin doesn't have time to see the new jobs launched on the slaves when it gets requests to map the other jobs, thus placing them all on the same slave. If there's no cleaner solution available, then I'd suggest that the plugin would remember the jobs it has mapped to a particular slave for a few seconds, and factor them into the load balancing decisions within that time frame. Project: Jenkins Priority: Major Reporter: Sampo Niskanen 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] [jira] (JENKINS-23292) jira-plugin uses emails from jira
twolfart created JENKINS-23292 jira-plugin uses emails from jira Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jira Created: 03/Jun/14 1:50 PM Description: When sending an email, the jira-plugin provides an email adress from JIRA instead of the regular email adress combined from committer and the configured domain. if the username exists in jira, jenkins will use the email without any further notice that this happened the email adress is used even if the jira-account in question has no permission for the project being build (how should jenkins know?) the email adress is even used from disabled jira accounts (how should jenkins know?) this feature of the plugin can't be disabled This can lead to emails being sent to wrong recipients. Environment: Jenkins 1.558, Jira-Plugin 1.39, Email-ext plugin 2.37.2.2 Fix Versions: current Project: Jenkins Priority: Critical Reporter: twolfart 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] [customtools-plugin] (JENKINS-22925) [Custom Tools] - Parameter definition does not return the default value
Oleg Nenashev resolved JENKINS-22925 as Fixed [Custom Tools] - Parameter definition does not return the default value Will be fixed in the new release Change By: Oleg Nenashev (03/Jun/14 2:18 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] [job-dsl-plugin] (JENKINS-23289) ClassCastException in JobDSL whith removed Folder
Romain Chalumeau commented on JENKINS-23289 ClassCastException in JobDSL whith removed Folder I should precise the versions : Jenkins : 1.559 Cloudbees Folder : 4.5 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-2888) Maven artifact id in permalinks
Oleg Nenashev updated JENKINS-2888 Maven artifact id in permalinks Change By: Oleg Nenashev (03/Jun/14 2:28 PM) Component/s: maven Component/s: maven2 Component/s: gui 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] [job-dsl-plugin] (JENKINS-23289) ClassCastException in JobDSL whith removed Folder
Daniel Spilker assigned JENKINS-23289 to Daniel Spilker ClassCastException in JobDSL whith removed Folder Change By: Daniel Spilker (03/Jun/14 2:39 PM) Assignee: JustinRyan DanielSpilker 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-23273) RPM post-install should not do a chown -R jenkins:jenkins /var/lib/jenkins
Daniel Beck commented on JENKINS-23273 RPM post-install should not do a chown -R jenkins:jenkins /var/lib/jenkins FYI this doesn't do what the issue title suggests. It makes the value of JENKINS_USER (loaded from /etc/sysconfig/jenkins) the owner, or jenkins if the variable is undefined. It also does not attempt to set the group. It'd probably be safe if you defined the JENKINS_USER env variable for RPM to use. Still, the performance issue remains. JENKINS-12231 probably just needs to be solved non-recursively (and needs to include /var/cache/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] [core] (JENKINS-23273) RPM post-install should not do a chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}
Ralph Bolton
updated JENKINS-23273
RPM post-install should not do a chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}
Change By:
Ralph Bolton
(03/Jun/14 2:42 PM)
Summary:
RPMpost-installshouldnotdoachown-R
jenkins
${JENKINS_USER
:
-
jenkins
}${JENKINS_HOME:-
/var/lib/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] [core] (JENKINS-23273) RPM post-install should not do a chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}
Ralph Bolton
commented on JENKINS-23273
RPM post-install should not do a chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}
sorry, my mistake. You're right, it doesn't affect group. I wasn't aware of previous issues with running Jenkins as users other than 'jenkins', and so was imprecise in my description. I've edited to correct.
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-12231) RPM upgrade does not honor JENKINS_USER, and always resets files ownership to jenkins
Daniel Beck commented on JENKINS-12231 RPM upgrade does not honor JENKINS_USER, and always resets files ownership to jenkins Is there a reason the patch does not include /var/cache/jenkins? And that it's recursive is probably really unnecessary, as noted in JENKINS-23273. Francisco Lozano: Doesn't your /etc/sysconfig/jenkins define as JENKINS_USER the name of the Jenkins user? 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] [ant] (JENKINS-23207) Issue when saving/applying changes.
Mark Waite commented on JENKINS-23207 Issue when saving/applying changes. That is not enough information to duplicate the problem. I'd rather close the bug as "Not a bug" if we can't duplicate it, since there is no hope of anyone making any changes for the bug report unless they can duplicate the issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-23266) GitSCM rebuilds all the time while using poll scm
Mark Waite commented on JENKINS-23266 GitSCM rebuilds all the time while using poll scm That is an unfortunate side effect of the design decision made long ago to split on the slash in the "branch to build". I'm not willing to break compatibility with that old design decision because of the number of users of the git plugin (and the git client plugin) and the many ways in which they depend on those plugins. Rather than break compatibility, Alexander Link has proposed that we accept "refs/heads/namespace/master" as an intentional declaration of the specific branch, without changing the semantics of other forms (like origin/master, */master). Would you be willing to assist with the evaluation of Alexander's proposed changes? They are included in https://github.com/jenkinsci/git-client-plugin/pull/135 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-23273) RPM post-install should not do a chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}
Daniel Beck
commented on JENKINS-23273
RPM post-install should not do a chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}
Also, my comment was partially incorrect as well: As it'll load /etc/sysconfig/jenkins (unless you messed with the overall format of the file or specify a custom user somewhere else, in which case it's your own fault), it'll do the right thing.
HOWEVER, it'll chown recursively when it doesn't need to. I expect the entire problem to vanish when the -R is removed.
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-23294) Interpret X-Forwarded-Port
Jesse Glick created JENKINS-23294 Interpret X-Forwarded-Port Issue Type: Bug Assignee: Jesse Glick Components: core Created: 03/Jun/14 3:57 PM Description: Under some conditions a reverse proxy may define X-Forwarded-Port yet the Jenkins servlet container still returns 80 for ServletRequest.getServerPort. This causes problems for computing Jenkins.getRootUrlFromRequest, the current implementation of which treats the default port as 80 regardless of the scheme; we would like the default to be 443 when X-Forwarded-Proto: https, yet this will only work if the servlet container coöperates. Easier to have Jenkins itself interpret this header when set. Project: Jenkins Labels: proxy https Priority: Major Reporter: Jesse Glick 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-23294) Interpret X-Forwarded-Port
Jesse Glick started work on JENKINS-23294 Interpret X-Forwarded-Port Change By: Jesse Glick (03/Jun/14 3:57 PM) Status: Open InProgress 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
Daniel Beck commented on JENKINS-19134 Disallow Users to set a custom workspace What's your goal? If it's providing your users a child-proof UI (e.g. to prevent config mistakes), check out the Cloudbees Template plugin. It only provides UI for what you explicitly allow configured. Cloudbees Nodes Plus helps as well, limiting some nodes to running jobs that are explicitly allowed to run on them, independent of the label mechanism. IOW, it can be done in plugins. If it's security, just forget about that. You absolutely need to be able to trust the users you give job config permissions. Hiding an input field will not achieve this. I'd run multiple masters instead, to prevent untrusted users from messing with your stuff. Or something else entirely? 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] [scm-sync-configuration] (JENKINS-14847) Apply button not taken into account
Ben Eastmond commented on JENKINS-14847 Apply button not taken into account I believe the issue some are having, including myself, may actually be a result of JENKINS-21640 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-23281) Jenkins.getUser(...) is debilitatingly slow with a large number of users
abayer commented on JENKINS-23281 Jenkins.getUser(...) is debilitatingly slow with a large number of users And something is messed up on that volume, apparently - stat i/o and the like is really nasty on it in general, based on tests from outside Jenkins. So this may not be as bad as it seemed. 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-9430) zip of workspace folders does garble filenames with german characters.
Johannes Schmieder commented on JENKINS-9430 zip of workspace folders does garble filenames with german characters. I testet Jenkins ver. 1.554.1 running with java ver. 1.6.0_20 and jenkins jvm parameter -Dfile.encoding=UTF-8. Zipped workspaces containing files or directories with umlauts the umlauts are garbled. If running jenkins with java ver. 1.7.0_40 and jenkins jvm parameter -Dfile.encoding=UTF-8 the zipped workspaces containing files or directories with umlauts are as expected. 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-21335) Forward slashes in a File Parameter's file location cause parameter download links to break
Daniel Beck commented on JENKINS-21335 Forward slashes in a File Parameters file location cause parameter download links to break I confirm the issue on Jenkins 1.561 on CentOS 6 behind Apache reverse proxy. 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-23294) Interpret X-Forwarded-Port
Jesse Glick updated JENKINS-23294 Interpret X-Forwarded-Port Change By: Jesse Glick (03/Jun/14 4:57 PM) URL: https://github.com/jenkinsci/jenkins/pull/1265 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-9430) zip of workspace folders does garble filenames with german characters.
Johannes Schmieder edited a comment on JENKINS-9430 zip of workspace folders does garble filenames with german characters. I testet Jenkins ver. 1.554.1 running with java ver. 1.6.0_20 and jenkins jvm parameter -Dfile.encoding=UTF-8. Zipped workspaces containing files or directories with umlauts the umlauts are garbled. If running jenkins with java ver. 1.7.0_40 and jenkins jvm parameter -Dfile.encoding=UTF-8 the zipped workspaces containing files or directories with umlauts are as expected. Zipped workspaces have been validated with 7-zip. 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-21335) Forward slashes in a File Parameter's file location cause parameter download links to break
Daniel Beck commented on JENKINS-21335 Forward slashes in a File Parameters file location cause parameter download links to break ... however not on a localhost. And I know my Apache reverse proxy is broken. Eric: What version of Jenkins are you using? Is there a note complaining about your reverse proxy setup on the "Manage Jenkins" page? 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] [ssh-slaves] (JENKINS-23217) Prefix/Suffix Start Slave Command does not automatically append/prepend
Daniel Beck
commented on JENKINS-23217
Prefix/Suffix Start Slave Command does not automatically append/prepend
An easy solution would be to (optionally create a temporary script file and) run multiple commands one after the other in the shell. One per line. All shells should support that.
But there's a problem with that: Any change here will be backwards incompatible.
{{LANG=en_US.UTF-8 }} should work like a charm in bash as a prefix command, but not if run independently.
I don't see the benefit justifying the cost here.
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-23270) After migrating to another IP hyperlink in Slaves in label still refers to old value.
Oliver Gondža commented on JENKINS-23270 After migrating to another IP hyperlink in Slaves in label still refers to old value. Actually, I believe this issue is valid. According to https://wiki.jenkins-ci.org/display/JENKINS/Hyperlinks+in+HTML, relative links should be used wherever possible. And it is possible in form validation handler. Needles to say it was me who introduced this in https://github.com/jenkinsci/jenkins/commit/f34ea92edeaf9cb7ff174a6974b950a8e13f97aa. 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] [active-directory] (JENKINS-22830) Slow login w/ Active directory plugin
Jesse Glick updated JENKINS-22830 Slow login w/ Active directory plugin Change By: Jesse Glick (03/Jun/14 5:35 PM) Labels: performanceregression 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-23273) RPM post-install should not do a chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}
Jesse Glick
updated JENKINS-23273
RPM post-install should not do a chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}
Change By:
Jesse Glick
(03/Jun/14 6:12 PM)
Labels:
regression
rpmyum
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-21605) Logging all UpstreamCause's floods Jenkins in large setups
Dirk Thomas commented on JENKINS-21605 Logging all UpstreamCauses floods Jenkins in large setups @jglick Can you please look into this issue? You have fixed the original ticket for us (15747) and this regression makes our logging nearly unusable. 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-21605) Logging all UpstreamCause's floods Jenkins in large setups
Dirk Thomas edited a comment on JENKINS-21605 Logging all UpstreamCauses floods Jenkins in large setups Can someone please look into this issue? The original ticket was already fixed (15747) and this regression makes our logging nearly unusable. 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-21605) Logging all UpstreamCause's floods Jenkins in large setups
Dirk Thomas assigned JENKINS-21605 to Jesse Glick Logging all UpstreamCauses floods Jenkins in large setups Since you have fixed the original ticket for us could you please look into fixing this regression? Change By: Dirk Thomas (03/Jun/14 6:22 PM) Assignee: JesseGlick 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-21605) Logging all UpstreamCause's floods Jenkins in large setups
Jesse Glick commented on JENKINS-21605 Logging all UpstreamCauses floods Jenkins in large setups Do not really have time for it. File a pull request if you know how to fix it, or if you are a CloudBees support customer open a ticket. 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] [jenkinswalldisplay] (JENKINS-23295) Paint Interval help file not found
Nikolai Colton created JENKINS-23295 Paint Interval help file not found Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jenkinswalldisplay Created: 03/Jun/14 6:48 PM Description: Paint Interval help shows "ERROR: Failed to load help file: Not Found" rather than the information about the setting. Project: Jenkins Priority: Minor Reporter: Nikolai Colton 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] [master-slave] (JENKINS-23255) Minor network connectivity drop fails the build on slave
Devsh sharma reopened JENKINS-23255 Minor network connectivity drop fails the build on slave More info on environment is as follow :- 1 - I am using java web start to launch slave (using Vsphere cloud plugin). 2 - All my machines are windows based and are running on ESX. 3 - The other key observation in this case is , the network connectivity remains lost for 50-60 secs and in some worst case may renew the IP as well. the error I get is as follow :- FATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Socket closed hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Socket closed at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:722) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:167) at com.sun.proxy.$Proxy48.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:925) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at org.jenkins_ci.plugins.run_condition.BuildStepRunner$2.run(BuildStepRunner.java:110) at org.jenkins_ci.plugins.run_condition.BuildStepRunner$Fail.conditionalRun(BuildStepRunner.java:154) at org.jenkins_ci.plugins.run_condition.BuildStepRunner.perform(BuildStepRunner.java:105) at org.jenkinsci.plugins.conditionalbuildstep.singlestep.SingleConditionalBuilder.perform(SingleConditionalBuilder.java:108) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:784) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:565) at hudson.model.Run.execute(Run.java:1670) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: hudson.remoting.RequestAbortedException: java.net.SocketException: Socket closed at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:782) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.net.SocketException: Socket closed at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(Unknown Source) at java.net.SocketInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:77) at java.io.ObjectInputStream$PeekInputStream.peek(Unknown Source) at java.io.ObjectInputStream$BlockDataInputStream.peek(Unknown Source) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.readObject(Unknown Source) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:71) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Change By: Devsh sharma (03/Jun/14 7:04 PM) Resolution: Incomplete 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:
[JIRA] [tap] (JENKINS-23296) TAP Plugin not communicating with other plugins
andrew cooke created JENKINS-23296 TAP Plugin not communicating with other plugins Issue Type: Bug Affects Versions: current Assignee: Bruno P. Kinoshita Components: tap Created: 03/Jun/14 7:02 PM Description: I have inherited a plugin (https://github.com/andrewcooke-isti/JiraTestResultReporter) that creates Jira issues from test results. It works fine with JUnit, but not with TAP. It's quite possible this is some kind of error in my plugin, so apologies in advance, but what seems to be happening is that when I call getFailedTests() on a TestResultAction instance, it returns an empty set, even when tests have failed. I have no idea how this information is created, but the underlying AbstractTestResultAction returns an empty set. So I wondered if perhaps you need to over-ride that? For Junit, that method returns a set of CaseResult instances that I can use to generate test reports. I should emphasize that your plugin seems to work fine otherwise - it parses the TAP output and generates tables of results. Please contact me (and...@acooke.org) if you have more questions. I can modify my plugin to get more info if you need it. Thanks for your help and sorry this is so vague. Environment: CentOS 6.4, Tomcat 7.0.53, Jenkins 1.562 Project: Jenkins Priority: Major Reporter: andrew cooke 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-23297) Error when adding users or changing permissions
Robert Greathouse created JENKINS-23297 Error when adding users or changing permissions Issue Type: Bug Assignee: stephenconnolly Components: credentials Created: 03/Jun/14 8:00 PM Description: Following stack trace generated when trying to add a user or change an existing user's authorizations. javax.servlet.ServletException: java.lang.ClassCastException: net.sf.json.JSONArray cannot be cast to java.lang.Boolean at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at com.cloudbees.jenkins.support.SupportMetricsFilter.doFilter(SupportMetricsFilter.java:80) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at com.cloudbees.jenkins.support.SupportMetricsFilter.doFilter(SupportMetricsFilter.java:105) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:208) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:181) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at org.jenkinsci.plugins.suppress_stack_trace.SuppressionFilter.doFilter(SuppressionFilter.java:34) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at com.cloudbees.jenkins.ha.HAHealthCheckFilter.doFilter(HAHealthCheckFilter.java:52) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at
[JIRA] [mstestrunner] (JENKINS-20367) If a failed test result the plugin causes a Failed build
Michael Fowler assigned JENKINS-20367 to Ido Ran If a failed test result the plugin causes a Failed build Change By: Michael Fowler (03/Jun/14 8:07 PM) Assignee: IdoRan 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] [vsphere-cloud] (JENKINS-21810) Additional options on slave disconnection
Steven Visagie commented on JENKINS-21810 Additional options on slave disconnection Sorry for the delayed response. I had a look and see that both new options "Revert and Restart" and "Revert and Reset" build on the "Revert" option which in turn builds on the "Shutdown" option which does a graceful shutdown i.e. shut down the virtual machine through the guest operating system. In VMWare vSphere client, a virtual machine doesn't have to be gracefully shutdown: it can be "hard powered down" which is like hitting the power switch on a physical machine. I haven't yet tested the new options but since the virtual machines takes some time to shutdown, we've found that a graceful shutdown doesn't work in our use case. Currently we're using the "Suspend" option which immediately suspends the machine, breaking the connection between the slave and the host. Since this option works, I suspect that providing a way to "hard power down" instead of "shutdown" will resolve the issue. This could take the form of options: Power Down (turn it off) Power Down and Revert (turn it off and then revert to the snapshot) Power Down and Restart (turn it off and then restart in the current state) Power Down, Revert and Restart (turn it off, revert to the snapshot and power up) 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-23298) No summary shown for projects inside folders
Jesse Glick created JENKINS-23298 No summary shown for projects inside folders Issue Type: Bug Assignee: Lucie Votypkova Components: disk-usage Created: 03/Jun/14 8:33 PM Description: If you have some jobs inside folders, and some at top level, /plugin/disk-usage/ (the Disk usage sidebar link from /) only shows information about the top-level jobs. Jobs inside folders show a Disk Usage note on the index page but otherwise nothing, and there is no apparent way to see usage of all jobs within a given folder. There should be a per-folder action for this purpose. Project: Jenkins Labels: folders Priority: Major Reporter: Jesse Glick 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-16805) Keep this build forever build gets deleted by Discard old builds
robsimon commented on JENKINS-16805 Keep this build forever build gets deleted by Discard old builds build doesn't get removed so this particular issue is gone. however, i've noticed that one build before the locked stays as well instead of getting removed. removal is set to keep 100 builds 40389 ... 40290 40287 (locked) 40285 should have been removed as 40286, 40288 and 40289 got removed. 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-16805) Keep this build forever build gets deleted by Discard old builds
robsimon edited a comment on JENKINS-16805 Keep this build forever build gets deleted by Discard old builds current jenkins version 1.563 locked build (keep this forever) doesn't get removed so this particular issue is gone. however, i've noticed that one build before the locked stays as well instead of getting removed. removal is set to keep 100 builds 40389 ... 40290 40287 (locked) 40285 should have been removed as 40286, 40288 and 40289 got removed. 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] [scm-sync-configuration] (JENKINS-14847) Apply button not taken into account
Frédéric Camblor commented on JENKINS-14847 Apply button not taken into account Disagree, these are different topics (apply button implies some design changes to current scm-sync-config behaviour, mainly due to the XHR form submission) 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-16805) Keep this build forever build gets deleted by Discard old builds
Daniel Beck
commented on JENKINS-16805
Keep this build forever build gets deleted by Discard old builds
robsimon:
Is the build really still there, or is it a stale page load? Reload the browser window. If it's really still there:
Create a new Log Recorder at /log for the logger hudson.tasks.LogRotator on level FINER. Then, run in script console: Jenkins.instance.getItemByFullName('yourjobnamehere').logRotate() and check your logger for what it says prevents deletion of 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/d/optout.
[JIRA] [jclouds] (JENKINS-22963) Unable to connect to digitalocean cloud
Ignasi Barrera resolved JENKINS-22963 as Fixed Unable to connect to digitalocean cloud Fixed. See https://github.com/jenkinsci/jclouds-plugin/pull/69 Change By: Ignasi Barrera (03/Jun/14 9:15 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-16805) Keep this build forever build gets deleted by Discard old builds
robsimon commented on JENKINS-16805 Keep this build forever build gets deleted by Discard old builds java.io.IOException: jobname #40285: C:\Jenkins\jobs\jobname\builds\2014-05-19_08-41-18 looks to have already been deleted; siblings: .2014-03-02_00-41-38, .2014-03-29_04-42-01, .2014-03-31_16-42-06, .2014-04-01_12-42-18, .2014-04-01_20-42-08, .2014-04-12_08-41-59, .2014-04-17_16-42-17, .2014-04-27_00-42-21, .2014-05-08_08-41-39, .2014-05-09_12-41-45, .2014-05-11_04-41-53, .2014-05-19_08-41-18, 2013-12-11_10-01-34, 2014-05-19_16-41-19, 2014-05-20_04-41-03, 2014-05-20_08-41-03, 2014-05-20_12-41-06, 2014-05-20_16-41-05, 2014-05-20_20-41-06, 2014-05-21_00-41-06, 2014-05-21_04-41-07, 2014-05-21_08-41-08, 2014-05-21_12-41-09, 2014-05-21_16-41-10, 2014-05-21_20-41-11, 2014-05-22_00-41-12, 2014-05-22_04-41-12, 2014-05-22_08-41-13, 2014-05-22_12-41-14, 2014-05-22_16-41-14, 2014-05-22_20-41-15, 2014-05-23_00-41-18, 2014-05-23_04-41-17, 2014-05-23_08-41-18, 2014-05-23_12-41-20, 2014-05-23_16-41-19, 2014-05-23_20-41-20, 2014-05-24_03-15-12, 2014-05-24_04-41-22, 2014-05-24_08-41-22, 2014-05-24_12-41-23, 2014-05-24_16-41-25, 2014-05-24_20-41-25, 2014-05-25_00-41-26, 2014-05-25_04-41-26, 2014-05-25_08-41-27, 2014-05-25_12-42-29, 2014-05-25_16-41-29, 2014-05-25_20-41-30, 2014-05-26_00-44-56, 2014-05-26_04-41-31, 2014-05-26_08-41-32, 2014-05-26_12-41-42, 2014-05-26_16-41-34, 2014-05-26_20-41-34, 2014-05-27_00-41-35, 2014-05-27_04-41-36, 2014-05-27_08-41-37, 2014-05-27_12-41-38, 2014-05-27_16-41-39, 2014-05-27_20-41-39, 2014-05-28_00-41-41, 2014-05-28_04-41-41, 2014-05-28_08-41-42, 2014-05-28_12-41-42, 2014-05-28_16-41-44, 2014-05-28_20-41-44, 2014-05-29_00-41-46, 2014-05-29_04-41-46, 2014-05-29_08-41-47, 2014-05-29_12-41-47, 2014-05-29_16-41-49, 2014-05-29_20-41-49, 2014-05-30_00-41-51, 2014-05-30_04-41-51, 2014-05-30_08-41-52, 2014-05-30_12-41-02, 2014-05-30_16-41-02, 2014-05-30_20-41-03, 2014-05-31_00-41-04, 2014-05-31_04-41-05, 2014-05-31_08-41-06, 2014-05-31_12-41-08, 2014-05-31_16-41-08, 2014-05-31_20-41-08, 2014-06-01_00-41-10, 2014-06-01_04-41-10, 2014-06-01_08-41-11, 2014-06-01_12-41-13, 2014-06-01_16-41-13, 2014-06-01_20-41-14, 2014-06-02_00-41-18, 2014-06-02_04-41-16, 2014-06-02_08-41-17, 2014-06-02_12-41-18, 2014-06-02_16-41-19, 2014-06-02_20-41-20, 2014-06-03_00-41-21, 2014-06-03_04-41-22, 2014-06-03_08-41-23, 2014-06-03_11-11-18, 2014-06-03_11-12-17, 2014-06-03_11-13-32, 2014-06-03_11-14-46, 2014-06-03_11-18-58, 2014-06-03_11-19-59, 2014-06-03_11-32-48, 2014-06-03_11-33-34, 2014-06-03_11-35-03, 2014-06-03_11-35-56, 2014-06-03_11-53-03, 2014-06-03_11-53-34, 2014-06-03_12-41-24, 2014-06-03_13-34-21, 32696, 40287, 40290, 40291, 40292, 40293, 40294, 40295, 40296, 40297, 40298, 40299, 40300, 40301, 40302, 40303, 40304, 40305, 40306, 40307, 40308, 40309, 40310, 40311, 40312, 40313, 40314, 40315, 40316, 40317, 40318, 40319, 40320, 40321, 40322, 40323, 40324, 40325, 40326, 40327, 40328, 40329, 40330, 40331, 40332, 40333, 40334, 40335, 40336, 40337, 40338, 40339, 40340, 40341, 40342, 40343, 40344, 40345, 40346, 40347, 40348, 40349, 40350, 40351, 40352, 40353, 40354, 40355, 40356, 40357, 40358, 40359, 40360, 40361, 40362, 40363, 40364, 40365, 40366, 40367, 40368, 40369, 40370, 40371, 40372, 40373, 40374, 40375, 40376, 40377, 40378, 40379, 40380, 40381, 40382, 40383, 40384, 40385, 40386, 40387, 40388, 40389, lastFailedBuild, lastStableBuild, lastSuccessfulBuild, lastUnstableBuild, lastUnsuccessfulBuild at hudson.model.Run.delete(Run.java:1454) at hudson.tasks.LogRotator.perform(LogRotator.java:129) at hudson.model.Job.logRotate(Job.java:441) at hudson.model.Job$logRotate.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:112) at Script1.run(Script1.groovy:1) at groovy.lang.GroovyShell.evaluate(GroovyShell.java:580) at groovy.lang.GroovyShell.evaluate(GroovyShell.java:618) at groovy.lang.GroovyShell.evaluate(GroovyShell.java:589) at hudson.util.RemotingDiagnostics$Script.call(RemotingDiagnostics.java:139) at hudson.util.RemotingDiagnostics$Script.call(RemotingDiagnostics.java:111) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) at hudson.util.RemotingDiagnostics.executeGroovy(RemotingDiagnostics.java:108) at jenkins.model.Jenkins._doScript(Jenkins.java:3449) at
[JIRA] [core] (JENKINS-16805) Keep this build forever build gets deleted by Discard old builds
robsimon commented on JENKINS-16805 Keep this build forever build gets deleted by Discard old builds Jun 03, 2014 2:32:51 PM FINE hudson.tasks.LogRotator Running the log rotation for hudson.model.FreeStyleProject@338ce0d9jobname with numToKeep=100 daysToKeep=-1 artifactNumToKeep=3 artifactDaysToKeep=-1 Jun 03, 2014 2:32:51 PM FINER hudson.tasks.LogRotator jobname #40287 is not to be removed or purged of artifacts because it’s marked as a keeper Jun 03, 2014 2:32:51 PM FINE hudson.tasks.LogRotator jobname #40285 is to be removed 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-16805) Keep this build forever build gets deleted by Discard old builds
Daniel Beck commented on JENKINS-16805 Keep this build forever build gets deleted by Discard old builds Could you provide some context for the first message with the stack trace? 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-16805) Keep this build forever build gets deleted by Discard old builds
Daniel Beck commented on JENKINS-16805 Keep this build forever build gets deleted by Discard old builds Also, after running it and getting "jobname #40285 is to be removed", is the build still there in Jenkins? On the disk? 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] [copyartifact] (JENKINS-17950) Allow copying artifacts from last (even failed) build
Josh Davidson commented on JENKINS-17950 Allow copying artifacts from last (even failed) build Same issue here. My use case is nearly identical to Drew's. 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-16805) Keep this build forever build gets deleted by Discard old builds
robsimon
commented on JENKINS-16805
Keep this build forever build gets deleted by Discard old builds
stack trace came from Jenkins script console while running: Jenkins.instance.getItemByFullName('xyz').logRotate()
yes, directory for #40285 is still on HDD. It can still be access via file system or Jenkins UI. Compared with legit build directories it starts with a . and is named as follows: .2014-05-19_08-41-18
2013-12-11_10-01-34 build directory which isn't visible in UI
2014-05-19_16-41-19 locked
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-16805) Keep this build forever build gets deleted by Discard old builds
Daniel Beck commented on JENKINS-16805 Keep this build forever build gets deleted by Discard old builds In the regular Jenkins log, there should be an error related to failing to delete files. The '.' gets added when Jenkins removes a build. 2013-12-11_10-01-34 build directory which isn't visible in UI Is there a config.xml file in the directory? What happens to both of these builds when you reload configuration from disk? 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] [vsphere-cloud] (JENKINS-21810) Additional options on slave disconnection
Jason Swager commented on JENKINS-21810 Additional options on slave disconnection Maybe you just need a "Hard Power Down"? If the slave is configured with a snapshot, that snapshot will be reverted to on slave startup as part of a normal startup. 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] [active-directory] (JENKINS-22830) Slow login w/ Active directory plugin
Kohsuke Kawaguchi commented on JENKINS-22830 Slow login w/ Active directory plugin Oh boy. The original change was introduced in response to a bug someone filed indicating that 1.36 didn't list all the groups they should be seeing. I've just spent good time googling the performance of this operator. There are some that reports this is faster than recursive lookup, and others that report this is slower, as in the case of this bug report. Overall, people do seem to favor this recursive search operator over other options. Does anyone know any AD person who can shed some lights on this? Fow now I'm going to introduce a switch that can be used to force one way or the other. 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] [active-directory] (JENKINS-22830) Slow login w/ Active directory plugin
Kohsuke Kawaguchi commented on JENKINS-22830 Slow login w/ Active directory plugin For my internal book-keeping, the original request for this change came from ZD-16865. 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] [job-dsl-plugin] (JENKINS-23289) ClassCastException in JobDSL whith removed Folder
Chris Dore commented on JENKINS-23289 ClassCastException in JobDSL whith removed Folder Funny enough, I also ran into this just today. 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-16805) Keep this build forever build gets deleted by Discard old builds
robsimon commented on JENKINS-16805 Keep this build forever build gets deleted by Discard old builds 1) reloading from disk removed at least #40285 from the Jenkins UI. Why wouldn't it go away by itself without reloading the job configs? 2) 2013-12-11_10-01-34 contains: changelog.xml, log file and timestamper directory which contains timestamps file 3) when will those empty build directories being deleted from HDD which start with . as this job already has 13 of them? 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-16805) Keep this build forever build gets deleted by Discard old builds
Daniel Beck commented on JENKINS-16805 Keep this build forever build gets deleted by Discard old builds 1) reloading from disk removed at least #40285 from the Jenkins UI. Why wouldn't it go away by itself without reloading the job configs? My guess is that the build deletion got interrupted by some Windows process (e.g. your antivirus or search indexer) locking a file. Hence the build was still in memory, but no longer (in the expected location) on disk, so it could not be loaded again. 2) 2013-12-11_10-01-34 contains: changelog.xml, log file and timestamper directory which contains timestamps file No build.xml file, so it cannot be loaded. You should see a warning logged about this on Jenkins startup. 3) when will those empty build directories being deleted from HDD which start with . as this job already has 13 of them? To the best of my knowledge, when you delete them manually. Their existence means the deletion of a build failed. That a failure to delete the dot-build directory causes Jenkins to keep the build in memory seems weird. Should probably be filed as a bug if it's not already. 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-23280) Version 1.554.2 broke reverse proxy
Daniel Beck commented on JENKINS-23280 Version 1.554.2 broke reverse proxy Did you test whether that message also appears in 1.554.2 without hiding Jenkins behind a reverse proxy, or why do you claim that? What's the URL configured in Manage Jenkins » Configure System? HTTP or HTTPS? What happens when you change it? Is your reverse proxy setting the X-Forwarded-Proto header? 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-23243) Add url redirect support for renamed projects
Daniel Beck commented on JENKINS-23243 Add url redirect support for renamed projects https://github.com/jenkinsci/item-forwarder-plugin I really need to release this some time... 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.
