[JIRA] [git] (JENKINS-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Mark Waite edited a comment on JENKINS-17614 Jenkins triggers builds on git SCM changes, but nothing changed Andrew Matheny I don't understand how a job which does not poll could trigger on SCM changes. Does that mean you have the job configured to both "Build after other projects are built" and to "Poll SCM"? If you don't intend to poll SCM for changes, couldn't you delete the polling from that job? 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] [script-security] (JENKINS-25118) GroovyPostbuildRecorder$BadgeManager.setBuildNumber cannot be used in sandbox
ikedam commented on JENKINS-25118 GroovyPostbuildRecorder$BadgeManager.setBuildNumber cannot be used in sandbox https://github.com/jenkinsci/script-security-plugin/pull/6 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] (JENKINS-21464) Unwanted repetitive builds of the same git commit hash
Mark Waite closed JENKINS-21464 as Fixed Unwanted repetitive builds of the same git commit hash Change By: Mark Waite (13/Oct/14 4:02 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] [ant] (JENKINS-23207) Issue when saving/applying changes.
Mark Waite resolved JENKINS-23207 as Cannot Reproduce Issue when saving/applying changes. After several months with no further response of details to duplicate the problem, I'm resolving this as "Cannot Reproduce" Change By: Mark Waite (13/Oct/14 3:59 AM) Status: Open Resolved Resolution: Cannot Reproduce 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] [ant] (JENKINS-23207) Issue when saving/applying changes.
Mark Waite closed JENKINS-23207 as Cannot Reproduce Issue when saving/applying changes. Change By: Mark Waite (13/Oct/14 3:59 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] [git] (JENKINS-21309) Git plugins changes URL for Bitbucket is incorrect
Mark Waite commented on JENKINS-21309 Git plugins changes URL for Bitbucket is incorrect I could not duplicate this bug in August, or in February, and I still can't duplicate it today. I recommend it be closed as "Cannot Reproduce". I see that the config.xml for the Jenkins job shows that the job was last saved with a git plugin version 2.2.1. If you make a minor change to the job definition (extend the description by one character, or something equally as harmless), does it resolve 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] [git] (JENKINS-20939) git plugin doesn't detect changes when I create duplicate sub name branch.
Mark Waite closed JENKINS-20939 as Fixed git plugin doesn't detect changes when I create duplicate sub name branch. Change By: Mark Waite (13/Oct/14 3:46 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] [git] (JENKINS-20939) git plugin doesn't detect changes when I create duplicate sub name branch.
Mark Waite resolved JENKINS-20939 as Fixed git plugin doesn't detect changes when I create duplicate sub name branch. A pull request from Alexander Link added a new syntax to more precisely specify branches, without breaking compatibility with existing uses. That is available in git-client-plugin 1.10.2 and in git-plugin 2.2.5. Change By: Mark Waite (13/Oct/14 3:46 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] [git] (JENKINS-20446) Git Plugin 2.0 has changed contents of GIT_BRANCH
Mark Waite resolved JENKINS-20446 as Won't Fix Git Plugin 2.0 has changed contents of GIT_BRANCH The git plugin wiki page documents the current behavior by saying that GIT_BRANCH is the 'name of the remote repository (defaults to origin), followed by name of the branch currently being used, e.g. "origin/master" or "origin/foo"'. There are now assertions in GitSCMTest which test that the description in the wiki page is correct, by testing that the GIT_BRANCH environment variable is "origin/master". With those two conditions, I'm reasonably confident that the git plugin 2.0 behavior is the expected current behavior and the intended future behavior. Change By: Mark Waite (13/Oct/14 3:42 AM) Status: Open Resolved Resolution: Won't Fix 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] (JENKINS-20446) Git Plugin 2.0 has changed contents of GIT_BRANCH
Mark Waite closed JENKINS-20446 as Won't Fix Git Plugin 2.0 has changed contents of GIT_BRANCH Change By: Mark Waite (13/Oct/14 3:42 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] [script-security] (JENKINS-25119) Sandbox cannot handle methods Groovy provides additionally
ikedam commented on JENKINS-25119 Sandbox cannot handle methods Groovy provides additionally Methods groovy provides for String: http://groovy.codehaus.org/groovy-jdk/java/lang/String.html I don't know how Groovy handle them. Maybe this is a limitation (no workaround). 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] [script-security] (JENKINS-25119) Sandbox cannot handle methods Groovy provides additionally
ikedam created JENKINS-25119 Sandbox cannot handle methods Groovy provides additionally Issue Type: Bug Assignee: Jesse Glick Components: script-security Created: 13/Oct/14 3:33 AM Description: Running a following script "30".toInteger(); Results following error: org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: unclassified method java.lang.String toInteger at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:63) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:111) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:108) at org.kohsuke.groovy.sandbox.impl.Checker$checkedCall.callStatic(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:50) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:157) at Script1.run(Script1.groovy) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.run(GroovySandbox.java:119) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SecureGroovyScript.evaluate(SecureGroovyScript.java:160) at org.jvnet.hudson.plugins.groovypostbuild.GroovyPostbuildRecorder.perform(GroovyPostbuildRecorder.java:355) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:780) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:752) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:705) at hudson.model.Run.execute(Run.java:1617) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) It looks caused for String.toInteger() is not provided in JDK and additionally provided by Groovy. Environment: Windows 8 64bit, Jenkins 1.509.4, groovy-postbuild 2.0, script-security 1.6 Project: Jenkins Priority: Major Reporter: ikedam 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] (JENKINS-16646) Git push tag in case if build SUCCESS only, UNSTABLE result is not pushing a tag.
Mark Waite updated JENKINS-16646 Git push tag in case if build SUCCESS only, UNSTABLE result is not pushing a tag. Publish only if build succeeds - screen clip Change By: Mark Waite (13/Oct/14 3:24 AM) Attachment: publish-only-if-ok.png 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] (JENKINS-16646) Git push tag in case if build SUCCESS only, UNSTABLE result is not pushing a tag.
Mark Waite commented on JENKINS-16646 Git push tag in case if build SUCCESS only, UNSTABLE result is not pushing a tag. The git publisher has a post build action has a checkbox to push only on success. Is that sufficient to meet this need? 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] [script-security] (JENKINS-25118) GroovyPostbuildRecorder$BadgeManager.setBuildNumber cannot be used in sandbox
ikedam updated JENKINS-25118 GroovyPostbuildRecorder$BadgeManager.setBuildNumber cannot be used in sandbox Change By: ikedam (13/Oct/14 3:18 AM) Assignee: wolfs Jesse Glick Component/s: groovy-postbuild 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] [script-security] (JENKINS-25118) GroovyPostbuildRecorder$BadgeManager.setBuildNumber cannot be used in sandbox
ikedam commented on JENKINS-25118 GroovyPostbuildRecorder$BadgeManager.setBuildNumber cannot be used in sandbox This looks caused for: signature of setBuildNumber is boolean setBuildNumber (int). Groovy passes integers with Integer.class. GroovyCallSiteSelector fails to identify setBuildNumber as int.class.isinstance(new Integer(1)) returns false. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-postbuild] (JENKINS-25118) GroovyPostbuildRecorder$BadgeManager.setBuildNumber cannot be used in sandbox
ikedam created JENKINS-25118 GroovyPostbuildRecorder$BadgeManager.setBuildNumber cannot be used in sandbox Issue Type: Bug Assignee: wolfs Components: groovy-postbuild, script-security Created: 13/Oct/14 3:15 AM Description: When groovy-postbuild uses GroovyPostbuildRecorder$BadgeManager.setBuildNumber in the script-security sandbox, the script fails with following log: Groovy script failed: org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: unclassified method org.jvnet.hudson.plugins.groovypostbuild.GroovyPostbuildRecorder$BadgeManager setBuildNumber java.lang.Integer at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:63) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:111) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:108) at org.kohsuke.groovy.sandbox.impl.Checker$checkedCall.callStatic(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:50) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:157) at Script1.run(Script1.groovy) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.run(GroovySandbox.java:119) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SecureGroovyScript.evaluate(SecureGroovyScript.java:160) at org.jvnet.hudson.plugins.groovypostbuild.GroovyPostbuildRecorder.perform(GroovyPostbuildRecorder.java:355) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:780) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:752) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:705) at hudson.model.Run.execute(Run.java:1617) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) And it's not recorded to pending signatures. Environment: Windows 8 64bit, Jenkins 1.509.4, Groovy Postbuild 2.0, Script Security 1.6 Project: Jenkins Priority: Major Reporter: ikedam 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] (JENKINS-15377) Failed to Connect to Repository Error when Creating Job - Jenkins Github Plugin
Mark Waite closed JENKINS-15377 as Fixed Failed to Connect to Repository Error when Creating Job - Jenkins Github Plugin Change By: Mark Waite (13/Oct/14 3:13 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] [git] (JENKINS-15377) Failed to Connect to Repository Error when Creating Job - Jenkins Github Plugin
Mark Waite resolved JENKINS-15377 as Fixed Failed to Connect to Repository Error when Creating Job - Jenkins Github Plugin As far as I know, the git plugin now supports proxies for http and https repositories. Change By: Mark Waite (13/Oct/14 3: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] [multijob-plugin] (JENKINS-19680) Multijob plugin removes subBuillds from list when job name is the same but build number is different (fix proposed)
Alex V commented on JENKINS-19680 Multijob plugin removes subBuillds from list when job name is the same but build number is different (fix proposed) While we are waiting for this fix to be implemented , is there any other workaround than cloning the subjobs ? Cloning all subjobs cannot be practical in some setup. Would a lock on concurrent multijob builds work for example ? 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] [warnings] (JENKINS-25054) javax.servlet.ServletException: java.lang.IllegalArgumentException when depth != 0 in job API
Toby Collett updated JENKINS-25054 javax.servlet.ServletException: java.lang.IllegalArgumentException when depth != 0 in job API I have managed to isolate this to jobs that are using the warnings plugin. When we configure our jobs with the warnings console parser we get this stack trace with depth > 1. Change By: Toby Collett (13/Oct/14 12:52 AM) Environment: Jenkins ver. 1.583 , warnings plugin 4.42 Attachment: config.xml Component/s: warnings Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [other] (JENKINS-434) option on whether to show workspace or not
Taylor Leese commented on JENKINS-434 option on whether to show workspace or not Ah, seems like you just need to set matrix-based security and add the github organization as a user/group. 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] [other] (JENKINS-434) option on whether to show workspace or not
Taylor Leese commented on JENKINS-434 option on whether to show workspace or not What is the proper way to make sure the workspace isn't viewable if you are using the GitHub Authentication Plugin? I see a comment in the plugin that says below, but there isn't any additional info: Version 0.9 (Released January 8, 2012) Thanks to Kohsuke Kawaguchi for several commits that allow github organizations to be specified using the matrix-based security. Taylor 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-25116) Jenkins won't schedule builds
Taylor Leese commented on JENKINS-25116 Jenkins won't schedule builds Yes, when I reenable the option it stops working and yes, the proxy compatibility option is on. Currently, I have Jenkins setup to run behind nginx. Here is some information regarding the request/response: Headers: Cache-Control must-revalidate,no-cache,no-store Connection keep-alive Content-Encoding gzip Content-Type text/html;charset=ISO-8859-1 Date Mon, 13 Oct 2014 00:27:09 GMT Server nginx/1.6.2 Transfer-Encoding chunked view source .crumb e537ac28fab87ecb9a9319aaf5bc193b Accept text/_javascript_, text/html, application/xml, text/xml, / Accept-Encoding gzip, deflate Accept-Language en-US,en;q=0.5 Cache-Control no-cache Connection keep-alive Content-Length 0 Content-Type application/x-www-form-urlencoded; charset=UTF-8 Cookie JSESSIONID.bae0ecf2=mk3f6tod1v51fh5xb4xbgm5c; screenResolution=1440x900 Host jenkins.fountain.com Pragma no-cache Referer https://jenkins.fountain.com/job/Build/ User-Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:32.0) Gecko/20100101 Firefox/32.0 X-Prototype-Version 1.7 X-Requested-With XMLHttpRequest Response: Error 403 No valid crumb was included in the request HTTP ERROR 403 Problem accessing /job/Build/build. Reason: No valid crumb was included in the requestPowered by Jetty:// 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] [maven-plugin] (JENKINS-23846) Jenkins Maven support doesn't handle version ranges in parent definitions
Kanstantsin Shautsou commented on JENKINS-23846 Jenkins Maven support doesn't handle version ranges in parent definitions Current maven-plugin based on 3.1.0 ... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-17170) Jenkins auto install tools feature floods Nexus of HTTP request
Kanstantsin Shautsou commented on JENKINS-17170 Jenkins auto install tools feature floods Nexus of HTTP request Weird. https://github.com/jenkinsci/jenkins/blob/70f5968160b0a1cf81dc451fd2aacf1e0f9201ea/core/src/main/java/hudson/tools/DownloadFromUrlInstaller.java#L67 has check before. Both DownloadFromUrlInstaller and ZipExtractionInstaller do the same: "download and extract". JDKInstaller also has such check https://github.com/jenkinsci/jenkins/blob/70f5968160b0a1cf81dc451fd2aacf1e0f9201ea/core/src/main/java/hudson/tools/JDKInstaller.java#L126 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-24932) Build fails if mirror of "unpack archive" Maven installation procedure is unreachable
Kanstantsin Shautsou commented on JENKINS-24932 Build fails if mirror of "unpack archive" Maven installation procedure is unreachable Do you have /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.3 path on lab76 ? 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] (JENKINS-24809) Github-Jenkins Trigger issue with slave
Mark Waite resolved JENKINS-24809 as Cannot Reproduce Github-Jenkins Trigger issue with slave After two weeks with no response to my observation that I'm unable to duplicate this bug, I'm closing it as "Cannot Reproduce". I run a Jenkins instance with a Linux master and several Windows slaves and do not see this problem. Change By: Mark Waite (12/Oct/14 8:30 PM) Status: Open Resolved Resolution: Cannot Reproduce 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-25117) wget $JENKINS_URL/jenkins/git/notifyCommit?url= does not trigger build when slave is offline
Mark Waite updated JENKINS-25117 wget $JENKINS_URL/jenkins/git/notifyCommit?url="" does not trigger build when slave is offline Change By: Mark Waite (12/Oct/14 8:26 PM) Component/s: git This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
SCM/JIRA link daemon commented on JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception Code changed in jenkins User: Oleg Nenashev Path: src/main/java/hudson/plugins/git/util/BuildData.java http://jenkins-ci.org/commit/git-plugin/d15e4108e18cef7b66160f670e5d30f2ca2c652c Log: JENKINS-23641 - Annotate BuildData::getLastBuiltRevision() Signed-off-by: Oleg Nenashev 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] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
SCM/JIRA link daemon commented on JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception Code changed in jenkins User: Oleg Nenashev Path: src/main/java/hudson/plugins/git/util/BuildData.java http://jenkins-ci.org/commit/git-plugin/d0180c4a7e8ba3b72b1e7a5010ee578c92bd34e5 Log: JENKINS-23641 - Annotate BuildData::getLastBuiltRevision() Signed-off-by: Oleg Nenashev 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] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
Oleg Nenashev commented on JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception Better issue's analysis: https://github.com/jenkinsci/github-plugin/pull/46 Annotation for the git-plugin: https://github.com/jenkinsci/git-plugin/pull/259 I'm going to add an option, which disables the build failing if there's no info about Git changeset. Would it be a convenient solution? 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] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
SCM/JIRA link daemon commented on JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception Code changed in jenkins User: Mark Waite Path: src/main/java/hudson/plugins/git/util/BuildData.java http://jenkins-ci.org/commit/git-plugin/e0760d629ffe4a8f6b278ca66f7846450f1724e8 Log: Merge pull request #259 from oleg-nenashev/JENKINS-23641 JENKINS-23641 - Annotate BuildData::getLastBuiltRevision() Compare: https://github.com/jenkinsci/git-plugin/compare/e43d17f78690...e0760d629ffe 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-25117) wget $JENKINS_URL/jenkins/git/notifyCommit?url= does not trigger build when slave is offline
Daniel Beck commented on JENKINS-25117 wget $JENKINS_URL/jenkins/git/notifyCommit?url="" does not trigger build when slave is offline Did this happen within 10 minutes of a Jenkins start? 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] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
Oleg Nenashev commented on JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception Also experienced the issue, it breaks our branch management flows. Hope to submit a patch soon. 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-18682) Strange NoClassDefFoundError on slave
Daniel Beck resolved JENKINS-18682 as Cannot Reproduce Strange NoClassDefFoundError on slave Aviv Yam: As the stack trace is different, please just file a new issue. Also, please provide more information, this wiki page lists what to include: https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue In this specific case, the specific OS affected would be essential for any report. Change By: Daniel Beck (12/Oct/14 6:06 PM) Status: Reopened Resolved Resolution: Cannot Reproduce 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] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
Oleg Nenashev started work on JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception Change By: Oleg Nenashev (12/Oct/14 6:02 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] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
Oleg Nenashev assigned JENKINS-23641 to Oleg Nenashev Builds are failing due to GitHubCommitNotifier exception Change By: Oleg Nenashev (12/Oct/14 6:02 PM) Assignee: Oleg Nenashev 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-18682) Strange NoClassDefFoundError on slave
ikedam updated JENKINS-18682 Strange NoClassDefFoundError on slave Looks happened without flexible publish. Removed flexible-publish from component/s. Change By: ikedam (12/Oct/14 5:48 PM) Summary: Strange NoClassDefFoundError on slave with flexible-publish Assignee: ikedam Component/s: flexible-publish 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] [throttle-concurrent-builds-plugin] (JENKINS-19986) Throttle Concurrent Builds plugin doesn't appear to work
Oleg Nenashev resolved JENKINS-19986 as Duplicate Throttle Concurrent Builds plugin doesn't appear to work Closing as a duplicate of JENKINS-13619 (fixed in throttle-concurrents-1.8.3) Change By: Oleg Nenashev (12/Oct/14 5:40 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds-jenkins] (JENKINS-25110) Update Jclouds to 1.8.0
arun suresh resolved JENKINS-25110 as Fixed Update Jclouds to 1.8.0 Change By: arun suresh (12/Oct/14 5:11 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18682) Strange NoClassDefFoundError on slave with flexible-publish
Aviv Yam updated JENKINS-18682 Strange NoClassDefFoundError on slave with flexible-publish Change By: Aviv Yam (12/Oct/14 4:49 PM) 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] [envinject] (JENKINS-14193) EnvInject doesn't pass variables defined in prebuild step if maven project is used
Kanstantsin Shautsou edited a comment on JENKINS-14193 EnvInject doesn't pass variables defined in prebuild step if maven project is used Fixed in 2.7 maven-plugin version. Details: JENKINS-20884 2.7 will appear in update center when INFRA-178 will be resolved. Markus Meisterernst, if it solves your issue you may donate based on this info https://wiki.jenkins-ci.org/display/JENKINS/Donation 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-18682) Strange NoClassDefFoundError on slave with flexible-publish
Aviv Yam commented on JENKINS-18682 Strange NoClassDefFoundError on slave with flexible-publish Jenkins version: 1.571 Run Condition Plugin: 1.0 Java: Slave: java version "1.7.0_45" OpenJDK Runtime Environment (rhel-2.4.3.4.el6_5-x86_64 u45-b15) OpenJDK 64-Bit Server VM (build 24.45-b08, mixed mode) Jenkins: java -version java version "1.7.0_60" Java(TM) SE Runtime Environment (build 1.7.0_60-b19) Java HotSpot(TM) 64-Bit Server VM (build 24.60-b09, mixed mode) publisher: Archive the artifacts Launch slave via SSH 2014-10-10 16:22:32 ERROR: Failed to archive artifacts: *.tar.gz 2014-10-10 16:22:32 java.io.IOException: java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: Could not initialize class jnr.posix.JavaLibCHelper 2014-10-10 16:22:32 at hudson.FilePath.copyRecursiveTo(FilePath.java:2047) 2014-10-10 16:22:32 at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61) 2014-10-10 16:22:32 at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:183) 2014-10-10 16:22:32 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 2014-10-10 16:22:32 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:772) 2014-10-10 16:22:32 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:736) 2014-10-10 16:22:32 at hudson.model.Build$BuildExecution.post2(Build.java:183) 2014-10-10 16:22:32 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:685) 2014-10-10 16:22:32 at hudson.model.Run.execute(Run.java:1757) 2014-10-10 16:22:32 at hudson.matrix.MatrixRun.run(MatrixRun.java:146) 2014-10-10 16:22:32 at hudson.model.ResourceController.execute(ResourceController.java:88) 2014-10-10 16:22:32 at hudson.model.Executor.run(Executor.java:234) 2014-10-10 16:22:32 Caused by: java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: Could not initialize class jnr.posix.JavaLibCHelper 2014-10-10 16:22:32 at hudson.remoting.Channel$3.adapt(Channel.java:772) 2014-10-10 16:22:32 at hudson.remoting.Channel$3.adapt(Channel.java:767) 2014-10-10 16:22:32 at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55) 2014-10-10 16:22:32 at hudson.FilePath.copyRecursiveTo(FilePath.java:2045) 2014-10-10 16:22:32 ... 11 more 2014-10-10 16:22:32 Caused by: java.lang.NoClassDefFoundError: Could not initialize class jnr.posix.JavaLibCHelper 2014-10-10 16:22:32 at jnr.posix.JavaPOSIX.(JavaPOSIX.java:31) 2014-10-10 16:22:32 at jnr.posix.POSIXFactory.getJavaPOSIX(POSIXFactory.java:91) 2014-10-10 16:22:32 at jnr.posix.POSIXFactory.loadPOSIX(POSIXFactory.java:57) 2014-10-10 16:22:32 at jnr.posix.LazyPOSIX.loadPOSIX(LazyPOSIX.java:33) 2014-10-10 16:22:32 at jnr.posix.LazyPOSIX.posix(LazyPOSIX.java:29) 2014-10-10 16:22:32 at jnr.posix.LazyPOSIX.stat(LazyPOSIX.java:267) 2014-10-10 16:22:32 at hudson.util.IOUtils.mode(IOUtils.java:128) 2014-10-10 16:22:32 at hudson.util.io.TarArchiver.visit(TarArchiver.java:101) 2014-10-10 16:22:32 at hudson.util.DirScanner.scanSingle(DirScanner.java:49) 2014-10-10 16:22:32 at hudson.FilePath$ExplicitlySpecifiedDirScanner.scan(FilePath.java:2571) 2014-10-10 16:22:32 at hudson.FilePath.writeToTar(FilePath.java:2083) 2014-10-10 16:22:32 at hudson.FilePath.access$1000(FilePath.java:180) 2014-10-10 16:22:32 at hudson.FilePath$41.invoke(FilePath.java:2024) 2014-10-10 16:22:32 at hudson.FilePath$41.invoke(FilePath.java:2020) 2014-10-10 16:22:32 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2492) 2014-10-10 16:22:32 at hudson.remoting.UserRequest.perform(UserRequest.java:118) 2014-10-10 16:22:32 at hudson.remoting.UserRequest.perform(UserRequest.java:48) 2014-10-10 16:22:32 at hudson.remoting.Request$2.run(Request.java:328) 2014-10-10 16:22:32 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 2014-10-10 16:22:32 at java.util.concurrent.FutureTask.run(FutureTask.java:262) 2014-10-10 16:22:32 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 2014-10-10 16:22:32 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 2014-10-10 16:22:32 at java.lang.Thread.run(Thread.java:744) 2014-10-10 16:22:32 Sending e-mails to: haim.at...@emc.com igor.alter...@emc.com ayelet.co...@emc.com 2014-10-10 16:22:37 Finished: FAILURE
[JIRA] [core] (JENKINS-18682) Strange NoClassDefFoundError on slave with flexible-publish
Aviv Yam reopened JENKINS-18682 Strange NoClassDefFoundError on slave with flexible-publish Change By: Aviv Yam (12/Oct/14 4:45 PM) Resolution: Cannot Reproduce 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] [envinject] (JENKINS-14193) EnvInject doesn't pass variables defined in prebuild step if maven project is used
Kanstantsin Shautsou resolved JENKINS-14193 as Fixed EnvInject doesn't pass variables defined in prebuild step if maven project is used Fixed in 2.7 maven-plugin version. Details: JENKINS-20884 Change By: Kanstantsin Shautsou (12/Oct/14 4:42 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] [gerrit-trigger] (JENKINS-24948) Git/Gerrit environment Variables are not available in Maven projects
Kanstantsin Shautsou commented on JENKINS-24948 Git/Gerrit environment Variables are not available in Maven projects Update center temporary broken INFRA-178 you may update it directly 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-5253) artifacts archiving: add option for treating patterns in case insensitive way
Dominique Brice assigned JENKINS-5253 to Dominique Brice artifacts archiving: add option for treating patterns in case insensitive way Change By: Dominique Brice (12/Oct/14 4:34 PM) Assignee: Dominique Brice 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-633) Configuration related form validation errors need to be toned down
Daniel Beck updated JENKINS-633 Configuration related form validation errors need to be toned down Change By: Daniel Beck (12/Oct/14 4:30 PM) Issue Type: Bug Improvement Priority: Major Minor 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-89) Clean up fingerprint DB periodically
Daniel Beck resolved JENKINS-89 as Fixed Clean up fingerprint DB periodically Seems to have been reopened for request for assistance, so resolving again. Change By: Daniel Beck (12/Oct/14 4:28 PM) Status: Reopened 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-9688) Build runs on master without executor and get stuck
Daniel Beck resolved JENKINS-9688 as Incomplete Build runs on master without executor and get stuck Too old and too little detail in the issue report to help further investigation, so resolving as incomplete. Please file a new issue if this happens with a recent version of Jenkins (no older than ten weeks or so), and provide relevant information: Installed plugins, job configuration, how this can be reproduced, etc. See also the wiki for what other information may be relevant: https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue Change By: Daniel Beck (12/Oct/14 4:27 PM) Status: Open Resolved Resolution: Incomplete 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] [rebuild] (JENKINS-16661) Rebuild plugin crashes when used in conjuction with Random String Parameter Plugin
Daniel Beck updated JENKINS-16661 Rebuild plugin crashes when used in conjuction with Random String Parameter Plugin Change By: Daniel Beck (12/Oct/14 4:17 PM) Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-11962) Symlinking lastSuccessful build shouldn't fail with concurrent jobs
Daniel Beck commented on JENKINS-11962 Symlinking lastSuccessful build shouldn't fail with concurrent jobs Can this be reproduced in more recent versions of Jenkins (no older than 8-10 weeks or so)? If so, what OS and what version and vendor of Java are you using? Please include log excerpts, content of the /systemInfo URL in your comment. Also relevant: https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+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] [core] (JENKINS-7339) maven.test.failure.ignore ignored when set globally
Daniel Beck resolved JENKINS-7339 as Not A Defect maven.test.failure.ignore ignored when set globally As km explained, this appears to not be a defect. If you disagree, please show that MAVEN_OPTS can be used to set system properties outside Jenkins, and that this issue is specific to maven builds in Jenkins. Detailed steps to reproduce the problem would be helpful as well. Change By: Daniel Beck (12/Oct/14 4:07 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] [core] (JENKINS-19358) cpu and memory on Jenkins master keeps increasing quickly
Daniel Beck resolved JENKINS-19358 as Incomplete cpu and memory on Jenkins master keeps increasing quickly No response to comment asking for additional information in four months, so resolving as incomplete. Some instructions what information to include in a bug report are available in the wiki: https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue Change By: Daniel Beck (12/Oct/14 4:05 PM) Status: Open Resolved Resolution: Incomplete 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-7459) plugin proxy configuration is also used for auto-installers, should be optional
Daniel Beck resolved JENKINS-7459 as Cannot Reproduce plugin proxy configuration is also used for auto-installers, should be optional That checkbox exists in the form of the list of host names that should not be accessed via proxy. Change By: Daniel Beck (12/Oct/14 4:03 PM) Status: Open Resolved Resolution: Cannot Reproduce 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-3539) File parameter, file is touched if no argument given
Daniel Beck commented on JENKINS-3539 File parameter, file is touched if no argument given Probably caused by https://github.com/jenkinsci/jenkins/commit/4a95cc6f9269108e607077dc9fd57f06e4c9af26 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-16182) java.lang.NullPointerException at hudson.model.Project.createTransientActions(Project.java:212)
Daniel Beck resolved JENKINS-16182 as Cannot Reproduce java.lang.NullPointerException at hudson.model.Project.createTransientActions(Project.java:212) No response to comment asking for updated information in ten months, resolving as Cannot Reproduce. In this issue, the exact job config.xml posted would be essential for further investigation, please don't reopen or file a new issue without providing it. Also, it looks like the XML was incomplete e.g. by not including a element. Make sure not to submit broken or partial XML files before filing a new issue or reopening. Change By: Daniel Beck (12/Oct/14 3:48 PM) Status: Open Resolved Resolution: Cannot Reproduce 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-15526) toJSON broken: [JENKINS-11618] reintroduced a bug fixed by prototypejs 1.7
Daniel Beck commented on JENKINS-15526 toJSON broken: [JENKINS-11618] reintroduced a bug fixed by prototypejs 1.7 Is this still a problem in recent Jenkins versions? How can this be reproduced? What is the impact of this 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] [core] (JENKINS-24458) doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions
SCM/JIRA link daemon commented on JENKINS-24458 doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions Code changed in jenkins User: Kohsuke Kawaguchi Path: core/pom.xml http://jenkins-ci.org/commit/jenkins/8ae29e50c7356a8e2ec9be1126bad957dab0117a Log: [JENKINS-24458 JENKINS-11543] integrated the newer version of stapler with reduced log level (cherry picked from commit c57f9ed577b9635f01aa5affabf1f770b689a115) Conflicts: changelog.html 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-23471) Channel reader thread consumes all CPUs
SCM/JIRA link daemon commented on JENKINS-23471 Channel reader thread consumes all CPUs Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html pom.xml http://jenkins-ci.org/commit/jenkins/9c82fc42eb08b89047c544aaa586291ad1485472 Log: [JENKINS-23471 JENKINS-24050] Integrated the fix in remoting to Jenkins 1.580. (cherry picked from commit 8fc609fe0952b285d5b26a59fd5ff4c29704d33d) 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-24050) All slaves disconnect and no new slaves can connect due to CancelledKeyException in org.jenkinsci.remoting
SCM/JIRA link daemon commented on JENKINS-24050 All slaves disconnect and no new slaves can connect due to CancelledKeyException in org.jenkinsci.remoting Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html pom.xml http://jenkins-ci.org/commit/jenkins/9c82fc42eb08b89047c544aaa586291ad1485472 Log: [JENKINS-23471 JENKINS-24050] Integrated the fix in remoting to Jenkins 1.580. (cherry picked from commit 8fc609fe0952b285d5b26a59fd5ff4c29704d33d) 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-24453) Jenkins server got blue screen to death
SCM/JIRA link daemon commented on JENKINS-24453 Jenkins server got blue screen to death Code changed in jenkins User: Kohsuke Kawaguchi Path: core/pom.xml http://jenkins-ci.org/commit/jenkins/21fb398bfa7068f6f72154763bdbb09baddf313d Log: JENKINS-24453[ZD-20503] Incorporated a newer version of winp. This version checks the critical flag of the process, as killing such a process results in BSoD. (cherry picked from commit 040b7d4047b324f17c0971f2511f954eb173fa23) Conflicts: changelog.html Compare: https://github.com/jenkinsci/jenkins/compare/b105627b7357^...21fb398bfa70 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-7478) Wrong EOL (UNIX type: LF) in Windows batch files executed for build steps of type "Execute Windows batch command"
SCM/JIRA link daemon commented on JENKINS-7478 Wrong EOL (UNIX type: LF) in Windows batch files executed for build steps of type "Execute Windows batch command" Code changed in jenkins User: David Ruhmann Path: core/src/main/java/hudson/tasks/BatchFile.java core/src/main/java/hudson/tasks/Shell.java core/src/main/java/hudson/tools/AbstractCommandInstaller.java core/src/main/java/hudson/tools/BatchCommandInstaller.java core/src/main/java/hudson/tools/CommandInstaller.java core/src/main/java/hudson/util/LineEndingConversion.java test/src/test/java/hudson/tasks/BatchFileTest.java test/src/test/java/hudson/tasks/ShellTest.java test/src/test/java/hudson/tools/BatchCommandInstallerTest.java test/src/test/java/hudson/tools/CommandInstallerTest.java test/src/test/java/hudson/util/LineEndingConversionTest.java http://jenkins-ci.org/commit/jenkins/efae48a451b1dbb15a13abff26b0bec269a63909 Log: [FIXED JENKINS-7478] Create Line Ending Conversion utility to convert scripts to proper OS line ending type. Tests included. (cherry picked from commit 67ac47af0709dde6297dffeb210b03d8b65f6033) 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-11543) UTF-8 encoding issue of build parameters as soon as including File parameter
SCM/JIRA link daemon commented on JENKINS-11543 UTF-8 encoding issue of build parameters as soon as including File parameter Code changed in jenkins User: Kohsuke Kawaguchi Path: core/pom.xml http://jenkins-ci.org/commit/jenkins/8ae29e50c7356a8e2ec9be1126bad957dab0117a Log: [JENKINS-24458 JENKINS-11543] integrated the newer version of stapler with reduced log level (cherry picked from commit c57f9ed577b9635f01aa5affabf1f770b689a115) Conflicts: changelog.html 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-24614) "unknown format type" on console output
SCM/JIRA link daemon commented on JENKINS-24614 "unknown format type" on console output Code changed in jenkins User: Daniel Beck Path: core/src/main/resources/hudson/model/Run/console_he.properties http://jenkins-ci.org/commit/jenkins/4d455fbb0d2f33bd87a8c38580f7ff2ffb78b0ac Log: [FIXED JENKINS-24614] Broken format string in Hebrew console output (cherry picked from commit 07fd5fa45d4b818fc11de97ce99ab6b3423aca85) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-24948) Git/Gerrit environment Variables are not available in Maven projects
Kanstantsin Shautsou commented on JENKINS-24948 Git/Gerrit environment Variables are not available in Maven projects Then wait or directly download https://updates.jenkins-ci.org/download/plugins/maven-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-15710) Web Prefix with 2 levels causes site to be unreachable
Daniel Beck resolved JENKINS-15710 as Cannot Reproduce Web Prefix with 2 levels causes site to be unreachable Works for me in Jenkins 1.58x, probably resolved by the switch to Jetty in 1.535. Change By: Daniel Beck (12/Oct/14 2:25 PM) Status: Open Resolved Resolution: Cannot Reproduce 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-15526) toJSON broken: [JENKINS-11618] reintroduced a bug fixed by prototypejs 1.7
Daniel Beck updated JENKINS-15526 toJSON broken: [JENKINS-11618] reintroduced a bug fixed by prototypejs 1.7 Change By: Daniel Beck (12/Oct/14 2:26 PM) Labels: jenkins 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] [flexible-publish] (JENKINS-25017) BuildTrigger in Flexible Publish doesn't work since Jenkins 1.501
wernight commented on JENKINS-25017 BuildTrigger in Flexible Publish doesn't work since Jenkins 1.501 I confirm the workaround (using Parameterized Trigger together with Flexible Trigger) to be working. 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] [remoting] (JENKINS-16393) "Unable to call join" build failures
Daniel Beck updated JENKINS-16393 "Unable to call join" build failures Change By: Daniel Beck (12/Oct/14 1:58 PM) Component/s: remoting Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-16459) /configure can be broken by one plugin class loading issue
Daniel Beck updated JENKINS-16459 /configure can be broken by one plugin class loading issue Change By: Daniel Beck (12/Oct/14 1:57 PM) Labels: robustness 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] [artifactdeployer] (JENKINS-19664) Archived artifact of promoted build corrupted after download!
Daniel Beck commented on JENKINS-19664 Archived artifact of promoted build corrupted after download! Is the file really different, or rather truncated? 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-21463) Job parameter replaces Linux path environment variable
Daniel Beck resolved JENKINS-21463 as Won't Fix Job parameter replaces Linux path environment variable Behaves as designed, see http://javadoc.jenkins-ci.org/hudson/EnvVars.html Change By: Daniel Beck (12/Oct/14 1:51 PM) Status: Open Resolved Resolution: Won't Fix 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-21178) Matrix jobs fails randomly during building the changelog
Daniel Beck commented on JENKINS-21178 Matrix jobs fails randomly during building the changelog Does this still occur? How are your jobs configured? How are they triggered? What's the source of the @UNDEFINED in the URL? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23654) UpdateCenter stuck at preparation phase when jenkins server is behind GFW
Daniel Beck commented on JENKINS-23654 UpdateCenter stuck at preparation phase when jenkins server is behind GFW JENKINS-15124 notes that some shit proxies return nice looking error pages instead of error responses, so having a reference URL with defined content that can be compared would be nice. 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-15124) Incorrect proxy settings for plugin manager does not provide meaningful error/feedback.
Daniel Beck resolved JENKINS-15124 as Not A Defect Incorrect proxy settings for plugin manager does not provide meaningful error/feedback. The problem here is that some proxies are configured to return a nice looking error page that contains no useful semantic error. In that, this isn't a Jenkins bug (We may be able to detect this using a better connect check URL as I suggested on JENKINS-23654.) However, this should not break plugin installs. Verification of the downloaded zip file is already filed as JENKINS-14616 though. Change By: Daniel Beck (12/Oct/14 1:41 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] [core] (JENKINS-25117) wget $JENKINS_URL/jenkins/git/notifyCommit?url= does not trigger build when slave is offline
Daniel Beck updated JENKINS-25117 wget $JENKINS_URL/jenkins/git/notifyCommit?url="" does not trigger build when slave is offline Change By: Daniel Beck (12/Oct/14 1:37 PM) Priority: Critical Major Component/s: core Component/s: git Component/s: slave-utilization 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-publisher] (JENKINS-13609) Lost of the latest build after jenkins restart
Daniel Beck resolved JENKINS-13609 as Cannot Reproduce Lost of the latest build after jenkins restart No response to comment asking for updated information in over a year, so resolving as Cannot Reproduce. Change By: Daniel Beck (12/Oct/14 1:29 PM) Status: Open Resolved Resolution: Cannot Reproduce 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] [slave-utilization] (JENKINS-25117) wget $JENKINS_URL/jenkins/git/notifyCommit?url= does not trigger build when slave is offline
ken graham created JENKINS-25117 wget $JENKINS_URL/jenkins/git/notifyCommit?url="" does not trigger build when slave is offline Issue Type: Bug Assignee: Unassigned Components: slave-utilization Created: 12/Oct/14 1:23 PM Description: Polling log for affected job(s): We need to schedule a new build to get a workspace, but deferring 202,880ms in the hope that one will become available soon (all_suitable_nodes_are_offline) ### This means the notifyCommit code was executed. It also means that it did not trigger any of the nodes the job is tied to to be brought online, even though they are configured to be brought online when needed. Environment: Jenkins 1.583, git plugin Project: Jenkins Priority: Critical Reporter: ken graham 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-12550) System default JDK wrongly used if JDK is created first
Daniel Beck commented on JENKINS-12550 System default JDK wrongly used if JDK is created first Of course, given how weird the behavior is with one JDK installation, a job last configured when there was no or one JDK will change behavior depending on whether there are one or two JDKs configured globally. With one configured JDK, that will be used, with two configured, the system default will be used. 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-12550) System default JDK wrongly used if JDK is created first
Daniel Beck
resolved JENKINS-12550 as Cannot Reproduce
System default JDK wrongly used if JDK is created first
Cannot Reproduce on 1.58x:
Create maven Job. No in XML;
println Jenkins.instance.getItemByFullName('JENKINS-12550').JDK
in Script Console prints null
Add the first JDK in the global config
Repeat step 1. No , script prints JDK name.
Configure and Save the first Maven job. Still no , script prints JDK name.
Create a new maven job. Still no , script prints JDK name.
Add a second JDK in the global config. No , script prints JDK name.
Configure and Save a Maven job. Now there is in XML (Default), script prints null again.
Configure a Maven job to use a specified JDK, and Save. Now there is in XML (JDK name), script prints JDK name.
Change By:
Daniel Beck
(12/Oct/14 1:13 PM)
Status:
Open
Resolved
Resolution:
Cannot Reproduce
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-7217) Clean Workspace only cleans the most recent slave
Daniel Beck commented on JENKINS-7217 Clean Workspace only cleans the most recent slave Well, it cleans the workspace you're viewing, which is the most recent one. Needs an improvement of the workspace browser to support selection of specific node/workspace I think, then this will follow naturally. 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-7822) Maven settings file not found (concurrent build of same project)
Daniel Beck resolved JENKINS-7822 as Duplicate Maven settings file not found (concurrent build of same project) Duplicates JENKINS-11825 as which it was fixed in https://github.com/jenkinsci/jenkins/commit/142a7bb9a479b8456a97f3ddabe65277db4643a9 Change By: Daniel Beck (12/Oct/14 12:31 PM) Status: Open Resolved Resolution: Duplicate 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] (JENKINS-24683) Add support for bind mounting volumes
Harald Albers commented on JENKINS-24683 Add support for bind mounting volumes Created PR #16 for the --volumes part. Dropping my request for --volumes-from as I don't think it's really important at the current project stage. 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-8242) Thread cannot be close when shuting down tomcat
Daniel Beck resolved JENKINS-8242 as Incomplete Thread cannot be close when shuting down tomcat Given the age of this issue, this needs to be reproduced on a much more recent version (no older than eight weeks). Therefore resolving as Incomplete. If this occurs in recent Jenkins version, please file a new issue, after reading this wiki page on what information to include: https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue Change By: Daniel Beck (12/Oct/14 12:16 PM) Status: Open Resolved Resolution: Incomplete 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-16167) Timer triggers with comments do not work after copy
Daniel Beck resolved JENKINS-16167 as Not A Defect Timer triggers with comments do not work after copy Not a defect, only happens when you use e.g. curl --data @config.xml rather than curl --data-binary @config.xml. Only the latter retains line breaks, which are essential for this format: * * * * * # foo is invalid. # foo * * * * * is all comment, and the trigger is stripped from the job. Change By: Daniel Beck (12/Oct/14 12:13 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] [core] (JENKINS-16167) Timer triggers with comments do not work after copy
Daniel Beck edited a comment on JENKINS-16167 Timer triggers with comments do not work after copy Confirmed (with different but similarly broken behavior) on 1.583; if the timer spec contains a comment, the timer will silently be discarded. 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-16167) Timer triggers with comments do not work after copy
Daniel Beck commented on JENKINS-16167 Timer triggers with comments do not work after copy Confirmed on 1.583; if the timer spec contains a comment, the timer will silently be discarded. 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-16395) The path parameter in the REST API should support wildcard '*'.
Daniel Beck resolved JENKINS-16395 as Fixed The path parameter in the REST API should support wildcard '*'. Appears to have been resolved by https://github.com/stapler/stapler/commit/bcb1ab27fa0751a0a9904e41107628f12c0c73c3 while the bot was asleep. Change By: Daniel Beck (12/Oct/14 10:51 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-17267) Git clean or wipeout workspace follows symlink on Windows slaves
Daniel Beck
commented on JENKINS-17267
Git clean or wipeout workspace follows symlink on Windows slaves
It doesn't help that the Java runtime (maybe assisted by Windows) claims that junction points are a directory.
Create a new freestyle project named JENKINS-17267, add a Windows Batch build step:
mklink /d s c:\existingTargetFolder
mklink /j j c:\existingTargetFolder
md d
Build once. Then open Script Console and run the following script:
def s = new File(Jenkins.instance.getItemByFullName('JENKINS-17267').someWorkspace.child('s').getRemote())
def j = new File(Jenkins.instance.getItemByFullName('JENKINS-17267').someWorkspace.child('j').getRemote())
def d = new File(Jenkins.instance.getItemByFullName('JENKINS-17267').someWorkspace.child('d').getRemote())
[s, j, d].each {
println java.nio.file.Files.isDirectory(it.toPath())
println java.nio.file.Files.isDirectory(it.toPath(), java.nio.file.LinkOption.NOFOLLOW_LINKS)
println java.nio.file.Files.isSymbolicLink(it.toPath())
println ""
}
return
Output:
true
false
true
true
true
false
true
true
false
In other words, a pure Java program has no chance to distinguish between a junction and an actual folder.
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-17267) Git clean or wipeout workspace follows symlink on Windows slaves
Daniel Beck commented on JENKINS-17267 Git clean or wipeout workspace follows symlink on Windows slaves Same issue occurs when using 'Wipe Out Workspace' so more of a core issue than git I think. Workaround is to use directory symbolic links (mklink /d) rather than junction points (mklink /j). 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-18601) Create view breaks during creation of new view
Daniel Beck resolved JENKINS-18601 as Incomplete Create view breaks during creation of new view The issue William Clifford is experiencing stems from an incomplete request in a weird attempt to emulate a web browser. No json argument for structured form submission. https://github.com/stapler/stapler/blob/master/core/src/main/java/org/kohsuke/stapler/RequestImpl.java#L878 https://wiki.jenkins-ci.org/display/JENKINS/Structured+Form+Submission AFAICT the correct approach is to do something similar to 'Create Job' documented at the /api URL. Hence no relevant response to Oleg's comment asking for updated and additional information in several months. Resolving as incomplete. Please file a new issue instead of reopening if this occurs again. Please only file an issue if it affects recent (no older than eight weeks) versions of Jenkins. Before filing an issue, make sure _javascript_ is enabled. Include any _javascript_ errors in your report. Change By: Daniel Beck (12/Oct/14 10:02 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-24948) Git/Gerrit environment Variables are not available in Maven projects
Doron Shai commented on JENKINS-24948 Git/Gerrit environment Variables are not available in Maven projects it was not released yet 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.
