[JIRA] (JENKINS-40609) Add possibillity to copy / "alias" warning parser
Title: Message Title Lukas Goormann closed an issue as Fixed duplicate to be fixed... Jenkins / JENKINS-40609 Add possibillity to copy / "alias" warning parser Change By: Lukas Goormann Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-18708) Make it possible to have several files as input for one parser
Title: Message Title Lukas Goormann commented on JENKINS-18708 Re: Make it possible to have several files as input for one parser Ulli Hafner: sounds great... additionally that would give the possibility to "rename" the parsers output for less confusion in the dev-team in case a parser is just reused (once) for different than original tool... thumps up for that solution. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40609) Add possibillity to copy / "alias" warning parser
Title: Message Title Lukas Goormann reopened an issue hmm I cannot see how to do this without the need of recreate the regex by myself (where I might oversee something) find out how to call that other parser in the groovy script (didn't find snippet by googling so far). if this is still possible without to much extra effort it might be a good idea to shortly document that in the plugins wikipage or in the dynamic parser help itself. thx Jenkins / JENKINS-40609 Add possibillity to copy / "alias" warning parser Change By: Lukas Goormann Resolution: Duplicate Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40609) Add possibillity to copy / "alias" warning parser
Title: Message Title Lukas Goormann updated an issue Jenkins / JENKINS-40609 Add possibillity to copy / "alias" warning parser Change By: Lukas Goormann The warning plugin is a nice and powerful tool.There are several build-in parsers existing for standard formats.The statistics and graphs are build separated depending on the chosen parser.In my / our case we have several tools / builds within the same job which give warnings that can be parsed by the same (eg. gcc4) parser. It would be very nice if it would be possible to have an own chart / statistics etc. for each of the tools / buildtypes , since in this case it is easier / faster to reproduce and work on the certain warning, filter relevant ones for a given use case etc . . So the idea is to have the easy available possibility of a renamed / aliased parser using the regex / algorithm of the parent parser, but stores / publishes the results in an own list / chart / etc.The configuration might be similar to the own groovy script ones, just choose the parent parser form the existing and add the alias names... Afterwards, if the output of the tools is found in separated files it would be possible to parse each with its own "parser" . This could be also very helpful in pipeline jobs to differ the results of several stages...thx Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40609) Add possibillity to copy / "alias" warning parser
Title: Message Title Lukas Goormann created an issue Jenkins / JENKINS-40609 Add possibillity to copy / "alias" warning parser Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-plugin Created: 2016/Dec/21 4:54 PM Priority: Minor Reporter: Lukas Goormann The warning plugin is a nice and powerful tool. There are several build-in parsers existing for standard formats. The statistics and graphs are build on the chosen parser. In my / our case we have several tools / builds within the same job which give warnings that can be parsed by the same (eg. gcc4) parser. It would be very nice if it would be possible to have an own chart / statistics etc. for each of the tools / buildtypes. So the idea is to have the easy available possibility of a renamed / aliased parser using the regex / algorithm of the parent parser, but stores / publishes the results in an own list / chart / etc. The configuration might be similar to the own groovy script ones, just choose the parent parser form the existing and add the alias names... This could be also very helpful in pipeline jobs to differ the results of several stages... thx Add Comment
[JIRA] [cppcheck] (JENKINS-23575) Post-Build-Step Publish Cppcheck results not available in job generator project
Lukas Goormann commented on JENKINS-23575 Post-Build-Step Publish Cppcheck results not available in job generator project Hi Micheal, Thx for your reply. I veryfied the problem again, using Jenkins 1.578 and Cppcheck plugin 1.19, Job Generator plugin 1.22 on Win7 System. Browser is IE9 (update Version 9.0.30 )(due to Company Restrictions). Results: Refresh Configuration Page as well as reloading Jenkins Configuration as well as Restarting Jenkins didn't help. Other Publishers in Same menu are working fine. Tried Portable Version of Firefox: Works! (- IE9 Problem?) Additional: Collegue tried Manually build/installed Version of CppCheckPlugin (own build not through update center), also 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/d/optout.
[JIRA] [cppcheck] (JENKINS-23575) Post-Build-Step Publish Cppcheck results not available in job generator project
Lukas Goormann edited a comment on JENKINS-23575 Post-Build-Step Publish Cppcheck results not available in job generator project Hi Micheal, Thx for your reply. I veryfied the problem again, using Jenkins 1.578 and Cppcheck plugin 1.19, Job Generator plugin 1.22 on Win7 System. Browser is IE9 (update Version 9.0.30 )(due to Company Restrictions). Results: Refresh Configuration Page as well as reloading Jenkins Configuration as well as Restarting Jenkins didn't help. Other Publishers in Same menu are working fine. Tried Portable Version of Firefox: Works! (- IE9 Problem?) Deletion of temp-Files of IE does not help either Additional: Collegue tried Manually build/installed Version of CppCheckPlugin (own build not through update center), also 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/d/optout.
[JIRA] [cppcheck] (JENKINS-23575) Post-Build-Step Publish Cppcheck results not available in job generator project
Lukas Goormann reopened JENKINS-23575 Post-Build-Step Publish Cppcheck results not available in job generator project Hmmm progress made... can now find the "Publish CppCheck" step in the job-generator Postbuild menu, but clicking it does not have any visible effect... Change By: Lukas Goormann (15/Aug/14 12:47 PM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [cppcheck] (JENKINS-23575) Post-Build-Step Publish Cppcheck results not available in job generator project
Lukas Goormann updated JENKINS-23575 Post-Build-Step Publish Cppcheck results not available in job generator project After some research it is looking like a cppcheck plugin problem Change By: Lukas Goormann (15/Jul/14 8:35 AM) Assignee: SylvainBenner GregoryBoissinot Environment: Jenkins1.569,CppCheckPlugin1.18 ,jobgenerator Description: Thepost-build-stepprovidedbythecppcheckpluginisnotavailableinthe jobgenerator plugin. Component/s: cppcheck Component/s: jobgenerator This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jobgenerator] (JENKINS-23575) Post-Build-Step Publish Cppcheck results not available in job generator project
Lukas Goormann assigned JENKINS-23575 to Sylvain Benner Post-Build-Step Publish Cppcheck results not available in job generator project Guess its not too difficult, but I have no experience in any Jenkins Plugin Programming... Change By: Lukas Goormann (27/Jun/14 12:00 PM) Assignee: SylvainBenner This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jobgenerator] (JENKINS-23575) Post-Build-Step Publish Cppcheck results not available in job generator project
Lukas Goormann created JENKINS-23575 Post-Build-Step Publish Cppcheck results not available in job generator project Issue Type: Improvement Assignee: Unassigned Components: jobgenerator Created: 25/Jun/14 4:03 PM Description: The post-build-step provided by the cppcheck plugin is not available in the job genereator plugin. Environment: Jenkins 1.569, CppCheck Plugin 1.18 Project: Jenkins Labels: plugin jenkins post-build jobgenerator cppcheck Priority: Major Reporter: Lukas Goormann This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jobgenerator] (JENKINS-23575) Post-Build-Step Publish Cppcheck results not available in job generator project
Lukas Goormann updated JENKINS-23575 Post-Build-Step Publish Cppcheck results not available in job generator project Change By: Lukas Goormann (25/Jun/14 4:04 PM) Description: Thepost-build-stepprovidedbythecppcheckpluginisnotavailableinthejob genereator generator plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-10628) SCM build trigger not working correctly with variables in SVN URL
Lukas Goormann commented on JENKINS-10628 SCM build trigger not working correctly with variables in SVN URL Having the described issue with Jenkins 1.568, Subversion Plugin 2.4 and Credentials Plugin 1.14: Started on 23.06.2014 14:27:01 Received SCM poll call on for RC.TR.app.core.build.All on 23.06.2014 14:27:01 ERROR: Abfrage der aktuellen Revision schlug fehl für Repository https:// .../correctVariableRepacement org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS /svn/.../correctVariableRepacement failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:384) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:180) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:148) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.run(SvnRemoteGetInfo.java:46) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.run(SvnRemoteGetInfo.java:31) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNWCClient.doInfo(SVNWCClient.java:2461) at hudson.scm.SubversionSCM.parseSvnInfo(SubversionSCM.java:1235) at hudson.scm.CompareAgainstBaselineCallable.call(CompareAgainstBaselineCallable.java:78) at hudson.scm.CompareAgainstBaselineCallable.call(CompareAgainstBaselineCallable.java:26) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) at hudson.scm.SubversionSCM.compareRemoteRevisionWith(SubversionSCM.java:1415) at hudson.scm.SCM.poll(SCM.java:401) at hudson.model.AbstractProject._poll(AbstractProject.java:1428) at hudson.model.AbstractProject.poll(AbstractProject.java:1331) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:509) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:538) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32) at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthenticationManager.java:185)}} at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:694) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382) ... 33 more Done. Took 0,12 Sekunden No changes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe
[JIRA] [subversion] (JENKINS-10628) SCM build trigger not working correctly with variables in SVN URL
Lukas Goormann edited a comment on JENKINS-10628 SCM build trigger not working correctly with variables in SVN URL Having the described issue with Jenkins 1.568, Subversion Plugin 2.4 and Credentials Plugin 1.14: Started on 23.06.2014 14:27:01 Received SCM poll call on for RC.TR.app.core.build.All on 23.06.2014 14:27:01 ERROR: Abfrage der aktuellen Revision schlug fehl für Repository https:// .../correctVariableRepacement org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS /svn/.../correctVariableRepacement failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:384) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:180) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:148) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.run(SvnRemoteGetInfo.java:46) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.run(SvnRemoteGetInfo.java:31) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNWCClient.doInfo(SVNWCClient.java:2461) at hudson.scm.SubversionSCM.parseSvnInfo(SubversionSCM.java:1235) at hudson.scm.CompareAgainstBaselineCallable.call(CompareAgainstBaselineCallable.java:78) at hudson.scm.CompareAgainstBaselineCallable.call(CompareAgainstBaselineCallable.java:26) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) at hudson.scm.SubversionSCM.compareRemoteRevisionWith(SubversionSCM.java:1415) at hudson.scm.SCM.poll(SCM.java:401) at hudson.model.AbstractProject._poll(AbstractProject.java:1428) at hudson.model.AbstractProject.poll(AbstractProject.java:1331) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:509) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:538) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32) at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthenticationManager.java:185) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:694) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382) ... 33 more Done. Took 0,12 Sekunden No changes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To
[JIRA] [subversion] (JENKINS-10628) SCM build trigger not working correctly with variables in SVN URL
Lukas Goormann edited a comment on JENKINS-10628 SCM build trigger not working correctly with variables in SVN URL Having similar issue with Jenkins 1.568, Subversion Plugin 2.4 and Credentials Plugin 1.14 when using a variable in the SVN URL on and the SCM build trigger. Ouput of the Subversion-Request-Log: Started on 23.06.2014 14:27:01 Received SCM poll call on for RC.TR.app.core.build.All on 23.06.2014 14:27:01 ERROR: Abfrage der aktuellen Revision schlug fehl für Repository https:// .../correctVariableRepacement org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS /svn/.../correctVariableRepacement failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:384) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:180) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:148) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.run(SvnRemoteGetInfo.java:46) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.run(SvnRemoteGetInfo.java:31) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNWCClient.doInfo(SVNWCClient.java:2461) at hudson.scm.SubversionSCM.parseSvnInfo(SubversionSCM.java:1235) at hudson.scm.CompareAgainstBaselineCallable.call(CompareAgainstBaselineCallable.java:78) at hudson.scm.CompareAgainstBaselineCallable.call(CompareAgainstBaselineCallable.java:26) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) at hudson.scm.SubversionSCM.compareRemoteRevisionWith(SubversionSCM.java:1415) at hudson.scm.SCM.poll(SCM.java:401) at hudson.model.AbstractProject._poll(AbstractProject.java:1428) at hudson.model.AbstractProject.poll(AbstractProject.java:1331) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:509) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:538) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32) at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthenticationManager.java:185) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:694) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382) ... 33 more Done. Took 0,12 Sekunden No changes Will either one of the provided Patches help here? and how to apply it? or is another fix needed? Thanks in advance... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators.
[JIRA] [subversion] (JENKINS-10628) SCM build trigger not working correctly with variables in SVN URL
Lukas Goormann edited a comment on JENKINS-10628 SCM build trigger not working correctly with variables in SVN URL Having similar issue with Jenkins 1.568, Subversion Plugin 2.4 and Credentials Plugin 1.14 when using a variable in the SVN URL and the SCM build trigger. Ouput of the Subversion-Request-Log: Started on 23.06.2014 14:27:01 Received SCM poll call on for RC.TR.app.core.build.All on 23.06.2014 14:27:01 ERROR: Abfrage der aktuellen Revision schlug fehl für Repository https:// .../correctVariableRepacement org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS /svn/.../correctVariableRepacement failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:384) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:180) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:148) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.run(SvnRemoteGetInfo.java:46) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.run(SvnRemoteGetInfo.java:31) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNWCClient.doInfo(SVNWCClient.java:2461) at hudson.scm.SubversionSCM.parseSvnInfo(SubversionSCM.java:1235) at hudson.scm.CompareAgainstBaselineCallable.call(CompareAgainstBaselineCallable.java:78) at hudson.scm.CompareAgainstBaselineCallable.call(CompareAgainstBaselineCallable.java:26) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) at hudson.scm.SubversionSCM.compareRemoteRevisionWith(SubversionSCM.java:1415) at hudson.scm.SCM.poll(SCM.java:401) at hudson.model.AbstractProject._poll(AbstractProject.java:1428) at hudson.model.AbstractProject.poll(AbstractProject.java:1331) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:509) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:538) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32) at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthenticationManager.java:185) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:694) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382) ... 33 more Done. Took 0,12 Sekunden No changes Will either one of the provided Patches help here? and how to apply it? or is another fix needed? Thanks in advance... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators.
[JIRA] [role-strategy] (JENKINS-16415) Unable to add project roles using Role stratedy plugin
Lukas Goormann commented on JENKINS-16415 Unable to add project roles using Role stratedy plugin With me problem occurs with IE 9. (Usage mandatory in our organization) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [clone-workspace] (JENKINS-18350) Add option for skipping copying / restoring old builds of workspaces
Lukas Goormann created JENKINS-18350 Add option for skipping copying / restoring old builds of workspaces Issue Type: Improvement Assignee: abayer Components: clone-workspace, clone-workspace-scm Created: 14/Jun/13 11:48 AM Description: A project using a cloned workspace as input allways restores / copies the workspace, no matter, if it has changed or not. It would be nice to be able to skip that step, in case the input-workspace has not changed / was not rebuild. In our case I have a prebuild slow-changing workspace as start environment for testing some rapidly changing modules (using some scripts to update them). Here it would be usefull, if the workspace would be restored only, if it has changed. Project: Jenkins Priority: Major Reporter: Lukas Goormann This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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.
