[JIRA] [delivery-pipeline] (JENKINS-22211) Parallel stages display distorted
Johan Bloemberg commented on JENKINS-22211 Parallel stages display distorted Hi Patrik, thx, installed it yesterday as soon as it was available. Didn't have to wait long. Looks much better There is still a minor glitch but not as big as the previous one: http://auth-83051f68-ec6c-44e0-afe5-bd8902acff57.cdn.spilcloud.com/10/1395214255_Screen_Shot_2014-03-19_at_08.29.18.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22142) No autocompletion and NullPointerException when using 'Copy Existing Job'
Croesus Kall commented on JENKINS-22142 No autocompletion and NullPointerException when using Copy Existing Job Stopped getting this error - probably as a result of restarting jenkins (even though it had been tried before). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plot] (JENKINS-21493) NullPointerException in Publisher
Alexander Opitz closed JENKINS-21493 as Fixed NullPointerException in Publisher Works after update. Change By: Alexander Opitz (19/Mar/14 9:44 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [unity3d-plugin] (JENKINS-21610) Starting Unity with the flag -force-d3d9-ref doesn't work as intended
lacostej commented on JENKINS-21610 Starting Unity with the flag -force-d3d9-ref doesnt work as intended Hello! A few questions: Is this on a master or a slave? Under which user is jenkins running ? Could you try running the env command from both you CMD and from the execute CMD on the jenkins job ? and post them here (removing sensitive info if needed). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer] (JENKINS-17651) Allow more than 1 line as indicator
SCM/JIRA link daemon commented on JENKINS-17651 Allow more than 1 line as indicator Code changed in jenkins User: Andrew Bayer Path: src/main/java/com/sonyericsson/jenkins/plugins/bfa/model/FailureReader.java src/main/java/com/sonyericsson/jenkins/plugins/bfa/model/MultilineBuildLogFailureReader.java src/main/java/com/sonyericsson/jenkins/plugins/bfa/model/indication/MultilineBuildLogIndication.java src/main/resources/com/sonyericsson/jenkins/plugins/bfa/Messages.properties src/main/resources/com/sonyericsson/jenkins/plugins/bfa/model/indication/MulitlineBuildLogIndication/config.jelly src/main/resources/com/sonyericsson/jenkins/plugins/bfa/model/indication/MulitlineBuildLogIndication/help-pattern.html src/main/resources/com/sonyericsson/jenkins/plugins/bfa/model/indication/MulitlineBuildLogIndication/help-testText.html src/main/resources/com/sonyericsson/jenkins/plugins/bfa/model/indication/MulitlineBuildLogIndication/help-textSource.html src/test/java/com/sonyericsson/jenkins/plugins/bfa/BuildFailureScannerHudsonTest.java src/test/java/com/sonyericsson/jenkins/plugins/bfa/model/FailureReaderTest.java src/test/java/com/sonyericsson/jenkins/plugins/bfa/model/indication/MultilineBuildLogIndicationTest.java http://jenkins-ci.org/commit/build-failure-analyzer-plugin/e39dd0a3bcfc5ddc6d847ef4a9ab6d0f9d85 Log: FIXED JENKINS-17651 Added a new multi-line build log indication This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer] (JENKINS-17651) Allow more than 1 line as indicator
SCM/JIRA link daemon commented on JENKINS-17651 Allow more than 1 line as indicator Code changed in jenkins User: Robert Sandell Path: src/main/java/com/sonyericsson/jenkins/plugins/bfa/model/FailureReader.java src/main/java/com/sonyericsson/jenkins/plugins/bfa/model/MultilineBuildLogFailureReader.java src/main/java/com/sonyericsson/jenkins/plugins/bfa/model/indication/MultilineBuildLogIndication.java src/main/resources/com/sonyericsson/jenkins/plugins/bfa/Messages.properties src/main/resources/com/sonyericsson/jenkins/plugins/bfa/model/indication/MulitlineBuildLogIndication/config.jelly src/main/resources/com/sonyericsson/jenkins/plugins/bfa/model/indication/MulitlineBuildLogIndication/help-pattern.html src/main/resources/com/sonyericsson/jenkins/plugins/bfa/model/indication/MulitlineBuildLogIndication/help-testText.html src/main/resources/com/sonyericsson/jenkins/plugins/bfa/model/indication/MulitlineBuildLogIndication/help-textSource.html src/test/java/com/sonyericsson/jenkins/plugins/bfa/BuildFailureScannerHudsonTest.java src/test/java/com/sonyericsson/jenkins/plugins/bfa/model/FailureReaderTest.java src/test/java/com/sonyericsson/jenkins/plugins/bfa/model/indication/MultilineBuildLogIndicationTest.java http://jenkins-ci.org/commit/build-failure-analyzer-plugin/2b34a5a0ad4e32b9e19347526a5668a6e0ed7964 Log: Merge pull request #12 from abayer/jenkins-17651-mk2 FIXED JENKINS-17651 Added a new multi-line build log indication Compare: https://github.com/jenkinsci/build-failure-analyzer-plugin/compare/42438a124310...2b34a5a0ad4e This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer] (JENKINS-17651) Allow more than 1 line as indicator
SCM/JIRA link daemon resolved JENKINS-17651 as Fixed Allow more than 1 line as indicator Change By: SCM/JIRA link daemon (19/Mar/14 10:48 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-21137) git fetch does not have support for --progress option in 1.7.x version of git client binary
Marius Gedminas commented on JENKINS-21137 git fetch does not have support for --progress option in 1.7.x version of git client binary I made the mistake of upgrading all my Jenkins plugins yesterday. Now all my 10.04 builds are failing because of this issue. Downgrading the plugin to 1.4.0 doesn't help: now I'm getting FATAL: null java.util.NoSuchElementException at java.util.ArrayList$Itr.next(ArrayList.java:757) at hudson.plugins.git.GitSCM.buildEnvVars(GitSCM.java:1345) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:938) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1079) at hudson.model.AbstractProject.checkout(AbstractProject.java:1414) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:671) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:580) at hudson.model.Run.execute(Run.java:1676) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Is there a solution that doesn't involve adding random PPAs to my Ubuntu 10.04 LTS systems? I don't care for pretty progress bars during clone time, and I'm managing my git credentials just fine with SSH pubkeys. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21217) projects fully loaded on start causing slow startup
Artur Szostak commented on JENKINS-21217 projects fully loaded on start causing slow startup I can confirm the same problem and same kind of stack traces (also with matrix projects) for Jenkins v1.532.2. In my case it takes up to 2 hours to startup. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit] (JENKINS-22236) LinkageError when using Maven 3.1.1 and 3.2.1 with Jenkins 1.555
Julian Payne updated JENKINS-22236 LinkageError when using Maven 3.1.1 and 3.2.1 with Jenkins 1.555 Change By: Julian Payne (19/Mar/14 10:58 AM) Summary: LinkageErrorwhenusingMaven3. 1.1and3. 2.1withJenkins1.555 Description: WhenusingMaven3.2.1withJenkins1.555theunittestsblockwithaLinkageErrorlikethis:Runningasf.artifact.ArtifactHandlerManagerTestTestsrun:1,Failures:0,Errors:0,Skipped:0,Timeelapsed:0.149sec-inasf.artifact.ArtifactHandlerManagerTestExceptioninthreadThread-11java.lang.LinkageError:org.apache.maven.surefire.shade.org.apache.maven.shared.utils.io.IOUtil atjava.lang.ClassLoader.defineClassImpl(NativeMethod) atjava.lang.ClassLoader.defineClass(ClassLoader.java:364) atjava.security.SecureClassLoader.defineClass(SecureClassLoader.java:154) atjava.net.URLClassLoader.defineClass(URLClassLoader.java:777) atjava.net.URLClassLoader.access$400(URLClassLoader.java:96) atjava.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:1225) atjava.security.AccessController.doPrivileged(AccessController.java:366) atjava.net.URLClassLoader.findClass(URLClassLoader.java:660) atorg.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRealm.java:389) atorg.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:42) atorg.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:259) atorg.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235) atorg.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227) atorg.apache.maven.surefire.shade.org.apache.maven.shared.utils.cli.StreamPumper.run(StreamPumper.java:95)OncethiserroroccurstheJenkinsjobblocks.IdonotgettheseerrorsifIruntheunittestsdirectlywithMaven3.2.1IcouldnotfindanythingofinterestintheManageJenkins-Jenkinslog IamalsoseeingthiserroroccasionallywithMaven3.1.1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodelabelparameter] (JENKINS-22226) Triggering a build with a parameterized node label is stuck in Pending - waiting for executors...
ikedam updated JENKINS-6 Triggering a build with a parameterized node label is stuck in Pending - waiting for executors... Sounds not related to parameterized-trigger plugin. Removed parameterized-trigger from components. Change By: ikedam (19/Mar/14 11:10 AM) Component/s: parameterized-trigger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-21137) git fetch does not have support for --progress option in 1.7.x version of git client binary
Marius Gedminas commented on JENKINS-21137 git fetch does not have support for --progress option in 1.7.x version of git client binary Attempting to add JGit to the list of Git installations in Manage Jenkins makes it crash instantly and restart after a couple of minutes. The JGit I just added disappears after the restart. Attempting to add -Dorg.jenkinsci.plugins.gitclient.Git.useCLI=false to the command-line of the slave doesn't do anything (I restarted Jenkins to make sure the slave was restarted with that option): I'm still getting the command-line error from git 1.7.0 for builds on that 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/d/optout.
[JIRA] [build-failure-analyzer] (JENKINS-22135) Optionally record BFA statistics for *all* builds, not just unsuccessful builds
SCM/JIRA link daemon resolved JENKINS-22135 as Fixed Optionally record BFA statistics for *all* builds, not just unsuccessful builds Change By: SCM/JIRA link daemon (19/Mar/14 11:22 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer] (JENKINS-22135) Optionally record BFA statistics for *all* builds, not just unsuccessful builds
SCM/JIRA link daemon commented on JENKINS-22135 Optionally record BFA statistics for *all* builds, not just unsuccessful builds Code changed in jenkins User: Andrew Bayer Path: src/main/java/com/sonyericsson/jenkins/plugins/bfa/BuildFailureScanner.java src/main/java/com/sonyericsson/jenkins/plugins/bfa/db/KnowledgeBase.java src/main/java/com/sonyericsson/jenkins/plugins/bfa/db/LocalFileKnowledgeBase.java src/main/java/com/sonyericsson/jenkins/plugins/bfa/db/MongoDBKnowledgeBase.java src/main/resources/com/sonyericsson/jenkins/plugins/bfa/db/MongoDBKnowledgeBase/config.jelly src/test/java/com/sonyericsson/jenkins/plugins/bfa/CauseManagementHudsonTest.java src/test/java/com/sonyericsson/jenkins/plugins/bfa/db/EmbeddedMongoStatisticsTest.java src/test/java/com/sonyericsson/jenkins/plugins/bfa/db/EmbeddedMongoTest.java src/test/java/com/sonyericsson/jenkins/plugins/bfa/db/MongoDBAuthenticationHudsonTest.java src/test/java/com/sonyericsson/jenkins/plugins/bfa/db/MongoDBKnowledgeBaseTest.java http://jenkins-ci.org/commit/build-failure-analyzer-plugin/f1a599f985dea050a94d413ea051271d4e56b90a Log: FIXED JENKINS-22135 Optionally store successful builds in the statistics as well This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer] (JENKINS-22135) Optionally record BFA statistics for *all* builds, not just unsuccessful builds
SCM/JIRA link daemon commented on JENKINS-22135 Optionally record BFA statistics for *all* builds, not just unsuccessful builds Code changed in jenkins User: Robert Sandell Path: src/main/java/com/sonyericsson/jenkins/plugins/bfa/BuildFailureScanner.java src/main/java/com/sonyericsson/jenkins/plugins/bfa/db/KnowledgeBase.java src/main/java/com/sonyericsson/jenkins/plugins/bfa/db/LocalFileKnowledgeBase.java src/main/java/com/sonyericsson/jenkins/plugins/bfa/db/MongoDBKnowledgeBase.java src/main/resources/com/sonyericsson/jenkins/plugins/bfa/db/MongoDBKnowledgeBase/config.jelly src/test/java/com/sonyericsson/jenkins/plugins/bfa/CauseManagementHudsonTest.java src/test/java/com/sonyericsson/jenkins/plugins/bfa/db/EmbeddedMongoStatisticsTest.java src/test/java/com/sonyericsson/jenkins/plugins/bfa/db/EmbeddedMongoTest.java src/test/java/com/sonyericsson/jenkins/plugins/bfa/db/MongoDBAuthenticationHudsonTest.java src/test/java/com/sonyericsson/jenkins/plugins/bfa/db/MongoDBKnowledgeBaseTest.java http://jenkins-ci.org/commit/build-failure-analyzer-plugin/4b8836542828a9c71ea856160e4b9dc67b3f3fb5 Log: Merge pull request #13 from abayer/jenkins-22135 FIXED JENKINS-22135 Optionally store successful builds in the statistics as well Compare: https://github.com/jenkinsci/build-failure-analyzer-plugin/compare/2b34a5a0ad4e...4b8836542828 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-21137) git fetch does not have support for --progress option in 1.7.x version of git client binary
Marius Gedminas commented on JENKINS-21137 git fetch does not have support for --progress option in 1.7.x version of git client binary Gave up on the alternatives and upgraded Git to 1.9.1 from the PPA. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [postbuildscript] (JENKINS-22230) PostBuildScript updates job configuration every time job runs
Jakub Czaplicki commented on JENKINS-22230 PostBuildScript updates job configuration every time job runs I was able to reproduce the SYSTEM-job-config-update issue having the following versions: Jenkins ver. 1.553 Post-Build Script Plug-in plugin ver.0.10 Metadata plugin ver.1.1.0b The SYSTEM stopped updating job configuration after updating the Post-Build script plugin to ver.0.16: Jenkins ver. 1.553 Post-Build Script Plug-in plugin ver.0.16 Metadata plugin ver.1.1.0b It seems that the issue has been fixed somewhere between version 0.10 and 0.16. Perhaps this change was a fix: https://github.com/jenkinsci/postbuildscript-plugin/commit/b225c1b845bd8b26b153de9fda03dac5c3259b7e ? I am going to resolve this ticket now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [postbuildscript] (JENKINS-22230) PostBuildScript updates job configuration every time job runs
Jakub Czaplicki resolved JENKINS-22230 as Wont Fix PostBuildScript updates job configuration every time job runs Change By: Jakub Czaplicki (19/Mar/14 11:34 AM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [websphere-deployer] (JENKINS-21643) Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment)
schaudhari schaudhari commented on JENKINS-21643 Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment) Hi @kal did this work, as I am also facing the same issue This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [websphere-deployer] (JENKINS-21871) Generated EAR fails to install (issues ADMC0046W)
schaudhari schaudhari commented on JENKINS-21871 Generated EAR fails to install (issues ADMC0046W) Hi I am also facing same issues while deploying EAR file? any suggestions? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-12729) Add configurable username/password for submodules that require authentication
Trevor Baker commented on JENKINS-12729 Add configurable username/password for submodules that require authentication We have submodules with different ssh deploy keys that the top level repo. We get around the limitation by specifying the key to use in ssh/config for the submodule "Host" though in-job configuration would be preferable. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ui-changes] (JENKINS-22257) Using Internet Explorer 8 with Jenkins 1.555 there is Oops! - stack trace
Yariv Sheizaf created JENKINS-22257 Using Internet Explorer 8 with Jenkins 1.555 there is Oops! - stack trace Issue Type: Bug Assignee: Unassigned Components: ui-changes Created: 19/Mar/14 1:03 PM Description: The console output in Internet explorer 8 under Jenkins 1.555 fails. Write "Oops" and then jelly problem: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Users/Build/AppData/Local/Temp/jetty-0.0.0.0-8080-jenkins.war--any-/webapp/WEB-INF/lib/jenkins-core-1.555.jar!/hudson/model/Run/console.jelly:42:38: j:when unknown format type at at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:79) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at
[JIRA] [url-change-trigger] (JENKINS-22258) url content not saved across cron inactive times
Trevor Baker created JENKINS-22258 url content not saved across cron inactive times Issue Type: Bug Assignee: dfabulich Components: url-change-trigger Created: 19/Mar/14 1:14 PM Description: I have a url trigger with a text context and default regex of ".*" The cron schedule is "0 08-16 * * 1-5", which is to say business hours during business days. Each morning the trigger runs at 8am to check the content and seems to have forgotten the state from the last invocation at 4pm the previous day. It prints: Inspecting TXT content for URL https://jenkins/job/myjob/lastSuccessfulBuild/buildNumber Polling started on Mar 19, 2014 8:01:19 AM Polling for the job myjob Looking nodes where the poll can be run. Looking for a node to the restricted label master. Restrict on master label. Polling on master. Polling on master. Using Basic Authentication with the user 'user' Invoking the url: https://jenkins/job/myjob/lastSuccessfulBuild/buildNumber Inspecting the content Capturing URL context. Waiting next schedule to check a change. Polling complete. Took 0.66 sec. No changes. This effectively means the earliest the job can be triggered is the second cron trigger of the day. I would expect that the URL Trigger plugin would remember the value from the previous day and calculate changes from that. Jenkins has not been restarted overnight. Environment: url-trigger 0.37 Jenkins 1.554 Tomcat 7 Linux Project: Jenkins Priority: Major Reporter: Trevor Baker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21622) Build creates new workspace@2 (and so on) when option concurrent builds NOT checked
Alex Lorenz updated JENKINS-21622 Build creates new workspace@2 (and so on) when option concurrent builds NOT checked We have the same behavior, and our Jenkins disk volume is regularly out of space now, because several jobs behave like this. Change By: Alex Lorenz (19/Mar/14 1:15 PM) Priority: Minor Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21622) Build creates new workspace@2 (and so on) when option concurrent builds NOT checked
Alex Lorenz updated JENKINS-21622 Build creates new workspace@2 (and so on) when option concurrent builds NOT checked Change By: Alex Lorenz (19/Mar/14 1:24 PM) Environment: WindowsTomcat LinuxStandalone This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21622) Build creates new workspace@2 (and so on) when option concurrent builds NOT checked
Alex Lorenz updated JENKINS-21622 Build creates new workspace@2 (and so on) when option concurrent builds NOT checked Change By: Alex Lorenz (19/Mar/14 1:26 PM) Affects Version/s: current This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [websphere-deployer] (JENKINS-21643) Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment)
Greg Peters commented on JENKINS-21643 Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment) If you point your browser to WebSphere's Admin Console on the server where Jenkins resides, can you view the admin console in the browser? If you can't, you won't be able to deploy. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21622) Build creates new workspace@2 (and so on) when option concurrent builds NOT checked
Alex Lorenz updated JENKINS-21622 Build creates new workspace@2 (and so on) when option concurrent builds NOT checked Change By: Alex Lorenz (19/Mar/14 1:44 PM) Environment: WindowsTomcat LinuxStandalone Priority: Major Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21622) Build creates new workspace@2 (and so on) when option concurrent builds NOT checked
Alex Lorenz commented on JENKINS-21622 Build creates new workspace@2 (and so on) when option concurrent builds NOT checked Resolved for us. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [websphere-deployer] (JENKINS-21643) Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment)
schaudhari schaudhari commented on JENKINS-21643 Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment) Hi Greg, I am able to get to Admin Console from my build machine, after accepting the certificate exception. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21622) Build creates new workspace@2 (and so on) when option concurrent builds NOT checked
Mark Waite commented on JENKINS-21622 Build creates new workspace@2 (and so on) when option concurrent builds NOT checked What was the solution that resolved it for you? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22039) Credentialed git init is failing with a file exists error - reusing same temporary directory for all credentials
Mark Waite updated JENKINS-22039 Credentialed git init is failing with a file exists error - reusing same temporary directory for all credentials Change By: Mark Waite (19/Mar/14 2:19 PM) Summary: Credentialed gitinitisfailingwithafileexistserror -reusingsametemporarydirectoryforallcredentials This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22039) Credentialed git init fails with file exists - reuses same tmp dir for all credentials
Mark Waite updated JENKINS-22039 Credentialed git init fails with file exists - reuses same tmp dir for all credentials Change By: Mark Waite (19/Mar/14 2:20 PM) Summary: Credentialedgitinit isfailing fails with a fileexists error - reusing reuses same temporarydirectory tmpdir forallcredentials This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [websphere-deployer] (JENKINS-21643) Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment)
Greg Peters commented on JENKINS-21643 Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment) Did you import that certificate onto the jenkins server and make it trusted per the instructions? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21622) Build creates new workspace@2 (and so on) when option concurrent builds NOT checked
Alex Lorenz commented on JENKINS-21622 Build creates new workspace@2 (and so on) when option concurrent builds NOT checked Unrelated to this issue: The @ workspaces were from an older Jenkins version after all. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds] (JENKINS-15820) JClouds plugin deadlock
Ryan Smith commented on JENKINS-15820 JClouds plugin deadlock This seems to be a problem with every implementation of hudson.slaves.RetentionStrategy that uses a synchronized check method if that method can terminate a 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/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-22259) Make EC2 instances self shutdown
Kohsuke Kawaguchi created JENKINS-22259 Make EC2 instances self shutdown Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: acceptance-test-harness Created: 19/Mar/14 3:33 PM Description: EC2Provider does instance pooling, which means instances will be left running. Stephen had a great idea that we should make those instances self-terminate after certain inactivity. We can define "activity" in various ways, but for example we could have cron touch a marker file if it finds active SSH sessions, and then have the instance shutdown if the marker file is older than say a few hours. As for how to make instances terminate automatically when they go down, see http://stackoverflow.com/questions/10541363/self-terminating-aws-ec2-instance Project: Jenkins Priority: Major Reporter: Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-user-vars] (JENKINS-22260) Ideas for other variables to support
Frank Merrow
created JENKINS-22260
Ideas for other variables to support
Issue Type:
Improvement
Assignee:
Unassigned
Components:
build-user-vars
Created:
19/Mar/14 3:35 PM
Description:
I saw the announcement of your update today. This seems like a good plugin for two other variables:
1. One I have LONG WANTED is ${MASTER_HOSTNAME} for use with Perforce Client Specs: ${MASTER_HOSTNAME}_{JOB_NAME}. This exists on Windows as ${COMPUTERNAME}, but not on Linux at all and nothing available to both.
2. If you really wanted to go hog wild and move this plugin into the "indispensable" category . . . allow the user to define variables via a Groovy script. Then I could define ANYTHING I want. That though would be a big step forward as you'd need configuration pages and such.
Frank
Project:
Jenkins
Priority:
Major
Reporter:
Frank Merrow
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [gui] (JENKINS-4561) Delete All Disabled Modules Not visible for project users
vdupain commented on JENKINS-4561 Delete All Disabled Modules Not visible for project users same issue with Jenkins 1.532.1 with projects matrix security strategy. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp] (JENKINS-17807) HockeyAppRecorder.getProjectActions throws NullPointerException
SCM/JIRA link daemon commented on JENKINS-17807 HockeyAppRecorder.getProjectActions throws NullPointerException Code changed in jenkins User: Chris Barnes Path: src/main/java/hockeyapp/HockeyappRecorder.java http://jenkins-ci.org/commit/hockeyapp-plugin/742e2015ee79938fa6dcf414d99bcf7080bffbc7 Log: JENKINS-17807 Fix NPE on building with certain other plugins installed Fixes https://issues.jenkins-ci.org/browse/JENKINS-17807 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp] (JENKINS-17807) HockeyAppRecorder.getProjectActions throws NullPointerException
SCM/JIRA link daemon commented on JENKINS-17807 HockeyAppRecorder.getProjectActions throws NullPointerException Code changed in jenkins User: Jerome Lacoste Path: src/main/java/hockeyapp/HockeyappRecorder.java http://jenkins-ci.org/commit/hockeyapp-plugin/62bd18ed3e11203f869f771067da2a3dbb741f5a Log: JENKINS-17807 no need to check for null jobs, just their results This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mailer] (JENKINS-22115) FATAL: hudson/tasks/Mailer$UserProperty
Sarah Cartwright commented on JENKINS-22115 FATAL: hudson/tasks/Mailer$UserProperty We are seeing the same problem, again with Jenkins 1.544, git-plugin 2.0.4, mailer-plugin 1.8 and all plugins up-to-date. This causes builds to fail even after the successful build message has been mailed out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [master-slave] (JENKINS-21875) NullPointerException when trying to mark slave temporarily offline
Mkay kk commented on JENKINS-21875 NullPointerException when trying to mark slave temporarily offline same issue , Jenkins 1.554 Red Hat Enterprise Linux Client release 5.10 (Tikanga) any workaround please? thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp] (JENKINS-17807) HockeyAppRecorder.getProjectActions throws NullPointerException
lacostej resolved JENKINS-17807 as Fixed HockeyAppRecorder.getProjectActions throws NullPointerException Merged Change By: lacostej (19/Mar/14 4:06 PM) Status: Open Resolved Assignee: OliverH lacostej Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-17346) git project building twice every time new change committed
Douglas Paul updated JENKINS-17346 git project building twice every time new change committed I see this issue, too. Each commit triggers 2 builds. I'm on Jenkins 1.533, using Git client plugin 1.4.0. We poll once per minute, our quiet period is 10 seconds, and builds take about 10 minutes. We've configured only 1 executor. Might also be worth mentioning that we have two jobs that poll the same Git repository. (One only builds master, the other only builds branches with a particular naming convention.) Change By: Douglas Paul (19/Mar/14 4:20 PM) Environment: MacOS ,Linux This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [master-slave] (JENKINS-21875) NullPointerException when trying to mark slave temporarily offline
Shane H commented on JENKINS-21875 NullPointerException when trying to mark slave temporarily offline I downgraded to v1.549 on Debian v6.0.5 and the issue went away. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22211) Parallel stages display distorted
Patrik Boström commented on JENKINS-22211 Parallel stages display distorted Thanks for the feedback Johan. What browser are you using? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [svnmerge] (JENKINS-12495) svnmerge fails when running on a Jenkins slave
Indra Gunawan commented on JENKINS-12495 svnmerge fails when running on a Jenkins slave Hugues, The plug-in works! I am greatly appreciative of your fix that came in quickly. Thank you. -Indra This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [websphere-deployer] (JENKINS-21643) Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment)
Greg Peters commented on JENKINS-21643 Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment) If you're using WebSphere ND you would point to the DMGR. Is that where your configuration is pointing? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22211) Parallel stages display distorted
Patrik Boström commented on JENKINS-22211 Parallel stages display distorted Johan, it is because of the longer stage name "OOSS-create-version". We need to handle longer stage name in a better way in the plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22211) Parallel stages display distorted
Johan Bloemberg commented on JENKINS-22211 Parallel stages display distorted Chrome Version 33.0.1750.152, OSX. I just noticed i have two projects with similar workflow, one having this issue the other not. I will try to find the difference and report back here. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-agent] (JENKINS-19817) JCE cannot authenticate the provider BC for Windows 7 Slave
Thomas Carsuzan commented on JENKINS-19817 JCE cannot authenticate the provider BC for Windows 7 Slave Just added a comment on https://issues.jenkins-ci.org/browse/JENKINS-18897 It may help you. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [websphere-deployer] (JENKINS-21643) Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment)
schaudhari schaudhari commented on JENKINS-21643 Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment) Yep Greg, My DMGR is working at SOAP port -- 8880 and in plugin I have configured the same port, you are referring to same configuration right? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22261) Link for Manage Old Data fails with a Content Encoding Error error in the browser.
Artur Szostak created JENKINS-22261 Link for Manage Old Data fails with a Content Encoding Error error in the browser. Issue Type: Bug Assignee: Unassigned Components: core Created: 19/Mar/14 4:44 PM Description: After an upgrade of Jenkins from 1.518 to 1.532.2 and updating all the plugins I get a notification in the management panel that there is data stored in an older format and/or unreadable data. However, when I click on the "Manage Old Data" link to try and resolve this the web browser indicates that the page is not loadable because of a "Content Encoding Error". In the Jenkins logs I find the stack trace indicated below: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/diska/home/jenkins/install/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.532.2.jar!/hudson/diagnosis/OldDataMonitor/manage.jelly:35:59: j:forEach java.util.ConcurrentModificationException at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:79) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] [junit] (JENKINS-17278) getting NPE exception with test trends chart not showing up on jenkins v1.505
evernat commented on JENKINS-17278 getting NPE exception with test trends chart not showing up on jenkins v1.505 Is it reproduced with a recent Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [websphere-deployer] (JENKINS-21643) Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment)
Greg Peters edited a comment on JENKINS-21643 Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment) Let's do this. Can you attach the WAR file you're trying to deploy? or a simple WAR what's not deploying so I can replicate it on my environment? I'm assuming it's a WAR (EAR is fine too). Just attach it to this thread and I'll investigate. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-17290) Category titles in Available Plugins list appear wrong in reverse sort order
evernat edited a comment on JENKINS-17290 Category titles in Available Plugins list appear wrong in reverse sort order reproduced with Jenkins 1.553 with Firefox This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-17290) Category titles in Available Plugins list appear wrong in reverse sort order
evernat commented on JENKINS-17290 Category titles in Available Plugins list appear wrong in reverse sort order reproduced with Jenkins 1.553 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-14902) CreateJob CLI command don't support hierarchical job model
Jesse Glick resolved JENKINS-14902 as Fixed CreateJob CLI command dont support hierarchical job model I presume those commits were intended to fix this issue. Change By: Jesse Glick (19/Mar/14 5:43 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-21575) P4 Plugin doesn't populate RESTapi data with changeSet kind
Rob Petti assigned JENKINS-21575 to Unassigned P4 Plugin doesnt populate RESTapi data with changeSet kind Change By: Rob Petti (19/Mar/14 5:44 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-21698) Perforce plugin should support credentials
Rob Petti assigned JENKINS-21698 to Unassigned Perforce plugin should support credentials Change By: Rob Petti (19/Mar/14 5:44 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-14616) Corrupted plugin updates leads to plugin uninstall and lost job configuration
evernat commented on JENKINS-14616 Corrupted plugin updates leads to plugin uninstall and lost job configuration No news on this critical issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-21091) Config flip-flopping
Rob Petti assigned JENKINS-21091 to Unassigned Config flip-flopping Change By: Rob Petti (19/Mar/14 5:44 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-20927) FATAL: ${NODE_NAME}: Found unresolved macro at '${NODE_NAME}'
Rob Petti
assigned JENKINS-20927 to Unassigned
FATAL: ${NODE_NAME}: Found unresolved macro at ${NODE_NAME}
Change By:
Rob Petti
(19/Mar/14 5:45 PM)
Assignee:
RobPetti
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-13171) Unstable builds due to SEVERE: I/O error in channel Channel to Maven
evernat resolved JENKINS-13171 as Incomplete Unstable builds due to SEVERE: I/O error in channel Channel to Maven No response from the reporter, so resolving as incomplete. Change By: evernat (19/Mar/14 5:45 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-20901) Failed Perforce workspace wipe causes later builds to run with missing files
Rob Petti assigned JENKINS-20901 to Unassigned Failed Perforce workspace wipe causes later builds to run with missing files Change By: Rob Petti (19/Mar/14 5:45 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-21498) Use Upstream Project revision does not seem to be working correctly
Rob Petti assigned JENKINS-21498 to Unassigned Use Upstream Project revision does not seem to be working correctly Change By: Rob Petti (19/Mar/14 5:44 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-20735) P4_LABEL variable not set
Rob Petti assigned JENKINS-20735 to Unassigned P4_LABEL variable not set Change By: Rob Petti (19/Mar/14 5:45 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-20124) Unable to sync to perforce on a MAC
Rob Petti assigned JENKINS-20124 to Unassigned Unable to sync to perforce on a MAC Change By: Rob Petti (19/Mar/14 5:46 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [conditional-buildstep] (JENKINS-19802) Conditional Build Step for Current build status never triggers - or doesn't seem to
Sajajd Rehman commented on JENKINS-19802 Conditional Build Step for Current build status never triggers - or doesnt seem to Ok nor sure it will be relevant here but I spent quite a few hours debugging it and in the end it turned out to be super condition at the bottom saying "Execute script only if build succeeds" was causing issue. This box (Execute script only if build succeeds)is checked by default. unchecked that and now conditional steps work as expected. Though I might be having totally different issue then described here This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-19864) Fail creation of the P4 workspace if client name violates naming policy
Rob Petti assigned JENKINS-19864 to Unassigned Fail creation of the P4 workspace if client name violates naming policy Change By: Rob Petti (19/Mar/14 5:46 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-17439) Perforce Quick Clean Does Not Remove All Build Files; Fails to Halt the Build
Rob Petti assigned JENKINS-17439 to Unassigned Perforce Quick Clean Does Not Remove All Build Files; Fails to Halt the Build Change By: Rob Petti (19/Mar/14 5:47 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-20044) Unable to create work space in the slave machines
Rob Petti assigned JENKINS-20044 to Unassigned Unable to create work space in the slave machines Change By: Rob Petti (19/Mar/14 5:46 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-16972) detects valid p4 output as authentication error
Rob Petti assigned JENKINS-16972 to Unassigned detects valid p4 output as authentication error Change By: Rob Petti (19/Mar/14 5:48 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-17304) When using label to sync, list of changes is incorrect
Rob Petti assigned JENKINS-17304 to Unassigned When using label to sync, list of changes is incorrect Change By: Rob Petti (19/Mar/14 5:48 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-17630) java.lang.OutOfMemoryError: unable to create new native thread
Rob Petti assigned JENKINS-17630 to Unassigned java.lang.OutOfMemoryError: unable to create new native thread Change By: Rob Petti (19/Mar/14 5:47 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-21699) Perforce forgets password
Rob Petti assigned JENKINS-21699 to Unassigned Perforce forgets password Change By: Rob Petti (19/Mar/14 5:43 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-16637) problems exposing P4CLIENT and P4PASSWD to env
Rob Petti assigned JENKINS-16637 to Unassigned problems exposing P4CLIENT and P4PASSWD to env Change By: Rob Petti (19/Mar/14 5:48 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-13646) Automatically Created Clients missing Owner: in clientspec
Rob Petti assigned JENKINS-13646 to Unassigned Automatically Created Clients missing Owner: in clientspec Change By: Rob Petti (19/Mar/14 5:50 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-8529) Perforce plug-in isn't showing changes in polling
Rob Petti assigned JENKINS-8529 to Unassigned Perforce plug-in isnt showing changes in polling Change By: Rob Petti (19/Mar/14 5:52 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-11600) Implement Entry.getDate and Entry.getRevision for email-ext support
Rob Petti assigned JENKINS-11600 to Unassigned Implement Entry.getDate and Entry.getRevision for email-ext support Change By: Rob Petti (19/Mar/14 5:51 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-12806) Perforce Plugin causes config page to throw error if workspace mapping exceeds 2974 bytes
Rob Petti assigned JENKINS-12806 to Unassigned Perforce Plugin causes config page to throw error if workspace mapping exceeds 2974 bytes Change By: Rob Petti (19/Mar/14 5:50 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-9675) Deleting a Job hangs and blocks all other Perforce activities
Rob Petti assigned JENKINS-9675 to Unassigned Deleting a Job hangs and blocks all other Perforce activities Change By: Rob Petti (19/Mar/14 5:51 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-9697) Perforce Plugin running on a Windows 2008R2 slave fails to poll or check out.
Rob Petti assigned JENKINS-9697 to Unassigned Perforce Plugin running on a Windows 2008R2 slave fails to poll or check out. Change By: Rob Petti (19/Mar/14 5:51 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-10606) Support Matrix Builds
Rob Petti assigned JENKINS-10606 to Unassigned Support Matrix Builds Change By: Rob Petti (19/Mar/14 5:51 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-5343) Incorrect client spec generated
Rob Petti assigned JENKINS-5343 to Unassigned Incorrect client spec generated Change By: Rob Petti (19/Mar/14 5:52 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-13529) Currently all workspaces are created with submitunchanged. Workspace SubmitOptions should be configurable
Rob Petti assigned JENKINS-13529 to Unassigned Currently all workspaces are created with submitunchanged. Workspace SubmitOptions should be configurable Change By: Rob Petti (19/Mar/14 5:50 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22211) Parallel stages display distorted
Johan Bloemberg commented on JENKINS-22211 Parallel stages display distorted Yes, the other project has a shorter stage name. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-agent] (JENKINS-18897) ssh-agent slave: 'JCE cannot authenticate the provider BC', because 'Class is on the bootclasspath'
Thomas Carsuzan commented on JENKINS-18897 ssh-agent slave: JCE cannot authenticate the provider BC, because Class is on the bootclasspath I also had the same behaviour. The reason is simple : The bouncycastle jar is not in the slave.jar classpath. I think the solution may be to add the bouncycastle.jar in the slave.jar classpath MANIFEST.MF and always launch the slave.jar with the bouncycastle.jar in the same folder = When the slave is configured with : "Launch slave agents on Unix machines via SSH" : The bouncycastle.jar would be copied at the same time as the slave.jar and in the same folder "Launch slave via execution of command on the Master" : The bouncycastle.jar would be downloaded at http://yourserver:port/jnlpJars/bouncycastle.jar like the slave.jar and would have to be in the same folder I have not look at other slave start methods. While waiting for a good resolution, a simple fix is just to copy the bouncycastle jar into your jkd/jre/lib/ext folder. ex : cp /tmp/jetty-0.0.0.0-8080-jenkins.war-any/webapp/WEB-INF/lib/bcprov-jdk15on-1.47.jar jkd/jre/lib/ext/ I think this is the reason why stephenconnolly did not have any problem (not sure). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-14787) Perforce plugin does not substitute all variables when polling for new changes
Rob Petti assigned JENKINS-14787 to Unassigned Perforce plugin does not substitute all variables when polling for new changes Change By: Rob Petti (19/Mar/14 5:49 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-22140) Cann't get P4PASSWD from environment variable
Rob Petti resolved JENKINS-22140 as Not A Defect Cannt get P4PASSWD from environment variable Change By: Rob Petti (19/Mar/14 5:42 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-5838) Perforce client viewspec was corrupted by hudson
Rob Petti assigned JENKINS-5838 to Unassigned Perforce client viewspec was corrupted by hudson Change By: Rob Petti (19/Mar/14 5:52 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-16512) v1.3.x perforce plugin doesn't work with the latest perforce 2012.2
Rob Petti assigned JENKINS-16512 to Unassigned v1.3.x perforce plugin doesnt work with the latest perforce 2012.2 Change By: Rob Petti (19/Mar/14 5:48 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-19699) No way to set P4HOST (for Assembla hosted repo)
Rob Petti assigned JENKINS-19699 to Unassigned No way to set P4HOST (for Assembla hosted repo) Change By: Rob Petti (19/Mar/14 5:47 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-19794) Prevent password exposure in perforce
Rob Petti assigned JENKINS-19794 to Unassigned Prevent password exposure in perforce Change By: Rob Petti (19/Mar/14 5:46 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21459) Jenkins don't run jobs from queue (there are available executors)
Sarah Cartwright updated JENKINS-21459 Jenkins dont run jobs from queue (there are available executors) Change By: Sarah Cartwright (19/Mar/14 6:14 PM) Environment: windows8x86java1.7.0_25jenkins1.538and1.548 and1.544 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [websphere-deployer] (JENKINS-21643) Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment)
schaudhari schaudhari commented on JENKINS-21643 Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment) Yes.. I have imported the certificates in jenkins server, also my test connections is success but when I deploy EAR file it gives same error as above This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-11024) Some commands don't work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others
Jesse Glick commented on JENKINS-11024 Some commands dont work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others JENKINS-12543 covers the problems with username/password authentication. I could not reproduce any problems in current trunk with SSH authentication. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-12543) CliAuthenticator (username/password) called too late to parse arguments (like job names)
Jesse Glick updated JENKINS-12543 CliAuthenticator (username/password) called too late to parse arguments (like job names) JENKINS-14745 fixed a bug whereby no authentication was available, ever, while parsing CLI arguments such as job names. That fix worked for SSH authentication (i …), which sets a transport authentication, but did not help with a CLIAuthenticator like --username … --password …. Meaning that unless the anonymous user can see your jobs (or computers, etc.), the command cannot be run. This is because CLICommand.main first sets the transport authentication, if any; then parses arguments, including both authenticator arguments like --username and specific command arguments; then asks the authenticator for its authentication, if any (also uses stored authentication from login here); then checks Overall/Read; and finally runs the command. But the parsing of regular command arguments (for e.g. get-job) often needs to be done while authenticated. The situation with CLIRegisterer, used by commands defined implicitly with @CLIMethod (like disable-job), is different, because the MethodBinder list is called after using the authenticator. So SSH authentication worked fine without any special help from JENKINS-14745. Unfortunately this code creates an authenticator but never configures it! So it always falls back to using transport authentication—and thus suffers from identical symptoms as regular CLI commands, though for a completely different reason. Change By: Jesse Glick (19/Mar/14 6:22 PM) Summary: CLIpermissions CliAuthenticator(username/password)calledtoolatetoparsearguments(likejobnames) Labels: clisecurity Priority: Major Critical Component/s: core Component/s: cli This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [websphere-deployer] (JENKINS-21643) Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment)
schaudhari schaudhari updated JENKINS-21643 Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment) This is simple FFDC Browser app Change By: schaudhari schaudhari (19/Mar/14 6:14 PM) Attachment: LV.ear This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
