[JIRA] [_unsorted] (JENKINS-34315) Subversion E200015 ISVNAuthentication failure when checking out
Title: Message Title Jonathan Grant created an issue Jenkins / JENKINS-34315 Subversion E200015 ISVNAuthentication failure when checking out Issue Type: Bug Assignee: Oleg Nenashev Components: _unsorted Created: 2016/Apr/18 5:07 PM Environment: Jenkins 1.642.4 Windows7 Priority: Minor Reporter: Jonathan Grant Fresh install of Jenkins 1.642.4 Sub version checkout is ok. Because the bundled Subversion doesn't support 1.8 format, I used the plugin manger to update Subversion to 2.5.7 (the latest). Now I see this error below. Any help appreciated E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. Started by user anonymous Building in workspace c:\jenkins\shared_ws Updating http://myserver/trunk at revision '2016-04-18T18:04:22.189 +0100' org.tmatesoft.svn.core.SVNCancelException: svn: E200015: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:60) at org.tmatesoft.svn.core.internal.wc.SVNErrorManage
[JIRA] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Title: Message Title Jonathan Grant commented on JENKINS-18935 Re: Make Subversion plugin support Subversion 1.8 Hello Xaviou My 1.642.4 came with Subversion plugin 1.54 I'll install it. I can see Jenkins site has 2.5.7 for download. Do you know if there is a reason this isn't included with Jenkins standard full installation? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Title: Message Title Jonathan Grant commented on JENKINS-18935 Re: Make Subversion plugin support Subversion 1.8 Hi, I'm running 1.642.4 and I see the same problem, Subversion 1.8 is not available in the list on Manage Jenkins. Any ideas? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [_unsorted] (JENKINS-34081) Source code checkout with multiple locations not working
Title: Message Title Jonathan Grant created an issue Jenkins / JENKINS-34081 Source code checkout with multiple locations not working Issue Type: Bug Assignee: Oleg Nenashev Components: _unsorted Created: 2016/Apr/07 10:31 AM Environment: Jenkins Windows 1.642.4 Priority: Minor Reporter: Jonathan Grant Fresh install of Jenkins Create "new item", free style project. called TEST Set "Advanced Project Options" and "use custom workspace" path. Under "Source Code Management" Subversion. Set the URL Click "add more locations" Set additional URL. Start the TEST After checking out the first location, the second checkout wipes out the first So the checkout is left with only the second checkout. I didn't find a way to workaround this problem.
[JIRA] [subversion-plugin] (JENKINS-32553) svn: PROPFIND request failed can we add a retry after timeout?
Title: Message Title Jonathan Grant commented on JENKINS-32553 Re: svn: PROPFIND request failed can we add a retry after timeout? Hi Ashivini Your issue appears unrelated to the issue I reported. Please see my description. It's better if you post your comments on the JENKINS-5750 issue you found, if that is related to your issue. Regards, Jonathan Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-32553) svn: PROPFIND request failed can we add a retry after timeout?
Title: Message Title Jonathan Grant updated an issue Jenkins / JENKINS-32553 svn: PROPFIND request failed can we add a retry after timeout? Change By: Jonathan Grant Summary: svn: PROPFIND request failed can we add a retry after timeout? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-32553) svn: PROPFIND request failed
Title: Message Title Jonathan Grant commented on JENKINS-32553 Re: svn: PROPFIND request failed Ashvini - I don't think your issue is related. Your issue appears to be svn permissions. Worth checking with your svn server administrator. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32500) Failed to parse the build number in the permalink
Title: Message Title Jonathan Grant commented on JENKINS-32500 Re: Failed to parse the build number in the permalink Hi Daniel Oops, you are right, yes I see it there in this log. I must have confused it with another ticket. Could some recovery mechanism be added? Delete the file, and let the system create a new one after a successful build? It seems a little severe to throw an exception and stop. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32500) Failed to parse the build number in the permalink
Title: Message Title
Jonathan Grant commented on JENKINS-32500
Re: Failed to parse the build number in the permalink
Hi Daniel
That was the whole log, nothing before (except Jenkins starting), nothing after.
There is enough information to improve the code that displays "Failed to parse the build number in the permalink" but doesn't output any useful info to help me fix the issue in the local files. Jenkins is running on a Windows 7 machine, it could be the lastSuccessfulBuild file, sometimes that seems to be a genuine file, and sometimes it is a text file containing a build number. It would be more straightforward if Jenkins never used symbolic links.
PeepholePermalink.java:106
Can this be improved to output the exact path and file that was being searched?
catch (NumberFormatException e) { LOGGER.log(Level.WARNING, "Failed to parse the build number in the permalink cache:" + f, e); // if we fail to read the cache, fall back to the re-computation }
catch (IOException e) { // this happens when the symlink doesn't exist // (and it cannot be distinguished from the case when the actual I/O error happened }
Can the LOGGER be updated to output the path of the file please? Thank you, Jon
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [_unsorted] (JENKINS-33102) Build queue jobs do not start
Title: Message Title Jonathan Grant commented on JENKINS-33102 Re: Build queue jobs do not start You're right, its a duplicate. Any news on if someone can work on this issue? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [_unsorted] (JENKINS-33102) Build queue jobs do not start
Title: Message Title Jonathan Grant created an issue Jenkins / JENKINS-33102 Build queue jobs do not start Issue Type: Bug Assignee: Oleg Nenashev Components: _unsorted Created: 23/Feb/16 1:01 PM Environment: Windows 7 1.568 Priority: Minor Reporter: Jonathan Grant Hello with 4 jobs waiting to start, the Jenkins log is showing these repeat every few seconds any ideas? Could more debug output on where the "" string comes from be added please Feb 23, 2016 12:39:57 PM SEVERE hudson.triggers.SafeTimerTask run Timer task hudson.model.Queue$MaintainTask@42cad9 failed java.lang.NumberFormatException: For input string: "" at java.lang.NumberFormatException.forInputString(Unknown Source) at java.lang.Integer.parseInt(Unknown Source) at java.lang.Integer.parseInt(Unknown Source) at jenkins.model.PeepholePermalink.resolve(PeepholePermalink.java:92) at hudson.model.Job.getLastSuccessfulBuild(Job.java:854) at hudson.model.Job.getEstimatedDurationCandidates(Job.java:941) at hudson.model.Job.getEstimatedDuration(Job.java:975) at hudson.model.queue.MappingWorksheet.(MappingWorksheet.java:335) at hudson.model.queue.MappingWorksheet.(MappingWorksheet.java:318) at hudson.model.Queue.maintain(Queue.java:1044) at hudson.model.Queue$MaintainTask.doRun(Queue.java:2010) at hudson.triggers.SafeTimerTask.run(SafeTimerTas
[JIRA] [_unsorted] (JENKINS-32553) svn: PROPFIND request failed
Title: Message Title Jonathan Grant created an issue Jenkins / JENKINS-32553 svn: PROPFIND request failed Issue Type: Bug Assignee: Oleg Nenashev Components: _unsorted Created: 21/Jan/16 2:58 PM Environment: Windows 1.608 Priority: Minor Reporter: Jonathan Grant Hello Is there a way for Jenkins to have a retry mechanism? The server is available.. so I can only think for an instant there was an intermittent network issue. Could Jenkins retry for 30 seconds? ERROR: Failed to update https://myserver/svn/trunk/ org.tmatesoft.svn.core.SVNException: svn: E175002: PROPFIND /svn/trunk failed at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.findStartingProperties(DAVUtil.java:136) at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.getVCCPath(DAVUtil.java:172) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.java:1284) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:839) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.updateInternal(SvnNgAbstractUpdate.java:192) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.update(SvnNgAbstractUpdate.java:76) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNg
[JIRA] [_unsorted] (JENKINS-32546) Jenkins can't run from queue Timer task hudson.model.Queue$MaintainTask failed
Title: Message Title Jonathan Grant created an issue Jenkins / JENKINS-32546 Jenkins can't run from queue Timer task hudson.model.Queue$MaintainTask failed Issue Type: Bug Assignee: Oleg Nenashev Components: _unsorted Created: 21/Jan/16 10:27 AM Environment: Windows 1.608 Priority: Minor Reporter: Jonathan Grant Hello I am seeing this error repeat in the log every few minutes. Is there a way Jenkins could output the origin of the empty input string? I wonder where this error is coming form. Jan 21, 2016 10:20:11 AM SEVERE hudson.triggers.SafeTimerTask run Timer task hudson.model.Queue$MaintainTask@19c4e48 failed java.lang.NumberFormatException: For input string: "" at java.lang.NumberFormatException.forInputString(Unknown Source) at java.lang.Integer.parseInt(Unknown Source) at java.lang.Integer.parseInt(Unknown Source) at jenkins.model.PeepholePermalink.resolve(PeepholePermalink.java:92) at hudson.model.Job.getLastSuccessfulBuild(Job.java:854) at hudson.model.Job.getEstimatedDurationCandidates(Job.java:941) at hudson.model.Job.getEstimatedDuration(Job.java:975) at hudson.model.queue.MappingWorksheet.(MappingWorksheet.java:335) at hudson.model.queue.MappingWorksheet.(MappingWorksheet.java:318) at hudson.model.Queue.maintain(Queue.java:1044) at hudson.model.Queue$MaintainTask.doRun(Queue.java:201
[JIRA] [core] (JENKINS-21459) Jenkins don't run jobs from queue (there are available executors)
Title: Message Title Jonathan Grant commented on JENKINS-21459 Re: Jenkins don't run jobs from queue (there are available executors) I can see that another of our Jenkins may be recovering, by creating the file. However, could Jenkins then not throw an exception? It could handle the situation more gracefully WARNING: Failed to parse the build number in the permalink cache:c:\jenkins\jobs\hello_world\builds\lastSuccessfulBuild java.lang.NumberFormatException: For input string: "" at java.lang.NumberFormatException.forInputString(Unknown Source) at java.lang.Integer.parseInt(Unknown Source) at java.lang.Integer.parseInt(Unknown Source) at jenkins.model.PeepholePermalink.resolve(PeepholePermalink.java:92) at hudson.model.Job.getLastSuccessfulBuild(Job.java:888) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectIm pl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) WARNING: Failed to parse the build number in the permalink cache:c:\jenkins\jobs\hello_world\builds\lastStableBuild java.lang.NumberFormatException: For input string: "" at java.lang.NumberFormatException.forInputString(Unknown Source) at java.lang.Integer.parseInt(Unknown Source) at java.lang.Integer.parseInt(Unknown Source) at jenkins.model.PeepholePermalink.resolve(PeepholePermalink.java:92) at jenkins.model.PeepholePermalink$RunListenerImpl.onCompleted(PeepholePermalink.java:233) at hudson.model.listeners.RunListener.fireCompleted(RunListener.java:199) at hudson.model.Run.execute(Run.java:1786) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-21459) Jenkins don't run jobs from queue (there are available executors)
Title: Message Title Jonathan Grant commented on JENKINS-21459 Re: Jenkins don't run jobs from queue (there are available executors) Hello Could this be the cause of the issue? WARNING: Symbolic links enabled on this platform but disabled for this user; run as administrator or use Local Security Policy > Security Settings > Local Policies > User Rights Assignment > Create symbolic links Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21459) Jenkins don't run jobs from queue (there are available executors)
Title: Message Title Jonathan Grant commented on JENKINS-21459 Re: Jenkins don't run jobs from queue (there are available executors) I see the same, but could Jenkins output the exact job name to make to clearer? I'm not sure which lastSuccessfulBuild I should fix! Jenkins is fully up and running Jan 18, 2016 2:02:10 PM INFO hudson.model.UpdateSite updateData Obtained the latest update center data file for UpdateSource default Jan 18, 2016 4:38:20 PM WARNING hudson.ExpressionFactory2$JexlExpression evaluate Caught exception evaluating: job.lastSuccessfulBuild in /. Reason: java.lang.reflect.InvocationTargetException Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32500) Failed to parse the build number in the permalink
Title: Message Title Jonathan Grant commented on JENKINS-32500 Re: Failed to parse the build number in the permalink Hello Oleg It is part of the Jenkins server log: http://testmachine:8080/log/all Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [_unsorted] (JENKINS-32500) Failed to parse the build number in the permalink
Title: Message Title Jonathan Grant created an issue Jenkins / JENKINS-32500 Failed to parse the build number in the permalink Issue Type: Bug Assignee: Oleg Nenashev Components: _unsorted Created: 18/Jan/16 2:13 PM Environment: Windows7 ver1.608 Priority: Minor Reporter: Jonathan Grant Hello I see this exception below. BUILD_NUMBER is available in the environment, and then I see an Exception, would be nice if Jenkins could handle more gracefully... Jan 18, 2016 12:50:38 PM WARNING jenkins.model.PeepholePermalink resolve Failed to parse the build number in the permalink cache:c:\jenkins\jobs\d1h_hello_world\builds\lastSuccessfulBuild java.lang.NumberFormatException: For input string: "" at java.lang.NumberFormatException.forInputString(Unknown Source) at java.lang.Integer.parseInt(Unknown Source) at java.lang.Integer.parseInt(Unknown Source) at jenkins.model.PeepholePermalink.resolve(PeepholePermalink.java:92) at hudson.model.Job.getLastSuccessfulBuild(Job.java:888) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org
[JIRA] [plugin] (JENKINS-23626) Implement "cancel all" action for the Build Queue (like Hudson version 2.2.1)
Jonathan Grant commented on JENKINS-23626 Implement "cancel all" action for the Build Queue (like Hudson version 2.2.1) I stopped after 20 mins after trying to satisfy all the Maven install requirements. Can you put together a step by step guide and an installer EXE for me to run? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-23626) Implement "cancel all" action for the Build Queue (like Hudson version 2.2.1)
Jonathan Grant commented on JENKINS-23626 Implement "cancel all" action for the Build Queue (like Hudson version 2.2.1) Hi Daniel, Oleg Thank you for steps to build. Is there a way you could publish as a plugin? I've not got time to prepare a build environment at present. Regards, Jon This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23655) Jenkins Windows Service SVN checkout permissions problem
Jonathan Grant commented on JENKINS-23655 Jenkins Windows Service SVN checkout permissions problem Thanks for your reply. Yes, I restarted the Service. Also I rebooted since then too. I've asked on the users list now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23626) Build Queue no longer has "cancel all" like Hudson version 2.2.1
Jonathan Grant commented on JENKINS-23626 Build Queue no longer has "cancel all" like Hudson version 2.2.1 Thank you for the effort of making this Daniel Any chance of providing a built version? I'm just using an installed version of Jenkins at present. Or even better, could it be added to the official Jenkins install next version please. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23655) Jenkins Windows Service SVN checkout permissions problem
Jonathan Grant created JENKINS-23655 Jenkins Windows Service SVN checkout permissions problem Issue Type: Bug Assignee: Unassigned Components: core Created: 02/Jul/14 9:27 AM Description: Hello Could I report a possible problem with Jenkins Service. On Windows this runs as group "LocalService", this then follows my "Build a free-style software project" item, which does: SVN checkout Build step calls my "build.bat" build.bat has problems copying file, because all files and directories checked out from SVN by Jenkins have Owner "Administrators" If I change the Jenkins Service in Control Panel->Administrative Tools->Services to run as a specific user "OFFICE\builduser" (Rather than "Local System account"). I delete the SVN checkout, and run again the Jenkins Item, I still see all files and directories checked out by Jenkins have Owner "Administrators". Any idea how to get files to be checked out by Jenkins to have the correct Owner? If I login to the machine as builduser, "run CMD.exe as Administrator", it can run build.bat without problems, so it seems a permissions problem. build.bat runs some cygwin commands, that otherwise work when run as a regular user (me on my machine, or the machine with Jenkins) Thanks for any suggestions. Project: Jenkins Priority: Major Reporter: Jonathan Grant This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project] (JENKINS-23540) (our case 11519) Post build step not run and difficult to know why
Jonathan Grant commented on JENKINS-23540 (our case 11519) Post build step not run and difficult to know why Many thanks Jens My "Build a free-style software project" are working well. So I will stay using these now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23626) Build Queue no longer has "cancel all" like Hudson version 2.2.1
Jonathan Grant commented on JENKINS-23626 Build Queue no longer has "cancel all" like Hudson version 2.2.1 Can it be considered as an enhancement request? Let me know if you prefer me to create a new ticket with a clearer request. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [codahale-metrics-graphite] (JENKINS-23626) Build Queue no longer has "cancel all" like Hudson version 2.2.1
Jonathan Grant created JENKINS-23626 Build Queue no longer has "cancel all" like Hudson version 2.2.1 Issue Type: Bug Assignee: stephenconnolly Components: codahale-metrics-graphite Created: 30/Jun/14 3:25 PM Description: Not sure what component this is When I start a build which triggers adding 20 to the queue. I see them all listed. However, the "Build Queue" no longer has "(cancel all)" link below it, like Hudson version 2.2.1 had. could that be added back please? I need to manually click on 20 icons.. an wait for it to refresh to check the builds cancelled at present... Environment: Windows7 Project: Jenkins Priority: Major Reporter: Jonathan Grant This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-23621) Jenkins using out of date SVN library format 29
Jonathan Grant created JENKINS-23621 Jenkins using out of date SVN library format 29 Issue Type: Bug Assignee: Unassigned Components: subversion Created: 30/Jun/14 11:00 AM Description: 1.568 using out of date SVN library format 29. Could I ask for Jenkins to be updated to use latest SVN library format for checkouts please? Latest cygwin.com "svn" package uses format 31, however Jenkins 1.568 is using out of date format 29 This means that my job cannot update or commit files on the checkout made by Jenkins any more. (I am migrating from Hudson on older machine) svn: E155036: Please see the 'svn upgrade' command svn: E155036: The working copy at '/cygdrive/c/jenkins/shared_ws/sdk_build' is too old (format 29) to work with client version '1.8.9 (r1591380)' (expects format 31). You need to upgrade the working copy first. Environment: Windows7 Jenkins 1.568 Latest cygwin.com install of "svn" Project: Jenkins Priority: Major Reporter: Jonathan Grant This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [component] (JENKINS-23540) (our case 11519) Post build step not run and difficult to know why
Jonathan Grant commented on JENKINS-23540 (our case 11519) Post build step not run and difficult to know why Hi Jens Thank you for your reply. I had a breakthrough, found this website where someone else had the same problem: http://stackoverflow.com/questions/13756215/jenkins-console-output-is-virtually-empty So when I used "Build multi-configuration project" it did not work reliably Since I changed to "Build a free-style software project" my builds work reliably. e.g. builds run once (rather than duplicate), output is present (rather than missing). It is straight forward to reproduce on Windows7. Could I ask you to try: 1) Install latest Jenkins 2) Create multi-configuration project 3) add a build step like mine "@echo test" 4) add svn checkout. 5) Run This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [component] (JENKINS-23540) (our case 11519) Post build step not run and difficult to know why
Jonathan Grant commented on JENKINS-23540 (our case 11519) Post build step not run and difficult to know why sdk_dev_cfg_00 appears to running twice in its log: Started by upstream project "build" build number 14 originally caused by: Started by user anonymous Started by upstream project "build" build number 14 originally caused by: Started by user anonymous Building in workspace C:\jenkins\shared_ws\sdk Triggering default default completed with result SUCCESS Finished: SUCCESS It also isn't actually doing the build 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/d/optout.
[JIRA] [component] (JENKINS-23540) (our case 11519) Post build step not run and difficult to know why
Jonathan Grant commented on JENKINS-23540 (our case 11519) Post build step not run and difficult to know why Hi Jens Test ct Custom Directory . false https://duesvn2.ad.ree.renesas.com/automotive/svnASG_SDK/trunk . infinity false false false true false false false #Build at mid day each weekday 0 12 * * 1-5 #Build at 20:00 each weekday 0 20 * * 1-5 false shared_ws\sdk @echo ATE build folder: %cd% sdk_dev_cfg00 SUCCESS 0 BLUE true jon...@ff.com false false false This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [component] (JENKINS-23540) (our case 11519) Post build step not run and difficult to know why
Jonathan Grant commented on JENKINS-23540 (our case 11519) Post build step not run and difficult to know why That "@echo ATE Build folder %cd%" is not displayed Started by user anonymous Building in workspace C:\jenkins\shared_ws\sdk Updating https://d/fff/trunk at revision '2014-06-25T11:00:54.501 +0100' D v.bat At revision 21677 Triggering default default completed with result SUCCESS Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered Triggering a new build of sdk_dev_cfg00 Triggering a new build of sdk_dev_cfg00 Finished: SUCCESS Also I don't know why sdk_dev_cfg00 is being triggered twice.. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [component] (JENKINS-23540) (our case 11519) Post build step not run and difficult to know why
Jonathan Grant commented on JENKINS-23540 (our case 11519) Post build step not run and difficult to know why If I have this as Windows Build step when I click "configure" it doesn't occur: echo build folder: echo %cd% However, If I replace that with "build.bat" it doesn't work either. If I add two separate commands, then it does work. Bizarre 1st command: echo ATE build folder: echo %cd% 2nd command: build.bat This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [component] (JENKINS-23540) (our case 11519) Post build step not run and difficult to know why
Jonathan Grant
commented on JENKINS-23540
(our case 11519) Post build step not run and difficult to know why
config.xml
1.568
1
NORMAL
true
false
${JENKINS_HOME}/workspace/${ITEM_FULLNAME}
${ITEM_ROOTDIR}/builds
5
1
All
test
false
false
All
0
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [component] (JENKINS-23540) (our case 11519) Post build step not run and difficult to know why
Jonathan Grant commented on JENKINS-23540 (our case 11519) Post build step not run and difficult to know why Started by user anonymous Building in workspace C:\jenkins\workspace\build Updating https://gdfg at revision '2014-06-24T15:42:03.338 +0100' U xx At revision 21676 Triggering default default completed with result SUCCESS Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered Triggering a new build of sdk_dev_cfg00 Finished: SUCCESS This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [component] (JENKINS-23540) Post build step not run and difficult to know why
Jonathan Grant created JENKINS-23540 Post build step not run and difficult to know why Issue Type: Bug Affects Versions: current Assignee: Praqma Support Components: component Created: 23/Jun/14 1:53 PM Description: I just installed on Windows7, after checkout from SVN, my post build "BAT" file doesn't run.. and unclear why - could the output trigger be included to make it simpler to see why not running? The trigger used to work ok in Hudson. Thank you for any suggestions [snip] AUinternal.zip U. At revision 21668 Triggering default default completed with result FAILURE Finished: FAILURE Environment: Windows7 Project: Jenkins Priority: Minor Reporter: Jonathan Grant This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23486) Uninstalling Jenkins leaves Program Files full of files
Jonathan Grant commented on JENKINS-23486 Uninstalling Jenkins leaves Program Files full of files Hi Thanks for the reply Normally user data is stored under c:\users\username\AppData\AppName etc It seems nicer to me if the uninstall would remove the "C:\Program Files\Jenkins" folder. Or maybe it could have an option as part of the uninstaller to ask the user the question? Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
