[JIRA] [job-dsl-plugin] (JENKINS-26152) Generated views are not deleted when removed from DSL
unguiculus updated JENKINS-26152 Generated views are not deleted when removed from DSL Change By: unguiculus (18/Dec/14 8:09 AM) URL: https://github.com/jenkinsci/job-dsl-plugin/pull/339 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-26153) JUnit missing builds
Gergely Pilisi created JENKINS-26153 JUnit missing builds Issue Type: Bug Assignee: Unassigned Components: junit-plugin Created: 18/Dec/14 8:16 AM Description: After a failed test report publishing my old builds (~600) are missing from the graph. I've updated Jenkins and the plugin is the newest version too. The old builds are present, they aren't deleted. How can I re-generate the graph for the whole project with the old builds included? Environment: Jenkins version: 1.580.1, 1.580.2 JUnit plugin version: 1.3 Project: Jenkins Labels: junit Priority: Major Reporter: Gergely Pilisi 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-26151) when trying to save the job configuration
nahum litvin updated JENKINS-26151 when trying to save the job configuration Change By: nahum litvin (18/Dec/14 8:21 AM) Component/s: mstest-plugin Component/s: mstestrunner-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] [core] (JENKINS-26151) when trying to save the job configuration
nahum litvin updated JENKINS-26151 when trying to save the job configuration Change By: nahum litvin (18/Dec/14 8:20 AM) Component/s: mstestrunner-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] [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 Thank you for the very quick response and resolution! 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-25657) JUnit crashes during recording of test results in 1.580.1
Waldek M commented on JENKINS-25657 JUnit crashes during recording of test results in 1.580.1 Or maybe https://issues.jenkins-ci.org/browse/JENKINS-24946 ? 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] [clearcase-plugin] (JENKINS-9703) Find changes on a branch not working correctly with CC multisite
Waldek M commented on JENKINS-9703 Find changes on a branch not working correctly with CC multisite Same issue here. When changes aren't made on the same CC replica but arrive via replication, those changes never trigger the build. We could use a switch to change polling behavior - to either poll since last check, or since last build. 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] [clearcase-plugin] (JENKINS-9703) Find changes on a branch not working correctly with CC multisite
Waldek M edited a comment on JENKINS-9703 Find changes on a branch not working correctly with CC multisite Same issue here. When changes aren't made on the same CC replica but arrive via replication, those changes never trigger the build. We could use a switch to change polling behavior - to either poll since last check, or since last build. Update: As advised by colleague, using "Multisite poll buffer" from Advanced options. 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] [clearcase-plugin] (JENKINS-9703) Find changes on a branch not working correctly with CC multisite
Waldek M edited a comment on JENKINS-9703 Find changes on a branch not working correctly with CC multisite Same issue here. When changes aren't made on the same CC replica but arrive via replication, those changes never trigger the build. We could use a switch to change polling behavior - to either poll since last check, or since last build. Update: As advised by colleague, using "Multisite poll buffer" option. 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-26154) NullPointerException when creating claim for a failed test => author missing
Michael Schaufelberger created JENKINS-26154 NullPointerException when creating claim for a failed test => author missing Issue Type: Bug Assignee: Christian Bremer Components: claim-plugin Created: 18/Dec/14 9:25 AM Description: Sometimes when I assign a failed test to someone, I get a Jenkins error page (with the burning Jenkins image) showing the stack trace below. When I go back to the test, I see that the claim has been created successfully though, only the author is missing: "This test was assigned to John Doe by anonymous on Dec 18, 2014 10:10:55 AM." So if everything else works as expected this seems to be a minor bug. Stack trace: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:795) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:685) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) 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:727) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) 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.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at
[JIRA] [clearcase-plugin] (JENKINS-9703) Find changes on a branch not working correctly with CC multisite
Krzysztof Malinowski commented on JENKINS-9703 Find changes on a branch not working correctly with CC multisite Actually this can be worked around using existing option of multi-site poll buffer. Unfortunately, even if the polling is done since previous build, it still will not be reliable. Consider such scenario: 9.00 AM - VOB sync is performed 9.05 AM - a change is submitted in remote site 9.10 AM - a build is done locally 9.15 AM - VOB sync is performed bringing changes from remote replica from 9.05 Now, even if the polling is run since last build (that is 9.10 AM), it will not include remote changes. I think that while multi-site poll buffer is a bit naive workaround, it works quite well until something smarter is invented. 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-plugin] (JENKINS-22536) Date in changeset is in wrong format
Adrien Lecharpentier commented on JENKINS-22536 Date in changeset is in wrong format Mark, I'm not sure that just "removing" the original timezone offset is the way to go. What I've done so far is here: https://github.com/alecharp/git-plugin/commit/c04174ee94e8e6765b1d2bdaea0beeb291678ab8 In the documentation here (https://www.kernel.org/pub/software/scm/git/docs/git-commit.html#_date_formats), the dates in seconds from EPOC may have a timezone offset, which is important. Just removing it shouldn't convert correctly the date. What do you think? 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] [cli] (JENKINS-22346) CLI commands with private key for nonexistent user fail with EOFException from DataInputStream.readBoolean
Eugenio Marzo commented on JENKINS-22346 CLI commands with private key for nonexistent user fail with EOFException from DataInputStream.readBoolean Hi, same problem on Jenkins ver. 1.580.2 with the LDAP plugin 1.11. 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-24946) JUnit Tests Results fail to archive in V1.582
Waldek M commented on JENKINS-24946 JUnit Tests Results fail to archive in V1.582 I see. Yes, probably version of core might be the issue. I did upgrade to the latest core, however that one contains another critical bug (related to losing slave restrictions in a job), so I had to revert. I missed the upgrade to 1.2, so can't confirm. I can see a similar https://issues.jenkins-ci.org/browse/JENKINS-25657 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
SCM/JIRA link daemon commented on JENKINS-25682 Using Credentials as attributes shows all perforce credentials with same description Code changed in jenkins User: Jesse Glick Path: src/main/java/com/cloudbees/plugins/credentials/CredentialsNameProvider.java src/test/java/com/cloudbees/plugins/credentials/CredentialsNameProviderTest.java http://jenkins-ci.org/commit/credentials-plugin/813ca86ea4c749295556c20f60c4114a91db36e4 Log: JENKINS-25682 Adding test which failed in interfaceOfSuperclassAnnotated. 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
SCM/JIRA link daemon commented on JENKINS-25682 Using Credentials as attributes shows all perforce credentials with same description Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/plugins/credentials/CredentialsNameProvider.java src/test/java/com/cloudbees/plugins/credentials/CredentialsNameProviderTest.java http://jenkins-ci.org/commit/credentials-plugin/1d51a488fbdaa994f598648f96d579e644bc815e Log: Merge pull request #17 from jglick/JENKINS-25682-CredentialsNameProvider JENKINS-25682 Fixing interfaceOfSuperclassAnnotated Compare: https://github.com/jenkinsci/credentials-plugin/compare/f71aef05722a...1d51a488fbda 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-23131) Misleading permission scopes
SCM/JIRA link daemon commented on JENKINS-23131 Misleading permission scopes Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/plugins/credentials/CredentialsStore.java src/main/java/com/cloudbees/plugins/credentials/SystemCredentialsProvider.java src/main/java/com/cloudbees/plugins/credentials/UserCredentialsProvider.java http://jenkins-ci.org/commit/credentials-plugin/445667250c9d8f5e7b55a6f0f4da7d70425c28cc Log: [FIXED JENKINS-23131] Make CredentialsStore implement AccessControlled a52572825fcbaff9603f2202cb4488b722be7d7d already addressed the scoping issue 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-23131) Misleading permission scopes
SCM/JIRA link daemon resolved JENKINS-23131 as Fixed Misleading permission scopes Change By: SCM/JIRA link daemon (18/Dec/14 9:55 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26155) During build, the job page fails with : " can't parse argument number"
Zsombor g. created JENKINS-26155 During build, the job page fails with : " can't parse argument number" Issue Type: Bug Assignee: Unassigned Components: core Created: 18/Dec/14 9:56 AM Description: Opening the job page, during build is throwing an exception: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.593.jar!/lib/layout/main-panel.jelly:36:21: can't parse argument number: at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:735) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) 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 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.headerComplete(AbstractHttpConnection.java:949) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1011) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644) at org.eclipse.jetty.h
[JIRA] [core] (JENKINS-26048) Jenkins no longer cleaning up child processes when build stopped - as of 1.587
Daniel Beck commented on JENKINS-26048 Jenkins no longer cleaning up child processes when build stopped - as of 1.587 For the freestyle test - Would it tell us what we need to know if we created a freestyle project, but configure it to perform the same maven steps? Yes, that would be ideal. 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-26150) Build URL of queue item is not same address of the FQDN jenkins server.
Daniel Beck resolved JENKINS-26150 as Not A Defect Build URL of queue item is not same address of the FQDN jenkins server. Manage Jenkins » Configure System » Jenkins Location » Jenkins URL. Jenkins should even show a related warning on /manage when accessing it fully qualified but not having configured it that way. Change By: Daniel Beck (18/Dec/14 10:07 AM) Status: Open Resolved Resolution: Not A Defect 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-22097) Confusing terminology: Global domain vs. global scope
SCM/JIRA link daemon commented on JENKINS-22097 Confusing terminology: Global domain vs. global scope Code changed in jenkins User: Stephen Connolly Path: src/main/resources/com/cloudbees/plugins/credentials/Messages.properties http://jenkins-ci.org/commit/credentials-plugin/2f8bc2ffc1f3d1434357fdfaebe677fb8c4dd53a Log: [FIXED JENKINS-22097] Confusing terminology: Global domain vs. global scope 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-22097) Confusing terminology: Global domain vs. global scope
SCM/JIRA link daemon resolved JENKINS-22097 as Fixed Confusing terminology: Global domain vs. global scope Change By: SCM/JIRA link daemon (18/Dec/14 10:07 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-plugin] (JENKINS-21634) Show credential information on main screen
SCM/JIRA link daemon commented on JENKINS-21634 Show credential information on main screen Code changed in jenkins User: Stephen Connolly Path: src/main/resources/com/cloudbees/plugins/credentials/CredentialsStoreAction/DomainWrapper/index.jelly http://jenkins-ci.org/commit/credentials-plugin/a9bbb9dc60b0146b2891941351d3097d99340736 Log: [FIXED JENKINS-21634] Allow quicker updating of credentials 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-21634) Show credential information on main screen
SCM/JIRA link daemon resolved JENKINS-21634 as Fixed Show credential information on main screen Change By: SCM/JIRA link daemon (18/Dec/14 10:12 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25480) Swarm review callback trigger too many times for matrix project
SCM/JIRA link daemon commented on JENKINS-25480 Swarm review callback trigger too many times for matrix project Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/review/ReviewNotifier.java http://jenkins-ci.org/commit/p4-plugin/652d96e61335d1c2707c4c29fcb162886d3c3440 Log: Block Swarm URL callback for Matrix children Allow parent to aggregate result for Swarm callback. JENKINS-25480 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-plugin] (JENKINS-22536) Date in changeset is in wrong format
Mark Waite commented on JENKINS-22536 Date in changeset is in wrong format Adrien Lecharpentier I agree that removing the timezone information completely does not seem like the right thing to do, since timezone information is there. When I looked at it, it seemed there was an extra timezone definition appended to the end of the date. That meant it had two (sometimes conflicting) timezone definitions in the date. I thought that two timezone definitions in one time field were probably not right. 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-plugin] (JENKINS-22536) Date in changeset is in wrong format
Adrien Lecharpentier commented on JENKINS-22536 Date in changeset is in wrong format Yes, two timezone offset is not right, but I'm not sure that using the one from the `new Date()` is correct. As the project already depends on `joda-time`, my patch use it and normally the `DateTime` and `DateTimeZone` should correct that. I made my changes based on git-2.2.6 tag, but it's quite easy to move it to HEAD. But, as the git-plugin need 1.568 core now, I'd like to be able to backport this to the latest version compatible with the previous required core 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] [clearcase-plugin] (JENKINS-9703) Find changes on a branch not working correctly with CC multisite
Waldek M commented on JENKINS-9703 Find changes on a branch not working correctly with CC multisite Submitted documentation patch. https://github.com/jenkinsci/clearcase-plugin/pull/32 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] [clearcase-plugin] (JENKINS-9703) Find changes on a branch not working correctly with CC multisite
Waldek M assigned JENKINS-9703 to Waldek M Find changes on a branch not working correctly with CC multisite Change By: Waldek M (18/Dec/14 11:01 AM) Assignee: Vincent Latombe Waldek M 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] [clearcase-plugin] (JENKINS-9703) Find changes on a branch not working correctly with CC multisite
Waldek M started work on JENKINS-9703 Find changes on a branch not working correctly with CC multisite Change By: Waldek M (18/Dec/14 11:01 AM) Status: Open In Progress 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-17184) Allow setting a custom timeout when unlocking the keychain
lacostej reopened JENKINS-17184 Allow setting a custom timeout when unlocking the keychain This isn't merged. So not closed for now. Change By: lacostej (18/Dec/14 11:05 AM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-26116) AppName-dSYM.zip isn't a zip of AppName's dSYM
lacostej resolved JENKINS-26116 as Fixed AppName-dSYM.zip isn't a zip of AppName's dSYM Change By: lacostej (18/Dec/14 11:07 AM) Status: Open Resolved Assignee: lacostej 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] [xcode-plugin] (JENKINS-26116) AppName-dSYM.zip isn't a zip of AppName's dSYM
lacostej commented on JENKINS-26116 AppName-dSYM.zip isn't a zip of AppName's dSYM James, this a bug introduced in 1.4.5 and fixed in 1.4.6 released a few days back. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-26116) AppName-dSYM.zip isn't a zip of AppName's dSYM
lacostej closed JENKINS-26116 as Fixed AppName-dSYM.zip isn't a zip of AppName's dSYM Change By: lacostej (18/Dec/14 11:07 AM) Status: Resolved Closed 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] [parameterized-remote-trigger-plugin] (JENKINS-26127) java.net.MalformedURLException: no protocol: http%3A%2F%2Fmyserver
Dan Z. commented on JENKINS-26127 java.net.MalformedURLException: no protocol: http%3A%2F%2Fmyserver I see this problem might be fixed with pull 5 (which is not released yet): https://github.com/jenkinsci/parameterized-remote-trigger-plugin/pull/5 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] [veracode-scanner-plugin] (JENKINS-25823) Sandbox and Scan Name
Matteo Castellarin commented on JENKINS-25823 Sandbox and Scan Name Mike, thank you for your answer. I had a look to the Veracode plugin and we've already migrated to that one. FYI: ideally my request was indeed for having the possibility to tie the name back to the Jenkins build (or any other optional name, possibly with the possibility to use system properties of Jenkins). Thank you anyway for your kind answer! 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-26156) Erroneous handling of BodyInvoker.withDisplayName
Jesse Glick created JENKINS-26156 Erroneous handling of BodyInvoker.withDisplayName Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: workflow-plugin Created: 18/Dec/14 1:27 PM Description: In https://github.com/jenkinsci/workflow-plugin/commit/e24a64a7a6404be97f42340f4c44d3988be1052c you added createBodyBlockNode = (name==null); Is this not backwards? The Javadoc says that if name == null, the body is "anonymous", and anonymous body invocation suppress the generation of BlockStartNode/BlockEndNode which makes sense. Yet here you are saying that an anonymous body should create a body block node, which looks like a mistake. There appears to be no call to this method passing an actual display name anywhere in the codebase, and no test of how it should behave. I suspect that a call to non-null displayName would actually produce an IllegalStateException in start, since then startNodeActions would have a LabelAction. Note that ParallelStepExecution does call withStartAction, the only one to do so, and effectively sets a display name for the block, yet not using regular LabelAction; it seems the only purpose for the custom subclass is to assert branch names in a test. Furthermore, displayName is null by default, yet the Javadoc explicitly suggests calling withDisplayName(null), which will have no effect since createBodyBlockNode is also true by default. And many—but not all—steps indeed call withDisplayName(null). This all seems confused. Either blocks should be anonymous by default, in which case createBodyBlockNode should default to false, and all the calls to withDisplayName(null) should be deleted, and the name parameter should be marked @Nonnull, and the Javadoc should confirm the default behavior, and ParallelStepExecution should be handled somehow; or blocks should be visible by default, in which case displayName should have some default value (perhaps computed according to StepDescriptor.displayName?) and you would need to call withDisplayName(null) to turn it off. The first option seems more appropriate to me. Project: Jenkins Labels: api 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] [workflow-plugin] (JENKINS-26157) Subversion doesn't work correctly
Libor Ondrusek created JENKINS-26157 Subversion doesn't work correctly Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 18/Dec/14 1:59 PM Description: When i try use svn ulr: "http://someUrl" everytime I get java.lang.AbstractMethodError: you must override the new overload of checkout at hudson.scm.SCM.checkout(SCM.java:477) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:98) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:70) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousStepExecution.start(AbstractSynchronousStepExecution.java:34) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:137) 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:3) 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.GeneratedMethodAccessor445.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) 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.GeneratedMethodAccessor616.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) 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 org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:164) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:267) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$000(CpsThreadGroup.java:70) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:176) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:174) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:47) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:111) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) Finished: FAILURE Environment: svn 1.6, linux Centos 6.6, jenkins 1.594 installed from centos repo
[JIRA] [active-directory-plugin] (JENKINS-26158) Jenkins v1.586 breaks Active Directory authentication using jna for Subversion plugin.
Björn Olsson created JENKINS-26158 Jenkins v1.586 breaks Active Directory authentication using jna for Subversion plugin. Issue Type: Bug Assignee: Unassigned Attachments: SVN_AuthError.png Components: active-directory-plugin, subversion-plugin Created: 18/Dec/14 2:12 PM Description: We've set up SVNKit in our Jenkins instance to use JNA to collect credentials for SVN access by setting -Dsvnkit.http.ntlm=jna in jenkins.xml. This has been working perfectly until we tried to upgrade Jenkins to 1.586, when the Jenkins JNA implementation was bumped to jna 4.10. After that, we get an "E200015: No credential to try." error. Environment: Windows Server 2008 R2, Jenkins installed as a service. Java version for Jenkins is 1.7.0.07-b11 (32 bit). Project: Jenkins Labels: subversion jna authentication Priority: Blocker Reporter: Björn Olsson 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] [android-emulator-plugin] (JENKINS-26159) Emulator won't start when using android-20 API
Adam Vorin
created JENKINS-26159
Emulator won't start when using android-20 API
Issue Type:
New Feature
Assignee:
Christopher Orr
Components:
android-emulator-plugin
Created:
18/Dec/14 2:46 PM
Description:
When using android-20 API as a target there is a error during creating AVD:
[android] /home/builder/android-sdk/android-sdk/tools/android create avd -f -a -s 720x1280 -n hudson_pl-PL_300_720x1280_android-20 -t android-20 --abi armeabi-v7a
[android] Failed to run AVD creation command
Error: Invalid --tag default for the selected target.
The solution to this problem is here http://stackoverflow.com/a/25598879/1204234 , but when the working --abi parameter is used eg. android-wear/armeabi-v7a then the name of the AVD become incorrect because there is a slash in it:
[android] /home/builder/android-sdk/android-sdk/tools/android create avd -f -a -s 720x1280 -n hudson_pl-PL_300_720x1280_android-20_android-wear/armeabi-v7a -t android-20 --abi android-wear/armeabi-v7a
[android] Failed to run AVD creation command
Error: AVD name 'hudson_pl-PL_300_720x1280_android-20_android-wear/armeabi-v7a' contains invalid characters.
Allowed characters are: a-z A-Z 0-9 . _ -
When I modified method getGeneratedAvdName() in EmulatorConfig.java in the way shown below
private String getGeneratedAvdName() {
..
String abi = "";
if (targetAbi != null && osVersion.requiresAbi()) {
//BEFORE
//abi = "_" + targetAbi.replace(' ', '-').replace('_', '-');
//AFTER
abi = "_" + targetAbi.replaceAll("[^a-zA-Z0-9._-]", "-");
}
...
}
Compiled plugin and replaced the original it is working
Environment:
Jenkins ver. 1.592, android-emulator 2.12
Project:
Jenkins
Priority:
Minor
Reporter:
Adam Vorin
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] [build-pipeline-plugin] (JENKINS-26160) Folder issue: Cannot manually trigger jobs when those are in folders
Félix Belzunce Arcos created JENKINS-26160 Folder issue: Cannot manually trigger jobs when those are in folders Issue Type: Bug Assignee: Félix Belzunce Arcos Components: build-pipeline-plugin Created: 18/Dec/14 2:47 PM Description: Create a folder:: TestFolder Create the projects: TestFolder » Job1 TestFolder » Job2 TestFolder » Job3 (Can be blank jobs) Make Job1 have a downstream of Job2 and Job2 have a downstream of Job3. You need to do it through Post-build action -> Build other projects (manual step). Create a new Build Pipeline View and have Job1 be the Initial Job. Click Run - The build for first job should complete. Go into Job2 and trigger a manual build. Clicking trigger created the error message: Dec 11, 2014 5:56:09 PM SEVERE au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView triggerBuild No upstream trigger found for this TestFolder » Job2 Project: Jenkins Priority: Minor Reporter: Félix Belzunce Arcos 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-26155) During build, the job page fails with : " can't parse argument number"
Daniel Beck commented on JENKINS-26155 During build, the job page fails with : " can't parse argument number" What language are you using Jenkins in? 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-25924) error step
SCM/JIRA link daemon commented on JENKINS-25924 error step Code changed in jenkins User: Jesse Glick Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowJobNonRestartingTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/parallel/ParallelStepTest.java basic-steps/src/main/java/org/jenkinsci/plugins/workflow/steps/ErrorStep.java basic-steps/src/main/resources/org/jenkinsci/plugins/workflow/steps/ErrorStep/config.jelly basic-steps/src/main/resources/org/jenkinsci/plugins/workflow/steps/ErrorStep/help.html http://jenkins-ci.org/commit/workflow-plugin/65a08b2d2ca08a4260af86411c301ab8fcc3f9b4 Log: [FIXED JENKINS-25924] Added error step. 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-25924) error step
SCM/JIRA link daemon resolved JENKINS-25924 as Fixed error step Change By: SCM/JIRA link daemon (18/Dec/14 3:03 PM) Status: In Progress 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-26155) During build, the job page fails with : " can't parse argument number"
Zsombor g. commented on JENKINS-26155 During build, the job page fails with : " can't parse argument number" The browser set to hungarian. Do you think, this is a locale specific error ? 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-26157) Subversion doesn't work correctly
Jesse Glick resolved JENKINS-26157 as Not A Defect Subversion doesn't work correctly Version 2.5-beta-4 or later of the Subversion plugin is required. To get it you would need to enable the experimental update center. (Release of 2.5 final is on hold pending further testing of an unrelated feature that came in after beta 4: support for the 1.8 workspace format. Possibly I should just cut a 2.5 release based on the stuff before then, since the author of that code is away on holidays.) Change By: Jesse Glick (18/Dec/14 3:47 PM) Status: Open Resolved Resolution: Not A Defect 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-25736) Ability to pause a running flow
Jesse Glick updated JENKINS-25736 Ability to pause a running flow Change By: Jesse Glick (18/Dec/14 3:52 PM) Labels: api 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] [artifactory-plugin] (JENKINS-26161) [originalname] not expanded in artifact pattern
Jochen Kemnade created JENKINS-26161 [originalname] not expanded in artifact pattern Issue Type: Bug Assignee: yossis Components: artifactory-plugin Created: 18/Dec/14 4:32 PM Description: If I use [originalname] in the deploy artifact pattern, the artifacts end up as "[originalname]" in artifactory. Apparently, the property is not evaluated. Project: Jenkins Priority: Minor Reporter: Jochen Kemnade 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] [hockeyapp-plugin] (JENKINS-26059) Expand variables before using conditional
SCM/JIRA link daemon commented on JENKINS-26059 Expand variables before using conditional Code changed in jenkins User: Brenton Bartel Path: src/main/java/hockeyapp/HockeyappRecorder.java http://jenkins-ci.org/commit/hockeyapp-plugin/51c211eb03e5e51e80649bf26e146a5d5025bac3 Log: Effort to tackle https://issues.jenkins-ci.org/browse/JENKINS-26059 to expand var during conditional 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] [artifactory-plugin] (JENKINS-26161) [originalname] not expanded in artifact pattern
Jochen Kemnade commented on JENKINS-26161 [originalname] not expanded in artifact pattern I'm version 2.2.4 of the plug-on on Jenkins 1.593. 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] [artifactory-plugin] (JENKINS-26161) [originalname] not expanded in artifact pattern
Jochen Kemnade edited a comment on JENKINS-26161 [originalname] not expanded in artifact pattern I'm using version 2.2.4 of the plug-on on Jenkins 1.593. 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-26148) Incorrect implementation of RetryStepExecution.stop
Jesse Glick commented on JENKINS-26148 Incorrect implementation of RetryStepExecution.stop Just realized that CpsFlowExecution.interrupt only calls stop on getCurrentExecutions, which by its Javadoc only includes innermost executions. And this makes sense to me: it is only necessary to interrupt the stuff that is actually running, and if that throws up a FlowInterruptedException, then BodyExecutionCallback.onFailure should be called and the outer step should fail too. If that is right, then the current stop method is totally wrong: it should not call cancel on anything, and in fact it should be a no-op because it should never be called. (Or if it is called, it would be as a race condition between retries, meaning all it needs to do is immediately getContext().onFailure(cause).) But then Callback.onFailure needs to check for t instanceof InterruptedException and throw that up without retrying. And other stop methods on block-scoped steps are probably incorrect too. The correct handling of interruption by steps remains very unclear to me. There needs to be a definitive document explaining how interruption works and what steps are supposed to do in order to participate properly. And we need tests that actually trying interrupting flows at various points. 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] [notification-plugin] (JENKINS-26162) Plugin results in error: "artifacts Map already contains mapping of location"
Tim Ambler
created JENKINS-26162
Plugin results in error: "artifacts Map already contains mapping of location"
Issue Type:
Bug
Assignee:
Unassigned
Components:
notification-plugin
Created:
18/Dec/14 4:37 PM
Description:
I have this plugin enabled for a project. During the build, it generates this error:
Started by user — -
Notifying endpoint 'HTTP:http://localhost:9090/hubot/jenkins'
Building in workspace /var/lib/jenkins/workspace/XXX
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url g...@github.com:XXX/XXX.git # timeout=10
Fetching upstream changes from g...@github.com:XXX/XXX.git
> git --version # timeout=10
> git fetch --tags --progress g...@github.com:XXX/XXX.git +refs/heads/:refs/remotes/origin/
> git rev-parse refs/remotes/origin/master^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision f2032e23549d962696fc976ce85fd77aee940f80 (refs/remotes/origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f f2032e23549d962696fc976ce85fd77aee940f80
> git rev-list f2032e23549d962696fc976ce85fd77aee940f80 # timeout=10
[XXX] $ /bin/sh -xe /tmp/hudson1170039673840754778.sh
+ npm install
npm WARN package.json XXX@1.0.0 No repository field.
Archiving artifacts
Notifying endpoint 'HTTP:http://localhost:9090/hubot/jenkins'
ERROR: Failed to notify endpoint 'HTTP:http://localhost:9090/hubot/jenkins'
java.lang.RuntimeException: Adding artifacts mapping 'index.js/archive/http://jnx.lifeplansdev.com/job/XXX/9/artifact/lib/api/api/v1/index.js' - artifacts Map already contains mapping of location 'archive': {Gruntfile.js={archive=http://jnx.lifeplansdev.com/job/XXX/9/artifact/Gruntfile.js}, development.json={archive=http://jnx.lifeplansdev.com/job/XXX/9/artifact/config/development.json}, config.json={archive=http://jnx.lifeplansdev.com/job/XXX/9/artifact/config/config.json}, production.json={archive=http://jnx.lifeplansdev.com/job/XXX/9/artifact/config/production.json}, knexfile.js={archive=http://jnx.lifeplansdev.com/job/XXX/9/artifact/knexfile.js}, index.js={archive=http://jnx.lifeplansdev.com/job/XXX/9/artifact/index.js}}
at com.tikal.hudson.plugins.notification.model.BuildState.updateArtifact(BuildState.java:205)
at com.tikal.hudson.plugins.notification.model.BuildState.updateArchivedArtifacts(BuildState.java:151)
at com.tikal.hudson.plugins.notification.model.BuildState.updateArtifacts(BuildState.java:137)
at com.tikal.hudson.plugins.notification.Phase.buildJobState(Phase.java:94)
at com.tikal.hudson.plugins.notification.Phase.handle(Phase.java:41)
at com.tikal.hudson.plugins.notification.JobListener.onCompleted(JobListener.java:36)
at hudson.model.listeners.RunListener.fireCompleted(RunListener.java:199)
at hudson.model.Run.execute(Run.java:1810)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
Failed to notify endpoint 'HTTP:http://localhost:9090/hubot/jenkins' - java.lang.RuntimeException: Adding artifacts mapping 'index.js/archive/http://jnx.lifeplansdev.com/job/XXX/9/artifact/lib/api/api/v1/index.js' - artifacts Map already contains mapping of location 'archive': {Gruntfile.js={archive=http://jnx.lifeplansdev.com/job/XXX/9/artifact/Gruntfile.js}, development.json={archive=http://jnx.lifeplansdev.com/job/XXX/9/artifact/config/development.json}, config.json={archive=http://jnx.lifeplansdev.com/job/XXX/9/artifact/config/config.json}, production.json={archive=http://jnx.lifeplansdev.com/job/XXX/9/artifact/config/production.json}, knexfile.js={archive=http://jnx.lifeplansdev.com/job/XXX/9/artifact/knexfile.js}, index.js={archive=http://jnx.lifeplansdev.com/job/XXX/9/artifact/index.js}}
Finished: SUCCESS
Project:
Jenkins
Priority:
[JIRA] [workflow-plugin] (JENKINS-26163) StepExecutionIterator omits outer executions
Jesse Glick created JENKINS-26163 StepExecutionIterator omits outer executions Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: workflow-plugin Created: 18/Dec/14 4:40 PM Description: The Javadoc says Enumerates active running StepExecution s in the system. It is not specified exactly what "active" or "running" mean in this context, but at any rate I have found that StepExecutionIteratorImpl only includes innermost steps, not their containing block steps, because it calls FlowExecution.getCurrentExecutions which is documented to behave that way. This means that it is impossible to find a StepExecution of a block-scoped step unless it is not currently running its body. (Before or after running the body, it seems to work.) If this behavior is intentional, it needs to be documented more clearly, and I would request some way to get even enclosing executions. 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] [workflow-plugin] (JENKINS-26163) StepExecutionIterator omits outer executions
Jesse Glick commented on JENKINS-26163 StepExecutionIterator omits outer executions Alternately it would suffice to have something @CheckForNull StepExecution StepExecution.getParent() that would return an enclosing step if there is one. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26149) Workflow job with parallel builds never can finish
Jesse Glick reopened JENKINS-26149 Workflow job with parallel builds never can finish There is clearly something broken here, though I am not sure what. Are you able to reproduce this from scratch? Change By: Jesse Glick (18/Dec/14 5:07 PM) Resolution: Not A Defect Status: Resolved Reopened Assignee: Jesse Glick Kohsuke Kawaguchi 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-26149) Workflow job with parallel builds never can finish
Jesse Glick updated JENKINS-26149 Workflow job with parallel builds never can finish Change By: Jesse Glick (18/Dec/14 5:08 PM) Priority: Blocker Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26149) Workflow job with parallel builds never can finish
Jesse Glick assigned JENKINS-26149 to Jesse Glick Workflow job with parallel builds never can finish Change By: Jesse Glick (18/Dec/14 5:10 PM) Assignee: Kohsuke Kawaguchi 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-26149) BuildTriggerStepExecution does not survive restart
Jesse Glick updated JENKINS-26149 BuildTriggerStepExecution does not survive restart Change By: Jesse Glick (18/Dec/14 5:13 PM) Status: Reopened Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26149) BuildTriggerStepExecution does not survive restart
Jesse Glick updated JENKINS-26149 BuildTriggerStepExecution does not survive restart I am not sure why the freestyle projects were not built—according to the log they should have been started, though the code currently lacks some error checks that might explain why they were not—but at any rate I see a clear bug in that if Jenkins is restarted in the middle of this step, it is not correctly reloaded. Fortunately that part is easy to fix. Change By: Jesse Glick (18/Dec/14 5:13 PM) Summary: Workflow job with parallel builds never can finish BuildTriggerStepExecution does not survive restart Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Carlos Eduardo commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 The alternative provided by Jesse Glick is working gracefully to me. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [veracode-scanner-plugin] (JENKINS-25823) Sandbox and Scan Name
Mike Bockus commented on JENKINS-25823 Sandbox and Scan Name No prob! Glad the official plugin is working out for 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] [workflow-plugin] (JENKINS-25570) Wait-for-condition step
SCM/JIRA link daemon commented on JENKINS-25570 Wait-for-condition step Code changed in jenkins User: Jesse Glick Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/WaitForConditionStepTest.java basic-steps/src/main/java/org/jenkinsci/plugins/workflow/steps/WaitForConditionStep.java basic-steps/src/main/resources/org/jenkinsci/plugins/workflow/steps/WaitForConditionStep/config.jelly basic-steps/src/main/resources/org/jenkinsci/plugins/workflow/steps/WaitForConditionStep/help.html support/src/test/java/org/jenkinsci/plugins/workflow/test/steps/WatchYourStep.java http://jenkins-ci.org/commit/workflow-plugin/4de61d25f9c32d631baad8f366bff5fecc90d137 Log: [FIXED JENKINS-25570] Added waitUntil step. 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-25570) Wait-for-condition step
SCM/JIRA link daemon resolved JENKINS-25570 as Fixed Wait-for-condition step Change By: SCM/JIRA link daemon (18/Dec/14 6:13 PM) Status: In Progress 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-26155) During build, the job page fails with : " can't parse argument number"
Daniel Beck commented on JENKINS-26155 During build, the job page fails with : " can't parse argument number" It's possible. Change your browser's Accept-Language to test. Would be interesting to see the job config and/or a screenshot of the job page when no build is running (assuming it works then). Does this affect all jobs, or only specific ones? If the latter, what do they have in common? 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] [active-directory-plugin] (JENKINS-26158) Jenkins v1.586 breaks Active Directory authentication using jna for Subversion plugin.
Daniel Beck commented on JENKINS-26158 Jenkins v1.586 breaks Active Directory authentication using jna for Subversion plugin. What is the relationship to Active Directory Plugin? Does this issue still occur on Jenkins 1.594? Which version of the Subversion plugin are you using? Does the issue still occur with the newest release? 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-26164) Undesirable wrapping in UndeclaredThrowableException
Jesse Glick created JENKINS-26164 Undesirable wrapping in UndeclaredThrowableException Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 18/Dec/14 6:46 PM Description: CpsStepContext.replay wraps checked exceptions in UndeclaredThrowableException; it has to, because the call from DSL implements GroovyObject.invokeMethod which, mysteriously, does not allow checked exceptions. After a few false starts, in https://github.com/jenkinsci/workflow-plugin/commit/2432b1e7518a2963983e9a099ae16b9ebfe1ffc1 I have made CpsBodyExecution.FailureAdapter unwrap this, so that this hack is transparent to ErrorAction (needed to handle AbortException in WorkflowRun.finish) and BodyExecutionCallback.onFailure (needed for CatchErrorStep, similarly to print a polite message not a stack trace). Yet I have found that this wrapping is still not transparent: when a checked exception is thrown from a step (for example, an IOException from readFile), any Groovy code which tries to catch (IOException x) will not work; at the Groovy level, an UndeclaredThrowableException is received. 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] [workflow-plugin] (JENKINS-26164) Undesirable wrapping in UndeclaredThrowableException
Jesse Glick started work on JENKINS-26164 Undesirable wrapping in UndeclaredThrowableException Change By: Jesse Glick (18/Dec/14 6:46 PM) Status: Open In Progress 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-usercontent-plugin] (JENKINS-25212) http clone of git usercontent folder fails with some git versions, even though ssh clone works
Kohsuke Kawaguchi
commented on JENKINS-25212
http clone of git usercontent folder fails with some git versions, even though ssh clone works
After futher thinking and digging, I think the root cause is that CompressionFilter was using setHeader("Content-Encoding","gzip") as a trigger to automatically insert transparent gzip compression.
This just doesn't work with servlets that handle gzip content encoding on its own, such as jgit.
In https://github.com/stapler/stapler/compare/08d582d...5b6496c9 I made a fix to change the way the transparent content compression kicks in.
Because this is a core change, git-server plugin should work around this in the mean time by hiding "Accept-Encoding" from the 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] [git-usercontent-plugin] (JENKINS-25212) http clone of git usercontent folder fails with some git versions, even though ssh clone works
Kohsuke Kawaguchi
edited a comment on JENKINS-25212
http clone of git usercontent folder fails with some git versions, even though ssh clone works
After futher thinking and digging, I think the root cause is that CompressionFilter was using setHeader("Content-Encoding","gzip") as a trigger to automatically insert transparent gzip compression.
This just doesn't work with servlets that handle gzip content encoding on its own, such as jgit.
In https://github.com/stapler/stapler/compare/08d582d...5b6496c9 I made a fix to change the way the transparent content compression kicks in. This will be in Stapler 1.234.
Because this is a core change, git-server plugin should work around this in the mean time by hiding "Accept-Encoding" from the 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] [git-plugin] (JENKINS-24786) Since 2.2.6, environment variables are not expanded in git publisher
Carlos Alexandre commented on JENKINS-24786 Since 2.2.6, environment variables are not expanded in git publisher Hey there Mark, Any news on this issue? Today I updated to the latest 2.3 version..i was forced to rollback once again due to this issue :/ One thing I noted is that the GitPublisher only fails to expand a variable that is used in the Repository Url. If you use it on any other field, such as GitTag name or something similar, everything works as expected. Jenkins Core: 1.580.2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-24786) Since 2.2.6, environment variables are not expanded in git publisher
Carlos Alexandre edited a comment on JENKINS-24786 Since 2.2.6, environment variables are not expanded in git publisher Hey there Mark, Any news on this issue? Today I updated to the latest 2.3 version..i was forced to rollback once again due to this issue :/ One thing I noted is that the GitPublisher only fails to expand a variable that is used in the Repository Url. If you use it on any other field, such as GitTag name or something similar, everything works as expected. Jenkins Core: 1.580.2 Git Plugin version: 2.3.x 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] [dimensionsscm-plugin] (JENKINS-26165) Workflow integration
Jesse Glick created JENKINS-26165 Workflow integration Issue Type: New Feature Assignee: Unassigned Components: dimensionsscm-plugin Created: 18/Dec/14 6:54 PM Description: See the migration guide. 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] [dimensionsscm-plugin] (JENKINS-26165) Workflow integration
SCM/JIRA link daemon commented on JENKINS-26165 Workflow integration Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/d81b33553fad8b561bac81e181d32ce4c1f531ba Log: Adding JENKINS-26165 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-usercontent-plugin] (JENKINS-25212) http clone of git usercontent folder fails with some git versions, even though ssh clone works
SCM/JIRA link daemon resolved JENKINS-25212 as Fixed http clone of git usercontent folder fails with some git versions, even though ssh clone works Change By: SCM/JIRA link daemon (18/Dec/14 7:03 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] [git-usercontent-plugin] (JENKINS-25212) http clone of git usercontent folder fails with some git versions, even though ssh clone works
SCM/JIRA link daemon commented on JENKINS-25212 http clone of git usercontent folder fails with some git versions, even though ssh clone works Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/org/jenkinsci/plugins/gitserver/HttpGitRepository.java src/main/java/org/jenkinsci/plugins/gitserver/Jenkins2521Workaround.java http://jenkins-ci.org/commit/git-server-plugin/12842a74e8199742530ae16a70994ee66d730bf6 Log: [FIXED JENKINS-25212] Fixing this problem in this plugin by not allowing jgit to compress the response. This can be removed once we can depend on the core that has Stapler 1.234. 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] [docker-build-step-plugin] (JENKINS-24388) Add registry authentication
Wei Z commented on JENKINS-24388 Add registry authentication I am submitting a pull request to solve 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] [docker-build-step-plugin] (JENKINS-24388) Add registry authentication
Wei Z assigned JENKINS-24388 to Wei Z Add registry authentication Change By: Wei Z (18/Dec/14 7:17 PM) Assignee: vjuranek Wei Z 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] [docker-build-step-plugin] (JENKINS-24388) Add registry authentication
Wei Z started work on JENKINS-24388 Add registry authentication Change By: Wei Z (18/Dec/14 7:17 PM) Status: Open In Progress 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-26164) Undesirable wrapping in UndeclaredThrowableException
SCM/JIRA link daemon resolved JENKINS-26164 as Fixed Undesirable wrapping in UndeclaredThrowableException Change By: SCM/JIRA link daemon (18/Dec/14 7:24 PM) Status: In Progress 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] [workflow-plugin] (JENKINS-26164) Undesirable wrapping in UndeclaredThrowableException
SCM/JIRA link daemon commented on JENKINS-26164 Undesirable wrapping in UndeclaredThrowableException Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/WaitForConditionStepTest.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsBodyExecution.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsStepContext.java http://jenkins-ci.org/commit/workflow-plugin/b5371ac3413a5521d8d297621fc2503a3a4c7241 Log: [FIXED JENKINS-26164] Found the right exception that Groovy will automatically unwrap. 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-usercontent-plugin] (JENKINS-25212) http clone of git usercontent folder fails with some git versions, even though ssh clone works
Kohsuke Kawaguchi commented on JENKINS-25212 http clone of git usercontent folder fails with some git versions, even though ssh clone works git-server-plugin 1.6 is released to address this 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] [docker-build-step-plugin] (JENKINS-26166) PullImageCommand.isImagePulled() misuses DockerClient.listImagesCmd().withFilters()
Wei Z
created JENKINS-26166
PullImageCommand.isImagePulled() misuses DockerClient.listImagesCmd().withFilters()
Issue Type:
Bug
Assignee:
Wei Z
Components:
docker-build-step-plugin
Created:
18/Dec/14 7:52 PM
Description:
PullImageCommand.isImagePulled() calls
List images = client.listImagesCmd().withFilters(String.format("{\"%s\":[\"true\"]}", fromImage)).exec();
Syntax wise, it is correct, however, list image currently only accept one filter now, which is dangling (whose value is true or false).
See https://docs.docker.com/reference/commandline/cli/#filtering_1,
Also see here for the docker daemon implemenation:
https://github.com/docker/docker/blob/v1.1.0/server/server.go#L668
So the above call with fromImage as the filter simply doesn't do anything, and I have also Eclipse debug out below to prove this. The below debugger output is when it hits breakpoint inside of that function. Note that "fromImage" is "wzheng2310/foo", but the returned result contains only one entry " "tutum/hello-world:latest".
his PullImageCommand (id=9570)
fromImage "wzheng2310/foo" (id=9644)
registry "" (id=9645)
tag "1" (id=9646)
client DockerClientImpl (id=9577)
images ArrayList (id=9578)
elementData Object[10] (id=9579)
[0] Image (id=9582)
created 1416605801
id "7e6d00854917cab52b56fb2f2fd6300b485462c6dacf42483215c341954dacaa" (id=9584)
parentId "6853da9a3f45429aec73c2da79057ddb84af2322f874eb6a51d17ad2a4ceba61" (id=9585)
repoTags String[1] (id=9586)
[0] "tutum/hello-world:latest" (id=9587)
hash -1796321746
hash32 0
value (id=9588)
size 0
virtualSize 255255458
modCount 1
size 1
Environment:
Jenkins version 1.554.1, Ubuntu 14.04
Project:
Jenkins
Priority:
Minor
Reporter:
Wei Z
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] [docker-build-step-plugin] (JENKINS-26166) PullImageCommand.isImagePulled() misuses DockerClient.listImagesCmd().withFilters()
Wei Z started work on JENKINS-26166 PullImageCommand.isImagePulled() misuses DockerClient.listImagesCmd().withFilters() Change By: Wei Z (18/Dec/14 7:53 PM) Status: Open In Progress 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] [docker-build-publish-plugin] (JENKINS-26167) none default registry in PullImageCommand not working as expected
Wei Z created JENKINS-26167 none default registry in PullImageCommand not working as expected Issue Type: Bug Assignee: Wei Z Components: docker-build-publish-plugin Created: 18/Dec/14 8:24 PM Description: This is likely a bug on docker daemon, but we need a workaround. When a registry value is entered in the pull command, the current implementation will do client.pullImageCmd(fromImageRes).withTag(tagRes).withRegistry(registryRes).exec(); However, docker daemon show the following logs, which means that it still goes to the default docker hub to look for the image. Note that the POST request has QS parameter "registry=abcdef.com" in it, but docker daemon ignores it and still does: Calling GET https://index.docker.io/v1/repositories/wzheng2310/foo/images So we need a workaround for this before that issue is fixed on docker daemon side. [debug] server.go:1036 Calling POST /images/create [info] POST /images/create?tag=1&fromImage=wzheng2310/foo®istry=abcdef.com [d64cc68b] +job pull(wzheng2310/foo, 1) [debug] session.go:259 [registry] Calling GET https://index.docker.io/v1/repositories/wzheng2310/foo/images [debug] http.go:162 https://index.docker.io/v1/repositories/wzheng2310/foo/images – HEADERS: map[User-Agent:[docker/1.2.0 go/go1.3.1 git-commit/fa7b24f kernel/3.13.0-43-generic os/linux arch/amd64]] [debug] server.go:1036 Calling GET /images/json [info] GET /images/json?all=0&filters=%7B%22wzheng2310%2Ffoo%22:%5B%22true%22%5D%7D [d64cc68b] +job images() [d64cc68b] -job images() = OK (0) [debug] pull.go:89 Retrieving the tag list [debug] http.go:162 https://registry-1.docker.io/v1/repositories/wzheng2310/foo/tags – HEADERS: map[User-Agent:[docker/1.2.0 go/go1.3.1 git-commit/fa7b24f kernel/3.13.0-43-generic os/linux arch/amd64]] [debug] session.go:214 Got status code 200 from https://registry-1.docker.io/v1/repositories/wzheng2310/foo/tags Environment: Jenkins 1.554.1, Ubuntu 14.04 Project: Jenkins Priority: Minor Reporter: Wei Z 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] [docker-build-publish-plugin] (JENKINS-26167) none default registry in PullImageCommand not working as expected
Wei Z started work on JENKINS-26167 none default registry in PullImageCommand not working as expected Change By: Wei Z (18/Dec/14 8:24 PM) Status: Open In Progress 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] [docker-build-step-plugin] (JENKINS-26166) PullImageCommand.isImagePulled() misuses DockerClient.listImagesCmd().withFilters()
Wei Z commented on JENKINS-26166 PullImageCommand.isImagePulled() misuses DockerClient.listImagesCmd().withFilters() Below is some console log that I added inside of isImagePulled() function to illustrate the problem better. [Docker] INFO: Pulling image wzheng2310/foo:1 [Docker] INFO: isImagePulled: images size is 3 [Docker] INFO: isImagePulled: image is wzheng2310/foo:1 [Docker] INFO: isImagePulled: image is wzheng2310/foo:latest [Docker] INFO: isImagePulled: image is wei_private_repo/container-2:latest [Docker] INFO: isImagePulled: image is ..com/wei_private_repo/container-1:1 [Docker] INFO: isImagePulled: image is ..com/wei_private_repo/container-1:latest [Docker] INFO: isImagePulled: image is ..com/wei_private_repo/container-2:1 [Docker] INFO: isImagePulled: image is ..com/wei_private_repo/container-2:2 [Docker] INFO: isImagePulled: image is wei_private_repo/container-1:latest [Docker] INFO: isImagePulled: image is debian:jessie This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-26071) Configuration of HtmlPublisher's allowMissing
SCM/JIRA link daemon commented on JENKINS-26071 Configuration of HtmlPublisher's allowMissing Code changed in jenkins User: Knut Saua Mathiesen Path: docs/Job-reference.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/HtmlReportContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContextSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/3b718a6a49ced31b679dcda0718001fdadbe3542 Log: [FIXED JENKINS-26071] Extend HtmlPublisher for configuration of allowMissing 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-26071) Configuration of HtmlPublisher's allowMissing
SCM/JIRA link daemon commented on JENKINS-26071 Configuration of HtmlPublisher's allowMissing Code changed in jenkins User: Daniel Spilker Path: docs/Home.md docs/Job-reference.md docs/Migration.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/HtmlReportContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/HtmlReportTargetContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContextSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/941aa4539a0cf4105b34176ed41fea548936e539 Log: Merge branch 'JENKINS-26071' Conflicts: job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/HtmlReportContext.groovy Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/a095f797acf8...941aa4539a0c 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-26071) Configuration of HtmlPublisher's allowMissing
SCM/JIRA link daemon resolved JENKINS-26071 as Fixed Configuration of HtmlPublisher's allowMissing Change By: SCM/JIRA link daemon (18/Dec/14 8:45 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-24608) Test result link displays twice on matrix project page
Jon Starbird commented on JENKINS-24608 Test result link displays twice on matrix project page Also seeing the same thing, will add that the Trend reports are also Duplicated. Using Publish NUnit. Jenkins 1580.1 and NUnit 0.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] [job-dsl-plugin] (JENKINS-26071) Configuration of HtmlPublisher's allowMissing
Daniel Spilker commented on JENKINS-26071 Configuration of HtmlPublisher's allowMissing Will be released in 1.28. 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-25019) updateSecureSessionFlag fails to set secure cookie flag
Jesse Glick commented on JENKINS-25019 updateSecureSessionFlag fails to set secure cookie flag Since this fix makes it possible to run on Tomcat, a common container, whereas JENKINS-25337 affects a less common container and can be worked around by properly configuring it, I think this should still be an LTS candidate. 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-25019) updateSecureSessionFlag fails to set secure cookie flag
Jesse Glick commented on JENKINS-25019 updateSecureSessionFlag fails to set secure cookie flag Never mind, just saw that when unfixed this is only a warning. 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-24895) An existing connection was forcibly closed by the remote host
Anuvrath Joshi commented on JENKINS-24895 An existing connection was forcibly closed by the remote host Hi, I recently migrated from Hudson to Jenkins and form that time am facing this issues. It just randomly takes out some of the slave nodes. Slave logs look something like this: Failed to establish the connection with the slave fpm java.io.EOFException: unexpected stream termination at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:331) at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:280) at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:290) at org.jenkinsci.remoting.nio.NioChannelBuilder.build(NioChannelBuilder.java:36) at org.jenkinsci.remoting.nio.NioChannelBuilder.build(NioChannelBuilder.java:52) at jenkins.slaves.JnlpSlaveAgentProtocol$Handler.jnlpConnect(JnlpSlaveAgentProtocol.java:120) at jenkins.slaves.DefaultJnlpSlaveReceiver.handle(DefaultJnlpSlaveReceiver.java:63) at jenkins.slaves.JnlpSlaveAgentProtocol2$Handler2.run(JnlpSlaveAgentProtocol2.java:57) at jenkins.slaves.JnlpSlaveAgentProtocol2.handle(JnlpSlaveAgentProtocol2.java:31) at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:156) I never saw these issues when i was using Hudson(Same Master and Slave machines were used even at that time). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Nathan Lindshield commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 Same here too, 2.5 Snapshot is working great 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-plugin] (JENKINS-24786) Since 2.2.6, environment variables are not expanded in git publisher
Mark Waite commented on JENKINS-24786 Since 2.2.6, environment variables are not expanded in git publisher I have hit a wall on the fix. My attempts to find a way to retain the other fixes included in 2.2.6 and fix this bug have failed. I'd love to have other eyes on the code, or alternative ways to implement the 2.2.6 fix which introduced 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] [naginator-plugin] (JENKINS-26118) Naginator restarted build without any reason
SCM/JIRA link daemon commented on JENKINS-26118 Naginator restarted build without any reason Code changed in jenkins User: Kanstantsin Shautsou Path: src/main/java/com/chikli/hudson/plugin/naginator/NaginatorListener.java http://jenkins-ci.org/commit/naginator-plugin/2f78ea5aaf491ec178d44a6e2e3a78616c131c9b Log: Merge pull request #13 from KostyaSha/JENKINS-26118 JENKINS-26118 Add details and optimize logging Compare: https://github.com/jenkinsci/naginator-plugin/compare/14e42cdade94...2f78ea5aaf49 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] [naginator-plugin] (JENKINS-26118) Naginator restarted build without any reason
SCM/JIRA link daemon commented on JENKINS-26118 Naginator restarted build without any reason Code changed in jenkins User: Kanstantsin Shautsou Path: src/main/java/com/chikli/hudson/plugin/naginator/NaginatorListener.java http://jenkins-ci.org/commit/naginator-plugin/dab7b16280fe1b5974c581f7771be3ec0c8bb278 Log: JENKINS-26118 Add details and optimize logging 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.
