[JIRA] [p4-plugin] (JENKINS-28760) P4 Plugin does not respect line endings for template workspaces
Title: Message Title Matt Hauck commented on JENKINS-28760 Re: P4 Plugin does not respect line endings for template workspaces If you merge in this change, would it be possible to cut a new release with this fix in? It'd be much appreciated. =) 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] [p4-plugin] (JENKINS-28760) P4 Plugin does not respect line endings for template workspaces
Title: Message Title Matt Hauck commented on JENKINS-28760 Re: P4 Plugin does not respect line endings for template workspaces Pull request: https://github.com/jenkinsci/p4-plugin/pull/15 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] [p4-plugin] (JENKINS-28760) P4 Plugin does not respect line endings for template workspaces
Title: Message Title Matt Hauck created an issue Jenkins / JENKINS-28760 P4 Plugin does not respect line endings for template workspaces Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 05/Jun/15 3:59 AM Priority: Minor Reporter: Matt Hauck We use the P4 plugin in "template" mode, and we have all our workspaces always set to "Unix" line endings. The templates all have this line ending properly set. When the p4 plugin creates a workspace for a particular job, the created workspace always ends up with line ending setting of "Local". This ends up working fine for the Linux builds, of course, but the Windows builds always fail the first time, leading us to need to manually modify the line endings setting once in P4V for each newly created windows workspace. This may be related to JENKINS-27250, but I think it is a different issue Add Comment
[JIRA] [p4-plugin] (JENKINS-28301) Update P4 Documentation regarding Pin parameter
Title: Message Title A C updated an issue Jenkins / JENKINS-28301 Update P4 Documentation regarding Pin parameter Change By: A C Summary: Update P4 workflow checkout should accept a changelist Documentation regarding Pin parameter 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] [p4-plugin] (JENKINS-28301) P4 workflow checkout should accept a changelist parameter
Title: Message Title A C updated an issue Jenkins / JENKINS-28301 P4 workflow checkout should accept a changelist parameter Change By: A C Using the workflow plugin, the checkout step using PerforceScm does not provide any parameters for syncing to a particular changelist (or label, etc), and instead always syncs to head.-The workaround of manually running p4 sync has several drawbacks, including not appropriately setting Jenkin's knowledge of the changes being synced to.-As per comment below retitling as documentation task. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-28301) P4 workflow checkout should accept a changelist parameter
Title: Message Title A C updated an issue Jenkins / JENKINS-28301 P4 workflow checkout should accept a changelist parameter Change By: A C Using the workflow plugin, the checkout step using PerforceScm does not provide any parameters for syncing to a particular changelist (or label, etc), and instead always syncs to head.- The workaround of manually running p4 sync has several drawbacks, including not appropriately setting Jenkin's knowledge of the changes being synced to.-As per comment below retitling as documentation task. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-28301) P4 workflow checkout should accept a changelist parameter
Title: Message Title A C updated an issue Jenkins / JENKINS-28301 P4 workflow checkout should accept a changelist parameter Change By: A C Using the workflow plugin, the checkout step using PerforceScm does not provide any parameters for syncing to a particular changelist (or label, etc), and instead always syncs to head. - The workaround of manually running p4 sync has several drawbacks, including not appropriately setting Jenkin's knowledge of the changes being synced to. -As per comment below 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] [workflow-plugin] (JENKINS-28759) Batch steps on slaves randomly hang when complete
Title: Message Title
A C created an issue
Jenkins / JENKINS-28759
Batch steps on slaves randomly hang when complete
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
04/Jun/15 11:16 PM
Environment:
Jenkins 1.6.16 Workflow 1.7 Windows 8.1 Slaves
Labels:
batch
Priority:
Critical
Reporter:
A C
Batch steps that succeed are hanging, more frequently since the upgrade to Jenkins 1.6.16 + WF 1.7; I think this is recent, I do not recall encountering such issues with Jenkins 1.6.09 + WF 1.5. This is highly problematic for workflow scripts that rely on large numbers of batch steps. Note, the slave nodes in question may be considered "high-latency" with response times occasionally in seconds.
Reproduced 2 out of 4 times using the following test idiom, increasing the below loop to 1000 will probably make it a 100% reproduction, parallelizing anecdotally seems to increase reproduction:
node('slave') { for( int i = 0; i < 100; ++i ) { echo "i=$ {i}
[JIRA] [sauce-ondemand-plugin] (JENKINS-28758) Provide additional details within list of Sauce jobs
Title: Message Title Ross Rowe created an issue Jenkins / JENKINS-28758 Provide additional details within list of Sauce jobs Issue Type: Improvement Assignee: Ross Rowe Components: sauce-ondemand-plugin Created: 04/Jun/15 11:11 PM Priority: Minor Reporter: Ross Rowe The list of Sauce jobs that are presented on the Jenkins build/test result screen currently include Job Id, Name and Passed. This details that are displayed should also include the browser combination which was used Add Comment
[JIRA] [subversion-plugin] (JENKINS-28484) Subversion tagging not working - E200015: ISVNAuthentication provider did not provide credentials
Title: Message Title Arthur Ramsey commented on JENKINS-28484 Re: Subversion tagging not working - E200015: ISVNAuthentication provider did not provide credentials I think your issue may be different than mine. Take a look at JENKINS-22542. 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] [docker-build-publish-plugin] (JENKINS-27229) Docker publish plugin throws error "Please login prior to push" after publishing the image
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-27229 Re: Docker publish plugin throws error "Please login prior to push" after publishing the image I'm getting the same error. My environment is: CloudBees Docker Build and Publish plugin v1.0 Jenkins 1.609.1 Mac OSX 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-25930) Race condition creating build links during concurrent builds causes build failures
Title: Message Title Angelo Perera commented on JENKINS-25930 Re: Race condition creating build links during concurrent builds causes build failures We have a very large distributed Jenkins CI undertaking at the moment and our first few tests always fail due to this error. TraderPlus.UI.Test #4641 completed : FAILURE TraderPlus.UI.Test #4646 completed : FAILURE Build TraderPlus.UI.Test #4655 started Build TraderPlus.UI.Test #4654 started TraderPlus.UI.Test #4645 completed : FAILURE Build TraderPlus.UI.Test #4656 started TraderPlus.UI.Test #4648 completed : FAILURE Build TraderPlus.UI.Test #4657 started TraderPlus.UI.Test #4639 completed : FAILURE Build TraderPlus.UI.Test #4658 started TraderPlus.UI.Test #4642 completed : FAILURE Build TraderPlus.UI.Test #4659 started TraderPlus.UI.Test #4647 completed Build TraderPlus.UI.Test #4660 started TraderPlus.UI.Test #4644 completed Build TraderPlus.UI.Test #4661 started (Rest of the tests pass) Failure details: ln builds\lastSuccessfulBuild C:\Users\Administrator\.jenkins\jobs\TraderPlus.UI.Test\lastSuccessful failed java.nio.file.FileAlreadyExistsException: C:\Users\Administrator\.jenkins\jobs\TraderPlus.UI.Test\lastSuccessful at sun.nio.fs.WindowsException.translateToIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsFileSystemProvider.createSymbolicLink(Unknown Source) at java.nio.file.Files.createSymbolicLink(Unknown Source) 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 hudson.Util.createSymlinkJava7(Util.java:1227) at hudson.Util.createSymlink(Util.java:1143) at hudson.model.Run.createSymlink(Run.java:1848) at hudson.model.Run.updateSymlinks(Run.java:1829) at hudson.model.Run.execute(Run.java:1742) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) [EnvInject] - Loading node environment variables. Building remotely on au03-devcivm4 (UITest) in workspace D:\Jenkins\workspace\TraderPlus.UI.Test Running Jenkins ver. 1.616 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [svn-tag-plugin] (JENKINS-28615) Supplied credentials not used
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-28615 Supplied credentials not used Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed 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] [svn-tag-plugin] (JENKINS-28615) Supplied credentials not used
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28615 Re: Supplied credentials not used Code changed in jenkins User: Wannes Sels Path: src/main/java/hudson/plugins/svn_tag/SvnTagPlugin.java http://jenkins-ci.org/commit/svn-tag-plugin/172c3038e6607215aaf476b5d465a69761dbd274 Log: Use supplied credentials [FIXED JENKINS-28615] 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] [envinject-plugin] (JENKINS-28757) env variable not evaluated in property file path
Title: Message Title Mark Wigzell created an issue Jenkins / JENKINS-28757 env variable not evaluated in property file path Issue Type: Bug Assignee: Gregory Boissinot Components: envinject-plugin Created: 04/Jun/15 9:56 PM Environment: Jenkins 1.584, envinject-plugin 1.91.3 on iMac 10.10.2, Chrome Browser Labels: evaluate promotion inject variable Priority: Major Reporter: Mark Wigzell When running a promotion I'd like to take advantage of env. saved in ../builds/$PROMOTED_NUMBER/injectedEnvVars.txt. Specifically, in the "Promote builds when" box, I'm using "Inject Environment Variables" action to inject above mentioned variables. I have a build parameter in a parameterized job that I need to get a hold of. I must get the parameter from the saved env. variables for that job. Hence my attempt to evaluate PROMOTED_NUMBER. I know the variable is set because I created a SHELL build step before this, and echoed out the variables etc. As a work around I am copying the file into my workspace, then I don't have to use variables to refer to it in this "Inject Envir
[JIRA] [git-client-plugin] (JENKINS-28748) git plugin submodule init fail on large submodule
Title: Message Title Mark Waite commented on JENKINS-28748 Re: git plugin submodule init fail on large submodule Since authentication is not supported with submodules, I assume that means your repository is not secured. If it is not secured, could you configure the submodule URL to use the git protocol instead of the http or https protocol? That would then avoid the inactivity timeout problem reported in JENKINS-9168 . If the repository is secured, what protocol is being used to fetch the repository? 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] [workflow-plugin] (JENKINS-28756) "General SCM" dropdown offers SCMs not compatible with Workflow
Title: Message Title Jesse Glick started work on JENKINS-28756 Change By: Jesse Glick Status: Open In Progress 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] [docker-build-step-plugin] (JENKINS-28755) docker-java dependency should be shaded in docker-build-step
Title: Message Title Oleg Nenashev commented on JENKINS-28755 Re: docker-java dependency should be shaded in docker-build-step Stacktrace example: javax.servlet.ServletException: java.util.ServiceConfigurationError: com.github.dockerjava.api.command.DockerCmdExecFactory: Provider com.github.dockerjava.jaxrs.DockerCmdExecFactoryImpl not a subtype at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:491) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1074) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:168) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:185) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:689) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:391) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:146) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) at org.mortbay.jetty.Server.handle(Server.java:285) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:457) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:765) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:628) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:209) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:357) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:329) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475) Caused by: java.util.ServiceConfigurationError: com.github.dockerjava.api.command.DockerCmdExecFactory: Provider com.github.dockerjava.jaxrs.DockerCmdExecFactoryImpl not a subtype at java.util.ServiceLoader.fail(ServiceLoader.java:239) at java.util.ServiceLoader.access$300(ServiceLoader.java:185) at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:376) at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:404) at java.util.ServiceLoader$1.next(ServiceLoader.java:480) at com.github.dockerjava.core.Doc
[JIRA] [workflow-plugin] (JENKINS-28756) "General SCM" dropdown offers SCMs not compatible with Workflow
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-28756 "General SCM" dropdown offers SCMs not compatible with Workflow Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 04/Jun/15 8:45 PM Priority: Major Reporter: Jesse Glick Despite the list, all installed SCMs are offered in the dropdown. Seems to be because it is now a Snippetizer, not a WorkflowJob. Add Comment
[JIRA] [docker-traceability-plugin] (JENKINS-28693) docker-java dependency should be shaded in docker-traceability
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-28693 docker-java dependency should be shaded in docker-traceability Change By: Oleg Nenashev Summary: docker-java dependency should be shaded in docker-traceability 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] [docker-build-step-plugin] (JENKINS-28755) docker-java dependency should be shaded in docker-build-step
Title: Message Title Oleg Nenashev assigned an issue to vjuranek Jenkins / JENKINS-28755 docker-java dependency should be shaded in docker-build-step Change By: Oleg Nenashev Component/s: docker-build-step-plugin Component/s: docker-traceability-plugin Assignee: Oleg Nenashev vjuranek 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] [docker-traceability-plugin] (JENKINS-28755) docker-java dependency should be shaded in docker-build-step
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-28755 docker-java dependency should be shaded in docker-build-step Issue Type: Bug Assignee: Oleg Nenashev Components: docker-traceability-plugin Created: 04/Jun/15 8:40 PM Priority: Major Reporter: Oleg Nenashev Issues: docker-java does not guarantee the backward compatibility across versions (there're binary compatibility violations in the latest releases) sharing of incompatible lib as a plugin is not safe, so we want to setup the shading of the entire docker-java lib if we leave the plugin as is, there's may be a conflict with other plugins using docker-java Solution: Shade the docker-java library in the plugin I'm aware that this issue is a blocker for 1.0 release. Need some help to elaborate it.
[JIRA] [workflow-plugin] (JENKINS-28604) Parallel step will create 2nd executor on single-executor slaves
Title: Message Title A C commented on JENKINS-28604 Re: Parallel step will create 2nd executor on single-executor slaves After browsing the bug DB some more, one other potentially relevant note - these slaves do have a high latency connection to the master, on the order of many seconds to (rarely) a few minutes. 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] [fitnesse-plugin] (JENKINS-27940) Consider using jUnit output from FitNesse
Title: Message Title Serge Zukov commented on JENKINS-27940 Re: Consider using jUnit output from FitNesse The one and only benefit INHO is to plug into existing JENKINS test results infrastructure. FitNesse results are a bit of sidestep from rest of test results in Jenkins (yes, for the good reason) however it limits things user can achieve with it. For example you cannot accumulate FitNesse test results from several jobs into one (this feature is for junit tests only AFAIK). P.S. FitNesse junit output could be extended to embed things JENKINS needs (I implemented an absolute bare minimum). 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-28408) Jenkins can't load extension ContextExtensionPoint if dependency is optional
Title: Message Title Kirill Merkushev commented on JENKINS-28408 Re: Jenkins can't load extension ContextExtensionPoint if dependency is optional I use maven-hpi-plugin:1.106 (same with latest 1.113) If i add token macro as optional dep, then in manifest i see Plugin-Dependencies: token-macro:1.10;resolution:=optional And if i add job-dsl-plugin as optional, no any tag Plugin-Dependencies in manifest 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] [fitnesse-plugin] (JENKINS-27938) Unable to expand collapsed SLIM tables
Title: Message Title Serge Zukov commented on JENKINS-27938 Re: Unable to expand collapsed SLIM tables You won't need my page to reproduce it: FitNesse.SuiteAcceptanceTests.SuiteSlimTests.ChainWithInstanceTest In captured test results "do something with" will not be expandable. Yes, you are right - the issue affects collapsed scenarios. Does not affect collapsed page sections. 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] [git-plugin] (JENKINS-28260) Java String Index Out of Range
Title: Message Title Daniel Beck commented on JENKINS-28260 Re: Java String Index Out of Range Mark Waite Should this be resolved as duplicate? 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] [delivery-pipeline-plugin] (JENKINS-28055) Pipeline arrows are not displaying or displayed incorrectly
Title: Message Title Tommy Tynjä closed an issue as Won't Fix Validated the suggested workarounds which is deemed as a sufficient solution at this point, therefore closing this ticket. Jenkins / JENKINS-28055 Pipeline arrows are not displaying or displayed incorrectly Change By: Tommy Tynjä Status: Open Closed Resolution: Won't Fix 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-28408) Jenkins can't load extension ContextExtensionPoint if dependency is optional
Title: Message Title wolfs commented on JENKINS-28408 Re: Jenkins can't load extension ContextExtensionPoint if dependency is optional Shouldn't we fix the maven-hpi-plugin instead of the gradle jpi plugin? 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] [ec2-plugin] (JENKINS-28754) Jenkins EC2 Plugin should show timestamp in slave logs
Title: Message Title arash m created an issue Jenkins / JENKINS-28754 Jenkins EC2 Plugin should show timestamp in slave logs Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 04/Jun/15 5:33 PM Environment: Jenkins ver. 1.608 EC2 Plugin 1.27 Labels: ec2-plugin slave timestamp log Priority: Minor Reporter: arash m Currently the logs for slaves provisioned using the ec2-plugin don't contain any timestamps. This would be quite useful for debugging & troubleshooting purposes. Especially when we have situations where slaves abruptly have their connection terminated.
[JIRA] [terminal-plugin] (JENKINS-28753) Terminal Plugin throws Error 403 when "Prevent Cross Site Request Forgery exploits" is enabled
Title: Message Title Pavel Saab created an issue Jenkins / JENKINS-28753 Terminal Plugin throws Error 403 when "Prevent Cross Site Request Forgery exploits" is enabled Issue Type: Bug Assignee: kiy0taka Components: terminal-plugin Created: 04/Jun/15 5:32 PM Priority: Major Reporter: Pavel Saab When trying to use Terminal plugin 1.4. in Jenkins ver. 1.532.2 getting "[JENKINS TERMINAL] ERROR: 403". Error only occurs when "Prevent Cross Site Request Forgery exploits" security option is enabled. Add Comment
[JIRA] [dashboard-view-plugin] (JENKINS-20025) Dashboard View Plugin: Starting jobs returns error 'Form post required'
Title: Message Title Jesse Glick commented on JENKINS-20025 Re: Dashboard View Plugin: Starting jobs returns error 'Form post required' If the fix is merged, this should be Resolved/Fixed. 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] [docker-traceability-plugin] (JENKINS-28752) DockerTraceabiltyReport marks imageId as nonNull but for certain events its not always possible to obtain it.
Title: Message Title James Nord created an issue Jenkins / JENKINS-28752 DockerTraceabiltyReport marks imageId as nonNull but for certain events its not always possible to obtain it. Issue Type: Bug Assignee: Unassigned Components: docker-traceability-plugin Created: 04/Jun/15 5:11 PM Priority: Minor Reporter: James Nord DockerTraceabilityReport marks getImageId as Nonnull. However in the case a docker container is destroyed it may not be able to obtain this information. The Docker event will contain the containerId and the name of the image it is deployed from. But that image may itself have been removed by the time we request information about it, and so may not be able to retrieve it's details. Add Comment
[JIRA] [job-dsl-plugin] (JENKINS-28562) Need TriggerContext as ExtensibleContext
Title: Message Title Kirill Merkushev commented on JENKINS-28562 Re: Need TriggerContext as ExtensibleContext Thanks for quick fix! 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-28408) Jenkins can't load extension ContextExtensionPoint if dependency is optional
Title: Message Title Daniel Spilker commented on JENKINS-28408 Re: Jenkins can't load extension ContextExtensionPoint if dependency is optional Fix for the gradle-jpi-plugin: https://github.com/jenkinsci/gradle-jpi-plugin/pull/53 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] [dynamicparameter-plugin] (JENKINS-25748) Environment variables are not expanded and thus cannot be used as parameter values to Scriptler scripts
Title: Message Title Ioannis Moutsatsos commented on JENKINS-25748 Re: Environment variables are not expanded and thus cannot be used as parameter values to Scriptler scripts As an alternative to Dynamic Parameter plugin you can use the Active Choices plugin. It offers all of the functionality of the Dynamic Parameter plugin, multi-select, cascade updates and much more. Check it out here: https://wiki.jenkins-ci.org/display/JENKINS/Active+Choices+Plugin 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] [dynamicparameter-plugin] (JENKINS-27589) Jenkins fails on periodic build with Dynamic Choice Parameter Groovy script
Title: Message Title Ioannis Moutsatsos commented on JENKINS-27589 Re: Jenkins fails on periodic build with Dynamic Choice Parameter Groovy script As an alternative to Dynamic Parameter plugin you can use the Active Choices plugin. It offers all of the functionality of the Dynamic Parameter plugin, multi-select, cascade updates and much more. Check it out here: https://wiki.jenkins-ci.org/display/JENKINS/Active+Choices+Plugin 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-19578) Multi-select feature at Dynamic parameter plugin
Title: Message Title Ioannis Moutsatsos commented on JENKINS-19578 Re: Multi-select feature at Dynamic parameter plugin The uno-choices plugin is now released to the Jenkins community with the name Active Choices plugin. It offers all of the functionality of the Dynamic Parameter plugin, multi-select, cascade updates and much more. Check it out here: https://wiki.jenkins-ci.org/display/JENKINS/Active+Choices+Plugin 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-28408) Jenkins can't load extension ContextExtensionPoint if dependency is optional
Title: Message Title Daniel Spilker updated an issue Jenkins / JENKINS-28408 Jenkins can't load extension ContextExtensionPoint if dependency is optional Change By: Daniel Spilker Component/s: core 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] [gradle-jpi-plugin] (JENKINS-28408) Jenkins can't load extension ContextExtensionPoint if dependency is optional
Title: Message Title Daniel Spilker updated an issue Jenkins / JENKINS-28408 Jenkins can't load extension ContextExtensionPoint if dependency is optional Change By: Daniel Spilker Component/s: gradle-jpi-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-28408) Jenkins can't load extension ContextExtensionPoint if dependency is optional
Title: Message Title Daniel Spilker commented on JENKINS-28408 Re: Jenkins can't load extension ContextExtensionPoint if dependency is optional I think the problem is that the Job DSL plugin POM has packaging type of jpi (see http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/job-dsl/1.34/job-dsl-1.34.pom) as generated by the gradle-jpi-plugin. And the maven-hpi-plugin only considers the hpi packaging type as plugin dependency, see https://github.com/jenkinsci/maven-hpi-plugin/blob/maven-hpi-plugin-1.113/src/main/java/org/jenkinsci/maven/plugins/hpi/MavenArtifact.java#L64. 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] [_test] (JENKINS-28751) What will happen building a Jenkins project second time, which is setup to checkout from a SVN repository? Will checking out of whole repository be repeated taking a lot
Title: Message Title Oleg Nenashev resolved as Not A Defect Jenkins / JENKINS-28751 What will happen building a Jenkins project second time, which is setup to checkout from a SVN repository? Will checking out of whole repository be repeated taking a lot of time? Or only the changes added to the repository will be checked out? Change By: Oleg Nenashev Status: Open Resolved Resolution: Not A Defect 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] [_test] (JENKINS-28751) What will happen building a Jenkins project second time, which is setup to checkout from a SVN repository? Will checking out of whole repository be repeated taking a lot
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-28751 What will happen building a Jenkins project second time, which is setup to checkout from a SVN repository? Will checking out of whole repository be repeated taking a lot of time? Or only the changes added to the repository will be checked out? Change By: Oleg Nenashev Issue Type: Bug Task Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [_test] (JENKINS-28751) What will happen building a Jenkins project second time, which is setup to checkout from a SVN repository? Will checking out of whole repository be repeated taking a lot
Title: Message Title Oleg Nenashev commented on JENKINS-28751 Re: What will happen building a Jenkins project second time, which is setup to checkout from a SVN repository? Will checking out of whole repository be repeated taking a lot of time? Or only the changes added to the repository will be checked out? Not a bug, the most of questions are covered by the existing documentation (Wiki & built-in docs). If you still have open questions after reading it, ask your questions on #jenkins IRC channel or jenkinsci-users mailing lists. 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] [cobertura-plugin] (JENKINS-17749) Data displayed in Jenkins, do not correspond exactly to the data in the file coverage.xml
Title: Message Title Iván López commented on JENKINS-17749 Re: Data displayed in Jenkins, do not correspond exactly to the data in the file coverage.xml Have same issue with my tests. Jenkins appears to calculate the lines and percentages by its own, not reading the values in coverage.xml. In my case, the problem comes (I guess) because one file has no test at all, in coverage.xml they appear, and sums in totals, but jenkins doesn't take that file into account while calculating. If I write a little test using something in that file, everything is calculated correctly. 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] [_test] (JENKINS-28751) What will happen building a Jenkins project second time, which is setup to checkout from a SVN repository? Will checking out of whole repository be repeated taking a lot
Title: Message Title Parvathy Prasad updated an issue Jenkins / JENKINS-28751 What will happen building a Jenkins project second time, which is setup to checkout from a SVN repository? Will checking out of whole repository be repeated taking a lot of time? Or only the changes added to the repository will be checked out? Change By: Parvathy Prasad Summary: What will happen building a Jenkins project second time, which is setup to checkout from a SVN repository? Will checking out of whole repository be repeated taking a lot of time? Or only the changes added to the rewpository repository will be checked out? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-28408) Jenkins can't load extension ContextExtensionPoint if dependency is optional
Title: Message Title Daniel Spilker commented on JENKINS-28408 Re: Jenkins can't load extension ContextExtensionPoint if dependency is optional Does the manifest of your plugin list the job-dsl plugin as (optional) plugin dependency? Can you unzip the HPI and check META-INF/MANIFEST.MF? It should contain something like Plugin-Dependencies: job-dsl:1.34;resolution:=optional. Which version of the maven-hpi-plugin are you using? 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] [_test] (JENKINS-28751) What will happen building a Jenkins project setup to checkout from a SVN repository? Will checking out of whole repository be repeated taking a lot of time? Or only the
Title: Message Title Parvathy Prasad created an issue Jenkins / JENKINS-28751 What will happen building a Jenkins project setup to checkout from a SVN repository? Will checking out of whole repository be repeated taking a lot of time? Or only the changes added to the rewpository will be checked out? Issue Type: Bug Assignee: Oleg Nenashev Components: _test Created: 04/Jun/15 1:54 PM Priority: Minor Reporter: Parvathy Prasad What will happen building a Jenkins project setup to checkout from a SVN repository? Will checking out of whole repository be repeated taking a lot of time? Or only the changes added to the rewpository will be checked out? Add Comment
[JIRA] [job-dsl-plugin] (JENKINS-28562) Need TriggerContext as ExtensibleContext
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28562 Re: Need TriggerContext as ExtensibleContext Code changed in jenkins User: Daniel Spilker Path: docs/Extending-the-DSL.md docs/Home.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/Job.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/triggers/MavenTriggerContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/triggers/TriggerContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/jobs/MavenJob.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/triggers/MavenTriggerContextSpec.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/triggers/TriggerContextSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/beebf422fc16e3f2cb5d0d32d5b75a29a9e5deed Log: Merge pull request #496 from CoreMedia/ JENKINS-28562 JENKINS-28562 allow to extend the trigger context Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/f1ac175c49af...beebf422fc16 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-28562) Need TriggerContext as ExtensibleContext
Title: Message Title Daniel Spilker resolved as Fixed Will be released in 1.35 Jenkins / JENKINS-28562 Need TriggerContext as ExtensibleContext Change By: Daniel Spilker Status: In Progress Resolved Resolution: Fixed 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] [fitnesse-plugin] (JENKINS-28316) Publish Fitnesse results - fails on 1.12 - reverted to 1.8 - works again
Title: Message Title Ernst Schepp commented on JENKINS-28316 Re: Publish Fitnesse results - fails on 1.12 - reverted to 1.8 - works again Thanks Antoine! I will try it out as soon as it is ready for download in the Plugin Manager. 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] [artifactory-plugin] (JENKINS-27949) "off switch" for Bintray feature
Title: Message Title ryangardner edited a comment on JENKINS-27949 Re: "off switch" for Bintray feature we use artifactory pro internally and have no use for the bintray feature. The button showing up on all our jobs is unnecessary at best and confusing at worst. 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] [artifactory-plugin] (JENKINS-27949) "off switch" for Bintray feature
Title: Message Title ryangardner commented on JENKINS-27949 Re: "off switch" for Bintray feature we use artifactory pro internally and have no use for the bintray feature. 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] [hp-application-automation-tools-plugin] (JENKINS-28750) HP Automation Tools Issue with state = 'Stopping'
Title: Message Title Robert Nielsen created an issue Jenkins / JENKINS-28750 HP Automation Tools Issue with state = 'Stopping' Issue Type: Bug Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 04/Jun/15 1:34 PM Environment: Jenkins 1.5.73 on RHEL 7, hp-application-automation-tools-plugin version 3.0.7 Priority: Major Reporter: Robert Nielsen I have an issue where I’m not getting a report for my performance center runs attached to my test results. The output that I should receive is as follows: Test description: Component-Level Load Test Validating parameters before run Trying to login [PCServer='', User=''] Login succeeded Sending run request [Domain='', Project='', TestID='157', TestInstanceID='18', TimeslotDuration='1:00(h:mm)', PostRunAction='Collate And Analyze'] Run started (TestID: 157, RunID: 244, TimeslotID: 7502) RunID: 244 - State = Initializing RunID: 244 - State = Running RunID: 244 - State = Collating Results RunID: 244 - State = Creating Analysis Data RunID: 244 - State = Finished Publishing run report View report: http://hostname:8080/job/COMMERCE_ALM_LOAD/7/artifact/performanceTestsReports/pcRun244/Report.html Logout succeeded Result Status (PC RunID: 244): SUCCESS
[JIRA] [checkstyle-plugin] (JENKINS-28746) Plugin only publish first result file
Title: Message Title C. S. reopened an issue Jenkins / JENKINS-28746 Plugin only publish first result file Change By: C. S. Resolution: Fixed Status: Resolved Reopened 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] [checkstyle-plugin] (JENKINS-28746) Plugin only publish first result file
Title: Message Title C. S. resolved as Not A Defect Jenkins / JENKINS-28746 Plugin only publish first result file Change By: C. S. Status: Reopened Resolved Resolution: Not A Defect 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] [checkstyle-plugin] (JENKINS-28746) Plugin only publish first result file
Title: Message Title C. S. resolved as Fixed Thanks for your fast reponse. To be honest, I don't know what I can tell you to give more information. I am really confused. In my opinion checkstyle-result.xml contains all scanned files and the errors/warnings of the check. In my case the file checkstyle-result.xml contains only all scanned files and the console tells me there a X errors. Finally I found my mistake ... I did run first checkstyle:checkstyle on the tests resources and run checkstyle:check on main using in both cases the same outputFile. I was expecting that checkstyle:check just breaks and don't dump any file. That explains the checkstyle-result.xml on Jenkins containing only scanned files from main. The real background behind this issue was that Jenkins doesn't load any checkstyle-result.xml any more. I think it was overwritten by the two executions. Jenkins / JENKINS-28746 Plugin only publish first result file Change By: C. S. Status: Open Resolved Resolution: Fixed Add Comment
[JIRA] [checkstyle-plugin] (JENKINS-28746) Plugin only publish first result file
Title: Message Title
C. S. updated an issue
Jenkins / JENKINS-28746
Plugin only publish first result file
Change By:
C. S.
I have recognized that suddenly the checkstyle plugin doesn't publish any checkstyle result anymore. It seems that it finds the files "Checkstyle: 0 warnings from 3 analyses.". There is only one entry in the build log for the checkstyle plugin. No configuration about the output file of checkstyle. {code}[INFO] --- maven-checkstyle-plugin:2.15:check (default-cli) @ warehouse-parent ---log4j:WARN No appenders could be found for logger (org.apache.commons.digester3.Digester.sax).log4j:WARN Please initialize the log4j system properly.[CHECKSTYLE] Parsing file /.../target/checkstyle-result.xml[CHECKSTYLE] Successfully parsed file /.../target/checkstyle-result.xml of module Warehouse Parent POM with 0 unique warnings and 0 duplicates.[CHECKSTYLE] Computing warning deltas based on reference build #497[PMD] No report found for mojo check[INFO] [INFO] --- maven-dependency-plugin:2.8:copy (default) @ warehouse-parent ---[INFO] [INFO] --- jacoco-maven-plugin:0.7.5.201505241946:prepare-agent (default-prepare-agent) @ warehouse-parent ---[INFO] argLine set to "-javaagent:/home/jenkins/.m2/repository/org/jacoco/org.jacoco.agent/0.7.5.201505241946/org.jacoco.agent-0.7.5.201505241946-runtime.jar=destfile=/.../target/jacoco.exec"[INFO] [INFO] --- maven-checkstyle-plugin:2.15:checkstyle (compile) @ warehouse-parent ---[INFO] [INFO] --- maven-checkstyle-plugin:2.15:checkstyle (check-test) @ warehouse-parent ---{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [job-dsl-plugin] (JENKINS-28408) Jenkins can't load extension ContextExtensionPoint if dependency is optional
Title: Message Title Daniel Spilker commented on JENKINS-28408 Re: Jenkins can't load extension ContextExtensionPoint if dependency is optional Hm, no clue. All I did was following the docs, see https://wiki.jenkins-ci.org/display/JENKINS/Dependencies+among+plugins#Dependenciesamongplugins-Optionaldependencies and https://wiki.jenkins-ci.org/display/JENKINS/Defining+a+new+extension+point. 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-28749) Incorrect local modification being identified when svn:keywords are used on 1.8
Title: Message Title dan russell created an issue Jenkins / JENKINS-28749 Incorrect local modification being identified when svn:keywords are used on 1.8 Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 04/Jun/15 12:34 PM Environment: jenkins 1.583 subverison-plugin 2.5 Priority: Critical Reporter: dan russell We have just upgraded jenkins from using 1.5 subversion clients to using 1.8 When jenkins checks out a project that has files using svn:keywords it is incorrectly identifying local changes. The revision number in the file is being indicated as the n-1 time the file was physically changed and not the last time. When the project is checked out using command line svn 1.8.13 the files are checked out correctly with no local changes, so there appears to be a difference between jenkins svn and installed svn.
[JIRA] [git-client-plugin] (JENKINS-28748) git plugin submodule init fail on large submodule
Title: Message Title Florent Le Saout commented on JENKINS-28748 Re: git plugin submodule init fail on large submodule I forgot to mention that you can ask me more details if needed. 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] [git-client-plugin] (JENKINS-28748) git plugin submodule init fail on large submodule
Title: Message Title Florent Le Saout created an issue Jenkins / JENKINS-28748 git plugin submodule init fail on large submodule Issue Type: Bug Assignee: Nicolas De Loof Components: git-client-plugin Created: 04/Jun/15 12:19 PM Environment: Debian Stretch + Jenkins 1.616 (from jenkins deb repo) + openjdk-7 + git plugin 2.3.5 Labels: plugin git-client git-submodule Priority: Major Reporter: Florent Le Saout Git clone command works fine but when I do a submodule init I get a failure message in my build log : > git submodule update --init --recursive FATAL: Command "git submodule update --init --recursive" returned status code 1: stdout: stderr: Cloning into ''... error: RPC failed; result=18, HTTP code = 200 fatal: The remote end hung up unexpectedly fatal: protocol error: bad pack header Clone of 'https://git.xxx' into submodule path 'xxx' failed
[JIRA] [core] (JENKINS-27739) Changes to slave environment variables are ignored by master
Title: Message Title Gilad Baruchian commented on JENKINS-27739 Re: Changes to slave environment variables are ignored by master I have the same issue. Adding PATH=;%PATH% to a batch build step fixed it. Also uninstalling the slave using : installUtil /u c:\jenkins\jenkins-slave.exe sc delete jenkinsslave-c__jenkins and then recreating the slave fixed it. This makes it very hard to manage changes to PATH in the machine, I hope it will be resolved soon. 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] [checkstyle-plugin] (JENKINS-28746) Plugin only publish first result file
Title: Message Title Ulli Hafner commented on JENKINS-28746 Re: Plugin only publish first result file Can you please elaborate? Is there a warning in checkstyle-result.xml of Warehouse Parent POM? What do you mean with suddenly? Did you change anything in your setup? Are there other result files that are not parsed? 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] [google-storage-plugin] (JENKINS-23670) Please add option to remove prefix from local path when performing Classic Upload
Title: Message Title Steven Shipton commented on JENKINS-23670 Re: Please add option to remove prefix from local path when performing Classic Upload I changed the assignee to one of the maintainers to see if we can get any feedback. Maintainers are listed as Matthew Moore and Nghia Tran 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] [google-storage-plugin] (JENKINS-23670) Please add option to remove prefix from local path when performing Classic Upload
Title: Message Title Steven Shipton assigned an issue to Matthew Moore Jenkins / JENKINS-23670 Please add option to remove prefix from local path when performing Classic Upload Change By: Steven Shipton Assignee: Matthew Moore 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] [artifactdeployer-plugin] (JENKINS-28747) Add option to move files rather than copying
Title: Message Title Marco Ambu created an issue Jenkins / JENKINS-28747 Add option to move files rather than copying Issue Type: Improvement Assignee: Gregory Boissinot Components: artifactdeployer-plugin Created: 04/Jun/15 11:39 AM Priority: Minor Reporter: Marco Ambu As one of the main tasks of this plugin is to separate the build information from the build artifacts, it would be good to have an option to actually move files rather than copying as sometimes we do not want to keep the file in the workspace. Add Comment
[JIRA] [job-dsl-plugin] (JENKINS-28562) Need TriggerContext as ExtensibleContext
Title: Message Title Daniel Spilker commented on JENKINS-28562 Re: Need TriggerContext as ExtensibleContext https://github.com/jenkinsci/job-dsl-plugin/pull/496 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-28562) Need TriggerContext as ExtensibleContext
Title: Message Title Daniel Spilker started work on JENKINS-28562 Change By: Daniel Spilker Status: Open In Progress 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] [checkstyle-plugin] (JENKINS-28746) Plugin only publish first result file
Title: Message Title C. S. updated an issue Jenkins / JENKINS-28746 Plugin only publish first result file Change By: C. S. Summary: Plugin doesn't only publish first result files but find them file 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] [checkstyle-plugin] (JENKINS-28746) Plugin doesn't publish result files but find them
Title: Message Title
C. S. updated an issue
Jenkins / JENKINS-28746
Plugin doesn't publish result files but find them
Change By:
C. S.
I have recognized that suddenly the checkstyle plugin doesn't publish any checkstyle result anymore. It seems that it finds the files "Checkstyle: 0 warnings from 3 analyses.".There is no only one entry in the build log for the checkstyle plugin.No configuration about the output file of checkstyle. {code}[INFO] --- maven-checkstyle-plugin:2.15:check (default-cli) @ warehouse-parent ---log4j:WARN No appenders could be found for logger (org.apache.commons.digester3.Digester.sax).log4j:WARN Please initialize the log4j system properly.[CHECKSTYLE] Parsing file /.../target/checkstyle-result.xml[CHECKSTYLE] Successfully parsed file /.../target/checkstyle-result.xml of module Warehouse Parent POM with 0 unique warnings and 0 duplicates.[CHECKSTYLE] Computing warning deltas based on reference build #497[PMD] No report found for mojo check[INFO] [INFO] --- maven-dependency-plugin:2.8:copy (default) @ warehouse-parent ---[INFO] [INFO] --- jacoco-maven-plugin:0.7.5.201505241946:prepare-agent (default-prepare-agent) @ warehouse-parent ---[INFO] argLine set to "-javaagent:/home/jenkins/.m2/repository/org/jacoco/org.jacoco.agent/0.7.5.201505241946/org.jacoco.agent-0.7.5.201505241946-runtime.jar=destfile=/.../target/jacoco.exec"[INFO] [INFO] --- maven-checkstyle-plugin:2.15:checkstyle (compile) @ warehouse-parent ---[INFO] [INFO] --- maven-checkstyle-plugin:2.15:checkstyle (check-test) @ warehouse-parent ---{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [checkstyle-plugin] (JENKINS-28746) Plugin doesn't publish result files but find them
Title: Message Title C. S. created an issue Jenkins / JENKINS-28746 Plugin doesn't publish result files but find them Issue Type: Bug Assignee: Ulli Hafner Components: checkstyle-plugin Created: 04/Jun/15 10:10 AM Environment: Jenkins ver. 1.615 checkstyle-plugin 3.42 checkstyle 6.1.1 Priority: Minor Reporter: C. S. I have recognized that suddenly the checkstyle plugin doesn't publish any checkstyle result anymore. It seems that it finds the files "Checkstyle: 0 warnings from 3 analyses.". There is no entry in the build log for the checkstyle plugin. No configuration about the output file of checkstyle. Add Comment
[JIRA] [p4-plugin] (JENKINS-28726) Default matrix execution strategy produces NPE in latest p4 plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28726 Re: Default matrix execution strategy produces NPE in latest p4 plugin Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/PerforceScm.java src/test/java/org/jenkinsci/plugins/p4/PerforceScmTest.java http://jenkins-ci.org/commit/p4-plugin/786d7c69113b3dad90ad48276076dbdf7779d174 Log: Merge pull request #13 from tanium/matrix Fix JENKINS-28726: Allow for default matrix execution strategy Compare: https://github.com/jenkinsci/p4-plugin/compare/23e9daa55dad...786d7c69113b 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] [p4-plugin] (JENKINS-28726) Default matrix execution strategy produces NPE in latest p4 plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28726 Re: Default matrix execution strategy produces NPE in latest p4 plugin Code changed in jenkins User: unknown Path: src/main/java/org/jenkinsci/plugins/p4/PerforceScm.java src/test/java/org/jenkinsci/plugins/p4/PerforceScmTest.java http://jenkins-ci.org/commit/p4-plugin/dfbf2b7dc3e2df2e1176202faa56022c13073633 Log: Fix JENKINS-28726: Allow for default matrix execution strategy Do not assume that the user has selected "Perforce: Matrix Options". If user has selected "Classic" matrix execution strategy (the default) the perforce plugin would previously have thrown a null pointer exception. Instead, we should just proceed forward with the default behavior 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-28745) Again - Animated ball in job's build history widget won't open Console Output
Title: Message Title Andrey Regentov updated an issue Jenkins / JENKINS-28745 Again - Animated ball in job's build history widget won't open Console Output Change By: Andrey Regentov Labels: 1. 596.2-fixed 616 user-experience 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-28745) Again - Animated ball in job's build history widget won't open Console Output
Title: Message Title Andrey Regentov updated an issue Jenkins / JENKINS-28745 Again - Animated ball in job's build history widget won't open Console Output Change By: Andrey Regentov Environment: Linux/Windows, Jenkins ver 1. 594 616 ; Java 6/7, Jenkins run as service, container-less 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-28745) Again - Animated ball in job's build history widget won't open Console Output
Title: Message Title Andrey Regentov updated an issue Jenkins / JENKINS-28745 Again - Animated ball in job's build history widget won't open Console Output Change By: Andrey Regentov Version 1.616 has just the same regression as in JENKINS-26365. That description follows (version number changed) Seems like since ver. 1. 59* 616 ( particularly or 1. 594 615 ) there is no possibility to go from ball to Console Output. Link behind Ball (green/yellow/red, whatever) in Build History will contain URL for Job Page instead. See attached screenshot (highlighted in left lower corner). 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-22890) Jobs Failing Warning: this build has no associated authentication
Title: Message Title jose sanchez commented on JENKINS-22890 Re: Jobs Failing Warning: this build has no associated authentication i thinjk that i solved the warning Only this a problem with configuration of a task. If you check Configure Build Authorization and you fill Authorize Strategy with Run as User who Triggered build. the warning is out 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-28745) Again - Animated ball in job's build history widget won't open Console Output
Title: Message Title Andrey Regentov updated an issue Jenkins / JENKINS-28745 Again - Animated ball in job's build history widget won't open Console Output Change By: Andrey Regentov Version 1.616 has just the same regression as in Seems like since ver. 1.59* (particularly 1.594) there is no possibility to go from ball to Console Output. Link behind Ball (green/yellow/red, whatever) in Build History will contain URL for Job Page instead. See attached screenshot (highlighted in left lower corner). 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-28745) Again - Animated ball in job's build history widget won't open Console Output
Title: Message Title Andrey Regentov created an issue Jenkins / JENKINS-28745 Again - Animated ball in job's build history widget won't open Console Output Issue Type: Bug Assignee: Tom FENNELLY Components: core Created: 04/Jun/15 9:55 AM Environment: Linux/Windows, Jenkins ver 1.594; Java 6/7, Jenkins run as service, container-less Labels: 1.596.2-fixed user-experience Priority: Minor Reporter: Andrey Regentov Seems like since ver. 1.59* (particularly 1.594) there is no possibility to go from ball to Console Output. Link behind Ball (green/yellow/red, whatever) in Build History will contain URL for Job Page instead. See attached screenshot (highlighted in left lower corner).
[JIRA] [core] (JENKINS-28742) migration: loss builds of a task in web
Title: Message Title jose sanchez started work on JENKINS-28742 Change By: jose sanchez Status: Open In Progress 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-28742) migration: loss builds of a task in web
Title: Message Title jose sanchez stopped work on JENKINS-28742 Change By: jose sanchez Status: In Progress Open 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-28742) migration: loss builds of a task in web
Title: Message Title jose sanchez commented on JENKINS-28742 Re: migration: loss builds of a task in web I forgot to say that when I start jenkins in catalina.out I can see messages like this: jun 04, 2015 8:13:16 AM jenkins.model.RunIdMigrator doMigrate ADVERTENCIA: failed to process /datos/.jenkins/jobs/WREC_WREC_PRE/builds/2014-06-18_14-02-05 java.nio.file.FileAlreadyExistsException: /datos/.jenkins/jobs/WREC_WREC_PRE/builds/1 at sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:422) at sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262) at java.nio.file.Files.move(Files.java:1347) at sun.reflect.GeneratedMethodAccessor38.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at jenkins.model.RunIdMigrator.move(RunIdMigrator.java:297) at jenkins.model.RunIdMigrator.doMigrate(RunIdMigrator.java:264) at jenkins.model.RunIdMigrator.migrate(RunIdMigrator.java:166) at hudson.model.Job.onLoad(Job.java:194) at hudson.model.AbstractProject.onLoad(AbstractProject.java:318) at hudson.model.Project.onLoad(Project.java:98) at hudson.model.Items.load(Items.java:322) at jenkins.model.Jenkins$17.run(Jenkins.java:2655) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:905) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) and this ADVERTENCIA: Failed to inspect /datos/.jenkins/jobs/WREC_WREC_EXP/builds/2: /datos/.jenkins/jobs/WREC_WREC_EXP/builds/2/build.xml doesn't exist 01-jun-2015 23:24:53 jenkins.diagnostics.ooom.Problem$Inspector scan Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [job-dsl-plugin] (JENKINS-28744) Support for confguring publish over CIFS Plugin
Title: Message Title Mark Syms created an issue Jenkins / JENKINS-28744 Support for confguring publish over CIFS Plugin Issue Type: New Feature Assignee: Mark Syms Components: job-dsl-plugin Created: 04/Jun/15 9:36 AM Priority: Minor Reporter: Mark Syms Add support for configuring the Publish over CIFS plugin to the DSL. https://wiki.jenkins-ci.org/display/JENKINS/Publish+Over+CIFS+Plugin Add Comment
[JIRA] [core] (JENKINS-22890) Jobs Failing Warning: this build has no associated authentication
Title: Message Title jose sanchez commented on JENKINS-22890 Re: Jobs Failing Warning: this build has no associated authentication I happen the same. Warning: this build has no associated authentication, so build permissions may be lacking, and downstream projects which cannot even be seen by an anonymous user will be silently skipped Finished: SUCCESS i build a task of ant. in catalina.out only put SUCCESS. How I can get a stack trace? 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-28743) NPE if credentials aren't provided but necessary
Title: Message Title Pavel Janoušek created an issue Jenkins / JENKINS-28743 NPE if credentials aren't provided but necessary Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: core, external-monitor-job-plugin Created: 04/Jun/15 9:24 AM Environment: LTS 1.580 Priority: Minor Reporter: Pavel Janoušek I've tried to use Monitoring External Jobs plug-in as described on Wiki. Plug-in works correctly, but I'm not satisfied with error handling - user isn't navigated properly what goes wrong. Example: Jenkins instance needs a proper credentials provided by client, otherwise request is rejected... Well, through programatical way I've got an expected result: curl -X POST -d '"hexBinary">4142430A02000' https://<_hostname_>/hudson/job/<_job_>/postBuildResult "-//IETF//DTD HTML 2.0//EN"> 401 Authorization Required Authorization Required . . The same via Jenkins core produces a NPE:
[JIRA] [core] (JENKINS-28742) migration: loss builds of a task in web
Title: Message Title jose sanchez created an issue Jenkins / JENKINS-28742 migration: loss builds of a task in web Issue Type: Bug Assignee: Unassigned Attachments: bug_build_history.docx Components: core Created: 04/Jun/15 9:24 AM Environment: EXP Labels: loss builds Priority: Major Reporter: jose sanchez Hello JENKINS have migrated to the latest version. 1.616 Operating system is CentOS release 5.4 (Final) and run in tomcat6 with jdk 1.7 After migration we've had the loss of the old build of tasks. Attached doc with task WREC_WREC_PRE and no job/build in history. And sending directory listing with
[JIRA] [urltrigger-plugin] (JENKINS-28741) Host connection pool not found when URL requires proxy
Title: Message Title Dave Hunt created an issue Jenkins / JENKINS-28741 Host connection pool not found when URL requires proxy Issue Type: Bug Assignee: Gregory Boissinot Components: urltrigger-plugin Created: 04/Jun/15 9:11 AM Priority: Minor Reporter: Dave Hunt When the URL requires use of the Jenkins proxy, I am frequently seeing the following in the Jenkisn log (anonymised): SEVERE: Host connection pool not found, hostConfig=HostConfiguration[host=https://host, proxyHost=http://proxy] The trigger still appears to work, but this generates a lot of noise in the log file. Add Comment
[JIRA] [core] (JENKINS-28601) Order of job table reverse
Title: Message Title mwebber commented on JENKINS-28601 Re: Order of job table reverse The wrong sort order is also used if you look at the page for an individual job, and click on trend (on the left of the page, above the build history). Previously, the trend report showed the newest (at the top) to oldest (at the bottom). In 1.616, this order is reversed. I don't know if this error was also present in 1.615 or not. 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] [cloudformation-plugin] (JENKINS-28740) Can't use variables in "Cloud Formation recipe file. (.json)" field
Title: Message Title
Vladislav Tkatchev created an issue
Jenkins / JENKINS-28740
Can't use variables in "Cloud Formation recipe file. (.json)" field
Issue Type:
Bug
Assignee:
edovale
Components:
cloudformation-plugin
Created:
04/Jun/15 8:23 AM
Priority:
Minor
Reporter:
Vladislav Tkatchev
FATAL: /var/lib/jenkins/workspace/generate-templates/build/cftemplates/$ {TEMPLATE_BODY} (No such file or directory) java.io.FileNotFoundException: /var/lib/jenkins/workspace/generate-templates/build/cftemplates/${TEMPLATE_BODY}
(No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.(FileInputStream.java:146) at hudson.FilePath.read(FilePath.java:1752) at hudson.FilePath.readToString(FilePath.java:1853) at com.syncapse.jenkinsci.plugins.awscloudformationwrapper.CloudFormationBuildStep.newCloudFormation(CloudFormationBuildStep.java:103) at com.syncapse.jenkinsci.plugins.awscloudformationwrapper.CloudFormationBuildStep.perform(CloudFormationBuildStep.java:77) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.Build$BuildExecution.build(Build.java:205) at hudson.model.Build$BuildExecution.doRun(Build.java:162) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) at hudson.model.Run.execute(Run.java:1744) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) Finished: FAILURE
[JIRA] [debian-package-builder-plugin] (JENKINS-20267) GPG signing fails on squeeze, works on wheezy
Title: Message Title Joachim Knust resolved as Fixed # apt-get install -t squeeze-backports devscripts fixes the issue. Jenkins / JENKINS-20267 GPG signing fails on squeeze, works on wheezy Change By: Joachim Knust Status: Open Resolved Resolution: Fixed 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] [debian-package-builder-plugin] (JENKINS-20267) GPG signing fails on squeeze, works on wheezy
Title: Message Title Joachim Knust commented on JENKINS-20267 Re: GPG signing fails on squeeze, works on wheezy It works with devscripts package from squeeze-backports 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] [analysis-core-plugin] (JENKINS-24940) New Warnings link in Static Analysis results shows all warnings
Title: Message Title SCM/JIRA link daemon commented on JENKINS-24940 Re: New Warnings link in Static Analysis results shows all warnings Code changed in jenkins User: Ulli Hafner Path: src/main/java/org/jenkinsci/test/acceptance/plugins/analysis_core/AnalysisAction.java src/test/java/plugins/AnalysisCollectorPluginTest.java src/test/java/plugins/CheckStylePluginTest.java src/test/java/plugins/FindBugsPluginTest.java src/test/java/plugins/PmdPluginTest.java src/test/java/plugins/TaskScannerPluginTest.java src/test/java/plugins/WarningsPluginTest.java http://jenkins-ci.org/commit/acceptance-test-harness/c8a96001366835afd3d8fa15e4e6ed0dfd611443 Log: JENKINS-24940 Added checking of fixed and new warnings. Fixed and new warnings are now checked twice: right after a build and after a restart of Jenkins. Improved test cases: Added verification of fixed warnings. Use new summary table IDs when checking the cells. Check the overview values as well as the number of elements in the fixed warnings table. 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] [analysis-core-plugin] (JENKINS-24940) New Warnings link in Static Analysis results shows all warnings
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-24940 New Warnings link in Static Analysis results shows all warnings Change By: Ulli Hafner Status: Open Resolved Resolution: Fixed 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] [cloudfoundry-plugin] (JENKINS-28602) Error: Default domain calculated from "api" domain
Title: Message Title Andreas Buchen commented on JENKINS-28602 Re: Error: Default domain calculated from "api" domain Thanks for the super fast response. I'll test it once I am back in the office... 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.
