[JIRA] [junit-plugin] (JENKINS-26077) Multiple Test Reports Graphs and Links in Job Page
Vivekanand SV created JENKINS-26077 Multiple Test Reports Graphs and Links in Job Page Issue Type: Bug Assignee: Gregory Boissinot Attachments: Screen Shot 2014-12-16 at 2.12.41 pm.png Components: junit-plugin, xunit-plugin Created: 16/Dec/14 8:47 AM Description: I've upgraded Jenkins from 1.575 to 1.594. After updating, then I open the job page, I see 2 graphs and links for the test reports. Though test reports are correct and available, there are 2 instance of it pointing to the same URLs. I use xUnit plugin to publish my JUnit reports as I needed a way to change the build status based on the test PASS/FAIL count that I wanted which I was not able to do in JUnit plugin. I've attached the screen shot of the job page for reference. Environment: Jenkins version 1.594 JUnit Plugin Version - 1.3 xUnit Plugin Version - 1.92 All the above are latest at the time of posting this issue. Project: Jenkins Priority: Major Reporter: Vivekanand SV 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] [junit-plugin] (JENKINS-26077) Multiple Test Reports Graphs and Links in Job Page
Vivekanand SV updated JENKINS-26077 Multiple Test Reports Graphs and Links in Job Page Change By: Vivekanand SV (16/Dec/14 8:51 AM) Description: IveupgradedJenkinsfrom1.575to1.594.Afterupdating,thenIopenthejobpage,Isee2graphsandlinksforthetestreports.Thoughtestreportsarecorrectandavailable,thereare2instanceofitpointingtothesameURLs.IusexUnitplugintopublishmyJUnitreportsasIneededawaytochangethebuildstatusbasedonthetestPASS/FAILcountthatIwantedwhichIwasnotabletodoinJUnitplugin. Also,allthebuildsarenotshowninthegraphs.Inthereferenceimageattached, Ive beenusingbothCoberturaandxUnitforallthebuilds,buttestgraphstartsonlyfrombuild#322whileitshouldvestartedfrombuild#291asintheCoberturagraph.Ive attachedthescreenshotofthejobpageforreference. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25220) Dashboard Status of build images missing after upgrade to 1.584
Daniel Beck updated JENKINS-25220 Dashboard Status of build images missing after upgrade to 1.584 Change By: Daniel Beck (16/Dec/14 10:04 AM) Labels: dashboardplugin user-experience Component/s: core 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] [email-ext-plugin] (JENKINS-18567) Add Watch button to Job summary screen
Kanstantsin Shautsou commented on JENKINS-18567 Add Watch button to Job summary screen I see no watch buttons in job and got this stacktrace after opening user configuration. javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/Users/Shared/Jenkins/Home/war/WEB-INF/lib/jenkins-core-1.586.jar!/hudson/model/User/configure.jelly:52:65: st:include No page found 'config.jelly' for class hudson.plugins.emailext.watching.EmailExtWatchAction$UserProperty$DescriptorImpl at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.Stapler.service(Stapler.java:237) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:86) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at
[JIRA] [core] (JENKINS-26078) Path to java executable issue with Java 8 on Windows slave
davida2009 created JENKINS-26078 Path to java executable issue with Java 8 on Windows slave Issue Type: Bug Assignee: Unassigned Components: core Created: 16/Dec/14 10:59 AM Description: It seems that Oracle's Java 8 installer for Windows uses symlinks to specify the locations of the java executables: C:\dir \ProgramData\Oracle\Java\javapath Directory of C:\ProgramData\Oracle\Java\javapath 15/12/2014 10:41DIR . 15/12/2014 10:41DIR .. 15/12/2014 10:41SYMLINK java.exe [C:\Program Files\Java\jre1.8.0_25\bin\java.exe] 15/12/2014 10:41SYMLINK javaw.exe [C:\Program Files\Java\jre1.8.0_25\bin\javaw.exe] 15/12/2014 10:41SYMLINK javaws.exe [C:\Program Files\Java\jre1.8.0_25\bin\javaws.exe] The actual path to javaw.exe is now: "C:\Program Files\Java\jre1.8.0_25\bin\javaw.exe" To make this work with Jenkins, we have to add "C:\Program Files\Java\jre1.8.0_25\bin" to the system path so that Jenkins can find javaw.exe. I think a more correct way would be to specify: "C:\ProgramData\Oracle\Java\javapath\javaw.exe" in the "Path to java executable" field of the slave's configuration. But, if I do that, the slave fails to launch and spins at: Connecting to tmsd409 Checking if Java exists Jenkins-slave.xml on the slave shows: executablejavaw.exe/executable So my specified Java path appears not to be copied to the slave. Is this a bug? Project: Jenkins Priority: Minor Reporter: davida2009 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] [windows-slaves-plugin] (JENKINS-26078) Path to java executable issue with Java 8 on Windows slave
Daniel Beck updated JENKINS-26078 Path to java executable issue with Java 8 on Windows slave Change By: Daniel Beck (16/Dec/14 11:10 AM) Component/s: windows-slaves-plugin Component/s: core 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] [p4-plugin] (JENKINS-25682) Using Credentials as attributes shows all perforce credentials with same description
Paul Allen commented on JENKINS-25682 Using Credentials as attributes shows all perforce credentials with same description Thanks for looking into this... Not 100% sure how the @NameWith annotation works, but happy to add it where it is needed. Is there a way I can get a trial version of the Enterprise Jenkins to test this out? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-18567) Add Watch button to Job summary screen
Alex Earl commented on JENKINS-18567 Add Watch button to Job summary screen I should have mentioned that you need to enable watching in the global configuration, and watching is only enabled for jobs that have email-ext configured already. I'm not sure why you are getting that stack trace, I'll look into it. 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] [postbuildscript-plugin] (JENKINS-26079) Jobs triggered through execute build command using parameterized build trigger seem to wait indefinetely
Alex Dover created JENKINS-26079 Jobs triggered through execute build command using parameterized build trigger seem to wait indefinetely Issue Type: Bug Assignee: Gregory Boissinot Components: postbuildscript-plugin Created: 16/Dec/14 11:19 AM Description: We have multiple jobs (A B C) that trigger that all trigger the same job ( D ) as post build "Build Steps" What we see is that each of A,B or C would randomly hang on "Waiting for the completion of D" despite the fact that the D instance they called has completed long time ago (we're talking jobs hanging for days sometimes) The only thing we saw in JVM monitoring that was weird was things like one instance of A waiting for another instance of A with "waiting for Check point COMPLETED on A#XYZ) All the jobs in question have concurrent execution enabled. Unfortunately we're unable to provide an exact scenario in which the hang happens as it appears random and happens on some days but not others. Let me know if there is something in Jenkins logs i should look for to provide more debug info. This issue is critical for us, since we need to execute post-build events in a blocking manner and it seems this plugin is the only one giving us this ability. Environment: Jenkins 1.503 PostBuildScript 0.16 Project: Jenkins Priority: Critical Reporter: Alex Dover 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] [email-ext-plugin] (JENKINS-18567) Add Watch button to Job summary screen
Kanstantsin Shautsou commented on JENKINS-18567 Add Watch button to Job summary screen I added configuration to job, will check global configuration. 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] [clone-workspace-plugin] (JENKINS-12840) Do not use display name for a reference to parent job
Franta Mejta closed JENKINS-12840 as Fixed Do not use display name for a reference to parent job Fixed by https://github.com/jenkinsci/jenkins-clone-workspace-scm-plugin/commit/a659810f2c97aa02408acf022b8c0ee7ae9e6d8a. Change By: Franta Mejta (16/Dec/14 11:26 AM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18781) Configurable channel timeout for slaves
mark mann
commented on JENKINS-18781
Configurable channel timeout for slaves
hey all...
some kind of Jenkins slave connection management settings would help.
I have desperately tried searching through all the config settings for slave and master, but cannot find a way of tuning the poll interval, length of timeout and number of retries to help diagnose or fix my issue.
Using vagrant, I'm spinning up a number of Windows VMs on vsphere and experiencing "random" socket resets or timeouts.
Below is a snippet of the error from the jenkins job trace. (Vagrant is at the point that it is polling the new VMs to discover when they are online and so the connection timeout from WinRM is as expected) however, during this polling cycle Jenkins falls over with the second part of the error trace... "java.net.SocketException: Connection reset"
surely there is a way of setting a number of retries or increasing the length of timeout?
if ($LASTEXITCODE) { exit $LASTEXITCODE } else { exit 0 }
Message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. - connect(2) (http://10.30.40.12:5985)
INFO winrm: Checking whether WinRM is ready...
INFO winrmshell: Attempting to connect to WinRM...
INFO winrmshell: - Host: 10.30.40.12
INFO winrmshell: - Port: 5985
INFO winrmshell: - Username: Administrator
FATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset
hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset
at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41)
at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34)
at hudson.remoting.Request.call(Request.java:174)
at hudson.remoting.Channel.call(Channel.java:722)
at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:167)
at com.sun.proxy.$Proxy45.join(Unknown Source)
at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:950)
at hudson.Launcher$ProcStarter.join(Launcher.java:360)
at hudson.plugins.msbuild.MsBuildBuilder.perform(MsBuildBuilder.java:180)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804)
at hudson.model.Build$BuildExecution.build(Build.java:199)
at hudson.model.Build$BuildExecution.doRun(Build.java:160)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:585)
at hudson.model.Run.execute(Run.java:1684)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:231)
Caused by: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset
at hudson.remoting.Request.abort(Request.java:299)
at hudson.remoting.Channel.terminate(Channel.java:782)
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69)
Caused by: java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(Unknown Source)
at java.net.SocketInputStream.read(Unknown Source)
at java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:77)
at java.io.ObjectInputStream$PeekInputStream.peek(Unknown Source)
at java.io.ObjectInputStream$BlockDataInputStream.peek(Unknown Source)
at java.io.ObjectInputStream$BlockDataInputStream.peekByte(Unknown Source)
at java.io.ObjectInputStream.readObject0(Unknown Source)
at java.io.ObjectInputStream.readObject(Unknown Source)
at hudson.remoting.Command.readFrom(Command.java:92)
at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:71)
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)
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
[JIRA] [tap-plugin] (JENKINS-26080) In 'Tap Extended Test Result' page, the link to tap output file is wrong
Herbert Vojčík created JENKINS-26080 In Tap Extended Test Result page, the link to tap output file is wrong Issue Type: Bug Assignee: Bruno P. Kinoshita Components: tap-plugin Created: 16/Dec/14 11:33 AM Description: In 'Tap Extended Test Result' page on a build, there is the link to the raw output file just above the table with results. This link points to latest output from workspace, not the actual output of that build. This way, one can see old tap tests in a table, but not as a raw file. Project: Jenkins Priority: Minor Reporter: Herbert Vojčík 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] [email-ext-plugin] (JENKINS-18567) Add Watch button to Job summary screen
Kanstantsin Shautsou commented on JENKINS-18567 Add Watch button to Job summary screen Found this button, it shouldn't allow choose types of recipients "developers" etc. 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] [email-ext-plugin] (JENKINS-18567) Add Watch button to Job summary screen
Kanstantsin Shautsou commented on JENKINS-18567 Add Watch button to Job summary screen Please exclude "job" word from "Watch jobs" button text and url. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26081) footer-container is not fixed
Aleix CE created JENKINS-26081 footer-container is not fixed Issue Type: Bug Assignee: Unassigned Components: core Created: 16/Dec/14 11:47 AM Description: #footer-container is defined as position: absolute; but must be position: fixed; because footer moves up when any page is vertically scrolled. Environment: 1.594 Project: Jenkins Labels: gui Priority: Major Reporter: Aleix CE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25755) SPDY is not working on 1.580
Daniel Beck resolved JENKINS-25755 as Not A Defect SPDY is not working on 1.580 Appears to be configuration issue as described by user. Change By: Daniel Beck (16/Dec/14 11:50 AM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [weblogic-deployer-plugin] (JENKINS-21244) Un-escaped $ in module file name passed in command line to weblogic.jar results in the input file not found deployer
Jaap Coomans
commented on JENKINS-21244
Un-escaped $ in module file name passed in command line to weblogic.jar results in the input file not found deployer
A "fix" for this issue broke the functionality of the plugin for me.
In src/main/java/org/jenkinsci/plugins/deploy/weblogic/deployer/WebLogicDeployer.java the following line is added:
args.add("\""+ parameter.getSource()+"\"");
The result is that the source parameter is passed with two pairs of quotes (""/path/to/file""), of which the inner pair remains in the String that is being processed by the WebLogic deployer.
This finally results in a FileNotFoundException:
java.io.FileNotFoundException: /"/var/opt/jenkins/workspace/sample-project/target/sample-project-0.1.0-SNAPSHOT.war" (No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.(FileInputStream.java:131)
at weblogic.utils.FileUtils.copy(FileUtils.java:266)
at weblogic.utils.FileUtils.copy(FileUtils.java:245)
at weblogic.utils.FileUtils.copy(FileUtils.java:186)
at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.upload(ServerConnectionImpl.java:849)
at weblogic.deploy.api.spi.deploy.internal.BasicOperation.uploadFiles(BasicOperation.java:332)
at weblogic.deploy.api.spi.deploy.internal.BasicOperation.execute(BasicOperation.java:465)
at weblogic.deploy.api.spi.deploy.internal.BasicOperation.run(BasicOperation.java:178)
at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.deploy(WebLogicDeploymentManagerImpl.java:390)
at weblogic.deploy.api.tools.deployer.DeployOperation.execute(DeployOperation.java:51)
at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:139)
at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)
at weblogic.utils.compiler.Tool.run(Tool.java:158)
at weblogic.utils.compiler.Tool.run(Tool.java:115)
at weblogic.Deployer.run(Deployer.java:74)
at weblogic.Deployer.main(Deployer.java:55)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26081) footer-container is not fixed
Aleix CE commented on JENKINS-26081 footer-container is not fixed css/style.css 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] [email-ext-plugin] (JENKINS-18567) Add Watch button to Job summary screen
Alex Earl commented on JENKINS-18567 Add Watch button to Job summary screen Ok, it looks like UserProperty implementations have to provide a config.jelly that shows up in the user configuration area. I'll look into this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-23188) Tag List Empty
Saeed Ahmed commented on JENKINS-23188 Tag List Empty I have also same problem. well lets assume there no bugs in the plugin, then what would be procedure to get positive results? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-23188) Tag List Empty
Saeed Ahmed edited a comment on JENKINS-23188 Tag List Empty I have also same problem. well lets assume there no bugs in the plugin, then what would be procedure to get positive results? I have already build successfully. there are some tag in the repo. but I'm using own hosted gitlab repo. 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] [cpptest-plugin] (JENKINS-26082) Cpptest Plugin fails to link to job source code
Rasmus Pedersen created JENKINS-26082 Cpptest Plugin fails to link to job source code Issue Type: Bug Assignee: Gregory Boissinot Components: cpptest-plugin Created: 16/Dec/14 1:37 PM Description: When following the link to the source code I get an error equal to this (taken from https://groups.google.com/forum/#!topic/jenkinsci-users/ml_3pMHdYAg): 01 Copying the source file '/ac_realinfo_srvd/ac_realinfo_srvd/ac_realinfo_data_proc.c' from the workspace to the build folder 'C:\.jenkins\jobs\wacap1.8_inspection\builds\2014-05-05_20-44-43\workspace-files\ef148ebb.tmp' on the Jenkins master failed. 02 Is the file '/ac_realinfo_srvd/ac_realinfo_srvd/ac_realinfo_data_proc.c' a valid filename? 03 If you are building on a slave: please check if the file is accessible under '$JENKINS_HOME/[job-name]//ac_realinfo_srvd/ac_realinfo_srvd/ac_realinfo_data_proc.c' 04 If you are building on the master: please check if the file is accessible under '$JENKINS_HOME/[job-name]/workspace//ac_realinfo_srvd/ac_realinfo_srvd/ac_realinfo_data_proc.c' 05 java.io.IOException: remote file operation failed: /ac_realinfo_srvd/ac_realinfo_srvd/ac_realinfo_data_proc.c at hudson.remoting.Channel@f9f7bc:compiler_1.75 06 at hudson.FilePath.act(FilePath.java:916) 07 at hudson.FilePath.act(FilePath.java:893) 08 at hudson.FilePath.copyTo(FilePath.java:1821) 09 at hudson.plugins.analysis.core.HealthAwareRecorder.copyFilesWithAnnotationsToBuildFolder(HealthAwareRecorder.java:398) 10 at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:165) 11 at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:333) 12 at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) 13 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:745) 14 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:709) 15 at hudson.model.Build$BuildExecution.post2(Build.java:182) 16 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:658) 17 at hudson.model.Run.execute(Run.java:1734) 18 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 19 at hudson.model.ResourceController.execute(ResourceController.java:88) 20 at hudson.model.Executor.run(Executor.java:231) 21 Caused by: java.io.FileNotFoundException: /ac_realinfo_srvd/ac_realinfo_srvd/ac_realinfo_data_proc.c (没有那个文件或目录) 22 at java.io.FileInputStream.open(Native Method) 23 at java.io.FileInputStream.init(FileInputStream.java:138) 24 at hudson.FilePath$37.invoke(FilePath.java:1826) 25 at hudson.FilePath$37.invoke(FilePath.java:1821) 26 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2474) 27 at hudson.remoting.UserRequest.perform(UserRequest.java:118) 28 at hudson.remoting.UserRequest.perform(UserRequest.java:48) 29 at hudson.remoting.Request$2.run(Request.java:328) 30 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 31 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) 32 at java.util.concurrent.FutureTask.run(FutureTask.java:166) 33 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) 34 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) 35 at java.lang.Thread.run(Thread.java:722) What seems to be the problem is the two forward slashes in the file path. Project: Jenkins Priority: Minor Reporter: Rasmus Pedersen This message is automatically generated by JIRA.
[JIRA] [subversion-plugin] (JENKINS-24373) Support Redmine repo browsers that don't start at repository root
Roman Pickl commented on JENKINS-24373 Support Redmine repo browsers that dont start at repository root I came up with the following fix: https://github.com/jenkinsci/redmine-plugin/pull/16 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] [claim-plugin] (JENKINS-12437) Sticky Checkbox to Claim Failed Builds Following the Current One
Michael Schaufelberger commented on JENKINS-12437 Sticky Checkbox to Claim Failed Builds Following the Current One I wish this would work with the test failures. There is a checkbox "Sticky" but even for the test failure I claim directly it seems to forget my claim after a while. ... and I wonder why in the release notes (https://wiki.jenkins-ci.org/display/JENKINS/Claim+plugin) the feature "Option to sticky claim test failures if the failure is "similiar"" is struck through. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds-plugin] (JENKINS-26083) Jenkins jcloud pluging fails to get and assign floating ip on openstack
Razvan Dobre
created JENKINS-26083
Jenkins jcloud pluging fails to get and assign floating ip on openstack
Issue Type:
Bug
Assignee:
abayer
Attachments:
Screen Shot 2014-12-16 at 4.13.10 PM.png
Components:
jclouds-plugin
Created:
16/Dec/14 2:16 PM
Description:
I tried today to integrate jenkins with our openstack deployment (based on Juno) and everythings went smooth until it had to add a floating ip to the instances. At that point i get null pointer exception:
javax.servlet.ServletException: java.lang.RuntimeException: org.jclouds.compute.RunNodesException: error running 1 node group(fedora) location(RegionOne) image(39211c85-d56e-4ca1-b5b7-b36fa91c6e71) size(2) options({scriptPresent=true, securityGroups=[default], userMetadata={Name=fedora}, networks=[6c10f075-b6c1-4767-8a55-794d3d777a2d], userData=[B@10dcaa84, configDrive=false})
Execution failures:
1) ExecutionException on fedora-bc0:
java.util.concurrent.ExecutionException: java.lang.NullPointerException
at shaded.com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:299)
at shaded.com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:286)
at shaded.com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:116)
at org.jclouds.concurrent.FutureIterables$1.run(FutureIterables.java:125)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.NullPointerException
at org.jclouds.openstack.nova.v2_0.compute.functions.AllocateAndAddFloatingIpToNode.apply(AllocateAndAddFloatingIpToNode.java:100)
at org.jclouds.openstack.nova.v2_0.compute.functions.AllocateAndAddFloatingIpToNode.apply(AllocateAndAddFloatingIpToNode.java:53)
at shaded.com.google.common.util.concurrent.Futures$1.apply(Futures.java:711)
at shaded.com.google.common.util.concurrent.Futures$ChainingListenableFuture.run(Futures.java:849)
... 3 more
1 error[s]
Node failures:
0 error[s]
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
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:848)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30)
at
[JIRA] [core] (JENKINS-22932) Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted
Guillaume Agile commented on JENKINS-22932 Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted Same behavior between slaves and master running both on Windows 7sp1 / 2008R2 with Jenkins 1.592 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] [redmine-plugin] (JENKINS-24373) Support Redmine repo browsers that don't start at repository root
Roman Pickl updated JENKINS-24373 Support Redmine repo browsers that dont start at repository root Change By: Roman Pickl (16/Dec/14 3:27 PM) Component/s: redmine-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] [redmine-plugin] (JENKINS-26084) changes with commit message #1, #11 is not linked to redmine correctly
Roman Pickl
created JENKINS-26084
changes with commit message #1, #11 is not linked to redmine correctly
Issue Type:
Bug
Assignee:
gaooh
Components:
redmine-plugin
Created:
16/Dec/14 3:31 PM
Description:
The commit message "#1, #11" does not link to to redmine tickets in the changes view:
I tried the following Test in the Code:
assertAnnotatedTextEquals("#1, #11",
"a href=''#1/a, " +
"a href=''#11/a");
Fails
a href=''#1, #11/a
Project:
Jenkins
Priority:
Minor
Reporter:
Roman Pickl
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] [perforce-plugin] (JENKINS-26076) NPE on Manage Jenkins Page related to hudson.plugins.perforce.PerforcePasswordEncryptor
Kanstantsin Shautsou updated JENKINS-26076 NPE on Manage Jenkins Page related to hudson.plugins.perforce.PerforcePasswordEncryptor Change By: Kanstantsin Shautsou (16/Dec/14 3:30 PM) Environment: Ubunto Ubuntu 12. 4OS 04,jenkins1.580.1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-26076) NPE on Manage Jenkins Page related to hudson.plugins.perforce.PerforcePasswordEncryptor
Kanstantsin Shautsou updated JENKINS-26076 NPE on Manage Jenkins Page related to hudson.plugins.perforce.PerforcePasswordEncryptor Change By: Kanstantsin Shautsou (16/Dec/14 3:31 PM) Environment: Ubuntu12.04,jenkins1.580.1 ,perforce-plugin1.3.31 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] [redmine-plugin] (JENKINS-26084) changes with commit message #1, #11 is not linked to redmine correctly
Roman Pickl updated JENKINS-26084 changes with commit message #1, #11 is not linked to redmine correctly Change By: Roman Pickl (16/Dec/14 3:31 PM) Description: Thecommitmessage#1,#11doesnotlinkto to two redmineticketsinthechangesview:ItriedthefollowingTestintheCode:assertAnnotatedTextEquals(#1,#11,ahref="">ahref="">Failsahref=""> 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] [perforce-plugin] (JENKINS-26076) NPE on Manage Jenkins Page related to hudson.plugins.perforce.PerforcePasswordEncryptor
Kanstantsin Shautsou
updated JENKINS-26076
NPE on Manage Jenkins Page related to hudson.plugins.perforce.PerforcePasswordEncryptor
Change By:
Kanstantsin Shautsou
(16/Dec/14 3:33 PM)
Description:
WhenIdosomeconfigurationandclickonmanagejenkinspageitfaileswithfollowingNPE.
{code}
hudson.plugins.perforce.PerforcePasswordEncryptor.appearsToBeAnEncryptedPassword(PerforcePasswordEncryptor.java:30) athudson.plugins.perforce.PerforceSCM$PerforceSCMDescriptor.setDefaultP4Passwd(PerforceSCM.java:1929) athudson.plugins.perforce.PerforceSCM$PerforceSCMDescriptor.configure(PerforceSCM.java:1961) atjenkins.model.Jenkins.configureDescriptor(Jenkins.java:2898) atjenkins.model.Jenkins.doConfigSubmit(Jenkins.java:2861) atsun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod) atsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) atjava.lang.reflect.Method.invoke(Method.java:606) atorg.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) atorg.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) atorg.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) atorg.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) ...44more
{code}
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] [redmine-plugin] (JENKINS-26084) changes with commit message #1, #11 is not linked to redmine correctly
Roman Pickl updated JENKINS-26084 changes with commit message #1, #11 is not linked to redmine correctly Change By: Roman Pickl (16/Dec/14 3:33 PM) Environment: redmine-0.15,Jenkinsver.1.580.1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco-plugin] (JENKINS-22018) Support for ratcheting of minimum thresholds in Jacoco coverage
Seán Dunne commented on JENKINS-22018 Support for ratcheting of minimum thresholds in Jacoco coverage I'd like to add my voice to this issue. IMO being able to enforce that unit test coverage does not regress is a key feature of a coverage plugin. Would love to see it implemented! 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] [xcode-plugin] (JENKINS-15118) Avgtool does not Find Project File when Setting Technical Version in Xcode Build Step for Workspace-Based Project
James Parker commented on JENKINS-15118 Avgtool does not Find Project File when Setting Technical Version in Xcode Build Step for Workspace-Based Project I'm not getting an error when I set this. Instead it's just not changing the version / build number from what is actually set in the project settings. It was working fine until I updated my build server to Yosemite and installed Xcode 6 alongside Xcode 5. I'm running the latest version of the Xcode 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] [workflow-plugin] (JENKINS-26085) unable to git checkout via ssh key
Patrick Scharrenberg
created JENKINS-26085
unable to git checkout via ssh key
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
16/Dec/14 3:58 PM
Description:
Internally we use gitlab as out git reposity server.
Using a jenkins freestyle project and git plugin a checkout via git over ssh works fine using an ssh private key.
In a workflow project I do not get a working checkout. This is the output I get:
Starting...
Running: Git
git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
git config remote.origin.url git@git.local.domain:ps/project.git # timeout=10
Fetching upstream changes from git@git.local.domain:ps/project.git
git --version # timeout=10
git fetch --tags --progress git@git.local.domain:ps/project.git +refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
Running: Allocate node : Body : End
Running: Allocate node : End
Running: End of Workflow
ERROR: Error fetching remote repo 'origin'
Finished: FAILURE
.. when using the following project:
node('master'){
echo "Starting..."
git url: 'git@git.local.domain:ps/project.git', credentialsId:67c3072d-b9a7-44fa-a5aa-560ba9c1662f
}
I got the credentialsID from the working freestyle project.
When enabling ssh debug-log on the (git/ssh)server side it seems that jenkins/workflow tries to establish the ssh connection without offering a key based authentication and the connection is closed by the client in the ssh preauth phase.
I didn't get to manage to get debug output from the git-plugin when using the workflow plugin, but here is the exception I get from workflow:
Dec 16, 2014 3:50:09 PM FINE org.jenkinsci.plugins.workflow.cps.CpsThread
ran and produced error
java.lang.reflect.UndeclaredThrowableException
at org.jenkinsci.plugins.workflow.cps.CpsStepContext.replay(CpsStepContext.java:409)
at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:164)
at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:98)
at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:45)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:15)
at WorkflowScript.run(WorkflowScript:4)
at Unknown.Unknown(Unknown)
at ___cps.transform___(Native Method)
at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:69)
at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:100)
at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:76)
at sun.reflect.GeneratedMethodAccessor258.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
at com.cloudbees.groovy.cps.impl.CollectionLiteralBlock$ContinuationImpl.dispatch(CollectionLiteralBlock.java:55)
at com.cloudbees.groovy.cps.impl.CollectionLiteralBlock$ContinuationImpl.item(CollectionLiteralBlock.java:45)
at sun.reflect.GeneratedMethodAccessor116.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21)
at com.cloudbees.groovy.cps.Next.step(Next.java:58)
at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:145)
at
[JIRA] [core] (JENKINS-25986) Cannot save jenkins job after updating it
jose lopez commented on JENKINS-25986 Cannot save jenkins job after updating it Yes, I am running behind a firewall but not sure about my reverse proxy configuration. What am I should be looking for to understand if the reverse proxy is correctly configured? Thanks for the feedback This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-26086) ViolationsContext can't set min=0
pjdarton
created JENKINS-26086
ViolationsContext cant set min=0
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
16/Dec/14 4:04 PM
Description:
ViolationsContext.groovy doesn't differentiate between an integer zero and no integer being supplied.
This means that if you specify a zero in your configuration, the code supplies the default value instead.
e.g. if one uses the configuration:
example.groovy
violations() {
jslint(0, 1, 1, 'test-report/*.xml')
}
then one gets a jslint entry specifying a min of 10, not 0:
snippet.xml
entry
stringjslint/string
hudson.plugins.violations.TypeConfig
typejslint/type
min10/min
max1/max
unstable1/unstable
usePatterntrue/usePattern
patterntest-report/*.xml/pattern
/hudson.plugins.violations.TypeConfig
/entry
i.e. the code provided a "min" value of 0, but the resulting XML says 10.
I suspect that this is because ViolationsContext.groovy method createEntry(...) lines 34-36 use the ?: operator to decide whether or not to use a default value:
ViolationsContext.snippet.groovy
private createEntry(Integer min = null, Integer max = null, Integer unstable = null, String pattern = null) {
new ViolationsEntry(
min: min ?: 10,
max: max ?: 999,
unstable: unstable ?: 999,
pattern: pattern)
}
This means that createEntry() will return the same as createEntry(0,0,0,''), which means that if you specify min=0 then you get a min of 10, and I rather wanted to specify a min of 0...
I suspect that the line "min: min ?: 10," should be something like "min: min==null ? 10 : min," so it only gives a default value of min if a null value is given, not merely a "false" value.
Project:
Jenkins
Priority:
Minor
Reporter:
pjdarton
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26087) Jobs sitting on the queue waiting for next available executor.
jose lopez created JENKINS-26087 Jobs sitting on the queue waiting for next available executor. Issue Type: Bug Assignee: Unassigned Components: core Created: 16/Dec/14 4:08 PM Description: Jobs get stuck in the queue even if we have plenty of executors available. Jobs are supposed to go straight to the master node which i have set to "utilize this node as much as possible" but still no luck. This is what I see in the logs: Dec 16, 2014 10:05:15 AM INFO org.eclipse.jetty.util.log.JavaUtilLog info Started SelectChannelConnector@0.0.0.0:8080 Dec 16, 2014 10:05:15 AM INFO org.eclipse.jetty.util.log.JavaUtilLog info Started Ajp13SocketConnector@0.0.0.0:8009 Dec 16, 2014 10:05:15 AM INFO org.eclipse.jetty.util.log.JavaUtilLog info AJP13 is not a secure protocol. Please protect port 8009 Dec 16, 2014 10:05:15 AM INFO winstone.Logger logInternal Winstone Servlet Engine v2.0 running: controlPort=disabled Dec 16, 2014 10:05:15 AM INFO jenkins.InitReactorRunner$1 onAttained Started initialization Dec 16, 2014 10:05:16 AM INFO hudson.ClassicPluginStrategy createPluginWrapper Plugin build-pipeline-plugin.jpi is disabled Dec 16, 2014 10:05:16 AM INFO hudson.PluginManager$1$3$1 isDuplicate Ignoring /var/lib/jenkins/plugins/build-name-setter.hpi because /var/lib/jenkins/plugins/build-name-setter.jpi is already loaded Dec 16, 2014 10:05:16 AM INFO hudson.PluginManager$1$3$1 isDuplicate Ignoring /var/lib/jenkins/plugins/rtc.hpi because /var/lib/jenkins/plugins/rtc.jpi is already loaded Dec 16, 2014 10:05:16 AM INFO hudson.PluginManager$1$3$1 isDuplicate Ignoring /var/lib/jenkins/plugins/copy-to-slave.hpi because /var/lib/jenkins/plugins/copy-to-slave.jpi is already loaded Dec 16, 2014 10:05:16 AM INFO jenkins.InitReactorRunner$1 onAttained Listed all plugins Dec 16, 2014 10:05:16 AM INFO hudson.plugins.greenballs.PluginImpl start Green Balls! Dec 16, 2014 10:05:16 AM INFO jenkins.InitReactorRunner$1 onAttained Prepared all plugins Dec 16, 2014 10:05:18 AM INFO jenkins.InitReactorRunner$1 onAttained Started all plugins Dec 16, 2014 10:05:18 AM INFO jenkins.InitReactorRunner$1 onAttained Augmented all extensions Dec 16, 2014 10:05:19 AM INFO jenkins.InitReactorRunner$1 onAttained Loaded all jobs Dec 16, 2014 10:05:20 AM INFO org.jenkinsci.main.modules.sshd.SSHD start Started SSHD at port 60003 Dec 16, 2014 10:05:20 AM INFO jenkins.InitReactorRunner$1 onAttained Completed initialization Dec 16, 2014 10:05:20 AM INFO hudson.slaves.SlaveComputer tryReconnect Attempting to reconnect AutoSlave1 Dec 16, 2014 10:05:20 AM INFO hudson.slaves.SlaveComputer tryReconnect Attempting to reconnect AutoSlave2 Dec 16, 2014 10:05:20 AM INFO hudson.slaves.SlaveComputer tryReconnect Attempting to reconnect AutoSlave3 Dec 16, 2014 10:05:20 AM INFO hudson.slaves.SlaveComputer tryReconnect Attempting to reconnect AutoSlave4 Dec 16, 2014 10:05:20 AM INFO hudson.slaves.SlaveComputer tryReconnect Attempting to reconnect AutoSlave5 Dec 16, 2014 10:05:20 AM INFO hudson.slaves.SlaveComputer tryReconnect Attempting to reconnect AutoSlave6 Dec 16, 2014 10:05:20 AM INFO hudson.slaves.SlaveComputer tryReconnect Attempting to reconnect AutoSlave7 Dec 16, 2014 10:05:20 AM INFO hudson.slaves.SlaveComputer tryReconnect Attempting to reconnect AutoSlave8 Dec 16, 2014 10:05:20 AM INFO hudson.slaves.SlaveComputer tryReconnect Attempting to reconnect AutoSlave9 Dec 16, 2014 10:05:20 AM INFO hudson.slaves.SlaveComputer tryReconnect Attempting to reconnect AutoSlave10 Dec 16, 2014 10:05:20 AM INFO hudson.slaves.SlaveComputer tryReconnect Attempting to reconnect AutoSlave11 Dec 16, 2014 10:05:20 AM INFO hudson.slaves.SlaveComputer tryReconnect Attempting to reconnect AutoSlave12 Dec 16, 2014 10:05:20 AM INFO hudson.slaves.SlaveComputer tryReconnect Attempting to reconnect AutoSlave13 Dec 16, 2014 10:05:20 AM INFO hudson.slaves.SlaveComputer tryReconnect Attempting to reconnect AutoSlave14 Dec 16, 2014 10:05:20 AM INFO hudson.slaves.SlaveComputer tryReconnect Attempting to reconnect AutoSlave15 Dec 16, 2014 10:05:20 AM INFO
[JIRA] [workflow-plugin] (JENKINS-26085) Credentials support for git step
Jesse Glick updated JENKINS-26085 Credentials support for git step There is no credentialsId parameter for the git step. Currently if you need to pass credentials to a Git checkout, you must use the generic checkout step; the Snippet Generator is the easiest way to configure it. Change By: Jesse Glick (16/Dec/14 4:29 PM) Summary: unableto Credentialssupportfor git checkoutviasshkey step Issue Type: Bug NewFeature 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] [xcode-plugin] (JENKINS-15118) Avgtool does not Find Project File when Setting Technical Version in Xcode Build Step for Workspace-Based Project
lacostej commented on JENKINS-15118 Avgtool does not Find Project File when Setting Technical Version in Xcode Build Step for Workspace-Based Project James, do you have more logs ? 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] [p4-plugin] (JENKINS-25682) Using Credentials as attributes shows all perforce credentials with same description
Jesse Glick commented on JENKINS-25682 Using Credentials as attributes shows all perforce credentials with same description Easiest is to install the metaplugin https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Enterprise+by+CloudBees and choose the minimal (license-only) installation mode, asking for an evaluation license when prompted, then go and install the Templates plugin. If you do not want to bother with that, you can confirm the correct behavior in a (JenkinsRule-based) test by just calling CredentialsNameProvider.name on your credentials and asserting that the result is a meaningful label. If you are stuck, I can try producing a pull request. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26088) Cant save changes while Configuring System
jose lopez created JENKINS-26088 Cant save changes while Configuring System Issue Type: Bug Assignee: Unassigned Components: core Created: 16/Dec/14 4:40 PM Description: I hit the following exception when trying to save my changes on the configuration UI (Manage Jenkins -- Configure System) Stack trace javax.servlet.ServletException: java.lang.NullPointerException 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:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:960) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1021) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668) at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:898) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:920) at
[JIRA] [core] (JENKINS-26087) Jobs sitting on the queue waiting for next available executor.
jose lopez commented on JENKINS-26087 Jobs sitting on the queue waiting for next available executor. Forgot to add that if I restart Jenkins jobs seem to be going to the master and getting executed but after a while (2 or 3 jobs down the road) they start going back to the queue and not moving. This happens when I execute the jobs manually or triggered automatically by another job (pipeline) 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] [p4-plugin] (JENKINS-25682) Using Credentials as attributes shows all perforce credentials with same description
Paul Allen commented on JENKINS-25682 Using Credentials as attributes shows all perforce credentials with same description Thanks. I like the JenkinsRule test idea, always prefer to automate tests where I can. I'll give it a go, if I get any trouble I'll ask for help. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-4747) Timer Task: NoClassDefFoundError: at hudson.model.Hudson.getComputer
jose lopez commented on JENKINS-4747 Timer Task: NoClassDefFoundError: at hudson.model.Hudson.getComputer I am hitting the exact same exceptions on Jenkins 1.593. Opened https://issues.jenkins-ci.org/browse/JENKINS-26087?focusedCommentId=217811 to keep track of it This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25220) Dashboard Status of build images missing after upgrade to 1.584
Michael Merrell commented on JENKINS-25220 Dashboard Status of build images missing after upgrade to 1.584 Well, my pull request is still open, so it hasn't been fixed by that route. You can always make the change to the jelly file locally and repack the WAR file like I have. 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] [p4-plugin] (JENKINS-25682) Using Credentials as attributes shows all perforce credentials with same description
Paul Allen commented on JENKINS-25682 Using Credentials as attributes shows all perforce credentials with same description Ok, this change should resolve the issue: https://github.com/jenkinsci/p4-plugin/commit/aa910d56936a308600bdad568e2ab23ada636b7d Not sure why it didn't link the commit with JIRA? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19561) Unsafe inefficient concurrency in XStream
Jesse Glick updated JENKINS-19561 Unsafe inefficient concurrency in XStream Change By: Jesse Glick (16/Dec/14 6:17 PM) Labels: performancethreads xstream 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] [p4-plugin] (JENKINS-25682) Using Credentials as attributes shows all perforce credentials with same description
Jesse Glick commented on JENKINS-25682 Using Credentials as attributes shows all perforce credentials with same description The JIRA link daemon is dead, I think. Sangeeta Narang you can try this build if you want to verify: https://jenkins.ci.cloudbees.com/job/plugins/job/p4-plugin/org.jenkins-ci.plugins$p4/104/artifact/org.jenkins-ci.plugins/p4/1.0.24-SNAPSHOT/p4-1.0.24-SNAPSHOT.hpi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-25387) JGit in git client should support reference repositories
Craig Silverstein
commented on JENKINS-25387
JGit in git client should support reference repositories
Stephan, I have a kinda-crazy feature request: would it be possible to augment this functionality to also use reference repos for submodules? In our use case, we have a submodule that is as large as our 'main' module.
git submodule update supports the `--reference` flag, so I think this would be replacing the current `git submodule update --init --recursive` with something like (bash-style psuedocode):
git submodule init
refdir=`cat .git/objects/info/alternates`
for repo in `git submodule status | awk '{print $2}'`; do
if [ -d "$refdir/../modules/$repo/objects ]; then
git submodule update --reference $refdir/$repo --recursive -- $repo
else
git submodule update --recursive -- $repo
fi
done
(Though I admit I'm confused by how git references play around with submodules, so maybe the above won't work. It seemed to in my testing, at least.)
Thanks!
craig
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25986) Cannot save jenkins job after updating it
Daniel Beck commented on JENKINS-25986 Cannot save jenkins job after updating it There should be some warning on the /manage page if Jenkins detects a broken reverse proxy setup. Related wiki page: https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+says+my+reverse+proxy+setup+is+broken This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25986) Cannot save jenkins job after updating it
jose lopez commented on JENKINS-25986 Cannot save jenkins job after updating it Ok, seems that I don't have any problems with my reverse proxy. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-slaves-plugin] (JENKINS-25997) Jenkins node connectivity Issue using SSH agent
Kohsuke Kawaguchi commented on JENKINS-25997 Jenkins node connectivity Issue using SSH agent Please see Wiki page for the further diagnostic steps. We need more info to be able to help you. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-25482) Extended Email plugin triggers can't be configured
Daniel Spilker resolved JENKINS-25482 as Fixed Extended Email plugin triggers cant be configured Will be released in 1.28. Change By: Daniel Spilker (16/Dec/14 7:22 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25742) Concurrent job rename and edit view results in deadlock that puts Jenkins in a non responsive state
Daryl Spartz commented on JENKINS-25742 Concurrent job rename and edit view results in deadlock that puts Jenkins in a non responsive state I've submitted pull request with fix for this issue: https://github.com/jenkinsci/jenkins/pull/1488 See comments there on how to reproduce. I've reproduced on 1.593 and LTS we are using 1.565.3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-25387) JGit in git client should support reference repositories
Mark Waite commented on JENKINS-25387 JGit in git client should support reference repositories I don't think the code change which provided the reference implementation for JGit can be readily reused or reworked to support reference repositories for submodules. I think the core challenge is already indicated in your bash-style pseudocode. As far as I can tell, you assume the reference repository for each submodule must be at $refdir/$repo. My assumption is that is not general enough compared to the needs of the 50,000+ installations of git. I think adding reference support to submodules includes some of the same challenges as are represented in JENKINS-20941. That request asks for credential support. In the case of both credentials and reference repositories, we need to map a repository URL to something, and use that "something" in a later git command. I think git credentials with submodules might use the existing credentials system to attempt to choose a credential for the repository. That won't work all the time, but might be good enough. Reference repositories need to map a submodule repository URL to a local directory which contains the reference repository. Another approach would be to try to apply Jesse Glick's pattern of reference repository from the Mercurial plugin. I believe he creates a local clone of the repository on the Jenkins master server, then clones to slaves from the Jenkins master server. We might even want to extend it to clone a reference repository onto the slave node when a job runs. All those alternatives have some complications which will make them challenging. 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] [coverity-plugin] (JENKINS-19451) Broken links to coverity instance when SSL is used
Ken Dang assigned JENKINS-19451 to Ken Dang Broken links to coverity instance when SSL is used Change By: Ken Dang (16/Dec/14 7:37 PM) Assignee: KenDang This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-26089) Repository browser doesn't work for Visual studio team foundation server 2013
Thomas Scheyvaerts created JENKINS-26089 Repository browser doesnt work for Visual studio team foundation server 2013 Issue Type: Bug Assignee: redsolo Components: tfs-plugin Created: 16/Dec/14 7:51 PM Description: The URL's to the TFS repository browser (diff.aspx en cs.aspx) are changed in TFS 2013. Next is an overview of the new URL's. current webaccess URL: http://TFS-SERVER:8080/tfs/Main/cs.aspx?cs=CHANGESET-NR TFS 2013 URL: http://TFS-SERVER:8080/tfs/Main/_versionControl/changeset/CHANGESET-NR current diff URL: http://TFS-SERVER:8080/tfs/Main/diff.aspx?opath=FILE1ocs=CHANGESET-FILE1mpath=FILE2mcs=CHANGESET-FILE2 TFS 2013 URL: http:/TFS-SERVER:8080/tfs/Main/_versionControl/changeset/CHANGESET-FILE2#path=FILE_a=compare (Notice that you don't need to give the previous changeset number) Environment: tfs-plugin 3.1.1 TFS server 2013 Project: Jenkins Priority: Major Reporter: Thomas Scheyvaerts This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-26089) Repository browser doesn't work for Visual studio team foundation server 2013
Thomas Scheyvaerts updated JENKINS-26089 Repository browser doesnt work for Visual studio team foundation server 2013 Change By: Thomas Scheyvaerts (16/Dec/14 7:52 PM) Description: TheURLstotheTFSrepositorybrowser(diff.aspxencs.aspx)arechangedinTFS2013.NextisanoverviewofthenewURLs. + currentwebaccessURL: + http://TFS-SERVER:8080/tfs/Main/cs.aspx?cs=CHANGESET-NRTFS2013URL:http://TFS-SERVER:8080/tfs/Main/_versionControl/changeset/CHANGESET-NR + currentdiffURL: + http://TFS-SERVER:8080/tfs/Main/diff.aspx?opath=FILE1ocs=CHANGESET-FILE1mpath=FILE2mcs=CHANGESET-FILE2TFS2013URL:http:/TFS-SERVER:8080/tfs/Main/_versionControl/changeset/CHANGESET-FILE2#path=FILE_a=compare(Noticethatyoudontneedtogivethepreviouschangesetnumber) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-26089) Repository browser doesn't work for Visual studio team foundation server 2013
Thomas Scheyvaerts commented on JENKINS-26089 Repository browser doesnt work for Visual studio team foundation server 2013 It seems that the links where already changed in TFS 2012: see issue JENKINS-16207 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-25387) JGit in git client should support reference repositories
Craig Silverstein commented on JENKINS-25387 JGit in git client should support reference repositories Mark, thanks for your response. You're right that I am assuming that the repo that we're referencing has the same directory structure as our repo that is, that the submodules are in the same location in both cases. I think for jenkins, the common case is that you have to clone a repo in a number of different workspaces, and would like them all to --reference a common repo to speed up their fetches. In that case, all repos have the same structure, so using $refdir/$repo will work. (Note that $repo in my pseudocode isn't the name of a repo or anything like that, it's the directory that the submodule lives in inside the 'main' repo. I probably misnamed it. If all occurrences of $repo above were renamed to $submodule_dir, would that help? ) 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] [weblogic-deployer-plugin] (JENKINS-21244) Un-escaped $ in module file name passed in command line to weblogic.jar results in the input file not found deployer
Raphael CHAUMIER commented on JENKINS-21244 Un-escaped $ in module file name passed in command line to weblogic.jar results in the input file not found deployer A performed a rollback on the unexpected commit. The fixed version is 2.11 Sorry This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-22251) Executing tf using the TFS Plugin throws an IO exception
Ziv Tirosh commented on JENKINS-22251 Executing tf using the TFS Plugin throws an IO exception hi change the Path system variable to your IDE : C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE 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] [feature-branch-notifier-plugin] (JENKINS-23703) Feature Branch Notifier won't trigger
Tõnis Pool resolved JENKINS-23703 as Fixed Feature Branch Notifier wont trigger I've accepted Mads pull request and released plugin version 1.4. Closing this issue in hindsight. Change By: Tõnis Pool (16/Dec/14 9:16 PM) Status: Open Resolved Assignee: TõnisPool Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25971) Job list and console output are not properly aligned in the new UI
Chad Beaudin commented on JENKINS-25971 Job list and console output are not properly aligned in the new UI Is there a version slated for a fix for this? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [accurev-plugin] (JENKINS-11461) FATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset
Michael Hamann commented on JENKINS-11461 FATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset I'm seeing something very close to this on Jenkins 1.594. Our server is running on a CentOS VM, the slaves are Windows 7 VMs running via JNLP as a service. The slave VMs were "moved over" from our Hudson (2.2.1; also running on CentOS) server where we are NOT seeing this issue. The Hudson service as well as files/directories were deleted before the VMs were set up as Jenkins nodes. The Hudson and Jenkins instances are running on different CentOS VMs. We see the problem on all of our Jenkins Windows 7 slaves, and it occasionally occurs multiple times per day per node. My impression is that it is very likely to happen if the slaves sit idle for a long time (say 4+ hours). Once we get a failure, subsequent builds on the same node will run normally. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25971) Job list and console output are not properly aligned in the new UI
Daniel Beck commented on JENKINS-25971 Job list and console output are not properly aligned in the new UI This issue will be updated when a fix has been merged. It will then be released 1-2 weeks later. https://wiki.jenkins-ci.org/display/JENKINS/Release+Process This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26081) footer-container is not fixed
Daniel Beck updated JENKINS-26081 footer-container is not fixed Change By: Daniel Beck (16/Dec/14 10:09 PM) Labels: gui user-experience This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26081) footer-container is not fixed
Daniel Beck commented on JENKINS-26081 footer-container is not fixed Could you upload a screenshot (GIF, PNG or JPG) demonstrating the problem? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26087) Jobs sitting on the queue waiting for next available executor.
Daniel Beck updated JENKINS-26087 Jobs sitting on the queue waiting for next available executor. Change By: Daniel Beck (16/Dec/14 10:11 PM) Labels: java-ibm This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26087) Jobs sitting on the queue waiting for next available executor.
Daniel Beck commented on JENKINS-26087 Jobs sitting on the queue waiting for next available executor. Workaround: Use a JRE that doesn't suck as badly as J9. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26088) Cant save changes while Configuring System
Daniel Beck updated JENKINS-26088 Cant save changes while Configuring System May again be a J9 issue. Change By: Daniel Beck (16/Dec/14 10:14 PM) Labels: java-ibm This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26007) Job dependent on SSH Plugin does not fail when the plugin is not installed
Daniel Beck resolved JENKINS-26007 as Not A Defect Job dependent on SSH Plugin does not fail when the plugin is not installed Jenkins discards unloadable data when it encounters it. This is recorded on the 'Manage Jenkins » Manage Old Data' page that should contain specific information what cannot be loaded, and why. IIRC the /manage page shows an administrative monitor (or "warning") that points there if some data could not be loaded. Change By: Daniel Beck (16/Dec/14 10:20 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25880) Unable to delete/edit a Jenkins project
Daniel Beck commented on JENKINS-25880 Unable to delete/edit a Jenkins project Why are you writing "delete/edit'? How are you combining these two independent actions? Please provide the project's config.xml file. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25904) Workspace clean up does not get an exclusive lease
Daniel Beck updated JENKINS-25904 Workspace clean up does not get an exclusive lease Rewrote to make more general. I hope that's OK, otherwise just revert. Change By: Daniel Beck (16/Dec/14 10:25 PM) Summary: Workspace beingcleaned clean up byWorkspaceCleanupThreadcanbereusedbynextbuild doesnotgetanexclusivelease Description: Suggestedapproach:renamethendelete.See:https://github.com/jenkinsci/jenkins/pull/1478#issuecomment-65450375 Similarproblemsarisewhenusersmanuallywipetheworkspaceandthen(whileongoing)triggerabuild,orwipetheworkspacewhileabuildisongoing. Labels: workspace_corruption 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] [perforce-plugin] (JENKINS-26076) NPE on Manage Jenkins Page related to hudson.plugins.perforce.PerforcePasswordEncryptor
Oleg Nenashev started work on JENKINS-26076 NPE on Manage Jenkins Page related to hudson.plugins.perforce.PerforcePasswordEncryptor Change By: Oleg Nenashev (16/Dec/14 10:53 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-26076) NPE on Manage Jenkins Page related to hudson.plugins.perforce.PerforcePasswordEncryptor
Oleg Nenashev commented on JENKINS-26076 NPE on Manage Jenkins Page related to hudson.plugins.perforce.PerforcePasswordEncryptor Confirmed. I have checked value setup flows, but forgot to add proper checks to verify methods This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22941) Way to mark an Executable that should not block isReadyToRestart
Jesse Glick commented on JENKINS-22941 Way to mark an Executable that should not block isReadyToRestart Also would like an API allowing the flyweight WorkflowRun executable to block a restart while in the middle of a CPS native method. This is especially important for a potentially slow operation like ArtifactArchiver.perform which cannot be stopped partway through. When Jenkins goes into quiet mode, new CPS-transformed calls should not start (so the program counter should pause), and any native methods currently running should be allowed to run to completion before shutdown occurs. This API could be very similar to the one above; essentially a way of customizing the logic of what constitutes a “running executable”. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26090) Executables.getExecutor
Jesse Glick created JENKINS-26090 Executables.getExecutor Issue Type: Improvement Assignee: Unassigned Components: core Created: 16/Dec/14 11:16 PM Description: Should be extracted from Run. Project: Jenkins Labels: api workflow Priority: Minor Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26091) Marker interface for things with URL
Jesse Glick created JENKINS-26091 Marker interface for things with URL Issue Type: Improvement Assignee: Unassigned Components: core Created: 16/Dec/14 11:17 PM Description: Like ModelObject, want an interface with a String getUrl() method. For Workflow, this would be implemented at least by FlowExecution, FlowExecutionOwner, and FlowNode. Project: Jenkins Labels: api workflow Priority: Minor Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26092) executors.jelly interface underspecified
Jesse Glick created JENKINS-26092 executors.jelly interface underspecified Issue Type: Bug Assignee: Unassigned Components: core Created: 16/Dec/14 11:18 PM Description: Calls various unspecified methods on the Queue.Executable. Should be extracted into an interface. Project: Jenkins Labels: api workflow Priority: Minor Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26093) Code snippet generation for BuildTriggerStep.parameters
Jesse Glick created JENKINS-26093 Code snippet generation for BuildTriggerStep.parameters Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 16/Dec/14 11:28 PM Description: Should ideally look up the Job from the job field and dynamically include a list of value.jelly blocks; just not sure how to wire up the _javascript_ for this. A potential alternative (requiring a core change) would be for ParameterValue, not just ParameterDefinition, to be Describable (where config.jelly just calls value.jelly, passing it = instance), and these would all have a Descriptor, so that f:repeatableHeteroProperty field="parameters"/ would suffice to configure a ListParameterValue. Not as nice for the user, though. Kohsuke Kawaguchi also originally suggested adding ParameterDefinition.createValue(Object) as yet another alternative, but again this is not as friendly to snippet generation. Project: Jenkins Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [weblogic-deployer-plugin] (JENKINS-24789) Possibility to skip a deployment task during a build by specifying what task to disable with a build parameter
Raphael CHAUMIER commented on JENKINS-24789 Possibility to skip a deployment task during a build by specifying what task to disable with a build parameter This new featuree has been added to the 2.12 plugin version. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26094) DescribableHelper
Jesse Glick created JENKINS-26094 DescribableHelper Issue Type: New Feature Assignee: Unassigned Components: core Created: 16/Dec/14 11:34 PM Description: DescribableHelper seems like it belongs in core, or even Stapler. One abstraction problem is the use of ReflectionCache.getCachedClass from Groovy, which should perhaps be replaced with an extension point allowing coercions to be added in a modular fashion (such as the one currently hardcoded for URL). Project: Jenkins Labels: api workflow Priority: Minor Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26094) DescribableHelper
Jesse Glick updated JENKINS-26094 DescribableHelper Change By: Jesse Glick (16/Dec/14 11:34 PM) Priority: Minor Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [weblogic-deployer-plugin] (JENKINS-24789) Possibility to skip a deployment task during a build by specifying what task to disable with a build parameter
Raphael CHAUMIER resolved JENKINS-24789 as Fixed Possibility to skip a deployment task during a build by specifying what task to disable with a build parameter 2.12 Change By: Raphael CHAUMIER (16/Dec/14 11:34 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [weblogic-deployer-plugin] (JENKINS-24789) Possibility to skip a deployment task during a build by specifying what task to disable with a build parameter
Raphael CHAUMIER edited a comment on JENKINS-24789 Possibility to skip a deployment task during a build by specifying what task to disable with a build parameter This new feature has been added to the 2.12 plugin version. For further information. Look at the chapter 'Disabling deployment task at runtime' on the wiki page This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26095) Run.doStop
Jesse Glick created JENKINS-26095 Run.doStop Issue Type: Improvement Assignee: Unassigned Components: core Created: 16/Dec/14 11:38 PM Description: Lift up from AbstractBuild. See WorkflowRun.doStop. Project: Jenkins Labels: api workflow Priority: Minor Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [weblogic-deployer-plugin] (JENKINS-23700) Maven projects should default to search the target folder
Raphael CHAUMIER commented on JENKINS-23700 Maven projects should default to search the target folder Probably will be resolved when the issue JENKINS-20351 https://issues.jenkins-ci.org/browse/JENKINS-20351 will be implemented 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] [weblogic-deployer-plugin] (JENKINS-23700) Maven projects should default to search the target folder
Raphael CHAUMIER edited a comment on JENKINS-23700 Maven projects should default to search the target folder Probably will be resolved when the issue JENKINS-20351 will be implemented This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26096) Fixed FilePath.toComputer
Jesse Glick created JENKINS-26096 Fixed FilePath.toComputer Issue Type: Bug Assignee: Unassigned Components: core Created: 16/Dec/14 11:40 PM Description: As noted in FilePathPickle, the current version does not work if the slave has since been disconnected. It needs to be rewritten to use a listener. Project: Jenkins Labels: api workflow Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26097) AutoCompletionCandidates for Label
Jesse Glick created JENKINS-26097 AutoCompletionCandidates for Label Issue Type: Improvement Assignee: Unassigned Components: core Created: 16/Dec/14 11:45 PM Description: AbstractProjectDescriptor.doAutoCompleteLabel has a complex implementation including AutoCompleteSeeder that ought to be made available as an API in Label. Similarly doCheckLabel should be available as an API. For use from Workflow (ExecutorStep.DescriptorImpl), LabelValidator has to be generalized to handle any Job (probably meaning the nested class in AbstractProject should be deprecated and it should be moved to a top-level class). This is assuming that there are some meaningful implementations for other job types; until INFRA-180 is fixed this is tricky to verify but https://github.com/search?type=Codeq=user%3Ajenkinsci+LabelValidator turns up no hits. (SecurityTokensNodeProperty in cloudbees-folders-plus could add one, perhaps.) Project: Jenkins Labels: api workflow Priority: Minor Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26098) Asynch Queue.Executable
Jesse Glick created JENKINS-26098 Asynch Queue.Executable Issue Type: Improvement Assignee: Unassigned Components: core Created: 16/Dec/14 11:46 PM Description: PlaceholderExecutable currently occupies an actual Executor thread by just sleeping, which is wasteful since there is a cost to holding a running thread. Would be better if Queue.Executable had an optional mode which would be friendly to asynchronous jobs. Project: Jenkins Labels: api workflow performance threads Priority: Critical Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-plugin] (JENKINS-26099) Configurable ID for Credentials
Jesse Glick created JENKINS-26099 Configurable ID for Credentials Issue Type: Improvement Assignee: stephenconnolly Components: credentials-plugin Created: 16/Dec/14 11:49 PM Description: It should be easier to refer to a particular Credentials from a script. Currently you can use GenericSCMStep with a hardcoded ID (or see JENKINS-26085). But this looks ugly in the script. It would be nicer for not just Workflow but other non-UI-driven plugins as well (Templates, Job DSL, YAML Project, c.) if you could define a meaningful ID when creating a StandardCredentials. Perhaps this could be in an Advanced block when configuring the credentials. Without such a UI, you have to resort to editing $JENKINS_HOME/credentials.xml and reloading configuration from disk. Note that the actual lookup of the live StandardCredentials by its ID happens in some context, where the Item and DomainRestrictions are considered. So if the referent is not appropriate in the current context, the plugin code using the ID (for example, git-plugin) is responsible for rejecting the attempt, minimally just by saying that no Credentials with that ID could be found. In other words, security sanity checks can be done in UI forms but they must be done again at runtime anyway; this is true even for freestyle projects since you can just upload a new config.xml with an arbitrary credentialsId.../credentialsId. The Credentials plugin does of course need to take care to ensure that IDs are unique within a given CredentialsProvider when loading definitions from disk or adding definitions. Project: Jenkins Labels: workflow Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-6097) Update Center could upgrade plugins to latest-release-for-my-Hudson
Jesse Glick
commented on JENKINS-6097
Update Center could upgrade plugins to latest-release-for-my-Hudson
Outstanding tasks:
Directory name fix. Move u2/ to u/
Retire infra_update_center{,_stable,_experimental} once v3 is in production
Puppet shall not manage htacess and readme.html in local-modules/u_j_o/files
Merge v3 to master in git
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24141) SCM with non-AbstractProject, revisited
Jesse Glick commented on JENKINS-24141 SCM with non-AbstractProject, revisited Perhaps also need to add SCM.buildEnvVars(Run, FilePath, MapString,String). 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] [workflow-plugin] (JENKINS-26100) SCM steps should return revision state
Jesse Glick created JENKINS-26100 SCM steps should return revision state Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 16/Dec/14 11:59 PM Description: The return value of the git step should be the commit hash, etc., and there should be a way to pass that back in to a subsequent git step in case you want to check out the same revision in another workspace (without copying files). The workaround is to archive and then unarchive sources. Project: Jenkins Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-26102) Workflow step to wait for approval
Jesse Glick created JENKINS-26102 Workflow step to wait for approval Issue Type: New Feature Assignee: rsandell Components: gerrit-trigger-plugin Created: 17/Dec/14 12:06 AM Description: Similar input step as the human version but this time wait for a review to be set on some Gerrit label for a change/the change that triggered the flow. For example wait here until "Code Review +2" or any other arbitrary label. Project: Jenkins Labels: workflow Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
