[JIRA] [parameterized-trigger] (JENKINS-20651) File Parameters type causes the encoding of Chinese incorrect and blocks the build
liu fenglan created JENKINS-20651 File Parameters type causes the encoding of Chinese incorrect and blocks the build Issue Type: Bug Assignee: huybrechts Attachments: result.bmp, step1.bmp Components: parameterized-trigger Created: 19/Nov/13 8:18 AM Description: step: 1.Build with the parameters.With one file parameter at least and some of the names or values of the parameters are Chinese. 2.Click "build". result: The build is blocked because of the encoding of Chinese is incorrect. Project: Jenkins Labels: windows build plugin Priority: Major Reporter: liu fenglan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-20651) File Parameters type causes the encoding of Chinese incorrect and blocks the build
liu fenglan updated JENKINS-20651 File Parameters type causes the encoding of Chinese incorrect and blocks the build Change By: liu fenglan (19/Nov/13 8:22 AM) Affects Version/s: current This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jmeter] (JENKINS-4388) jmeter: Added error percentage threshold to set build status to unstable/failed
Ramakrishna Bejawar commented on JENKINS-4388 jmeter: Added error percentage threshold to set build status to unstable/failed Hi aespy Is the plug-in available with this fix, If available Could you Pls kindly share me the plug-in. Even I am facing the same issue. Thanks, RK Bejawar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkinswalldisplay] (JENKINS-20552) Show system messages
howama resolved JENKINS-20552 as Fixed Show system messages Change By: howama (19/Nov/13 9:00 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/groups/opt_out.
[JIRA] [jenkinswalldisplay] (JENKINS-19747) Claim information not shown while re-building
howama resolved JENKINS-19747 as Fixed Claim information not shown while re-building Now shown if the job is re-building and last completed job was claimed. Change By: howama (19/Nov/13 9:03 AM) Status: Open Resolved Assignee: ChristianPelster howama 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/groups/opt_out.
[JIRA] [active-directory] (JENKINS-16429) ComThread is leaking even when its peer is dead
Dennys Hsieh commented on JENKINS-16429 ComThread is leaking even when its peer is dead I found com4j-x86.dll is in %JENKINS_HOME%\plugins\active-directory\WEB-INF\lib, but it still doesn't work. And I try to put com4j-20120426-2.jar (extract from Activedirectory plugin) into jenkins.war (in WEB-INF\lib After restart Jenkins, it works... is this a good solution ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-20599) Handle several testpoints TAP result file
Javier Delgado stopped work on JENKINS-20599 Handle several testpoints TAP result file Change By: Javier Delgado (19/Nov/13 9:31 AM) Status: InProgress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Adam Ocsvari commented on JENKINS-20630 Jenkins fails to start The same here: Windows7 x64, running Jenkins as a service. Before the update to 1.540, it was working fine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20652) RPM package: logrotate not working
Roland Gruber created JENKINS-20652 RPM package: logrotate not working Issue Type: Bug Assignee: Unassigned Components: core Created: 19/Nov/13 9:40 AM Description: The RPM package includes a logrotate configuration. Unfortunately, it is not working. The log file is 0 byte after logrotate runs and nothing is logged any more. I think Jenkins does not get the signal from logrotate or does not cleanly reopen the log file. We have to restart the Jenkins process to get log messages again. root@server ~# ls -l /var/log/jenkins/ total 8252 rw-rr-. 1 jenkins jenkins 0 Nov 5 03:22 jenkins.log rw-rr-. 1 jenkins jenkins 527996 Sep 21 03:27 jenkins.log-20130921.gz rw-rr-. 1 jenkins jenkins 207705 Oct 4 03:24 jenkins.log-20131004.gz rw-rr-. 1 jenkins jenkins 787057 Oct 10 03:34 jenkins.log-20131010.gz Project: Jenkins Priority: Major Reporter: Roland Gruber This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Andy Bigos commented on JENKINS-20630 Jenkins fails to start +1. Running Win6 x64 as a service and got the same errors. Reverting to 1.539 works. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobconfighistory] (JENKINS-20511) hudson.maven.MavenBuild MissingFieldException: No field 'targetType' found in class 'hudson.plugins.jobConfigHistory.JobConfigBadgeAction'
Oleg Nenashev commented on JENKINS-20511 hudson.maven.MavenBuild MissingFieldException: No field targetType found in class hudson.plugins.jobConfigHistory.JobConfigBadgeAction The error also spams to "System errors log" in Monitoring plugin... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15873) Build ICONs are broken for Anonymous user when given read access
evernat commented on JENKINS-15873 Build ICONs are broken for Anonymous user when given read access Is it reproduced with a recent Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xcode] (JENKINS-20653) support xctool to build without xcodebuild
Daniel Chen created JENKINS-20653 support xctool to build without xcodebuild Issue Type: New Feature Affects Versions: current Assignee: Unassigned Components: xcode Created: 19/Nov/13 11:52 AM Description: support build project without xcodebuild, but with xctool. https://github.com/facebook/xctool Project: Jenkins Priority: Major Reporter: Daniel Chen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-flow] (JENKINS-20645) Build-flow plugin does not expose P4_CHANGELIST
Michael Rose commented on JENKINS-20645 Build-flow plugin does not expose P4_CHANGELIST That worked, Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-flow] (JENKINS-20645) Build-flow plugin does not expose P4_CHANGELIST
Michael Rose commented on JENKINS-20645 Build-flow plugin does not expose P4_CHANGELIST It would be nice if this was documented. I spent a lot of time search for this information before finally giving up and asking (though now the next person that search would eventually find this ticket). The only clue I found was in the build-flow plugin release 0.4 release notes: ... add groovy bindings for current build as "build", console output as "out", environment variables Map as "env", and triggered parameters of current build as "params" This seems misleading. When I print env from within the dsl script I get an empty map. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [slave-setup] (JENKINS-20654) Empty folders are not copied to the slave
Christian Frommeyer created JENKINS-20654 Empty folders are not copied to the slave Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: slave-setup Created: 19/Nov/13 12:16 PM Description: When copying files to the slaves the slave-setup-plugin misses directories that do not contain ordinary files. The reason seems to be that the plugin uses the copyRecursiveTo method of the FilePath class to copy the files (Line 92 in SetupDeployer). The implementation of this method only acts upon files and then creates parent directories (Line 1895-1900 of FilePath). This results in creating only directories that contain directly or indirectly files. Environment: Slave-Setup-Plugin 1.6; Jenkins 1.537; Linux; JBoss 7.1 Project: Jenkins Priority: Major Reporter: Christian Frommeyer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [config-file-provider] (JENKINS-15976) Provided maven settings.xml in maven builder is lost
Brett Delle Grazie updated JENKINS-15976 Provided maven settings.xml in maven builder is lost Change By: Brett Delle Grazie (19/Nov/13 12:19 PM) Labels: LTS This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [config-file-provider] (JENKINS-15976) Provided maven settings.xml in maven builder is lost
Brett Delle Grazie commented on JENKINS-15976 Provided maven settings.xml in maven builder is lost Hi, I've added LTS as this bug effects current LTS 1.509.4 Will the fix for this cleanly apply to current LTS? (1.509.4) or do we need to wait for LTS RC (1.532.1)? This particular issue is breaking several things in our setup. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-tracker] (JENKINS-20655) Unable to start the Jenkins applicaiton
praveen Jaikumar created JENKINS-20655 Unable to start the Jenkins applicaiton Issue Type: Bug Assignee: Unassigned Components: jenkins-tracker, jobgenerator Created: 19/Nov/13 12:55 PM Description: Since the logs are generting a huge space tried to create a soft link and moved the files to another location. After creating the soft link i am unable to bring up the jenkins. So i copied the file back but still i am unable to bring up the jenkins. PLease help me with this. I am also not sure where to find the logs.(its not in var Find the logs below: 11/19/13 5:51:51:415 CST 001a InitReactorRu E Failed LogRecorderManager.init java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.init.InitializerFinder.invoke(InitializerFinder.java:124) at hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:893) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919) at java.lang.Thread.run(Thread.java:736) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120) ... 8 more Caused by: hudson.util.IOException2: Unable to read /home/webadmin/.jenkins/log/Audit Trail.xml at hudson.XmlFile.unmarshal(XmlFile.java:168) at hudson.logging.LogRecorder.load(LogRecorder.java:260) at hudson.logging.LogRecorderManager.load(LogRecorderManager.java:99) at hudson.logging.LogRecorderManager.init(LogRecorderManager.java:194) ... 13 more Caused by: com.thoughtworks.xstream.io.StreamException: : input contained no data at com.thoughtworks.xstream.io.xml.XppReader.pullNextEvent(XppReader.java:126) at com.thoughtworks.xstream.io.xml.AbstractPullReader.readRealEvent(AbstractPullReader.java:148) at com.thoughtworks.xstream.io.xml.AbstractPullReader.readEvent(AbstractPullReader.java:141) at com.thoughtworks.xstream.io.xml.AbstractPullReader.move(AbstractPullReader.java:118) at com.thoughtworks.xstream.io.xml.AbstractPullReader.moveDown(AbstractPullReader.java:103) at com.thoughtworks.xstream.io.xml.XppReader.init(XppReader.java:63) at com.thoughtworks.xstream.io.xml.AbstractXppDriver.createReader(AbstractXppDriver.java:54) at com.thoughtworks.xstream.io.xml.AbstractXppDriver.createReader(AbstractXppDriver.java:65) at hudson.XmlFile.unmarshal(XmlFile.java:166) ... 16 more Caused by: java.io.EOFException: input contained no data at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:3003) at org.xmlpull.mxp1.MXParser.more(MXParser.java:3046) at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1410) at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1395) at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093) at com.thoughtworks.xstream.io.xml.XppReader.pullNextEvent(XppReader.java:109) ... 24 more 11/19/13 5:51:51:447 CST 001b WebAppMainE Failed to initialize Jenkins org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:246) at jenkins.InitReactorRunner.run(InitReactorRunner.java:43) at jenkins.model.Jenkins.executeReactor(Jenkins.java:904)
[JIRA] [copyartifact] (JENKINS-14999) Copy Artifact plugin: Unable to find project for artifact copy when using a build parameter
SCM/JIRA link daemon commented on JENKINS-14999 Copy Artifact plugin: Unable to find project for artifact copy when using a build parameter Code changed in jenkins User: ikedam Path: src/main/java/hudson/plugins/copyartifact/CopyArtifact.java src/test/java/hudson/plugins/copyartifact/CopyArtifactTest.java src/test/resources/hudson/plugins/copyartifact/CopyArtifactTest/testPerProjectPermissionTriggeredByUser/config.xml src/test/resources/hudson/plugins/copyartifact/CopyArtifactTest/testPerProjectPermissionTriggeredByUser/users/admin/config.xml src/test/resources/hudson/plugins/copyartifact/CopyArtifactTest/testPerProjectPermissionTriggeredByUser/users/test1/config.xml src/test/resources/hudson/plugins/copyartifact/CopyArtifactTest/testPerProjectPermissionTriggeredByUser/users/test2/config.xml http://jenkins-ci.org/commit/copyartifact-plugin/ce20ba90919582a0c6cc3b262f7d6cbbb7b36f5e Log: JENKINS-14999 Reverted unintended merging of #24. I'll handle this problem using QueueItemAuthenticator instead. Reverted 6f920cde153c03383271b0a1435528f21c723a88 and 46540cc88dee2ecc56ede5c389b48e4f89d1c539 . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [delivery-pipeline] (JENKINS-20588) consider Trigger/call builds on other projects from the Build configuration
Patrik Boström resolved JENKINS-20588 as Fixed consider Trigger/call builds on other projects from the Build configuration Fixed https://github.com/Diabol/delivery-pipeline-plugin/commit/4124b409ef6ec53297688c488067817abea3fb00 Change By: Patrik Boström (19/Nov/13 1:20 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/groups/opt_out.
[JIRA] [git] (JENKINS-20643) Git plugin does not work with Visual Studio Online
Mark Waite commented on JENKINS-20643 Git plugin does not work with Visual Studio Online I can duplicate the problem and believe there is a work around. If the additional behavior "Force polling using workspace" is added to the Git plugin configuration for the specific job, then I can clone my TFS repository from the Jenkins job. If I don't add the additional behavior "Force polling using workspace", then the job definition page shows the same error as described in the bug report. In both those cases, I defined a global credential with my Visual Studio Online user name and password, and used that credential in the Git plugin configuration for the job. I also can avoid that message if I embed the username and password in the Git URL, though that is much less attractive, since it places the username and password in cleartext in the job definition. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20643) Git plugin does not work with Visual Studio Online
Mark Waite updated JENKINS-20643 Git plugin does not work with Visual Studio Online Change By: Mark Waite (19/Nov/13 1:31 PM) Priority: Blocker Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20643) Git plugin does not work with Visual Studio Online
Mark Waite edited a comment on JENKINS-20643 Git plugin does not work with Visual Studio Online I can duplicate the problem and believe there is a work around. If the additional behavior "Force polling using workspace" is added to the Git plugin configuration for the specific job, then I can clone my Visual Studio Online git repository from the Jenkins job. If I don't add the additional behavior "Force polling using workspace", then the job definition page shows the same error as described in the bug report. In both those cases, I defined a global credential with my Visual Studio Online user name and password, and used that credential in the Git plugin configuration for the job. I also can avoid that message if I embed the username and password in the Git URL, though that is much less attractive, since it places the username and password in cleartext in the job definition. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20643) Git plugin does not work with Visual Studio Online
Mark Waite edited a comment on JENKINS-20643 Git plugin does not work with Visual Studio Online I can duplicate the problem and believe there is a work around. If the additional behavior "Force polling using workspace" is added to the Git plugin configuration for the specific job, then I can clone my Visual Studio Online git repository from the Jenkins job. If I don't add the additional behavior "Force polling using workspace", then the job definition page shows the same error as described in the bug report until I add a global credential for Visual Studio Online. Once I've added the global credential for Visual Studio Online and referenced it in the plugin definition for that job, then the "ls-remote" message disappears on the Linux machine I'm using as master server. It may yet happen on a Windows server. In each of those cases, I defined a global credential with my Visual Studio Online user name and password, and used that credential in the Git plugin configuration for the job. I also can avoid that message if I embed the username and password in the Git URL, though that is much less attractive, since it places the username and password in cleartext in the job definition. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-16995) NullPointerException when viewing test results
Jarkko Palviainen commented on JENKINS-16995 NullPointerException when viewing test results We noticed that the trigger seems to be renaming a (multiconfiguration) job. After jenkins restarts, the symptom appears. Also, copying the broken job to another name carries the bug to the new one. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20656) Viewing test report while set to russian locale causes stack trace/failure
Nathan Neulinger created JENKINS-20656 Viewing test report while set to russian locale causes stack trace/failure Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: Jenkins Error.png, jenkins-stack-trace.txt Components: core Created: 19/Nov/13 1:39 PM Description: Error does not occur on English/default locale. Project: Jenkins Priority: Minor Reporter: Nathan Neulinger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20656) Viewing test report while set to russian locale causes stack trace/failure
Nathan Neulinger commented on JENKINS-20656 Viewing test report while set to russian locale causes stack trace/failure local ticket: ENGOP-426 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20643) Git plugin does not work with Visual Studio Online
Mark Waite edited a comment on JENKINS-20643 Git plugin does not work with Visual Studio Online I can duplicate the problem and believe there is a work around. If the additional behavior "Force polling using workspace" is added to the Git plugin configuration for the specific job, then I can clone my Visual Studio Online git repository from the Jenkins job. If I don't add the additional behavior "Force polling using workspace", then the job definition page shows the same error as described in the bug report until I add a global credential for Visual Studio Online. Once I've added the global credential for Visual Studio Online and referenced it in the plugin definition for that job, then the "ls-remote" message disappears on the Linux machine I'm using as master server. It may yet happen on a Windows server. In each of those cases, I defined a global credential with my Visual Studio Online user name and password, and used that credential in the Git plugin configuration for the job. I also can avoid that message if I embed the username and password in the Git URL, though that is much less attractive, since it places the username and password in cleartext in the job definition. The multi-configuration job which I defined with https://markewaite.visualstudio.com/DefaultCollection/_git/JENKINS-20643 as the repository and my Visual Studio Online credentials was able launch on a Windows Home Server 2011 (initial workspace), and cloned successfully on Windows 7, Windows 8.1, Windows Home Server 2011 with x64 JRE, Windows Home Server 2011 with x86 JRE, Debian Wheezy, and Debian Jessie. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20643) Git plugin does not work with Visual Studio Online
Mark Waite edited a comment on JENKINS-20643 Git plugin does not work with Visual Studio Online I can duplicate the problem and believe there is a work around. If the additional behavior "Force polling using workspace" is added to the Git plugin configuration for the specific job, then I can clone my Visual Studio Online git repository from the Jenkins job. If I don't add the additional behavior "Force polling using workspace", then the job definition page shows the same error as described in the bug report until I add a global credential for Visual Studio Online. Once I've added the global credential for Visual Studio Online and referenced it in the plugin definition for that job, then the "ls-remote" message disappears on the Linux machine I'm using as master server. It may yet happen on a Windows server. In each of those cases, I defined a global credential with my Visual Studio Online user name and password, and used that credential in the Git plugin configuration for the job. I also can avoid that message if I embed the username and password in the Git URL, though that is much less attractive, since it places the username and password in cleartext in the job definition. The multi-configuration job which I defined with https://markewaite.visualstudio.com/DefaultCollection/_git/JENKINS-20643 as the repository and my Visual Studio Online credentials was able launch on a Windows Home Server 2011 (initial workspace), and cloned successfully on Windows 7, Windows 8.1, Windows Home Server 2011 with x64 JRE, Windows Home Server 2011 with x86 JRE, Debian Wheezy, and Debian Jessie. I used the git command line implementation for all the job definitions up to this point. When I switched to use the JGit implementation for a new multi-configuration job definition, the clone hangs on both Windows Home Server 2011 and on Windows 7 slave agents. That needs more investigation and a separate bug report. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-19979) DSL plugin 1.18 causes NPEs when saving or creating new jobs.
Marco Krikke commented on JENKINS-19979 DSL plugin 1.18 causes NPEs when saving or creating new jobs. Related thread: https://groups.google.com/forum/#!topic/job-dsl-plugin/A62YdsncdgM The issues described disappeared for me after upgrading to Jenkins 1.540 and applying the workaround suggested by Jake. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20643) Git plugin does not work with Visual Studio Online
Mark Waite edited a comment on JENKINS-20643 Git plugin does not work with Visual Studio Online I can duplicate the problem and believe there is a work around. If the additional behavior "Force polling using workspace" is added to the Git plugin configuration for the specific job, then I can clone my Visual Studio Online git repository from the Jenkins job. If I don't add the additional behavior "Force polling using workspace", then the job definition page shows the same error as described in the bug report until I add a global credential for Visual Studio Online. Once I've added the global credential for Visual Studio Online and referenced it in the plugin definition for that job, then the "ls-remote" message disappears on the Linux machine I'm using as master server. It may yet happen on a Windows server. In each of those cases, I defined a global credential with my Visual Studio Online user name and password, and used that credential in the Git plugin configuration for the job. I also can avoid that message if I embed the username and password in the Git URL, though that is much less attractive, since it places the username and password in cleartext in the job definition. The multi-configuration job which I defined with https://markewaite.visualstudio.com/DefaultCollection/_git/JENKINS-20643 as the repository and my Visual Studio Online credentials was able launch on a Windows Home Server 2011 (initial workspace), and cloned successfully on Windows 7, Windows 8.1, Windows Home Server 2011 with x64 JRE, Windows Home Server 2011 with x86 JRE, Debian Wheezy, and Debian Jessie. I used the git command line implementation for all the job definitions up to this point. When I switched to use the JGit implementation for a new multi-configuration job definition, the clone hung on both Windows Home Server 2011 and on Windows 7 slave agents. That needs more investigation and a separate bug report. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-20657) GIT throws an exception after setting repo URL
nomar morado created JENKINS-20657 GIT throws an exception after setting repo URL Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git-client Created: 19/Nov/13 2:05 PM Description: After i enter the repo URL the stacktrace is show below: Stack trace javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:777) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:841) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:727) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:841) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:727) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:841) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:630) at org.kohsuke.stapler.Stapler.service(Stapler.java:224) at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) at org.apache.catalina.ha.session.JvmRouteBinderValve.invoke(JvmRouteBinderValve.java:219) at org.apache.catalina.ha.tcp.ReplicationValve.invoke(ReplicationValve.java:333) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) at org.apache.catalina.valves.StuckThreadDetectionValve.invoke(StuckThreadDetectionValve.java:193) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
[JIRA] [jenkins-tracker] (JENKINS-20655) Unable to start the Jenkins applicaiton
praveen Jaikumar updated JENKINS-20655 Unable to start the Jenkins applicaiton Change By: praveen Jaikumar (19/Nov/13 2:29 PM) Description:
[JIRA] [security] (JENKINS-14313) login page redirects to login page
Thomas Demande commented on JENKINS-14313 login page redirects to login page Exact same issue for me (for a long time). Without Overall read permission for anonymous = login box after a successful login. If I add the anonymous Overall read permission = works as expected. Doesn't work even in Firefox. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [warnings] (JENKINS-20658) All builds that were using GMU Make + GCC now fail
James Howe created JENKINS-20658 All builds that were using GMU Make + GCC now fail Issue Type: Bug Assignee: Ulli Hafner Components: warnings Created: 19/Nov/13 3:15 PM Description: Upgrading to 4.37 and all my job configs have had the warning parser removed, resulting in every job failing with this exception. ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception java.io.IOException: Error: No warning parsers defined in the job configuration. at hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:316) at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:333) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:781) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:753) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706) at hudson.model.Run.execute(Run.java:1704) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) Project: Jenkins Priority: Critical Reporter: James Howe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [warnings] (JENKINS-20658) All builds that were using GNU Make + GCC now fail
James Howe updated JENKINS-20658 All builds that were using GNU Make + GCC now fail Change By: James Howe (19/Nov/13 3:18 PM) Summary: Allbuildsthatwereusing GMU GNU Make+GCCnowfail This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [accurev] (JENKINS-20507) Accurev plugin won't update latest code from accurev
Wilfredo Velazquez commented on JENKINS-20507 Accurev plugin wont update latest code from accurev I am seeing the same issue. Windows Server 2008, running Jenkins 1.539 I can verify that this broke as of plugin version 0.6.19 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Jonathan Johnson commented on JENKINS-20630 Jenkins fails to start Confirmed: There is something wrong with 1.540 that causes the JVM it to crash on Windows just after startup. I have a very similar issue. Windows 8, java 7_45, downloaded the latest Windows install of Jenkins version 1.540. Ran the the msi install and ran this command as administrator: C:\Program Files (x86)\Jenkinsjava -jar jenkins.war When it got to "INFO: Loaded all jobs" in the command console log output the JVM crashed and popped up a Java Virtual Machine has unexpected shut down dialog message. After a few more ties with no success I downloaded the previous build 1.539 war file from http://mirrors.jenkins-ci.org/war/1.539/ Overwrote C:\Program Files (x86)\Jenkinsjenkins.war Ran this again C:\Program Files (x86)\Jenkinsjava -jar jenkins.war and Jenkins started normally. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [warnings] (JENKINS-20658) All builds that were using GNU Make + GCC now fail
Ulli Hafner commented on JENKINS-20658 All builds that were using GNU Make + GCC now fail Did you also upgrade to 4.36? Or did you upgrade from 4.35? Can you please attach one of your Job config.xml files? Did you save or touch the job configurations after the upgrade? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [warnings] (JENKINS-20658) All builds that were using GNU Make + GCC now fail
Ulli Hafner edited a comment on JENKINS-20658 All builds that were using GNU Make + GCC now fail Did you also upgrade from 4.36? Or did you upgrade from 4.35? Can you please attach one of your Job config.xml files? Did you save or touch the job configurations after the upgrade? Is there a parser selected if you configure your job? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [warnings] (JENKINS-20658) All builds that were using GNU Make + GCC now fail
Ulli Hafner edited a comment on JENKINS-20658 All builds that were using GNU Make + GCC now fail Did you also upgrade from 4.36? Or did you upgrade from 4.35? Can you please attach one of your Job config.xml files? Did you save or touch the job configurations after the upgrade? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [accurev] (JENKINS-20507) Accurev plugin won't update latest code from accurev
Wilfredo Velazquez updated JENKINS-20507 Accurev plugin wont update latest code from accurev Change By: Wilfredo Velazquez (19/Nov/13 3:49 PM) Priority: Major Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [warnings] (JENKINS-20658) All builds that were using GNU Make + GCC now fail
James Howe commented on JENKINS-20658 All builds that were using GNU Make + GCC now fail Started on 4.35. Upgraded to 4.36. Restarted. All jobs failing. Config shows the parsing step is there, but no parser listed. Upgraded to 4.37 as it looked like there was a fix. Restarted. No change in problem. Downgraded to 4.28 (latest available at http://updates.jenkins-ci.org/download/plugins/warnings/). Everything fine again. config.xml has the following section. consoleParsers hudson.plugins.warnings.ConsoleParser parserNameGNU Make + GNU Compiler (gcc)/parserName /hudson.plugins.warnings.ConsoleParser /consoleParsers This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-10537) java.net.SocketTimeoutException: Read timed out
Kyle Leinen commented on JENKINS-10537 java.net.SocketTimeoutException: Read timed out My team is also seeing this. We are running Jenkins 1.538 with slave version 2.32. The master server is RHEL6 with Oracle Java 1.7.0_05 and the slaves are Win7 running Oracle Java 1.7.0_05. Across 25 JNLP nodes, we see around 10 drop-offs per week. We are seeing the same exception as the others reports above. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [plugin] (JENKINS-20659) Job Import plugin is unable to import jobs from cross linux platforms
Sai Anvesh Ganguri created JENKINS-20659 Job Import plugin is unable to import jobs from cross linux platforms Issue Type: Bug Assignee: Unassigned Attachments: 11-19-2013 11-43-45 AM.png Components: plugin Created: 19/Nov/13 4:51 PM Description: We are trying to import jobs from jenkins instance in SUSE to UBUNTU. The job import plugin fails to import jobs with the error "Not a Project". Please find the attachment. Any ideas/suggestions are appreciated. Thanks in advance Project: Jenkins Priority: Major Reporter: Sai Anvesh Ganguri This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Brandon Oakley commented on JENKINS-20630 Jenkins fails to start Having the same issue running Jenkins 1.540 on Tomcat 7.0.47 on Windows Server 2008 R2 Standard. Tomcat is running as a Windows Service. Once I downgraded to 1.539 it starts up perfectly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [warnings] (JENKINS-20658) All builds that were using GNU Make + GCC now fail
SCM/JIRA link daemon resolved JENKINS-20658 as Fixed All builds that were using GNU Make + GCC now fail Change By: SCM/JIRA link daemon (19/Nov/13 5: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/groups/opt_out.
[JIRA] [warnings] (JENKINS-20658) All builds that were using GNU Make + GCC now fail
Ulli Hafner commented on JENKINS-20658 All builds that were using GNU Make + GCC now fail Sorry, I missed this parser in the last fix. Release 4.38 is in progress and will appear in some minutes... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [warnings] (JENKINS-20658) All builds that were using GNU Make + GCC now fail
SCM/JIRA link daemon commented on JENKINS-20658 All builds that were using GNU Make + GCC now fail Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/warnings/parser/GnuMakeGccParser.java src/test/java/hudson/plugins/warnings/parser/ParserRegistryIntegrationTest.java http://jenkins-ci.org/commit/warnings-plugin/c96cad82d6fb69d3c7b5f01e8f1dacf8b1c41b02 Log: FIXED JENKINS-20658 Added old parser name as ID for make+gcc parser. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xshell] (JENKINS-20660) xshell: hudson.plugins.xshell.XShellBuilder.perform after updating to version 0.9
Kevin Wojniak created JENKINS-20660 xshell: hudson.plugins.xshell.XShellBuilder.perform after updating to version 0.9 Issue Type: Bug Assignee: Unassigned Components: xshell Created: 19/Nov/13 5:35 PM Description: I updated Jenkins to 1.540 and XShell to 0.9. Whenever I do a build I get an exception: Started by upstream project "MyProject" build number 560 originally caused by: Started by user Kevin Wojniak Building on master in workspace http://127.0.0.1:8080/job/MyProject/myproject=master/ws/ Fetching changes from the remote Git repository Fetching upstream changes from ssh://user@server/git/MyProject Checking out Revision fb1f25fe51ea374f732147c9dd2fef328e1b805c (origin/master) Cleaning workspace Resetting working tree FATAL: null java.lang.NullPointerException at java.util.regex.Pattern.init(Pattern.java:1132) at java.util.regex.Pattern.compile(Pattern.java:823) at hudson.plugins.xshell.XShellBuilder.perform(XShellBuilder.java:122) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) 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:566) at hudson.model.Run.execute(Run.java:1679) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) If I downgrade to 0.8 it works fine again. Environment: OS X 10.8.5 Project: Jenkins Priority: Blocker Reporter: Kevin Wojniak This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xshell] (JENKINS-20660) xshell: java.lang.NullPointerException from regex after updating to version 0.9
Kevin Wojniak updated JENKINS-20660 xshell: java.lang.NullPointerException from regex after updating to version 0.9 Change By: Kevin Wojniak (19/Nov/13 5:38 PM) Summary: xshell: hudson java . plugins lang . xshell.XShellBuilder.perform NullPointerExceptionfromregex afterupdatingtoversion0.9 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Gemini A updated JENKINS-20630 Jenkins fails to start Fails to start: Windows 2008 server running Apache Tomcat 7 Apache Tomcat 7 crashes Change By: Gemini A (19/Nov/13 6:09 PM) Attachment: hs_err_pid1000.log This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-flow] (JENKINS-20645) Build-flow plugin does not expose P4_CHANGELIST
Rob Petti commented on JENKINS-20645 Build-flow plugin does not expose P4_CHANGELIST I came up with the sample above by reading the documentation, though I agree that it could be clearer. You have to read the javadocs in order to get all the necessary information, but that shouldn't be required for an end-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/groups/opt_out.
[JIRA] [build-flow] (JENKINS-20645) Build-flow plugin does not expose P4_CHANGELIST
Rob Petti resolved JENKINS-20645 as Fixed Build-flow plugin does not expose P4_CHANGELIST Updated the build-flow wiki with this information. Change By: Rob Petti (19/Nov/13 6:28 PM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18828) Jobs disappear
Joe Mihalich commented on JENKINS-18828 Jobs disappear Hi, is anyone looking into this problem? I'm stuck on build 522 and cannot upgrade. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-flow] (JENKINS-20645) Build-flow plugin does not expose P4_CHANGELIST
Michael Rose
edited a comment on JENKINS-20645
Build-flow plugin does not expose P4_CHANGELIST
For future reference, what documentation are you referring to?
I was led astray by:
You can also access some pre-defined variables in the DSL :
"build" the current flow execution
"out" the flow build console
"env" the flow environment, as a Map
"params" triggered parameters
"upstream" the upstream job, assuming the flow has been triggered as a downstream job for another job.
So I tried env and found it was empty, then tried build.env and found it didn't exist. I didn't even think to inspect the build object further with *build.properties.each { out.println "$it.key - $it.value" }*
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-flow] (JENKINS-20645) Build-flow plugin does not expose P4_CHANGELIST
Michael Rose
commented on JENKINS-20645
Build-flow plugin does not expose P4_CHANGELIST
For future reference, what documentation are you referring to?
I was led astray by:
You can also access some pre-defined variables in the DSL :
"build" the current flow execution
"out" the flow build console
"env" the flow environment, as a Map
"params" triggered parameters
"upstream" the upstream job, assuming the flow has been triggered as a downstream job for another job.
So I tried env and found it was empty, then tried build.env and found it didn't exist. I didn't even think to inspect the build object further with build.properties.each { out.println "$it.key - $it.value" }
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [conditional-buildstep] (JENKINS-20543) error on delete job - java.lang.NoSuchMethodError: org.jenkinsci.plugins.conditionalbuildstep.ConditionalBuildStepHelper
javydreamercsw commented on JENKINS-20543 error on delete job - java.lang.NoSuchMethodError: org.jenkinsci.plugins.conditionalbuildstep.ConditionalBuildStepHelper Same for me. I'm running Jenkins 1.539 and 1.3.2. Looks like I installed 1.3.3 but haven't reset yet. Will report back. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [master-slave] (JENKINS-20107) master using more executors than specified
martin naughton commented on JENKINS-20107 master using more executors than specified if you set the number of executors to 2 will it run more than 2 jobs? Is this only specific to setting to 4 executors? In your picture it has 5 executing jobs. the fifth one does not have a number assigned to it. others have the number 1,2,3,4 assigned. Is it always just an extra ghost job or can it be more? It is always happening? Can you run with 2 and see if any more ghosts appear? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-flow] (JENKINS-20645) Build-flow plugin does not expose P4_CHANGELIST
Rob Petti
commented on JENKINS-20645
Build-flow plugin does not expose P4_CHANGELIST
'env' is the environment for the build flow job itself, not the job(s) the build flow runs. There should be something here, but I'm not sure why it would be empty. In any case, I don't see how it would be useful at all. :/
It was pretty vague:
You can pass parameters to jobs, and get the resulting AbstractBuild when required
AbstractBuilds have their own interface, which you can find on the javadoc at http://javadoc.jenkins-ci.org/. One of these functions is getEnvironment, which can simply be referenced as "b.environment", because groovy automatically calls getters if a member field isn't accessible. getEnvironment returns a Map object.
Putting it all together gives you 'b.environment.get("P4_CHANGELIST")'.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [master-slave] (JENKINS-15875) Cannot change Usage setting of master jenkins
martin naughton commented on JENKINS-15875 Cannot change Usage setting of master jenkins any update on this? If not i will close it since i see it working in the latest. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-flow] (JENKINS-20645) Build-flow plugin does not expose P4_CHANGELIST
Michael Rose commented on JENKINS-20645 Build-flow plugin does not expose P4_CHANGELIST Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [master-slave] (JENKINS-15875) Cannot change Usage setting of master jenkins
martin naughton started work on JENKINS-15875 Cannot change Usage setting of master jenkins Change By: martin naughton (19/Nov/13 6:53 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/groups/opt_out.
[JIRA] [master-slave] (JENKINS-12668) Slave uses wrong workspace for building a project and fails
martin naughton commented on JENKINS-12668 Slave uses wrong workspace for building a project and fails update on this? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-18759) Build Pipeline Plugin no longer maintaining parameters on Retry
Andrew Lazarus commented on JENKINS-18759 Build Pipeline Plugin no longer maintaining parameters on Retry I'm having the same retry problem with Jenkins 1.540 and plugin version 1.4.2. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18828) Jobs disappear
Joe Mihalich commented on JENKINS-18828 Jobs disappear Hey, anyone following this ticket. The issue here is the same as another reported issue: JENKINS-19398. Enable the javadoc plugin in jenkins, and the problem is solved. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Akira Yamamoto edited a comment on JENKINS-20630 Jenkins fails to start Same here: Windows Server 2008 R2 x64, running Jenkins as a service. Before the update to 1.540, it was working fine. java version "1.7.0_45" Java(TM) SE Runtime Environment (build 1.7.0_45-b18) Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Akira Yamamoto commented on JENKINS-20630 Jenkins fails to start Same here: Windows Server 2008 R2 x64, running Jenkins as a service. Before the update to 1.540, it was working fine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Joseph S commented on JENKINS-20630 Jenkins fails to start Same here, new windows 2012 box, just to run jenkins, Java crashes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Build Team updated JENKINS-20630 Jenkins fails to start jenkins.out.logs shows Problematic frame: C ntdll.dll+0x2df85 Change By: Build Team (19/Nov/13 7:22 PM) Attachment: hs_err_pid4968.log Attachment: jenkins.out.log This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Build Team commented on JENKINS-20630 Jenkins fails to start Having a similar issue with 1.540 in Standalone mode i.e. Jenkins service fails to start. The log "jenkins.out.log" shows this Problematic frame: C ntdll.dll+0x2df85 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Joseph S edited a comment on JENKINS-20630 Jenkins fails to start Same here, new Windows 2012 box, just to run Jenkins, Java crashes. As said before, latest 1.540 doesn't work. Rolled back to 1.539 and works just fine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Akira Yamamoto edited a comment on JENKINS-20630 Jenkins fails to start Same here: Windows Server 2008 R2 x64, running Jenkins as a service. Before the update to 1.540, it was working fine. java version "1.7.0_45" Java(TM) SE Runtime Environment (build 1.7.0_45-b18) Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode) There is a file jenkins.war.bak you can use it to restore to previous version. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Build Team edited a comment on JENKINS-20630 Jenkins fails to start Having a similar issue with 1.540 in Standalone mode i.e. Jenkins service fails to start. The log "jenkins.out.log" shows this Problematic frame: C ntdll.dll+0x2df85 Windows Server 2008 Standard R2 x64 Service Pack 1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Build Team edited a comment on JENKINS-20630 Jenkins fails to start Having a similar issue with 1.540 in Standalone mode i.e. Jenkins service fails to start. The log "jenkins.out.log" shows this Problematic frame: C ntdll.dll+0x2df85 Windows Server 2008 R2 Standard This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20661) Throwing AbortException in Publisher prints stacktrace
Mathieu Wang created JENKINS-20661 Throwing AbortException in Publisher prints stacktrace Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 19/Nov/13 7:30 PM Description: When an AbortException is thrown by any Publisher's "perform" method, the stacktrace is printed on the build's console output. AbstractBuild.AbstractBuildExecution#performAllBuildSteps catches all Exceptions and prints the stacktrace. Should add a catch clause for AbortException. Project: Jenkins Priority: Minor Reporter: Mathieu Wang This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-15898) Subversion back-end cannot handle renaming of jobs
Gavin Kingsley commented on JENKINS-15898 Subversion back-end cannot handle renaming of jobs This issue seems to impact us whenever a job is deleted. Currently have plug in version 0.0.7.3. Nov 20, 2013 8:39:12 AM hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy SEVERE: deleteHierarchy Problem during remove : SVN remove failed. Nov 20, 2013 8:39:12 AM hudson.plugins.scm_sync_configuration.SCMManipulator FINE: Deleting SCM hierarchy C:\Program Files\Jenkins\scm-sync-configuration\checkoutConfiguration\jobs\Update Qt on 1840-vpc-build1 from SCM ... Nov 20, 2013 8:39:12 AM hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness FINEST: Processing commit : Commit hudson.plugins.scm_sync_configuration.model.Commit@14c3977 : Author : Adam Gregory Comment : SPR 22718: Job Update Qt hierarchy renamed from jobs/Update Qt on 1840-vpc-build1 to jobs/Update Qt by agregory Changeset : A config.xml A jobs/Update Qt/ D jobs/Update Qt on 1840-vpc-build1/ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20662) When triggering a new build from current build page, 'Next Build' isn't shown after reloading page
Daniel Beck created JENKINS-20662 When triggering a new build from current build page, Next Build isnt shown after reloading page Issue Type: Bug Assignee: Unassigned Components: core Created: 19/Nov/13 7:59 PM Description: 1. Create a freestyle project 'foo' with a shell build step that executes sleep 30 and save. 2. Click 'Build Now' 3. Go to the build's page (/job/foo/1) and wait until the build finishes. 4. From the breadcrumb bar, select 'Build Now' from the 'foo' job's context menu. 5. Wait a second (so the build is actually started), then reload. Expected result: 'Next Build' link is shown Actual result: It's not If you open the job's main page at /job/foo e.g. in another tab, then reload the build page again, the 'Next Build' link appears after reloading. Environment: 1.532.1-rc1, 1.540 Project: Jenkins Labels: lazy-loading Priority: Major Reporter: Daniel Beck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20662) When triggering a new build from current build page, 'Next Build' isn't shown after reloading page
Daniel Beck updated JENKINS-20662 When triggering a new build from current build page, Next Build isnt shown after reloading page Change By: Daniel Beck (19/Nov/13 8:04 PM) Environment: 1.532.1-rc1,1.540 ,1.533,1.500 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Joseph S edited a comment on JENKINS-20630 Jenkins fails to start Same here, new Windows 2012 box, just to run Jenkins, Java crashes. As said before, latest 1.540 doesn't work. Rolled back to 1.539 and works just fine. Windows Server 2012 Standard Build 9200 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [repo] (JENKINS-17913) Need to evaluate ${param} in any configuration fields
Arvid E.P
resolved JENKINS-17913 as Fixed
Need to evaluate ${param} in any configuration fields
fixed in 1.6
Change By:
Arvid E.P
(19/Nov/13 8:36 PM)
Status:
Open
Resolved
Assignee:
ArvidE.P
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/groups/opt_out.
[JIRA] [core] (JENKINS-19099) Slow loading and large memory usage after 1.480.3 to 1.509.2 migration
Sean Whyte commented on JENKINS-19099 Slow loading and large memory usage after 1.480.3 to 1.509.2 migration I put a bounty on this on FreedomSponcors if someone can get this done this year. http://www.freedomsponsors.org/core/issue/408/slow-loading-and-large-memory-usage-after-14803-to-15092-migration This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [repo] (JENKINS-13720) The manifest branch, file other parameters should evaluate input parameters
Arvid E.P resolved JENKINS-13720 as Duplicate The manifest branch, file other parameters should evaluate input parameters Change By: Arvid E.P (19/Nov/13 8:38 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [conditional-buildstep] (JENKINS-13705) Builds are sequential when there is a Run conditional step build step, even though the project is configured for concurrent execution
Oleg Nenashev updated JENKINS-13705 Builds are sequential when there is a Run conditional step build step, even though the project is configured for concurrent execution Change By: Oleg Nenashev (19/Nov/13 8:37 PM) Component/s: conditional-buildstep This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [repo] (JENKINS-13077) Repo plugin should have an option to wipe out workspace
Arvid E.P assigned JENKINS-13077 to Arvid E.P Repo plugin should have an option to wipe out workspace Change By: Arvid E.P (19/Nov/13 8:40 PM) Assignee: ArvidE.P This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [repo] (JENKINS-13251) Allow setting repo-url during repo init
Arvid E.P resolved JENKINS-13251 as Fixed Allow setting repo-url during repo init fixed in 1.5 Change By: Arvid E.P (19/Nov/13 8:41 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/groups/opt_out.
[JIRA] [git] (JENKINS-16419) Jenkins Exception java.lang.StringIndexOutOfBoundsException: String index out of range: -114
Arvid E.P resolved JENKINS-16419 as Fixed Jenkins Exception java.lang.StringIndexOutOfBoundsException: String index out of range: -114 should be solved in 1.6 Change By: Arvid E.P (19/Nov/13 8:42 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/groups/opt_out.
[JIRA] [repo] (JENKINS-13077) Repo plugin should have an option to wipe out workspace
Arvid E.P updated JENKINS-13077 Repo plugin should have an option to wipe out workspace Change By: Arvid E.P (19/Nov/13 8:44 PM) Priority: Major Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [repo] (JENKINS-17574) Branch used by manifest is incorrectly compared to generate changelogs
Arvid E.P resolved JENKINS-17574 as Fixed Branch used by manifest is incorrectly compared to generate changelogs should be fixed in 1.6 Change By: Arvid E.P (19/Nov/13 8:45 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/groups/opt_out.
[JIRA] [maven] (JENKINS-11964) [Regression] Cannot build a single module in a Maven multi-module job with Maven 3
Rob Petti commented on JENKINS-11964 [Regression] Cannot build a single module in a Maven multi-module job with Maven 3 As near as I can tell, this hasn't been merged into master yet, so this should probably be left open? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [throttle-concurrents] (JENKINS-19986) Throttle Concurrent Builds plugin doesn't appear to work
jpschewe commented on JENKINS-19986 Throttle Concurrent Builds plugin doesnt appear to work Some more information that may be helpful fixing this plugin. I'm using the locks latches plugin with a matrix job. It used to be the case that the sub-jobs that run on each node could run concurrently as long as they were on different nodes. Now it appears that they run in serial in most cases. I say most as I think I've seen them run concurrently recently as well, but in most case they are running in serial. I know this isn't the same plugin, but I suspect both plugins depend on similar APIs and something in there has changed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [repo] (JENKINS-17913) Need to evaluate ${param} in any configuration fields
Paul Stath
commented on JENKINS-17913
Need to evaluate ${param} in any configuration fields
I'm unable to see version 1.6 of the repo plugin in Jenkins-Plugin Manager-Updates.
It still reads current version 1.5, as does the plugin page (https://wiki.jenkins-ci.org/display/JENKINS/Repo+Plugin)
I see where Arvid updated the page which indicates the latest version is 1.6.
Am I being impatient, or has the 1.6 plugin not been fully deployed yet?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [repo] (JENKINS-17913) Need to evaluate ${param} in any configuration fields
Arvid E.P
commented on JENKINS-17913
Need to evaluate ${param} in any configuration fields
patience
i just deployed it. the wiki might take a while to refresh.
http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/repo/1.6/
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [repo] (JENKINS-17913) Need to evaluate ${param} in any configuration fields
Arvid E.P
edited a comment on JENKINS-17913
Need to evaluate ${param} in any configuration fields
patience
i just deployed it. the wiki might take a while to refresh.
http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/repo/1.6/
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20618) upgrade from LTS 1.509.4 to LTS 1.532.1-SNAPSHOT -- layout.jelly java.io.IOException
Kohsuke Kawaguchi commented on JENKINS-20618 upgrade from LTS 1.509.4 to LTS 1.532.1-SNAPSHOT -- layout.jelly java.io.IOException I suspect this is just a result of a client disconnecting before the server has finished writing (for example when the user presses 'X' button on the browser while the page is loading.) We've changed the gzip library and so it must have changed the failure mode. We try to swallow this kind of error since it's not useful. Double checking now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-18759) Build Pipeline Plugin no longer maintaining parameters on Retry
Tom Akehurst commented on JENKINS-18759 Build Pipeline Plugin no longer maintaining parameters on Retry Could you provide some detail on how your builds and pipeline are configured? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [conditional-buildstep] (JENKINS-20543) error on delete job - java.lang.NoSuchMethodError: org.jenkinsci.plugins.conditionalbuildstep.ConditionalBuildStepHelper
javydreamercsw commented on JENKINS-20543 error on delete job - java.lang.NoSuchMethodError: org.jenkinsci.plugins.conditionalbuildstep.ConditionalBuildStepHelper after restart the project was not there anymore. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-18759) Build Pipeline Plugin no longer maintaining parameters on Retry
David Fuenmayor commented on JENKINS-18759 Build Pipeline Plugin no longer maintaining parameters on Retry The problem persist for me on Jenkins LTS 1.509.4 and plugin version 1.4.1 I have a downstream job triggered using build pipeline's manual trigger with some parameters. When the job fails I click on retry and nothing happens This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16781) Job and Project naming convention
Joris van der Pol updated JENKINS-16781 Job and Project naming convention Change By: Joris van der Pol (19/Nov/13 9:33 PM) Attachment: delete_project.png Attachment: new_job.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
