[JIRA] (JENKINS-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
Martin Falatic updated JENKINS-17186 Linux: if there is a recursive directory within the git repo youre building, the initial checkout will fail badly I'm changing this to a blocker because the only workaround is to downgrade the git plugins (or to entirely sidestep Jgit as suggested in other recent bugs). Change By: Martin Falatic (14/Mar/13 6:10 AM) Priority: Major Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17193) Missing Delete button
justinas Urbanavicius commented on JENKINS-17193 Missing Delete button v1.503 after update to v1.505 the button was still missing This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17192) Add support for phpunit3 coverage
justinas Urbanavicius commented on JENKINS-17192 Add support for phpunit3 coverage that explains it, i had type set to xml: type"xml" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17199) import statement doesn't work Build flow DSL
SCM/JIRA link daemon commented on JENKINS-17199 import statement doesnt work Build flow DSL Code changed in jenkins User: Nicolas De loof Path: src/main/groovy/com/cloudbees/plugins/flow/FlowDSL.groovy src/test/groovy/com/cloudbees/plugins/flow/BindingTest.groovy src/test/groovy/com/cloudbees/plugins/flow/BuildTest.groovy http://jenkins-ci.org/commit/build-flow-plugin/a810876d7cbe1c8e2d7a79221c6cd2b89048dec8 Log: Merge pull request #21 from jenkinsci/JENKINS-17199 Fixed JENKINS-17199 Compare: https://github.com/jenkinsci/build-flow-plugin/compare/e8af7da1bd05...a810876d7cbe You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17193) Missing Delete button
sogabe updated JENKINS-17193 Missing Delete button Change By: sogabe (14/Mar/13 7:17 AM) Attachment: cloverphp_missing_delete.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/groups/opt_out.
[JIRA] (JENKINS-17193) Missing Delete button
sogabe commented on JENKINS-17193 Missing Delete button I cant not reproduce it. see attached cloverphp_missing_delete.png file. In 1.505, "Delete" button shows up collectly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14542) Issue ID Pattern no longer working
sogabe resolved JENKINS-14542 as Fixed Issue ID Pattern no longer working Change By: sogabe (14/Mar/13 7:23 AM) Status: InProgress 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/groups/opt_out.
[JIRA] (JENKINS-17193) Missing Delete button
justinas Urbanavicius commented on JENKINS-17193 Missing Delete button Try adding more post build actions and clover coverage action as last This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17193) Missing Delete button
justinas Urbanavicius updated JENKINS-17193 Missing Delete button Added screenshot with full config visible, and all actions Change By: justinas Urbanavicius (14/Mar/13 7:41 AM) Attachment: FireShotScreenCapture#001-SITConfig[Jenkins].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/groups/opt_out.
[JIRA] (JENKINS-10502) Add an option to make archiving the artifacts non-fatal if they don't exist
lukas rytz commented on JENKINS-10502 Add an option to make archiving the artifacts non-fatal if they dont exist @pedro: setting the default value of the checkbox according to the system property looks also fine to me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17193) Missing Delete button
sogabe commented on JENKINS-17193 Missing Delete button Try to delete "xUnit" from post build action. Perhaps delete button shows up. "xUnit" plugin seems to cause this problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16868) Icons are not displayed with a reverse proxy
Tomas Westling commented on JENKINS-16868 Icons are not displayed with a reverse proxy By using getRootUrl, we got problems with users using a context path which isn't the root. We will look into the problem and see if we can find something which works for everyone. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-10407) builds/1234, lastSuccessful and lastStable symlinks not created
Steffen Sledz commented on JENKINS-10407 builds/1234, lastSuccessful and lastStable symlinks not created Ping! The problem still exists in 1.505. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17193) Missing Delete button
justinas Urbanavicius commented on JENKINS-17193 Missing Delete button you are right it does. Should i re-register this bug with xUnit ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16940) Git publisher fails with Invalid id: origin/master when trying to publish changes
Mark Waite resolved JENKINS-16940 as Fixed Git publisher fails with Invalid id: origin/master when trying to publish changes Seems to be resolved in Git plugin 1.3.0 and Git Client plugin 1.4.0. Unfortunately, that combination does not seem to push enough information to the destination repository in the post build action, so the Git publisher function still seems to be broken. Refer to https://groups.google.com/d/msg/jenkinsci-users/sVlEKgagwdg/CgRoyGE01xcJ for more information on the behavior of Git plugin 1.3.0 when pushing to a repository Change By: Mark Waite (14/Mar/13 9:31 AM) Status: Open Resolved Fix Version/s: current 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/groups/opt_out.
[JIRA] (JENKINS-17210) analysis-core version 1.49-h-1 dependency issue in hudson
Florian Schneider created JENKINS-17210 analysis-core version 1.49-h-1 dependency issue in hudson Issue Type: Bug Assignee: Ulli Hafner Components: analysis-core Created: 14/Mar/13 9:41 AM Description: When used within Hudson 3.0.0, the analysis core plugin throws errors because a dependency to Jenkins' DataBoundTokenMacro Plugin cannot be resolved. In the old Hudson Issue Tracker, there were rumors that the issue should have been resolved, but it isn't as I am still finding the error in today's log files. Project: Jenkins Priority: Major Reporter: Florian Schneider This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17210) analysis-core version 1.49-h-1 dependency issue in hudson
Florian Schneider commented on JENKINS-17210 analysis-core version 1.49-h-1 dependency issue in hudson Adding the Hudson Issue Tracker entries mentioned above: http://issues.hudson-ci.org/browse/HUDSON-9106 http://issues.hudson-ci.org/browse/HUDSON-9040 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17210) analysis-core version 1.49-h-1 dependency issue in hudson
Florian Schneider commented on JENKINS-17210 analysis-core version 1.49-h-1 dependency issue in hudson The MANIFEST.MF of the installed plugin under .hudons/plugins/analysis-core/META-INF surprisingly contains the following information: Plugin-Class: hudson.plugins.analysis.core.AnalysisCorePlugin Group-Id: org.hudsonci.plugins Short-Name: analysis-core Long-Name: Static Analysis Utilities Url: http://wiki.hudson-ci.org/x/CwDgAQ Plugin-Version: 1.49-h-1 Hudson-Version: 3.0.1-M1 Plugin-Dependencies: jfreechart-plugin:1.4,maven-plugin:2.2.1;resoluti on:=optional,dashboard-view:2.3-h-2;resolution:=optional,token-macro: 1.6-h-1;resolution:=optional This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15014) TestFlight automatically replaces old builds
lacostej commented on JENKINS-15014 TestFlight automatically replaces old builds BTW, I felt a bit bad to close this without being able to help more. So I implemented a troubleshooting mode (released in 1.3.5, pushed now) that allows to log the POST request/answer (hiding criticial information like passwords). The only drawback is that you have to actively enable it before the problem happens. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17208) Link to affected source from a warning does not function
Ulli Hafner commented on JENKINS-17208 Link to affected source from a warning does not function Which plug-in versions are you using? Is this the only source that does not show up? Is the source file generated? Is there a corresponding log message in the console log of your job? What is the source path of the warning in the file that is generated from findbugs? What is the path/filename in my findbugs-warnings.xml file in your build 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/groups/opt_out.
[JIRA] (JENKINS-17210) analysis-core version 1.49-h-1 dependency issue in hudson
Ulli Hafner resolved JENKINS-17210 as Not A Defect analysis-core version 1.49-h-1 dependency issue in hudson Please discuss this problem with the Hudson team, this is not a problem in my plug-in. Change By: Ulli Hafner (14/Mar/13 10:08 AM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15103) jenkins slave process does not let go of .git\objects\pack\*.pack file causeing Unable to delete when wiping workspace
Kirill Mescheryakov commented on JENKINS-15103 jenkins slave process does not let go of .git\objects\pack\*.pack file causeing Unable to delete when wiping workspace Seeing the same. Please fix. We dont have any workaround for 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/groups/opt_out.
[JIRA] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Brett Delle Grazie updated JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ Looks like Git plugin based on JGit is not observing environment variables like 'HOME' and not defaulting HOME to USERPROFILE in Windows. Note that Node and/or Job configurations can modify these environment variables - this case needs to be handled too In particular: SSH config location needs to be based on 'HOME' at the level of the job (defaulting to USERPROFILE in Windows if not set), same with Git configuration Change By: Brett Delle Grazie (14/Mar/13 10:23 AM) Summary: GIT plugin fetchfailingsinceupdate GitPlugin to Jenkins 1. 505 2.0+ Environment: Ubuntu12.04 ,Windows(any) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17193) Missing Delete button
sogabe updated JENKINS-17193 Missing Delete button change component to xUnit Change By: sogabe (14/Mar/13 10:28 AM) Assignee: sogabe GregoryBoissinot Component/s: xunit Component/s: cloverphp-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/groups/opt_out.
[JIRA] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Brett Delle Grazie edited a comment on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ Looks like Git plugin based on JGit is not observing environment variables like 'HOME' and not defaulting HOME to HOMEDRIVE\HOMEPATH in Windows. Note that Node and/or Job configurations can modify these environment variables - this case needs to be handled too In particular: SSH config location needs to be based on 'HOME' at the level of the job (defaulting to HOMEDRIVE\HOMEPATH in Windows if not set), same with Git configuration This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17127) Pass DISPLAY as environment variable to Maven builds
Uwe Stuehler commented on JENKINS-17127 Pass DISPLAY as environment variable to Maven builds Thank you for the helpful code snippet! It turns out that we were a little overeager in making sure that all processes started as jenkins get the same environment. The DISPLAY variable was set in all of /.profile, /.bash_profile and ~/.bashrc. The Xvfb plugin works fine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17127) Pass DISPLAY as environment variable to Maven builds
Uwe Stuehler resolved JENKINS-17127 as Cannot Reproduce Pass DISPLAY as environment variable to Maven builds Change By: Uwe Stuehler (14/Mar/13 10:51 AM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17083) Git Plugin 1.2.0 fails to use ENV vars (1.1.26 works)
Brett Delle Grazie commented on JENKINS-17083 Git Plugin 1.2.0 fails to use ENV vars (1.1.26 works) Related issue JENKINS-17204 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Brett Delle Grazie commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ Related issue JENKINS-17083 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Fwd: Delivery Status Notification (Failure)
Forwarded conversation Subject: Bug in the code From: *Uladzimir Ishutsinau* uladzimirishutsi...@gmail.com Date: 2013/3/14 To: jenkinsci-us...@googlegroups.com Report log: ===[JENKINS REMOTING CAPACITY]===channel started Executing Maven: -B -f /opt/jenkins/jobs/bots/workspace/bots/pom.xml clean install ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.comjava.lang.NullPointerException http://stacktrace.jenkins-ci.org/search?query=java.lang.NullPointerException at hudson.model.listeners.RunListener.all(RunListener.java:234) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.listeners.RunListener.allentity=method at hudson.model.listeners.RunListener.fireFinalized(RunListener.java:206) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.listeners.RunListener.fireFinalizedentity=method at hudson.model.Run.onEndBuilding(Run.java:1672) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.onEndBuildingentity=method at hudson.model.Run.execute(Run.java:1615) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.executeentity=method at hudson.maven.MavenBuild.access$600(MavenBuild.java:86) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenBuild.access$600entity=method at hudson.maven.MavenBuild$ProxyImpl2.close(MavenBuild.java:560) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenBuild$ProxyImpl2.closeentity=method at hudson.maven.AbstractMavenBuilder.end(AbstractMavenBuilder.java:106) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.AbstractMavenBuilder.endentity=method at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:758) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRunentity=method at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:592) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.runentity=method at hudson.model.Run.execute(Run.java:1543) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.executeentity=method at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild.runentity=method at hudson.model.ResourceController.execute(ResourceController.java:88) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.ResourceController.executeentity=method at hudson.model.Executor.run(Executor.java:236) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Executor.runentity=method project=hudson.maven.MavenModuleSet@1e19920[bots] project.getModules()=[hudson.maven.MavenModule@1599116[bots/by.uladzimir.site:bots][bots/by.uladzimir.site:bots][relativePath:bots], hudson.maven.MavenModule@1447997[bots/by.uladzimir.site:syncAd][bots/by.uladzimir.site:syncAd][relativePath:bots/syncAd], hudson.maven.MavenModule@8add78[bots/by.uladzimir.site:syncCaptcha][bots/by.uladzimir.site:syncCaptcha][relativePath:bots/syncCaptcha], hudson.maven.MavenModule@10eec9e[bots/by.uladzimir.site:synchAd][bots/by.uladzimir.site:synchAd][relativePath:bots/syncAd], hudson.maven.MavenModule@19c41fe[bots/by.uladzimir.site:synchCaptcha][bots/by.uladzimir.site:synchCaptcha][relativePath:bots/syncCaptcha]] project.getRootModule()=hudson.maven.MavenModule@1599116[bots/by.uladzimir.site:bots][bots/by.uladzimir.site:bots][relativePath:bots] FATAL: nulljava.lang.NullPointerException http://stacktrace.jenkins-ci.org/search?query=java.lang.NullPointerException at hudson.model.listeners.RunListener.all(RunListener.java:234) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.listeners.RunListener.allentity=method at hudson.model.listeners.RunListener.fireFinalized(RunListener.java:206) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.listeners.RunListener.fireFinalizedentity=method at hudson.model.Run.onEndBuilding(Run.java:1672) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.onEndBuildingentity=method at hudson.model.Run.execute(Run.java:1615) http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.executeentity=method at hudson.maven.MavenBuild.access$600(MavenBuild.java:86) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenBuild.access$600entity=method at hudson.maven.MavenBuild$ProxyImpl2.close(MavenBuild.java:560) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenBuild$ProxyImpl2.closeentity=method at hudson.maven.AbstractMavenBuilder.end(AbstractMavenBuilder.java:106) http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.AbstractMavenBuilder.endentity=method at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:758)
AUTO: Martin Schoepf is out of the office (returning 03.19.2013)
I am out of the office until 03.19.2013. Note: This is an automated response to your message Fwd: Delivery Status Notification (Failure) sent on 3/14/2013 12:15:47. This is the only notification you will receive while this person is away. -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17211) HTTP authentication is not possible with JGit implementation of git-client plugin
Marcus Klein created JENKINS-17211 HTTP authentication is not possible with JGit implementation of git-client plugin Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 14/Mar/13 11:20 AM Description: With the latest update of the git-client-plugin the default behavior is to use the JGit implementation instead of the git command line tool. For the git command line tool I set up HTTP authentication using the file .netrc in the home directory of Jenkins. This does not work anymore with the default JGit implementation. I had to switch back to the git command line tool, which is pretty annoying because the system property needs to be added to the JVM options of every slave. Environment: Debian Squeeze, Jenkins 1.505, running in standalone mode, multiple slaves running on MacOS X and Debian Squeeze Project: Jenkins Priority: Major Reporter: Marcus Klein This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17212) Git clean broken on Windows
ickersep created JENKINS-17212 Git clean broken on Windows Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 14/Mar/13 11:20 AM Description: Since the update of the Git Client plugin to 1.0.4 git clean doesn't work anymore on Windows build agents. It fails with (the file being different between different tries): Cleaning workspace FATAL: Could not delete file C:\JenkinsSlaveHome\slave2\workspace\Somejob\tmp\Store1\trash org.eclipse.jgit.api.errors.JGitInternalException: Could not delete file C:\JenkinsSlaveHome\slave2\workspace\Somejob\tmp\Store1\trash at org.eclipse.jgit.api.CleanCommand.call(CleanCommand.java:137) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.clean(JGitAPIImpl.java:305) at hudson.plugins.git.GitAPI.clean(GitAPI.java:248) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1213) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1196) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.io.IOException: Could not delete file C:\JenkinsSlaveHome\slave2\workspace\Gerrit-FieldWorks-Win-any-develop-debug\tmp\Store1\trash at org.eclipse.jgit.util.FileUtils.delete(FileUtils.java:142) at org.eclipse.jgit.api.CleanCommand.call(CleanCommand.java:132) ... 14 more Environment: Windows Project: Jenkins Priority: Major Reporter: ickersep This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17212) Git clean broken on Windows
ickersep updated JENKINS-17212 Git clean broken on Windows Change By: ickersep (14/Mar/13 11:24 AM) Description: SincetheupdateoftheGitClientpluginto1.0.4gitclean (Cleanaftercheckout) doesntworkanymoreonWindowsbuildagents.Itfailswith(thefilebeingdifferentbetweendifferenttries):CleaningworkspaceFATAL:CouldnotdeletefileC:\JenkinsSlaveHome\slave2\workspace\Somejob\tmp\Store1\trashorg.eclipse.jgit.api.errors.JGitInternalException:CouldnotdeletefileC:\JenkinsSlaveHome\slave2\workspace\Somejob\tmp\Store1\trash atorg.eclipse.jgit.api.CleanCommand.call(CleanCommand.java:137) atorg.jenkinsci.plugins.gitclient.JGitAPIImpl.clean(JGitAPIImpl.java:305) athudson.plugins.git.GitAPI.clean(GitAPI.java:248) athudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1213) athudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1196) athudson.FilePath$FileCallableWrapper.call(FilePath.java:2348) athudson.remoting.UserRequest.perform(UserRequest.java:118) athudson.remoting.UserRequest.perform(UserRequest.java:48) athudson.remoting.Request$2.run(Request.java:326) athudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) atjava.util.concurrent.FutureTask$Sync.innerRun(UnknownSource) atjava.util.concurrent.FutureTask.run(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor.runWorker(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(UnknownSource) atjava.lang.Thread.run(UnknownSource)Causedby:java.io.IOException:CouldnotdeletefileC:\JenkinsSlaveHome\slave2\workspace\Gerrit-FieldWorks-Win-any-develop-debug\tmp\Store1\trash atorg.eclipse.jgit.util.FileUtils.delete(FileUtils.java:142) atorg.eclipse.jgit.api.CleanCommand.call(CleanCommand.java:132) ...14more This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17213) Slave threads crashed when trying to lock a resource without having set a root url for Jenkins
Patrik Johansson created JENKINS-17213 Slave threads crashed when trying to lock a resource without having set a root url for Jenkins Issue Type: Bug Affects Versions: current Assignee: rsandell Attachments: error.log Components: external-resource-dispatcher Created: 14/Mar/13 11:58 AM Description: If I configure my job to use external resource selection criteria without first having reconfigured the Jenkins url I get the error below (also see attachment). In other words the url under Manage Jenkins/ Configure System/Jenkins url is set to http://localhost:8080 when this error occurs. If I change the url to something else (say http://test:8080) the error doesn't occur. The effect is that all build threads on the current slave server die with this error message: Exception in thread "Executor #1 for master" java.lang.IllegalStateException: Root URL isn't configured yet. Cannot compute absolute URL. at hudson.model.AbstractItem.getAbsoluteUrl(AbstractItem.java:419) at com.sonyericsson.jenkins.plugins.externalresource.dispatcher.ExternalResourceQueueTaskDispatcher.getUrl(ExternalResourceQueueTaskDispatcher.java:176) at com.sonyericsson.jenkins.plugins.externalresource.dispatcher.ExternalResourceQueueTaskDispatcher.canTake(ExternalResourceQueueTaskDispatcher.java:122) at hudson.model.Queue$JobOffer.canTake(Queue.java:254) at hudson.model.Queue.maintain(Queue.java:1032) at hudson.model.Queue.pop(Queue.java:863) at hudson.model.Executor.grabJob(Executor.java:285) at hudson.model.Executor.run(Executor.java:206) Environment: Linux Mint, Jenkins 1.505, External Resource Dispatcher 1.0b Project: Jenkins Labels: plugin Priority: Minor Reporter: Patrik Johansson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17214) vmware plugin causes crash of Jenkins
Bernhard Hiller created JENKINS-17214 vmware plugin causes crash of Jenkins Issue Type: Bug Affects Versions: current Assignee: stephenconnolly Components: vmware Created: 14/Mar/13 12:07 PM Description: On the Jenkins master, the VMWare SDK (latest version) was installed, and the VMWare plugin. A new project was created. In the "Build Environment" section, "VMware Server VIX Virtual Machine Activation" was selected and the fields filled in. Shortly after the build was started, the Jenkins process crashed (the computer remained running). The Jenkins service had to be restarted manually. The logs of the failed project show an error message: Gestartet durch Benutzer anonymous Baue auf Master in workspace C:\Programme\Jenkins\workspace\Integration-00 Setup Slave VMware Connecting to VMware Server host 4vsvad02:902 as user (my user name on the host) VMware VMware VIX error: The system returned an error. Communication with the virtual machine may have been interrupted hudson.plugins.vmware.VMwareRuntimeException: The system returned an error. Communication with the virtual machine may have been interrupted at hudson.plugins.vmware.VMware.checkError(VMware.java:63) at hudson.plugins.vmware.VMware.waitForJobAndGetJobResultHandle(VMware.java:51) at hudson.plugins.vmware.Host.init(Host.java:44) at hudson.plugins.vmware.VMware.connect(VMware.java:42) at hudson.plugins.vmware.VMwareActivationWrapper.setUp(VMwareActivationWrapper.java:276) at hudson.tasks.BuildWrapper.setUp(BuildWrapper.java:140) at hudson.model.Build$BuildExecution.doRun(Build.java:154) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1502) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Finished: FAILURE The Windows event log shows that an error occured with the Jenkins service, but no useful information: Unbehandelte Win32-Ausnahme in java.exe 356. Fehler beim Just-In-Time-Debugging der Ausnahme: Der Debugger konnte nicht gestartet werden, da kein Benutzer angemeldet ist. and: Dienst "Jenkins" wurde unerwartet beendet. Dies ist bereits 1 Mal passiert. This looks very similar to the discussion at http://jenkins.361315.n4.nabble.com/VMWare-plugin-crashing-hudson-td380323.html Environment: Jenkins runs on a VMWare virtual machine (Windows XP SP3, 32bit). The host is a Windows Server 2008 R2 (64bit) with VMWare Server 2.0.2. The virtual machine to be started is also hosted on this computer. Project: Jenkins Labels: plugin vmware Priority: Critical Reporter: Bernhard Hiller This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17215) TAP plugin can prevent Jenkins startup
Alex Newnham created JENKINS-17215 TAP plugin can prevent Jenkins startup Issue Type: Bug Affects Versions: current Assignee: Bruno P. Kinoshita Attachments: build.xml, stack2.txt Components: tap Created: 14/Mar/13 12:14 PM Description: Using TAP plugin v1.9 and Jenkins v1.496, the attached stack trace occurs in a loop when Jenkins is restarted. We are now seeing this prevent Jenkins starting up. Our Service Engineer tells me that the plugin is unable to load the attached build.xml Apart from becoming larger in size, the TAP test results we are producing have not changed appreciably to cause this problem. Environment: centos 6 Project: Jenkins Labels: tap Priority: Critical Reporter: Alex Newnham This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16868) Icons are not displayed with a reverse proxy
Tomas Westling commented on JENKINS-16868 Icons are not displayed with a reverse proxy I came up with solution that works for most cases. The one case it won't work is when you are running behind a reverse proxy and don't fill out the Jenkins URL in settings. getRootUrl() uses getRootUrlFromRequest() as a fallback if the field is left blank, but since it doesn't work behind reverse proxy we won't be able to find out the rootUR. Make sure to fill out the field I will try to release the fix as soon as I can. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17195) InvalidTagNameException with version 1.0.4 of git client
Christoph B commented on JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client This is pretty severe to me. Our complete build system stopped running because all of our 250 projects are prefixed by a text and followed by a space. Please repair this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17037) Null pointer exception when publishing results
sogabe resolved JENKINS-17037 as Fixed Null pointer exception when publishing results Change By: sogabe (14/Mar/13 12:34 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17073) Support specifying logger for phing
sogabe updated JENKINS-17073 Support specifying logger for phing Change By: sogabe (14/Mar/13 12:43 PM) Attachment: ansicolor.png Attachment: HtmlColorLogger.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/groups/opt_out.
[JIRA] (JENKINS-17073) Support specifying logger for phing
sogabe commented on JENKINS-17073 Support specifying logger for phing See attached files. If you use "AnsiColorLogger" or "HtmlColorLogger" instead of DefaultLogger, log is not colorized. So it makes no sense to specify logger. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16868) Icons are not displayed with a reverse proxy
Sylvain C. commented on JENKINS-16868 Icons are not displayed with a reverse proxy Great, the field is already filled. Thanks ! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17195) InvalidTagNameException with version 1.0.4 of git client
Christian Lipphardt commented on JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client Same here. Please fix it! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17195) InvalidTagNameException with version 1.0.4 of git client
Christian Lipphardt edited a comment on JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client Same here. Please fix it! (We can live with the fix to disable the internal tag for the moment tho) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17195) InvalidTagNameException with version 1.0.4 of git client
Christoph B commented on JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client I'm not going to disable the internal tagging temporarily by changing the configuration of 250 projects This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17211) HTTP authentication is not possible with JGit implementation of git-client plugin
Mikkel Bjerg commented on JENKINS-17211 HTTP authentication is not possible with JGit implementation of git-client plugin How do I set it so that it uses the original git command line? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17211) HTTP authentication is not possible with JGit implementation of git-client plugin
Marcus Klein commented on JENKINS-17211 HTTP authentication is not possible with JGit implementation of git-client plugin You have to add -Dorg.jenkinsci.plugins.gitclient.Git.useCLI=true to the JVM options of the master and every slave. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15992) Don't skip jobs when earlier job failed
Ben Golding
edited a comment on JENKINS-15992
Dont skip jobs when earlier job failed
I tried it (using 0.8), wrapping 3 jobs known to be unstable with ignore(ABORTED)
It does not seem to work as expected, at least inside of parallel block:
the jobs after the parallel block do not seem to be executed.
Please advise.
Console output
Started by timer
Building on master in workspace /localdev/bl/jenkins/jobs/nightly_start/workspace
ignore(ABORTED) {
Trigger job rsync_binmod_de02winterm20
rsync_binmod_de02winterm20 #80 completed : ABORTED
// ABORTED ignored
}
ignore(ABORTED) {
Trigger job rsync_binmod_de02winterm31
rsync_binmod_de02winterm31 #78 completed : ABORTED
// ABORTED ignored
}
ignore(ABORTED) {
Trigger job rsync_binmod_de02winterm37
rsync_binmod_de02winterm37 #5 completed : ABORTED
// ABORTED ignored
}
parallel {
Trigger job rsync_SDR_stormcs241
Trigger job rsync_SDR_de02winterm20
Trigger job checkbinmod
Trigger job downmerge_f2011.06
Trigger job rsync_SDR_de02winterm37
Trigger job rsync_SDR_de02winterm31
Trigger job rsync_SDR_stormcs240
Trigger job downmerge_g2012.06
Trigger job removebinmod
Trigger job downmerge_main
Trigger job rsync_binmod_stormcs240
Trigger job rsync_binmod_stormcs241
downmerge_f2011.06 @2590110 completed
rsync_binmod_stormcs240 #82 completed
checkbinmod #79 completed
removebinmod #77 completed
downmerge_g2012.06 @2590095 completed
downmerge_main @2590164 completed
rsync_binmod_stormcs241 #79 completed
rsync_SDR_de02winterm20 #84 completed
rsync_SDR_de02winterm31 #81 completed
rsync_SDR_de02winterm37 #6 completed
rsync_SDR_stormcs240 #82 completed
rsync_SDR_stormcs241 #80 completed
}
Sending e-mails to: ...
Finished: FAILURE
DSL
// preparation
parallel(
// local SDR
{ build("rsync_SDR_de02winterm20"); },
{ build("rsync_SDR_de02winterm31"); },
{ build("rsync_SDR_de02winterm37"); },
{ build("rsync_SDR_stormcs240"); },
{ build("rsync_SDR_stormcs241"); },
// local binary modules
ignore (ABORTED) { build("rsync_binmod_de02winterm20"); },
ignore (ABORTED) { build("rsync_binmod_de02winterm31"); },
ignore (ABORTED) { build("rsync_binmod_de02winterm37"); },
{ build("rsync_binmod_stormcs240"); },
{ build("rsync_binmod_stormcs241"); },
// update team branches
{ build("downmerge_f2011.06"); },
{ build("downmerge_g2012.06"); },
{ build("downmerge_main"); },
// clean up binary modules from older builds
{ build("removebinmod"); },
// sanity checks on nightly build output
{ build("checkbinmod"); },
);
guard {
// CDE builds / unit tests
parallel(
...
);
} rescue {
// save and datestamp today's build
build("archivebinmod");
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15992) Don't skip jobs when earlier job failed
Ben Golding
commented on JENKINS-15992
Dont skip jobs when earlier job failed
I tried it (using 0.8), wrapping 3 jobs known to be unstable with
ignore(ABORTED)
It does not seem to work as expected, at least inside of parallel block:
the jobs after the parallel block do not seem to be executed.
Please advise.
Console output
Started by timer
Building on master in workspace /localdev/bl/jenkins/jobs/nightly_start/workspace
ignore(ABORTED) {
Trigger job rsync_binmod_de02winterm20
rsync_binmod_de02winterm20 #80 completed : ABORTED
// ABORTED ignored
}
ignore(ABORTED) {
Trigger job rsync_binmod_de02winterm31
rsync_binmod_de02winterm31 #78 completed : ABORTED
// ABORTED ignored
}
ignore(ABORTED) {
Trigger job rsync_binmod_de02winterm37
rsync_binmod_de02winterm37 #5 completed : ABORTED
// ABORTED ignored
}
parallel {
Trigger job rsync_SDR_stormcs241
Trigger job rsync_SDR_de02winterm20
Trigger job checkbinmod
Trigger job downmerge_f2011.06
Trigger job rsync_SDR_de02winterm37
Trigger job rsync_SDR_de02winterm31
Trigger job rsync_SDR_stormcs240
Trigger job downmerge_g2012.06
Trigger job removebinmod
Trigger job downmerge_main
Trigger job rsync_binmod_stormcs240
Trigger job rsync_binmod_stormcs241
downmerge_f2011.06 @2590110 completed
rsync_binmod_stormcs240 #82 completed
checkbinmod #79 completed
removebinmod #77 completed
downmerge_g2012.06 @2590095 completed
downmerge_main @2590164 completed
rsync_binmod_stormcs241 #79 completed
rsync_SDR_de02winterm20 #84 completed
rsync_SDR_de02winterm31 #81 completed
rsync_SDR_de02winterm37 #6 completed
rsync_SDR_stormcs240 #82 completed
rsync_SDR_stormcs241 #80 completed
}
Sending e-mails to: ...
Finished: FAILURE
DSL
// preparation
parallel(
// local SDR
{ build("rsync_SDR_de02winterm20"); },
{ build("rsync_SDR_de02winterm31"); },
{ build("rsync_SDR_de02winterm37"); },
{ build("rsync_SDR_stormcs240"); },
{ build("rsync_SDR_stormcs241"); },
// local binary modules
ignore (ABORTED) { build("rsync_binmod_de02winterm20"); },
ignore (ABORTED) { build("rsync_binmod_de02winterm31"); },
ignore (ABORTED) { build("rsync_binmod_de02winterm37"); },
{ build("rsync_binmod_stormcs240"); },
{ build("rsync_binmod_stormcs241"); },
// update team branches
{ build("downmerge_f2011.06"); },
{ build("downmerge_g2012.06"); },
{ build("downmerge_main"); },
// clean up binary modules from older builds
{ build("removebinmod"); },
// sanity checks on nightly build output
{ build("checkbinmod"); },
);
guard {
// CDE builds / unit tests
parallel(
...
);
} rescue {
// save and datestamp today's build
build("archivebinmod");
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-6744) Need Good Run parameter
Geoff Cummings assigned JENKINS-6744 to Geoff Cummings Need Good Run parameter Change By: Geoff Cummings (14/Mar/13 2:39 PM) Assignee: huybrechts GeoffCummings This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17132) Show a warning when the eclipse parser is selected
jhurne updated JENKINS-17132 Show a warning when the eclipse parser is selected Change By: jhurne (14/Mar/13 2:54 PM) Summary: Warningspluginstuckparsingtheconsolewith Show a regexandblocksotherbuildsusing warningwhen the sameplugintocomplete eclipseparserisselected Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17132) Show a warning when the eclipse parser is selected
jhurne edited a comment on JENKINS-17132 Show a warning when the eclipse parser is selected We've been running with the javac parser for about a week now and we haven't seen the same issue come up again. So the problem is probably that the eclipse parser is very inefficient. It would be nice, however if a warning could be displayed when configuring the plugin if the eclipse parser is selected (to help others avoid this mistake). It seems reasonable to assume (but correct me if I am wrong) that most Jenkins users are compiling with javac and not eclipse. Maybe a warning like the following could be displayed: Warning: you have selected the eclipse parser which is known to have performance problems. You probably want to use the javac parser instead (unless you really want to parse output from the eclipse compiler output). Changing the bug name to reflect this change in focus. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Timothy Appnel commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ The org.jenkinsci.plugins.gitclient.Git.useCLI=true and other remedies mentioned here didn't work with git plugin 1.3.0 and git client 1.0.4 for me. I'm running a system with remote slaves and it seems that switch is getting lost that the buggy code runs. I dropped back to 1.2.0 and 1.03 and all is back to normal. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16868) Icons are not displayed with a reverse proxy
rsandell commented on JENKINS-16868 Icons are not displayed with a reverse proxy Commit: e4f7fb996be928c5fdb236a78e67e4350fcd512f This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16868) Icons are not displayed with a reverse proxy
rsandell resolved JENKINS-16868 as Fixed Icons are not displayed with a reverse proxy Fixed in version 1.4.1 Change By: rsandell (14/Mar/13 4:12 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/groups/opt_out.
[JIRA] (JENKINS-17195) InvalidTagNameException with version 1.0.4 of git client
SCM/JIRA link daemon commented on JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client Code changed in jenkins User: Nicolas De Loof Path: src/main/java/hudson/plugins/git/GitTagAction.java http://jenkins-ci.org/commit/git-plugin/b0a6db04e3afa05ec054757e076090e51be91755 Log: FIXED JENKINS-17195 avoid whitespace in tag name (enforced by JGit) Compare: https://github.com/jenkinsci/git-plugin/compare/8fb5de484064...b0a6db04e3af You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17195) InvalidTagNameException with version 1.0.4 of git client
SCM/JIRA link daemon resolved JENKINS-17195 as Fixed InvalidTagNameException with version 1.0.4 of git client Change By: SCM/JIRA link daemon (14/Mar/13 4:49 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/groups/opt_out.
[JIRA] (JENKINS-17216) Triggering on files not working
ickersep created JENKINS-17216 Triggering on files not working Issue Type: Bug Assignee: rsandell Components: gerrit-trigger Created: 14/Mar/13 5:00 PM Description: I'd like to trigger a build when any file under Build/Agent/ changes. For that I have the setting for File: Path=Build/Agent/* in the gerrit-plugin section of the job config (in addition to the project and several branches). In the git section I have Included Regions: Build/Agent/*. I would expect that it triggers a build only when a file under Build/Agent/ changes. Instead it triggers a build on any change. In case it matters: it's a multi-configuration project. Environment: gerrit-trigger 2.9.0, Gerrit 2.5.2 Project: Jenkins Priority: Major Reporter: ickersep This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17127) Pass DISPLAY as environment variable to Maven builds
Marc Günther reopened JENKINS-17127 Pass DISPLAY as environment variable to Maven builds Unfortunately, that's not entirely true. When a DISPLAY variable already exists in the environment of the slave, the plugin will overwrite it with the correct value in a "Execute shell" build step, but it will NOT overwrite it in a "Invoke Maven" build stop. I verified that the xvfb plugin actually changes the DISPLAY entry in the EnvVars map, but it seems the Maven build step changes it back later. Although looking at the source code, I can not find where it does that. I'm not sure if this really is a bug with this plugin, or with Jenkins Maven build step, as the plugin seems to do the right thing. Change By: Marc Günther (14/Mar/13 5:07 PM) Resolution: CannotReproduce 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/groups/opt_out.
[JIRA] (JENKINS-3265) Reload Configuration from Disk (or POSTing config.xml) loses info on running builds
SCM/JIRA link daemon commented on JENKINS-3265 Reload Configuration from Disk (or POSTing config.xml) loses info on running builds Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/src/main/java/hudson/model/AbstractProject.java core/src/main/java/jenkins/model/Jenkins.java http://jenkins-ci.org/commit/jenkins/25084f528208a5ab8e0f1ebd9ae80527bf0099d1 Log: FIXED JENKINS-3265 Made the in-flight build survive the reload from the disk. You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-3265) Reload Configuration from Disk (or POSTing config.xml) loses info on running builds
SCM/JIRA link daemon resolved JENKINS-3265 as Fixed Reload Configuration from Disk (or POSTing config.xml) loses info on running builds Change By: SCM/JIRA link daemon (14/Mar/13 5:10 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/groups/opt_out.
[JIRA] (JENKINS-15362) Regexp for file in trigger pattern
ickersep resolved JENKINS-15362 as Fixed Regexp for file in trigger pattern This got changed on the wiki page to f~.*\.txt in December. Change By: ickersep (14/Mar/13 5:14 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/groups/opt_out.
[JIRA] (JENKINS-16723) NPE when performing integration.
javydreamercsw commented on JENKINS-16723 NPE when performing integration. I'm getting the same thing. I made it work but you need to go in and manually remove the Merge info on the branch for it to work. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-3265) Reload Configuration from Disk (or POSTing config.xml) loses info on running builds
dogfood commented on JENKINS-3265 Reload Configuration from Disk (or POSTing config.xml) loses info on running builds Integrated in jenkins_main_trunk #2372 FIXED JENKINS-3265 (Revision 25084f528208a5ab8e0f1ebd9ae80527bf0099d1) Result = SUCCESS kohsuke : 25084f528208a5ab8e0f1ebd9ae80527bf0099d1 Files : core/src/main/java/jenkins/model/Jenkins.java changelog.html core/src/main/java/hudson/model/AbstractProject.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17217) Maven job stuck waiting for self
jvoegele created JENKINS-17217 Maven job stuck waiting for self Issue Type: Bug Assignee: Unassigned Attachments: stuck-maven-job.jpg Components: maven, maven2 Created: 14/Mar/13 6:16 PM Description: Recently several of our Jenkins Maven jobs are stuck waiting for themselves to finish executing before they can start executing. What I mean is that a Maven job is in the queue to execute, but never actually does execute because it says that it is waiting for itself to finish, even though it has never started. See for example the attached screenshot, which shows that the job named container-test-framework_trunk_publisher is waiting to run because the "upstream" job container-test-framework_trunk_publisher (self) is in the queue. However, container-test-framework_trunk_publisher is not listed as being upstream of itself in the "Upstream Projects" section, nor is it transitively upstream of itself as verified by clicking through the upstream projects listed. This is a recent behavior change, and the job configuration has not been changed for a long time so I believe it must be a bug in Jenkins or the Maven plugin. Project: Jenkins Priority: Critical Reporter: jvoegele This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17132) Show a warning when multi-line parser is selected
Ulli Hafner updated JENKINS-17132 Show a warning when multi-line parser is selected Change By: Ulli Hafner (14/Mar/13 7:14 PM) Summary: Showawarningwhen theeclipse multi-line parserisselected This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17132) Show a warning when multi-line parser is selected
Ulli Hafner commented on JENKINS-17132 Show a warning when multi-line parser is selected That might be a good idea. I made this issue more general as the doxygen parser also suffers from this behavior. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17217) Maven job stuck waiting for self
jvoegele commented on JENKINS-17217 Maven job stuck waiting for self After some further debugging, this problem appears to have been caused by the dependency-queue plugin, which I've now uninstalled and builds have gone back to normal. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17218) Environment variables broken in git 1.3 plug-in
lemmster
created JENKINS-17218
Environment variables broken in git 1.3 plug-in
Issue Type:
Bug
Affects Versions:
current
Assignee:
Nicolas De Loof
Components:
git
Created:
14/Mar/13 7:55 PM
Description:
With 1.3.0, the git plug-in has stopped to support Repository URLs containing an environment variable. E.g. file:///${JENKINS_HOME}/git/org.eclipse.ecf.git
Project:
Jenkins
Priority:
Major
Reporter:
lemmster
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Tomas Hellberg commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ I downgraded to 1.2.0/1.03 and now I get com.thoughtworks.xstream.mapper.CannotResolveClassException: hudson.plugins.git.GitSCM Any ideas? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
cray fellow commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ Thomas, hmmm, maybe try to find a way to propagate the useCLI to the slaves. Otherwise, it may just be a case where that combination of Git plugin and Git client plugin doesn't work so you could try another after studying the change log for both. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Tomas Hellberg commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ ... and Git is no longer a valid SCM option. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Tomas Hellberg commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ I managed now to get it working with 1.2.0/1.03. I believe that the problem was caused by a file git.hpi.disabled. I don't know why the plugin got disabled, but I'm up and running again now. Phew... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
cray fellow commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ good to hear! As for the current versions, I'm personally not in favor of these plugins moving toward reliance on JGit. I prefer having an identical environment at the command line to make sure stuff is all working OK when things go awry. Good thing we have an alternative with this useCLI property! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13669) NPE in hudson.plugins.mercurial.MercurialSCM.compareRemoteRevisionWith
Jesse Glick assigned JENKINS-13669 to Willem Verstraeten NPE in hudson.plugins.mercurial.MercurialSCM.compareRemoteRevisionWith Change By: Jesse Glick (14/Mar/13 9:11 PM) Assignee: JesseGlick WillemVerstraeten This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13669) NPE in hudson.plugins.mercurial.MercurialSCM.compareRemoteRevisionWith
Jesse Glick
commented on JENKINS-13669
NPE in hudson.plugins.mercurial.MercurialSCM.compareRemoteRevisionWith
Code in question introduced in:
commit bd53013835c998e2b9bc81d8de8bd7581f7d0e8a
Author: Willem Verstraeten willem.verstrae...@gmail.com
Date: Thu Jan 5 18:49:27 2012 +0100
Implement requiresWorkspaceForPolling
When using caching, all poll operations can be performed on the central cache, so no workspace is necessary
Indeed it is legitimate for possiblyCachedRepo to be null sometimes.
My first inclination would be to then skip the next two lines and continue with workspace-based polling:
if (possiblyCachedRepo != null) {
FilePath repositoryCache = new FilePath(new File(possiblyCachedRepo.getRepoLocation()));
return compare(launcher, listener, baseline, output, Hudson.getInstance(), repositoryCache);
}
I am not sure however what Jenkins will do if you first claimed you supported workspaceless polling but then when asked to poll in fact demand a workspace! The Javadoc for SCM is unclear on this point. Worth trying I guess.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13669) NPE in hudson.plugins.mercurial.MercurialSCM.compareRemoteRevisionWith
SCM/JIRA link daemon commented on JENKINS-13669 NPE in hudson.plugins.mercurial.MercurialSCM.compareRemoteRevisionWith Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/plugins/mercurial/MercurialSCM.java http://jenkins-ci.org/commit/mercurial-plugin/8f3d32c85266e5bb34fc4337fb7299e59738061a Log: FIXED JENKINS-13669 NPE when possiblyCachedRepo == null. You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13669) NPE in hudson.plugins.mercurial.MercurialSCM.compareRemoteRevisionWith
SCM/JIRA link daemon resolved JENKINS-13669 as Fixed NPE in hudson.plugins.mercurial.MercurialSCM.compareRemoteRevisionWith Change By: SCM/JIRA link daemon (14/Mar/13 9:18 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/groups/opt_out.
[JIRA] (JENKINS-17219) HTTPS URLs to Git repositories fail with 1.3.0
Kevin Fleming created JENKINS-17219 HTTPS URLs to Git repositories fail with 1.3.0 Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 14/Mar/13 9:40 PM Description: After upgrading to 'Jenkins Git Plugin' version 1.3.0, my jobs that specify an HTTPS URL to GitHub fail to clone the repository; changing the URL to the Git protocol solves the issue. The error produced with an HTTPS URL is this: git version 1.7.9.5 ERROR: Problem fetching from origin / origin - could be unavailable. Continuing anyway hudson.plugins.git.GitException: org.eclipse.jgit.api.errors.InvalidRemoteException: Invalid remote: origin at org.jenkinsci.plugins.gitclient.JGitAPIImpl.fetch(JGitAPIImpl.java:212) at hudson.plugins.git.GitAPI.fetch(GitAPI.java:230) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:793) at hudson.plugins.git.GitSCM.access$000(GitSCM.java:57) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1018) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:942) at hudson.FilePath.act(FilePath.java:865) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:942) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1101) at hudson.model.AbstractProject.checkout(AbstractProject.java:1353) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:683) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:588) at hudson.model.Run.execute(Run.java:1567) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: org.eclipse.jgit.api.errors.InvalidRemoteException: Invalid remote: origin at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:134) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.fetch(JGitAPIImpl.java:208) ... 17 more Caused by: org.eclipse.jgit.errors.NoRemoteRepositoryException: https://github.com/bloomberg/ci-slave-recipes: https://github.com/bloomberg/ci-slave-recipes/info/refs?service=git-upload-pack not found at org.eclipse.jgit.transport.TransportHttp.connect(TransportHttp.java:465) at org.eclipse.jgit.transport.TransportHttp.openFetch(TransportHttp.java:305) at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:136) at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:122) at org.eclipse.jgit.transport.Transport.fetch(Transport.java:1104) at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:128) ... 18 more ERROR: Could not fetch from any repository FATAL: Could not fetch from any repository hudson.plugins.git.GitException: Could not fetch from any repository at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1023) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:942) at hudson.FilePath.act(FilePath.java:865) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:942) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1101) at hudson.model.AbstractProject.checkout(AbstractProject.java:1353) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:683) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:588) at hudson.model.Run.execute(Run.java:1567) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Project: Jenkins Priority: Major Reporter: Kevin Fleming
[JIRA] (JENKINS-17211) HTTP authentication is not possible with JGit implementation of git-client plugin
Brant Bobby commented on JENKINS-17211 HTTP authentication is not possible with JGit implementation of git-client plugin For people who run Jenkins slaves on Windows as a system service, modify jenkins-slave.xml in the slave's root directory and add the flag to the arguments tag. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
Nicolas Berniolles commented on JENKINS-17186 Linux: if there is a recursive directory within the git repo youre building, the initial checkout will fail badly Hi, I have the same issue on my building machine Ubuntu-10.04. This bug prevent me to build several projects. Where can I find the plug in the version 1.0.3 in order to use the workaround? Thanks in advance This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17220) Add Maven 3.0.5 to the auto installer.
twolfart created JENKINS-17220 Add Maven 3.0.5 to the auto installer. Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: maven Created: 14/Mar/13 10:37 PM Description: http://jenkins.mirror.isppower.de/updates/updates/hudson.tasks.Maven.MavenInstaller.json doesn't list Maven 3.0.5. Please add Maven 3.0.5 to the auto installer files for hudson.tasks.Maven.MavenInstaller. Project: Jenkins Priority: Major Reporter: twolfart This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17221) You must use POST method to trigger builds warning message pops up preventing remote triggering of builds with parameters using wget URL http://server/job/myjob/buildWithParam
Leo Leung created JENKINS-17221 You must use POST method to trigger builds warning message pops up preventing remote triggering of builds with parameters using wget URL http://server/job/myjob/buildWithParameters?PARAMETER=Value Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: parameters Created: 14/Mar/13 11:45 PM Description: When trying to trigger builds remotely using the URL http://server/job/myjob/buildWithParameters?PARAMETER=Value, the following message comes up. You must use POST method to trigger builds. (From scripts you may instead pass a per-project authentication token, or authenticate with your API token.) If you see this page, it may be because a plugin offered a GET link; file a bug report for that plugin. There is a "Proceed" button which needs to be clicked on manually which causes (post-commit) remote triggering of builds via wget to fail. Environment: Any OS, SVN Project: Jenkins Labels: trigger remote parameterized build-on-commit Priority: Blocker Reporter: Leo Leung This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
Nicolas Berniolles commented on JENKINS-17186 Linux: if there is a recursive directory within the git repo youre building, the initial checkout will fail badly That's true. I was as well able to downgrade through Jenkins the git plugin, not this other one. Thanks for the tip This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
Martin Falatic commented on JENKINS-17186 Linux: if there is a recursive directory within the git repo youre building, the initial checkout will fail badly Note that I was able to downgrade the git plugin directly in the UI, but I had to actually do the git-client one manually. They're all available at: http://updates.jenkins-ci.org/download/plugins/ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17221) You must use POST method to trigger builds warning message pops up preventing remote triggering of builds with parameters using wget URL http://server/job/myjob/buildWithParam
Leo Leung
updated JENKINS-17221
You must use POST method to trigger builds warning message pops up preventing remote triggering of builds with parameters using wget URL http://server/job/myjob/buildWithParameters?PARAMETER=Value
Change By:
Leo Leung
(15/Mar/13 1:23 AM)
Description:
WhentryingtotriggerbuildsremotelyusingtheURLhttp://server/job/myjob/buildWithParameters?PARAMETER=Value,thefollowingmessagecomesup.{noformat}YoumustusePOSTmethodtotriggerbuilds.(Fromscriptsyoumayinsteadpassaper-projectauthenticationtoken,orauthenticatewithyourAPItoken.)Ifyouseethispage,itmaybebecauseapluginofferedaGETlink;fileabugreportforthatplugin.{noformat}ThereisaProceedbuttonwhichneedstobeclickedonmanuallywhichcauses(post-commit)remotetriggeringofbuildsviawgettofail.
Thisproblemdidnotexistin1.501,onltystartedtonoticethisissueinversions1.503and1.505.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17222) Add ability to specify more than one location when using the svn method
Chris Dore created JENKINS-17222 Add ability to specify more than one location when using the svn method Issue Type: Improvement Assignee: Justin Ryan Components: job-dsl-plugin Created: 15/Mar/13 2:50 AM Description: The SVN plugin supports multiple locations via the UI. The resulting XML contains multiple hudson.scm.SubversionSCM_-ModuleLocation nodes within the locations node. For example: ... locations hudson.scm.SubversionSCM_-ModuleLocation remotehttps://some.repo.com/proj1/trunk/remote localproject1/local /hudson.scm.SubversionSCM_-ModuleLocation hudson.scm.SubversionSCM_-ModuleLocation remotehttps://some.repo.com/proj2/branches/qwe/remote localproject2_qwe/local /hudson.scm.SubversionSCM_-ModuleLocation /locations ... The job-dsl-plugin could/should also support this. Project: Jenkins Priority: Minor Reporter: Chris Dore This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17222) Add ability to specify more than one location when using the svn method
Chris Dore commented on JENKINS-17222 Add ability to specify more than one location when using the svn method I'm willing to take a shot at adding this functionality. The solution I currently have in my head is to create another overload of the svn method which takes a list of maps. Each map containing the remote and local strings. So you could call it something like: scm([[svnUrl:'https://some.repo.com/proj1/trunk', localDir:'project1'], [svnUrl:'https://some.repo.com/proj2/branches/qwe', localDir:'project2_qwe']]) or maybe just a list of lists: scm([['https://some.repo.com/proj1/trunk', 'project1'], ['https://some.repo.com/proj2/branches/qwe', 'project2_qwe']]) Thoughts? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17222) Add ability to specify more than one location when using the svn method
Chris Dore edited a comment on JENKINS-17222 Add ability to specify more than one location when using the svn method I'm willing to take a shot at adding this functionality. The solution I currently have in my head is to create another overload of the svn method which takes a list of maps. Each map containing the remote and local strings. So you could call it something like: scm([[svnUrl:'https://some.repo.com/proj1/trunk', localDir:'project1'], [svnUrl:'https://some.repo.com/proj2/branches/qwe', localDir:'project2_qwe']]) or maybe just a list of lists: scm([['https://some.repo.com/proj1/trunk', 'project1'], ['https://some.repo.com/proj2/branches/qwe', 'project2_qwe']]) Thoughts on this interface? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17222) Add ability to specify more than one location when using the svn method
Chris Dore edited a comment on JENKINS-17222 Add ability to specify more than one location when using the svn method I'm willing to take a shot at adding this functionality. The solution I currently have in my head is to create another overload of the svn method which takes a list of maps. Each map containing the remote and local strings. So you could call it something like: svn([[svnUrl:'https://some.repo.com/proj1/trunk', localDir:'project1'], [svnUrl:'https://some.repo.com/proj2/branches/qwe', localDir:'project2_qwe']]) or maybe just a list of lists: svn([['https://some.repo.com/proj1/trunk', 'project1'], ['https://some.repo.com/proj2/branches/qwe', 'project2_qwe']]) Thoughts on this interface? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17222) Add ability to specify more than one location when using the svn method
Chris Dore commented on JENKINS-17222 Add ability to specify more than one location when using the svn method I already don't like the above idea at all. I don't think it's going to work out too well in groovy (ya, I'm new to groovy). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
Martin Falatic commented on JENKINS-17186 Linux: if there is a recursive directory within the git repo youre building, the initial checkout will fail badly When you say "the same" you mean you also have recursive symlinks? Also, did the plugin downgrade successfully resolve the issue for you? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17222) Add ability to specify more than one location when using the svn method
Justin Ryan
commented on JENKINS-17222
Add ability to specify more than one location when using the svn method
Copying from email:
Ideally we'd create a inner context to define concepts like this, like we do for the ant dsl method. The problem is that svn was written before we knew how to do that, so we just took a "configure" object. It's not really possible to make a change to the signature to take a context instead of a configure closure, without making it a breaking change. What do people feel about this? Should we "fix" the p4, svn and git commands?
In some respects, the resulting XML is pretty straightforward, though not completely obvious to someone new. E.g. from the ticket:
svn('https://some.repo.com/proj1/trunk', 'project1') \{
it / locations / 'hudson.scm.SubversionSCM_-ModuleLocation' \{
remote 'https://some.repo.com/proj2/branches/qwe'
local 'project2_qwe'
}
}
Maybe we can just document this (and pretend that the scm commands aren't as ugly as they are)?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17223) Failed build unity3d project with message Building Player from editor scripts requires Unity PRO
Roy Inganta Ginting created JENKINS-17223 Failed build unity3d project with message Building Player from editor scripts requires Unity PRO Issue Type: Bug Assignee: lacostej Attachments: consoleText.txt Components: unity3d-plugin Created: 15/Mar/13 4:30 AM Description: I found this in jenkins log "Building Player from editor scripts requires Unity PRO", but i'm pretty sure we have a valid unity license installed on the machine. Build project with Unity editor and windows command line is no problem. I attached jenkins log. Environment: Windows 7 ultimate service pack 1 64-bit Intel Core i7 RAM 8 GB ALIENWARE Project: Jenkins Priority: Blocker Reporter: Roy Inganta Ginting This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17223) Failed build unity3d project with message Building Player from editor scripts requires Unity PRO
lacostej resolved JENKINS-17223 as Cannot Reproduce Failed build unity3d project with message Building Player from editor scripts requires Unity PRO This message is coming from Unity not from the Jenkins plugin. 1. are you 100% sure you have a Unity PRO license ? 2. is it a trial ? is your license registered ? See http://forum.unity3d.com/threads/42533-Unity-3d-Pro-Trial-Version 3. if you have a registered PRO license and if command line building works, please show me the command line that you use to build on that machine Change By: lacostej (15/Mar/13 5:40 AM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
