[JIRA] [copyartifact] (JENKINS-22816) SocketException on copy artifact after upgrad
Andrzej Pasterczyk closed JENKINS-22816 as Duplicate SocketException on copy artifact after upgrad Fix in 1.563 confirmed. Thanks Change By: Andrzej Pasterczyk (13/May/14 7:41 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] [copyartifact] (JENKINS-16987) Path of fingerprinted files not saved by CopyArtifacts
James Ascroft-Leigh commented on JENKINS-16987 Path of fingerprinted files not saved by CopyArtifacts I noticed this too but I actually use this feature. I have carefully configured my jobs so that... All files that are archived are in a folder so they have at least one "/" in their path. All files that are consumed by a downstream project have a unique filename. I then use the presence of a "/" in the fingerprint filename in the build.xml file to distinguish between artifacts generated by a build and artifacts consumed by it. I know it is a horrible hack but it allows me to detect statically when a build needs to be rerun due to an updated upstream artifact. I'd love to hear a better suggestion for how to do this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-22301) Replace list-jobs CLI command with list-items
Oliver Gondža
updated JENKINS-22301
Replace list-jobs CLI command with list-items
Change By:
Oliver Gondža
(13/May/14 7:53 AM)
Description:
Create more flexible and well defined replacement for {{list-jobs}}.- Print full item names so it can be fed to other CLI commands.-
-
Print full display names when {{--show-display-names}} used.
-
- List items directly contained in {{View}}/{{ItemGroup}}.- List all items contained in {{View}}/{{ItemGroup}} (even indirectly) when called with {{--recursive}}.- {{\-\-folder x/y \-\-view z/q}} should list whatever {{$JENKINS/job/x/job/y/view/z/view/q/}} lists. {{\-\-folder}} defaults to Jenkins, when {{\-\-view}} is not provided all folder items are listed.
- Use {{--format}} to display custom item representation.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-22301) Replace list-jobs CLI command with list-items
Oliver Gondža commented on JENKINS-22301 Replace list-jobs CLI command with list-items https://github.com/jenkinsci/jenkins/pull/1164 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-21009) Allow manual trigger
Patrik Boström resolved JENKINS-21009 as Fixed Allow manual trigger Change By: Patrik Boström (13/May/14 8:01 AM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [debian-package-builder] (JENKINS-22868) Debian package automatic upgrade fails for a customized configuration
Al Nikolov edited a comment on JENKINS-22868 Debian package automatic upgrade fails for a customized configuration --- /etc/init.d/jenkins.orig 2014-05-13 11:05:58.564973080 +0300 +++ /etc/init.d/jenkins 2014-05-13 11:13:06.723067939 +0300 @@ -24,6 +24,7 @@ #DAEMON=$JENKINS_SH DAEMON=/usr/bin/daemon DAEMON_ARGS="--name=$NAME --inherit --env=JENKINS_HOME=$JENKINS_HOME --output=$JENKINS_LOG --pidfile=$PIDFILE" +[ -n "$PREFIX" ] && JENKINS_ARGS="$JENKINS_ARGS --prefix=$PREFIX" SU=/bin/su This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [debian-package-builder] (JENKINS-22868) Debian package automatic upgrade fails for a customized configuration
Al Nikolov edited a comment on JENKINS-22868 Debian package automatic upgrade fails for a customized configuration Please apply this diff in order to make the life easier --- /etc/init.d/jenkins.orig 2014-05-13 11:05:58.564973080 +0300 +++ /etc/init.d/jenkins 2014-05-13 11:13:06.723067939 +0300 @@ -24,6 +24,7 @@ #DAEMON=$JENKINS_SH DAEMON=/usr/bin/daemon DAEMON_ARGS="--name=$NAME --inherit --env=JENKINS_HOME=$JENKINS_HOME --output=$JENKINS_LOG --pidfile=$PIDFILE" +[ -n "$PREFIX" ] && JENKINS_ARGS="$JENKINS_ARGS --prefix=$PREFIX" SU=/bin/su This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [debian-package-builder] (JENKINS-22868) Debian package automatic upgrade fails for a customized configuration
Al Nikolov commented on JENKINS-22868 Debian package automatic upgrade fails for a customized configuration Unable to find source-code formatter for language: diff. Available languages are: _javascript_, sql, xhtml, actionscript, none, html, xml, java--- /etc/init.d/jenkins.orig 2014-05-13 11:05:58.564973080 +0300 +++ /etc/init.d/jenkins 2014-05-13 11:13:06.723067939 +0300 @@ -24,6 +24,7 @@ #DAEMON=$JENKINS_SH DAEMON=/usr/bin/daemon DAEMON_ARGS="--name=$NAME --inherit --env=JENKINS_HOME=$JENKINS_HOME --output=$JENKINS_LOG --pidfile=$PIDFILE" +[ -n "$PREFIX" ] && JENKINS_ARGS="$JENKINS_ARGS --prefix=$PREFIX" SU=/bin/su This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-19007) copy artifacts via permalink for promoted builds shows wrong link
Sam Wei commented on JENKINS-19007 copy artifacts via permalink for promoted builds shows wrong link I still face similar issue where the permalink only point to the latest job. I could not promote any older build version based on their artifact which stored in that particular build. @Jesse Glick, it would be nice if some one actually fix this. It still happen on version 1.3.0 copy artifacts This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-22993) Maven plugin version 2.3 freezes the ssh node if it runs with the mvn -T flag.
Thomas Herrlin created JENKINS-22993 Maven plugin version 2.3 freezes the ssh node if it runs with the mvn -T flag. Issue Type: Bug Assignee: Unassigned Attachments: jenkins.jstack.xz, simpleproject.tar.xz, slave.jstack.xz Components: maven Created: 13/May/14 8:50 AM Description: The problem started occurring after upgrading from maven plugin 2.1. The node becomes entirely unresponsive and any other builds or scm pollings also freeze on that node. The jenkins node need to be manually reconnected to clear the fault. If a git SCM poll was active on the node then the jenkins master must be restarted for the polling status page to clear. The problem does not seem to be intermittent and is easy to reproduce for us. Attaching jstacks and a mocked multimodule job that replicates the problem. Using SSH slaves plugin 1.6 and Jenkins LTS 1.554.1. Java 7u51 x86-64. Running on the master node without ssh slave plugin does not cause a freeze. Running without the -T flag does not cause a freeze. Running with maven-plugin 2.1 does not cause a freeze. Have not tested with maven plugin version 2.2. Tested with maven 3.1.1. Maven 3.2.1 with -T flag does not seem supported by the plugin at all. Goals: compile -T 4 MAVEN_OPTS=-Xms128M -Xmx1G -verbose:gc Jenkins is started via ubuntu upstart with the "java -jar jenkins.war" method. It is however manually installed. Jenkins JVM options: -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -Xloggc:/tmp/jenkins-test/loggc.txt -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=10 -XX:GCLogFileSize=10M -Xmx1024m -Xms1024m -XX:SoftRefLRUPolicyMSPerMB=2000 -XX:MaxPermSize=192m -server -Djava.awt.headless=true -Dhudson.master.headless=true -Dhudson.webstart.headless=true -Dorg.jenkinsci.plugins.gitclient.Git.useCLI=true -DJENKINS_HOME=/local/jenkins-test -jar /local/jenkins-test/jenkins.war --javaHome=/opt/local/dev_tools/java/x64/jdk1.7.0_51/jre --prefix=/jenkins --logfile=/local/jenkins-test/jenkins.log --httpListenAddress=127.0.0.1 --httpPort=18080 --httpsListenAddress=127.0.0.1 --httpsPort=-1 --ajp13ListenAddress=127.0.0.1 --ajp13Port=-1 --debug=5 --handlerCountMax=100 --handlerCountMaxIdle=20 Node JVM options: -Xms8m -Xmx128m -Dorg.jenkinsci.plugins.gitclient.Git.useCLI=true -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -Xloggc:/local/jenkins-test-agents/jenkinsadm/loggc.txt -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=10 No out of memory problem indications in -Xloggc or -verbose:gc. I have tried with and without these, no effect: Use private Maven repository: Local to workspace Run headless Disable triggering of downstream projects Disable automatic site documentation artifact archiving Disable automatic artifact archiving The "Build modules in parallel" functionality is not a viable option for us, we require that the build be done within the same job. Tried both with and without the "chrt -b 0" batch scheduler. Normally we start the nodes with the batch scheduler as a prefix. Tried to run nodes both on RHEL 6.2 over lan and Ubuntu 14.04 on localhost. Both are multicore machines. I have renamed some server and usernames for security reasons. Hanging job name: ThomasHerrlin_ticket_3348 Hanging slave node: server030 Jenkins console output: ... Executing Maven: -B -f /ssd/jenkins-test-agents/jenkinsadm/workspace/ThomasHerrlin_ticket_3348/pom.xml -T4 compile [GC 33024K->4405K(125952K), 0.0085580 secs] [GC 37429K->6340K(125952K), 0.0109360 secs] [INFO] Scanning for projects... [INFO] [INFO] Reactor Build Order: [INFO] [INFO] my-app1 [INFO] my-app2 [INFO] my-app3 [INFO] my-app4 [INFO] buildall_test [HUDSON] Collecting dependencies info [HUDSON] Collecting dependencies info[INFO] Building with 4 threads [HUDSON] Collecting dependencies info [HUDSON] Collecting dependencies info At this point it freezes. Environment: Linux RHEL 6.2 and Ubuntu 14.04. x86-6
[JIRA] [build-user-vars] (JENKINS-22974) NPE in BuildUser.makeUserBuildVariables()
Oleg Nenashev commented on JENKINS-22974 NPE in BuildUser.makeUserBuildVariables() https://github.com/jenkinsci/build-user-vars-plugin/pull/4 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22989) Default value for $BROWSER should be htmlunit
Ulli Hafner edited a comment on JENKINS-22989 Default value for $BROWSER should be htmlunit Did you try to start some acceptance tests with htmlunit? I never got this working so I thought this was just an experiment. I always get an UnsupportedOperationException so I thought _javascript_ is not well supported up to now... java.lang.UnsupportedOperationException: alert() at org.openqa.selenium.htmlunit.HtmlUnitDriver$HtmlUnitTargetLocator.alert(HtmlUnitDriver.java:1224) at org.jenkinsci.test.acceptance.SanityChecker.afterClickOn(SanityChecker.java:51) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.openqa.selenium.support.events.EventFiringWebDriver$1.invoke(EventFiringWebDriver.java:78) at com.sun.proxy.$Proxy35.afterClickOn(Unknown Source) at org.openqa.selenium.support.events.EventFiringWebDriver$EventFiringWebElement.click(EventFiringWebDriver.java:345) at org.jenkinsci.test.acceptance.po.CapybaraPortingLayer.clickButton(CapybaraPortingLayer.java:66) at org.jenkinsci.test.acceptance.po.Jenkins.restart(Jenkins.java:99) at org.jenkinsci.test.acceptance.po.PluginManager.installPlugin(PluginManager.java:121) at org.jenkinsci.test.acceptance.junit.WithPlugins$RuleImpl$1.installPlugins(WithPlugins.java:64) at org.jenkinsci.test.acceptance.junit.WithPlugins$RuleImpl$1.evaluate(WithPlugins.java:57) at org.jenkinsci.test.acceptance.junit.JenkinsAcceptanceTestRule$1.evaluate(JenkinsAcceptanceTestRule.java:50) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22989) Default value for $BROWSER should be htmlunit
Ulli Hafner edited a comment on JENKINS-22989 Default value for $BROWSER should be htmlunit Did you try to start some acceptance tests with htmlunit? I never got this working so I thought this was just an experiment. I always get an UnsupportedOperationException so I thought _javascript_ is not well supported in htmlunit up to now... java.lang.UnsupportedOperationException: alert() at org.openqa.selenium.htmlunit.HtmlUnitDriver$HtmlUnitTargetLocator.alert(HtmlUnitDriver.java:1224) at org.jenkinsci.test.acceptance.SanityChecker.afterClickOn(SanityChecker.java:51) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.openqa.selenium.support.events.EventFiringWebDriver$1.invoke(EventFiringWebDriver.java:78) at com.sun.proxy.$Proxy35.afterClickOn(Unknown Source) at org.openqa.selenium.support.events.EventFiringWebDriver$EventFiringWebElement.click(EventFiringWebDriver.java:345) at org.jenkinsci.test.acceptance.po.CapybaraPortingLayer.clickButton(CapybaraPortingLayer.java:66) at org.jenkinsci.test.acceptance.po.Jenkins.restart(Jenkins.java:99) at org.jenkinsci.test.acceptance.po.PluginManager.installPlugin(PluginManager.java:121) at org.jenkinsci.test.acceptance.junit.WithPlugins$RuleImpl$1.installPlugins(WithPlugins.java:64) at org.jenkinsci.test.acceptance.junit.WithPlugins$RuleImpl$1.evaluate(WithPlugins.java:57) at org.jenkinsci.test.acceptance.junit.JenkinsAcceptanceTestRule$1.evaluate(JenkinsAcceptanceTestRule.java:50) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22989) Default value for $BROWSER should be htmlunit
Ulli Hafner commented on JENKINS-22989 Default value for $BROWSER should be htmlunit Did you try to start some test with htmlunit? I never got this working so I thought this was just an experiment. I always get an UnsupportedOperationException so I thought _javascript_ is not well supported up to now... java.lang.UnsupportedOperationException: alert() at org.openqa.selenium.htmlunit.HtmlUnitDriver$HtmlUnitTargetLocator.alert(HtmlUnitDriver.java:1224) at org.jenkinsci.test.acceptance.SanityChecker.afterClickOn(SanityChecker.java:51) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.openqa.selenium.support.events.EventFiringWebDriver$1.invoke(EventFiringWebDriver.java:78) at com.sun.proxy.$Proxy35.afterClickOn(Unknown Source) at org.openqa.selenium.support.events.EventFiringWebDriver$EventFiringWebElement.click(EventFiringWebDriver.java:345) at org.jenkinsci.test.acceptance.po.CapybaraPortingLayer.clickButton(CapybaraPortingLayer.java:66) at org.jenkinsci.test.acceptance.po.Jenkins.restart(Jenkins.java:99) at org.jenkinsci.test.acceptance.po.PluginManager.installPlugin(PluginManager.java:121) at org.jenkinsci.test.acceptance.junit.WithPlugins$RuleImpl$1.installPlugins(WithPlugins.java:64) at org.jenkinsci.test.acceptance.junit.WithPlugins$RuleImpl$1.evaluate(WithPlugins.java:57) at org.jenkinsci.test.acceptance.junit.JenkinsAcceptanceTestRule$1.evaluate(JenkinsAcceptanceTestRule.java:50) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy] (JENKINS-22817) Bug in role strategy plugin
Oleg Nenashev commented on JENKINS-22817 Bug in role strategy plugin User notifications have been restored on Jenkins JIRA. Just a ping message... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22979) Add an option to prevent a slave from becoming the multiconf coordinator
Oleg Nenashev commented on JENKINS-22979 Add an option to prevent a slave from becoming the multiconf coordinator Use https://wiki.jenkins-ci.org/display/JENKINS/Matrix+Tie+Parent+Plugin for Jenkins 1.520 and below See "Advanced" options of the project in Jenkins 1.51 and 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] [core] (JENKINS-22979) Add an option to prevent a slave from becoming the multiconf coordinator
Oleg Nenashev resolved JENKINS-22979 as Not A Defect Add an option to prevent a slave from becoming the multiconf coordinator Change By: Oleg Nenashev (13/May/14 9:12 AM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22979) Add an option to prevent a slave from becoming the multiconf coordinator
Johannes Wienke commented on JENKINS-22979 Add an option to prevent a slave from becoming the multiconf coordinator I think both ideas model the solution the wrong way around. Basically, certain slaves cannot act as the coordinator for any job. So I really wouldn't want to add that restriction to every job on our server. And each time we add or change the slave setup we would have to do this again. Instead I just want to mark certain slaves as being an unusable at all apart from performing specifically designated tasks. As far as I can see, the Exclude Flighweight Task plugin somehow allows to do this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco] (JENKINS-22716) Jacoco: Zero coverage with java8
Risto Oikarinen commented on JENKINS-22716 Jacoco: Zero coverage with java8 Using 1.7 as source/target in maven-compiler-plugin results in "maven update" flipping project compiler & facets to 1.7 as well (Eclipse only). Not very nice if you have 1.8 dependencies... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22979) Add an option to prevent a slave from becoming the multiconf coordinator
Oleg Nenashev commented on JENKINS-22979 Add an option to prevent a slave from becoming the multiconf coordinator I also recommend to consider the following plugin: https://wiki.jenkins-ci.org/display/JENKINS/Job+Restrictions+Plugin It allows to restrict the jobs execution on slaves. Now you can use RegExp to determine multi-configuration jobs, but it is possible to add more specific filters upon the request. Please feel free to create feature requests if required This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22946) Upgrading from 1.544 to 1.562 causes multi platform jobs to abort slaves
Kent Granström updated JENKINS-22946 Upgrading from 1.544 to 1.562 causes multi platform jobs to abort slaves Change By: Kent Granström (13/May/14 9:54 AM) Description: After a Jenkins upgrade from 1.544 to 1.562 all multi-platform jobs started to abort themselves for no apparent reason. We have jobs configured to build on three platforms, Win, Mac and Linux. As soon as one of the platforms are ready all the others aborts themselves. This is an extract of the behaviour from the log:May 8, 2014 2:16:42 PM hudson.model.Run executeINFO: AnApplication/Conf=Dbg,label=mac #1651 main build action completed: SUCCESSMay 8, 2014 2:21:17 PM hudson.model.Run executeINFO: AnApplication/Conf=Rel,label=mac #1651 main build action completed: SUCCESSMay 8, 2014 2:21:36 PM hudson.model.Run executeINFO: AnApplication/Conf=Dbg,label=win #1651 abortedjava.lang.InterruptedExceptionat java.lang.Object.wait(Native Method)at hudson.remoting.Request.call(Request.java:146)at hudson.remoting.Channel.call(Channel.java:739)at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:168)at $Proxy62.join(Unknown Source)at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:951)at hudson.Launcher$ProcStarter.join(Launcher.java:362)at hudson.plugins.xshell.XShellBuilder.perform(XShellBuilder.java:118)at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:745)at hudson.model.Build$BuildExecution.build(Build.java:198)at hudson.model.Build$BuildExecution.doRun(Build.java:159)at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:518)at hudson.model.Run.execute(Run.java:1704)at hudson.matrix.MatrixRun.run(MatrixRun.java:146)at hudson.model.ResourceController.execute(ResourceController.java:88)at hudson.model.Executor.run(Executor.java:231)May 8, 2014 2:21:36 PM hudson.model.Run executeINFO: AnApplication/Conf=Dbg,label=linux #1651 abortedjava.lang.InterruptedExceptionat java.lang.Object.wait(Native Method)at hudson.remoting.Request.call(Request.java:146)at hudson.remoting.Channel.call(Channel.java:739)at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:168)at $Proxy62.join(Unknown Source)at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:951)at hudson.Launcher$ProcStarter.join(Launcher.java:362)at hudson.plugins.xshell.XShellBuilder.perform(XShellBuilder.java:118)at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:745)at hudson.model.Build$BuildExecution.build(Build.java:198)at hudson.model.Build$BuildExecution.doRun(Build.java:159)at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:518)at hudson.model.Run.execute(Run.java:1704) Additional information:FATAL: tried to access method hudson.tasks.test.AggregatedTestResultAction.add(Lhudson/tasks/test/AbstractTestResultAction;)V from class hudson.tasks.test.TestResultAggregatorjava.lang.IllegalAccessError: tried to access method hudson.tasks.test.AggregatedTestResultAction.add(Lhudson/tasks/test/AbstractTestResultAction;)V from class hudson.tasks.test.TestResultAggregator at hudson.tasks.test.TestResultAggregator.endRun(TestResultAggregator.java:57) at hudson.matrix.DefaultMatrixExecutionStrategyImpl.notifyEndBuild(DefaultMatrixExecutionStrategyImpl.java:219) at hudson.matrix.DefaultMatrixExecutionStrategyImpl.run(DefaultMatrixExecutionStrategyImpl.java:162) at hudson.matrix.MatrixBuild$MatrixBuildExecution.doRun(MatrixBuild.java:357) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:518) at hudson.model.Run.execute(Run.java:1704) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:306) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) at hudson.model.OneOffExecutor.run(OneOffExecutor.java:43)
[JIRA] [core] (JENKINS-22914) file transfer from slave to master failed with pipe closed
Oleg Nenashev commented on JENKINS-22914 file transfer from slave to master failed with pipe closed @robsimon Could you answer to the ticket? // Just a ping after the e-mail notifications fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-slaves] (JENKINS-22651) Could not copy slave.jar into ... on slave
Oleg Nenashev updated JENKINS-22651 Could not copy slave.jar into ... on slave Reassigned the issue to ssh-slaves @Yves, please define the plugin's version you use Change By: Oleg Nenashev (13/May/14 10:01 AM) Labels: failure slaves startup Assignee: Kohsuke Kawaguchi Component/s: ssh-slaves Component/s: master-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] [core] (JENKINS-22507) org.jvnet.hudson.reactor.ReactorException in Jenkins 1.556 after click on "monitor maven process" during a Build
Oleg Nenashev updated JENKINS-22507 org.jvnet.hudson.reactor.ReactorException in Jenkins 1.556 after click on "monitor maven process" during a Build The issue may be related to the core Change By: Oleg Nenashev (13/May/14 10:04 AM) Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22786) Jenkins job hangs and can't be killed
Oleg Nenashev commented on JENKINS-22786 Jenkins job hangs and can't be killed ping... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameters] (JENKINS-21841) Grouping of parameters in Jenkins job.
Oleg Nenashev updated JENKINS-21841 Grouping of parameters in Jenkins job. Not a bug Change By: Oleg Nenashev (13/May/14 10:07 AM) Issue Type: Bug New Feature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-21335) Forward slashes in a File Parameter's file location cause parameter download links to break
Oleg Nenashev updated JENKINS-21335 Forward slashes in a File Parameter's file location cause parameter download links to break The File Parameter is located in Jenkins core Change By: Oleg Nenashev (13/May/14 10:09 AM) Component/s: core Component/s: build-with-parameters This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-20477) OutOfMemory Permagen
Oleg Nenashev commented on JENKINS-20477 OutOfMemory Permagen Have you tried to increase the PermGen size? The default value usually is not enough for Jenkins This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco] (JENKINS-22716) Jacoco: Zero coverage with java8
Tamas Kende commented on JENKINS-22716 Jacoco: Zero coverage with java8 I have a java8 project, so I cannot compile with 1.7... any idea how can this happen? the maven-jacoco:report works fine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy] (JENKINS-17171) Token macro expansion not working in Groovy plugin 1.13
Steve Jansen commented on JENKINS-17171 Token macro expansion not working in Groovy plugin 1.13 @Slawomir - I packaged this as a GitHub pull request See https://github.com/jenkinsci/groovy-plugin/pull/14 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22786) Jenkins job hangs and can't be killed
Jake Bennett commented on JENKINS-22786 Jenkins job hangs and can't be killed Apologies, I didn't get the email for your first question for some reason, but I did for the second. I've still only seen the issue once. A week or so ago we restarted the Jenkins server to do some updates, which cleared the hangning job, and I've yet to see the issue again since. If I can reproduce again, I'll investigate if disabling the profiler is an option. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22786) Jenkins job hangs and can't be killed
Oleg Nenashev commented on JENKINS-22786 Jenkins job hangs and can't be killed OK, thanks No need in apologies, because there was an issue with e-mail notifications on Jenkins JIRA (about 1 or 2 weeks). I'd recommend to check other issues you watch. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22786) Jenkins job hangs and can't be killed
Jake Bennett commented on JENKINS-22786 Jenkins job hangs and can't be killed Awesome, thanks. I'll keep this posted with any developments. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco] (JENKINS-22716) Jacoco: Zero coverage with java8
Tamas Kende edited a comment on JENKINS-22716 Jacoco: Zero coverage with java8 I have a java8 project, so I cannot compile with 1.7... any idea where can be the issue? the maven-jacoco:report works fine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-blocker] (JENKINS-22994) Build blocker does not support relative paths when jobs has description set
Ireneusz Makowski created JENKINS-22994 Build blocker does not support relative paths when jobs has description set Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: build-blocker Created: 13/May/14 12:22 PM Description: Build blocker does not support jobs in relative folders when job description is set. For example: RootFolder – SubFolder1 – Job1 (description "Job Description") – SubFolder2 – Job2 I cannot use followin _expression_ in Job2: ../SubFolder1/Job1 Only this works: .Job Description. but this is not solution. Expected result: This works: ../SubFolder1/Job1 When Job1 is building then block Job2 Environment: Windows 2008 R2 64bit Jenkins 1.554.1 Project: Jenkins Priority: Critical Reporter: Ireneusz Makowski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22995) Failure to build docker image
Jesse Glick created JENKINS-22995 Failure to build docker image Issue Type: Bug Assignee: Oliver Gondža Components: acceptance-test-harness Created: 13/May/14 12:28 PM Description: Trying to run BROWSER=htmlunit TYPE=winstone_docker JENKINS_WAR=.../jenkins.war mvn clean test on a test suite produced Uploading context 6.656 kB Uploading context Step 0 : FROM ubuntu ---> 8dbd9e392a96 Step 1 : RUN apt-get update ---> Using cache ---> b9e5fab34737 Step 2 : RUN apt-get install -y openssh-server ---> Using cache ---> 6f0264ad8ca4 Step 3 : RUN mkdir -p /var/run/sshd ---> Using cache ---> 2e32d5188f70 Step 4 : RUN useradd test -d /home/test &&mkdir -p /home/test/.ssh &&chown test /home/test &&echo "test:test" | chpasswd &&echo 'ssh-rsa ... kohsuke@atlas' > /home/test/.ssh/authorized_keys ---> Using cache ---> fa4075b88a64 Step 5 : CMD /usr/sbin/sshd -D -e ---> Using cache ---> b675729dea06 Successfully built b675729dea06 Uploading context 2.56 kB Uploading context Step 0 : FROM jenkins/sshd Pulling repository jenkins/sshd 2014/05/13 08:22:13 HTTP code: 404 Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.007 sec <<< FAILURE! basicTest(com.cloudbees.jenkins.test.acceptance.BackupPluginTest) Time elapsed: 2.926 sec <<< ERROR! java.lang.Error: Failed to build image: 88e9b1c268ea at org.jenkinsci.test.acceptance.docker.Docker.build(Docker.java:97) at org.jenkinsci.test.acceptance.docker.Docker.build(Docker.java:153) at org.jenkinsci.test.acceptance.controller.WinstoneDockerController.startProcess(WinstoneDockerController.java:62) at org.jenkinsci.test.acceptance.controller.LocalController.startNow(LocalController.java:235) at org.jenkinsci.test.acceptance.controller.JenkinsController.start(JenkinsController.java:74) at org.jenkinsci.test.acceptance.FallbackConfig.createController(FallbackConfig.java:151) at ... at org.jenkinsci.test.acceptance.guice.TestLifecycle$1.get(TestLifecycle.java:50) at ... at org.jenkinsci.test.acceptance.junit.JenkinsAcceptanceTestRule$1.evaluate(JenkinsAcceptanceTestRule.java:46) at ... Anyway are you sure you do not want to use http://phusion.github.io/baseimage-docker/ which looks like it would be a proper replacement for SshdContainer/Dockerfile? Environment: a-t-h 1.2; Ubuntu 14.04 x64, lxc-docker-0.11.1, Java 7u51 Project: Jenkins Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [javadoc] (JENKINS-6547) Javadoc only published after successful build
Oleg Nenashev updated JENKINS-6547 Javadoc only published after successful build Reassigned the issue to the "javadoc" component Change By: Oleg Nenashev (13/May/14 12:32 PM) Component/s: javadoc Component/s: other This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22024) Windows "services" shows Jenkins as not running.. but it is.
Oleg Nenashev updated JENKINS-22024 Windows "services" shows Jenkins as not running.. but it is. Change By: Oleg Nenashev (13/May/14 12:41 PM) Labels: service winsw Assignee: Kohsuke Kawaguchi Component/s: windows-slaves This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22525) A Slave disappears every time Jenkins boots up
John Tal commented on JENKINS-22525 A Slave disappears every time Jenkins boots up FYI - Similar error of incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue" occurs on fresh install of Jenkins (v1.5623) when trying to add a newly defined slave. When an existing Jenkins installation is updated to latest (v1.5623) and multiple updates to the main configuration are made with restarts you can end up with all nodes disappearing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22525) A Slave disappears every time Jenkins boots up
John Tal edited a comment on JENKINS-22525 A Slave disappears every time Jenkins boots up FYI - Similar error of incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue" occurs on fresh install of Jenkins (v1.5623) when trying to add a newly defined slave. When an existing Jenkins installation is updated to latest (v1.5623) and multiple updates to the main configuration are made with restarts you can end up with all nodes disappearing. In our case is occurring on RHEL - Linux version 2.6.18-348.6.1.el5 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22525) A Slave disappears every time Jenkins boots up
John Tal edited a comment on JENKINS-22525 A Slave disappears every time Jenkins boots up FYI - Similar error of incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue" occurs on fresh install of Jenkins (v1.5623) when trying to add a newly defined slave. When an existing Jenkins installation is updated to latest (v1.5623) and multiple updates to the main configuration are made with restarts you can end up with all nodes disappearing. In our cases is occurring on RHEL - Linux version 2.6.18-348.6.1.el5 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22525) A Slave disappears every time Jenkins boots up
John Tal edited a comment on JENKINS-22525 A Slave disappears every time Jenkins boots up When an existing Jenkins installation is updated to latest (v1.5623) and multiple updates to the main configuration are made with restarts you can end up with all nodes disappearing. In our case is occurring on RHEL - Linux version 2.6.18-348.6.1.el5 Where in-place upgrades are made, is there a need to clear out directories such as .jenkins/cache or others? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18781) Configurable channel timeout for slaves
Sajajd Rehman commented on JENKINS-18781 Configurable channel timeout for slaves PING any fixers there? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22525) A Slave disappears every time Jenkins boots up
John Tal edited a comment on JENKINS-22525 A Slave disappears every time Jenkins boots up Was this an in place update/upgrade done recently? At least on RHEL with tomcat we have had to remove the old directory under webapps when dropping the new jenkins.war in place. Otherwise we can get these same symptoms (disappearing nodes) and see this same error with slightly different stack trace immediately after a fresh in place upgrade. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22525) A Slave disappears every time Jenkins boots up
John Tal edited a comment on JENKINS-22525 A Slave disappears every time Jenkins boots up Was this an in-place update/upgrade that done recently from a previous version of Jenkins (or even hudson)? At least on RHEL with tomcat we have had to remove the old directory under webapps when dropping the new jenkins.war in place. Otherwise we can get these same symptoms (disappearing nodes) and see this same error with slightly different stack trace immediately after a fresh in-place upgrade. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22525) A Slave disappears every time Jenkins boots up
John Tal edited a comment on JENKINS-22525 A Slave disappears every time Jenkins boots up Was this an in place update/upgrade that done recently from a previous version of Jenkins (or even hudson)? At least on RHEL with tomcat we have had to remove the old directory under webapps when dropping the new jenkins.war in place. Otherwise we can get these same symptoms (disappearing nodes) and see this same error with slightly different stack trace immediately after a fresh in place upgrade. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22525) A Slave disappears every time Jenkins boots up
John Tal edited a comment on JENKINS-22525 A Slave disappears every time Jenkins boots up Was this an in-place update/upgrade that done recently from a previous version of Jenkins (or even hudson)? At least on RHEL with tomcat we have had to remove the old directory under webapps when dropping the new jenkins.war in place. Otherwise we can get these same symptoms (disappearing nodes) and see this same error with slightly different stack trace immediately after a fresh in-place upgrade. Also note there is a ~/.jenkins/cache directory where jar file versions may be. Don't suggest you play in there unless step above has been tried and then, if still failing, after you have stopped jenkins to rename/delete cache contents. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [project-inheritance] (JENKINS-22885) Creation of Inheritance Project throws Exception
michaelhaug commented on JENKINS-22885 Creation of Inheritance Project throws Exception Since Jenkins 1.553 the inheritance plugin is broken. There are two possibilities: Downgrade Jenkins to version 1.552 if you want to use the latest inheritance plugin Downgrade the inheritance plugin to version 1.5.0 if you want to keep the latest 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] [core] (JENKINS-22991) Restart would not properly display username if user was not loaded.
Daniel Beck resolved JENKINS-22991 as Fixed Restart would not properly display username if user was not loaded. Resolving issue so it's actually eligible. Was merged into 1.562 by https://github.com/jenkinsci/jenkins/commit/22e64ab7c26313e9336f168020fbd90bd9caabbd Change By: Daniel Beck (13/May/14 1:47 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] [maven-metadata-plugin] (JENKINS-22996) Parameter not working in combination with Jenkins Release Plugin
Jochen Hinrichsen created JENKINS-22996 Parameter not working in combination with Jenkins Release Plugin Issue Type: Bug Affects Versions: current Assignee: Gesh Markov Components: maven-metadata-plugin Created: 13/May/14 1:47 PM Description: When using 'Build with parameter', the selection is passed to the build job. When using 'Release' via the Jenkins release plugin, nothing is passed. All other build/ releaes parameter types can be used like this. Project: Jenkins Priority: Major Reporter: Jochen Hinrichsen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [shared-workspace] (JENKINS-20059) Build job using shared-workspace is generating error when polling for Git source code changes
Pete W commented on JENKINS-20059 Build job using shared-workspace is generating error when polling for Git source code changes Is this plugin essentially 'parked' and not ready for productionm use for 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] [shared-workspace] (JENKINS-20059) Build job using shared-workspace is generating error when polling for Git source code changes
Pete W edited a comment on JENKINS-20059 Build job using shared-workspace is generating error when polling for Git source code changes Is this plugin essentially 'parked' and not ready for production use for 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] [core] (JENKINS-22946) Upgrading from 1.544 to 1.562 causes multi platform jobs to abort slaves
Kent Granström commented on JENKINS-22946 Upgrading from 1.544 to 1.562 causes multi platform jobs to abort slaves Incompatibility between slave and master was the cause. Setting up matching slave.jar solved the problem This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22853) SEVERE: Trying to unexport an object that's already unexported
Bo Madsen commented on JENKINS-22853 SEVERE: Trying to unexport an object that's already unexported I have just upgraded to 1.563, and the error is still there. So unfortunately no, it is not 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] [gui] (JENKINS-22997) Use bars instead of dots in build history
Hubert Grzeskowiak created JENKINS-22997 Use bars instead of dots in build history Issue Type: Improvement Assignee: Unassigned Components: gui Created: 13/May/14 2:20 PM Description: Every past build offers information about its spent time. In the build history however only dots are shown and it's not clear whether that mark the start or the end of a build process. The used widget is part of the SIMILE project and its well capable of showing bars. See example pages http://www.simile-widgets.org/timeline/examples/test_example2/test_example2.html and http://www.simile-widgets.org/timeline/examples/test_example/test.html . Project: Jenkins Labels: gui Priority: Minor Reporter: Hubert Grzeskowiak This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-blocker] (JENKINS-22994) Build blocker does not support relative paths when jobs has description set
Ireneusz Makowski
commented on JENKINS-22994
Build blocker does not support relative paths when jobs has description set
I believe here is an issue here:
if(task.getFullDisplayName().matches(blockingJob)) {
return subTask;
}
can you add add blocking possibility by FullName?
if(task.getFullName().matches(blockingJob)) {
return subTask;
} }
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-22998) Updated to 1.563 and jobs will not load
fuck you created JENKINS-22998 Updated to 1.563 and jobs will not load Issue Type: Bug Assignee: Peter Hayes Components: dashboard-view Created: 13/May/14 2:23 PM Description: Updated to 1.563 this morning and no jobs will load. Errors in log are: SEVERE: Failed Loading job Trunk groovy.lang.MissingPropertyException: No such property: hudson for class: Script1 at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:50) at org.codehaus.groovy.runtime.callsite.PogoGetPropertySite.getProperty(PogoGetPropertySite.java:49) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGroovyObjectGetProperty(AbstractCallSite.java:231) at Script1.run(Script1.groovy:1) at hudson.matrix.FilterScript.evaluate(FilterScript.java:36) at hudson.matrix.FilterScript.apply(FilterScript.java:73) at hudson.matrix.Combination.evalGroovyExpression(Combination.java:101) at hudson.matrix.Combination.evalGroovyExpression(Combination.java:91) at hudson.matrix.MatrixProject.rebuildConfigurations(MatrixProject.java:637) at hudson.matrix.MatrixProject.onLoad(MatrixProject.java:504) at hudson.model.Items.load(Items.java:273) at jenkins.model.Jenkins$18.run(Jenkins.java:2592) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:904) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) May 13, 2014 8:14:21 AM jenkins.InitReactorRunner$1 onTaskFailed Environment: Ubuntu 10.04 (fully updated) Project: Jenkins Priority: Blocker Reporter: fuck 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] [dashboard-view] (JENKINS-22998) Updated to 1.563 and jobs will not load
Oleg Nenashev commented on JENKINS-22998 Updated to 1.563 and jobs will not load Just an interest... What response are you expecting to get with such nickname? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-blocker] (JENKINS-22994) Build blocker does not support relative paths when jobs has description set
Ireneusz Makowski updated JENKINS-22994 Build blocker does not support relative paths when jobs has description set Change By: Ireneusz Makowski (13/May/14 2:23 PM) Description: Build blocker does not support jobs in relative folders when job description is set. For example:RootFolder-- SubFolder1 - - > Job1 (description "Job Description")-- SubFolder2 - - > Job2I cannot use followin _expression_ in Job2:../SubFolder1/Job1Only this works: .*Job Description.* but this is not solution. Expected result:This works:../SubFolder1/Job1When Job1 is building then block Job2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22999) Git Polling and Git Configuration check fail when behind a proxy server
Timothy Rundle created JENKINS-22999 Git Polling and Git Configuration check fail when behind a proxy server Issue Type: Bug Assignee: Nicolas De Loof Components: git-client Created: 13/May/14 2:26 PM Description: When there is a proxy server between Jenkins and the GIT Repository the GIT Polling and GIT Configuration check fail with unable to resolve host error. This is due to the proxy not being set. Project: Jenkins Priority: Minor Reporter: Timothy Rundle This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-22998) Updated to 1.563 and jobs will not load
fuck you commented on JENKINS-22998 Updated to 1.563 and jobs will not load There is a funny story behind the terrible nickname. I don't know how to change it, and JIRA won't let me create another account. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-19845) EC2 plugin incorrectly reports current instance count
David Walend edited a comment on JENKINS-19845 EC2 plugin incorrectly reports current instance count UPDATE – it's the same problem. I found a second Instance Cap field, tucked into (yet another) Advanced button. Changing that from 1 to 2 let jenkins start a machine. I've got similar symptoms, but not exactly the same. Everything was fine up until about a month ago. I didn't originally set a cap, tried setting the cap to 5, (with only the Jenkins server and one other machine are running in this account). No machine is starting when I start a new build (but the new job is queued). I get the log I've pasted below. I upgraded everything. No luck. Any thoughts? Thanks, Dave May 13, 2014 3:20:51 AM INFO hudson.plugins.ec2.EC2Cloud provision Excess workload after pending Spot instances: 1 May 13, 2014 3:20:51 AM INFO hudson.plugins.ec2.EC2Cloud addProvisionedSlave AMI Instance cap of 1 reached for ami ami-e318378a, not provisioning. May 13, 2014 3:20:51 AM INFO hudson.plugins.ec2.EC2Cloud provision Excess workload after pending Spot instances: 1 May 13, 2014 3:20:51 AM INFO hudson.plugins.ec2.EC2Cloud addProvisionedSlave AMI Instance cap of 1 reached for ami ami-e318378a, not provisioning. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-22537) Seemingly random failures of GitHub plugin PR builder
Leandro Lucarella commented on JENKINS-22537 Seemingly random failures of GitHub plugin PR builder Moved to: https://github.com/janinko/ghprb/issues/148 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22525) A Slave disappears every time Jenkins boots up
John Tal
edited a comment on JENKINS-22525
A Slave disappears every time Jenkins boots up
Was this an in-place update/upgrade that done recently from a previous version of Jenkins (or even hudson)? At least on RHEL with tomcat we have had to remove the old directory under webapps when dropping the new jenkins.war in place. Otherwise we can get these same symptoms (disappearing nodes) and see this same error with slightly different stack trace immediately after a fresh in-place upgrade.
Also note there is a ~/.jenkins/cache directory where jar file versions may be. Don't suggest you play in there unless step above has been tried and then, if still failing, after you have stopped jenkins to rename/delete cache contents.
With additional testing with in-place .war update Jenkins 1.528 does not show this issue ("incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue"). Whereas as dropping in-place higher Jenkins versions including 1.562 does have this issue.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up
John Tal
edited a comment on JENKINS-22525
A Slave disappears every time Jenkins boots up
Was this an in-place update/upgrade that done recently from a previous version of Jenkins (or even hudson)? At least on RHEL with tomcat we have had to remove the old directory under webapps when dropping the new jenkins.war in place. Otherwise we can get these same symptoms (disappearing nodes) and see this same error with slightly different stack trace immediately after a fresh in-place upgrade.
Also note there is a ~/.jenkins/cache directory where jar file versions may be. Don't suggest you play in there unless step above has been tried and then, if still failing, after you have stopped jenkins to rename/delete cache contents.
For an existing installation we are seeing this same issue when we update to Jenkins 1.562 ("incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue"). Whereas as dropping in-place a lower Jenkins version such as 1.528 does not show this issue.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-23000) Updated to 1.563 and jobs will not load
Adam Daughterson created JENKINS-23000 Updated to 1.563 and jobs will not load Issue Type: Bug Assignee: Peter Hayes Components: dashboard-view Created: 13/May/14 2:44 PM Description: Updated to 1.563 this morning and no jobs will load. Errors in log are: SEVERE: Failed Loading job Trunk groovy.lang.MissingPropertyException: No such property: hudson for class: Script1 at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:50) at org.codehaus.groovy.runtime.callsite.PogoGetPropertySite.getProperty(PogoGetPropertySite.java:49) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGroovyObjectGetProperty(AbstractCallSite.java:231) at Script1.run(Script1.groovy:1) at hudson.matrix.FilterScript.evaluate(FilterScript.java:36) at hudson.matrix.FilterScript.apply(FilterScript.java:73) at hudson.matrix.Combination.evalGroovyExpression(Combination.java:101) at hudson.matrix.Combination.evalGroovyExpression(Combination.java:91) at hudson.matrix.MatrixProject.rebuildConfigurations(MatrixProject.java:637) at hudson.matrix.MatrixProject.onLoad(MatrixProject.java:504) at hudson.model.Items.load(Items.java:273) at jenkins.model.Jenkins$18.run(Jenkins.java:2592) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:904) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) May 13, 2014 8:14:21 AM jenkins.InitReactorRunner$1 onTaskFailed Environment: Ubuntu 10.04 Project: Jenkins Priority: Major Reporter: Adam Daughterson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22525) A Slave disappears every time Jenkins boots up
John Tal
edited a comment on JENKINS-22525
A Slave disappears every time Jenkins boots up
Was this an in-place update/upgrade that done recently from a previous version of Jenkins (or even hudson)? At least on RHEL with tomcat we have had to remove the old directory under webapps when dropping the new jenkins.war in place. Otherwise we can get these same symptoms (disappearing nodes) and see this same error with slightly different stack trace immediately after a fresh in-place upgrade.
Also note there is a ~/.jenkins/cache directory where jar file versions may be. Don't suggest you play in there unless step above has been tried and then, if still failing, after you have stopped jenkins to rename/delete cache contents.
For an existing installation we are seeing this same issue when we update to Jenkins 1.562 ("incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue"). Whereas dropping in-place a lower Jenkins version such as 1.528 does not show this issue.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up
John Tal
edited a comment on JENKINS-22525
A Slave disappears every time Jenkins boots up
Was this an in-place update/upgrade that done recently from a previous version of Jenkins (or even hudson)? At least on RHEL with tomcat we have had to remove the old directory under webapps when dropping a new jenkins.war in place. Otherwise we can get these same symptoms (disappearing nodes) and see this same error with slightly different stack trace immediately after a fresh in-place upgrade.
Also note there is a ~/.jenkins/cache directory where jar file versions may be. Don't suggest you play in there unless step above has been tried and then, if still failing, after you have stopped jenkins to rename/delete cache contents.
With further testing we can get this same error to occur with different versions of Jenkins. For an existing installation we are seeing this same issue when we update to Jenkins 1.562 ("incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue"). Whereas dropping in-place a lower Jenkins version such as 1.528 does not show this issue.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up
John Tal
edited a comment on JENKINS-22525
A Slave disappears every time Jenkins boots up
Was this an in-place update/upgrade that done recently from a previous version of Jenkins (or even hudson)? At least on RHEL with tomcat we have had to remove the old directory under webapps when dropping a new jenkins.war in place. Otherwise we can get these same symptoms (disappearing nodes) and see this same error with slightly different stack trace immediately after a fresh in-place upgrade.
Also note there is a ~/.jenkins/cache directory where jar file versions may be. Don't suggest you play in there unless step above has been tried and then, if still failing, after you have stopped jenkins to rename/delete cache contents.
For an existing installation we are seeing this same issue when we update to Jenkins 1.562 ("incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue"). Whereas dropping in-place a lower Jenkins version such as 1.528 does not show this issue.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-22590) Promotion permalinks not offered when job name is parameterized
Jesse Glick resolved JENKINS-22590 as Fixed Promotion permalinks not offered when job name is parameterized This was merged; maybe JIRA autolinker is dead again. Change By: Jesse Glick (13/May/14 2:51 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix] (JENKINS-22998) Updated to 1.563 and jobs will not load
Oleg Nenashev updated JENKINS-22998 Updated to 1.563 and jobs will not load This bug is definitely a duplicate, but I have not found another one yet... Change By: Oleg Nenashev (13/May/14 2:54 PM) Component/s: matrix Component/s: dashboard-view This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix] (JENKINS-22998) Updated to 1.563 and jobs will not load
Adam Daughterson commented on JENKINS-22998 Updated to 1.563 and jobs will not load Thanks. You wouldn't happen to know how I can get rid of that account, would 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] [matrix] (JENKINS-22998) Updated to 1.563 and jobs will not load
Oleg Nenashev commented on JENKINS-22998 Updated to 1.563 and jobs will not load I suppose you could contact admins via Jenkins IRC. http://webchat.freenode.net/?channels=jenkins This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22914) file transfer from slave to master failed with pipe closed
robsimon commented on JENKINS-22914 file transfer from slave to master failed with pipe closed i had not yet the time to update our jenkins the filename is plain ascii chars. hence I've no idea why those cryptic chars appear. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23001) Build Queue Graph Does Not Show Jobs In The Queue When Use NodeLabel Parameter
tim johnston created JENKINS-23001 Build Queue Graph Does Not Show Jobs In The Queue When Use NodeLabel Parameter Issue Type: Bug Assignee: Dominik Bartholdi Components: nodelabelparameter Created: 13/May/14 3:29 PM Description: The build queue graph in Jenkins does not properly show jobs which are in the queue when the job is using the node label parameter. To reproduce: create a label in Jenkins called LabelX create a job which contains a nodelabel parameter and give it the value "LabelX". Make sure that the job can run concurrently and that the option "Restrict where this project can be run" is not clicked. execute enough instances of the job so that there are some jobs in the build queue click LabelX and then click on load statistics Expected: the queued jobs should be represented in the graph with the grey line Actual: the queued jobs are not displayed properly in the graph Project: Jenkins Priority: Minor Reporter: tim johnston This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix] (JENKINS-22998) Updated to 1.563 and jobs will not load
Adam Daughterson closed JENKINS-22998 as Duplicate Updated to 1.563 and jobs will not load Change By: Adam Daughterson (13/May/14 3:33 PM) Status: Open Closed Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [translation] (JENKINS-22982) Copy-Paste Errors in German Translation Resource for LogRotator
Harald Albers assigned JENKINS-22982 to Harald Albers Copy-Paste Errors in German Translation Resource for LogRotator Change By: Harald Albers (13/May/14 3:35 PM) Assignee: Harald Albers This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-23002) I need to remove a JIRA account of mine which was created in haste
Adam Daughterson assigned JENKINS-23002 to Adam Daughterson I need to remove a JIRA account of mine which was created in haste Change By: Adam Daughterson (13/May/14 3:38 PM) Assignee: Adam Daughterson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-23002) I need to remove a JIRA account of mine which was created in haste
Adam Daughterson created JENKINS-23002 I need to remove a JIRA account of mine which was created in haste Issue Type: Bug Assignee: Unassigned Components: jira Created: 13/May/14 3:37 PM Description: I stupidly created the account 'fuckyoupieceofshit' in haste, and need to have it removed. Project: Jenkins Priority: Major Reporter: Adam Daughterson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-23002) I need to remove a JIRA account of mine which was created in haste
Adam Daughterson closed JENKINS-23002 as Not A Defect I need to remove a JIRA account of mine which was created in haste Change By: Adam Daughterson (13/May/14 3:38 PM) Status: Open Closed Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator] (JENKINS-23003) Generating Ant build files for test projects
Xavier Gouchet created JENKINS-23003 Generating Ant build files for test projects Issue Type: Bug Affects Versions: current Assignee: Christopher Orr Components: android-emulator Created: 13/May/14 3:55 PM Description: I have a particular workspace configuration : I have a library project (lets call it "lib"), a unit test project (lets call it "test"), and a demo project using the lib (lets call it "demo"). Now both the "test" and "demo" project share the same package name (and its impossible for me to change the package names for either of them as it needs to be this package name). The problem is that the test project works on its own (it has its own activities) and only relies on the "lib" project. But the task insist on making the "test" dependant on the "demo" project. This results in jenkins building both project, and installing both on the emulator. The "demo" project being installed after, it replaces the "test" projects and so the instrumentation doesn't work. Environment: Linux (Debian) Project: Jenkins Priority: Major Reporter: Xavier Gouchet This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [translation] (JENKINS-22982) Copy-Paste Errors in German Translation Resource for LogRotator
Harald Albers started work on JENKINS-22982 Copy-Paste Errors in German Translation Resource for LogRotator Change By: Harald Albers (13/May/14 4:01 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-23004) Contributing 1st Active-Directory plugin test
Marco Miller created JENKINS-23004 Contributing 1st Active-Directory plugin test Issue Type: New Feature Assignee: Marco Miller Components: acceptance-test-harness Created: 13/May/14 4:04 PM Description: TODO Project: Jenkins Labels: plugin Priority: Major Reporter: Marco Miller This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23004) Contributing 1st Active-Directory plugin test
Marco Miller started work on JENKINS-23004 Contributing 1st Active-Directory plugin test Change By: Marco Miller (13/May/14 4:04 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-23004) Contributing 1st Active-Directory plugin test
Marco Miller updated JENKINS-23004 Contributing 1st Active-Directory plugin test Change By: Marco Miller (13/May/14 4:04 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] [core] (JENKINS-22853) SEVERE: Trying to unexport an object that's already unexported
Alan Norton commented on JENKINS-22853 SEVERE: Trying to unexport an object that's already unexported Latest Jenkins ver. 1.563 still exhibits this issue. I've see this exception ~500 times in the last 24hrs of running 1.563. My setup was hit pretty hard by https://issues.jenkins-ci.org/browse/JENKINS-22734, and the stability in 1.563 is considerably improved, but the java -jar /tmp/slave.jar process on EC2 (3.10.38-49.136.amzn1.x86_64 + java-1.7.0_55) slaves still dies occasionally. At this point, I'm unsure if this (SEVERE: Trying to unexport an object that's already unexported) is actually the cause of the slave.jar process dying. Open to suggestions as to how to provide better debugging information. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22853) SEVERE: Trying to unexport an object that's already unexported
Alan Norton edited a comment on JENKINS-22853 SEVERE: Trying to unexport an object that's already unexported Latest Jenkins ver. 1.563 still exhibits this issue. I've see this exception ~500 times (according to jenkins' master logs) in the last 24hrs of running 1.563. My setup was hit pretty hard by https://issues.jenkins-ci.org/browse/JENKINS-22734, and the stability in 1.563 is considerably improved (thanks!), but the java -jar /tmp/slave.jar process on EC2 (3.10.38-49.136.amzn1.x86_64 + java-1.7.0_55) slaves still dies occasionally. It seems to happen more frequently on jobs that produce a lot of verbose, debugging output. At this point, I'm unsure if this issue (SEVERE: Trying to unexport an object that's already unexported) is actually the cause of the slave.jar process dying or just a coincidental occurrence. Open to suggestions as to how to provide better debugging information. Happy to help in any way I can. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up
John Tal
edited a comment on JENKINS-22525
A Slave disappears every time Jenkins boots up
Was this an in-place update/upgrade that done recently from a previous version of Jenkins (or even hudson)? At least on RHEL with tomcat we have had to remove the old directory under webapps when dropping a new jenkins.war in place. Otherwise we can get these same symptoms (disappearing nodes) and see this same error with a slightly different stack trace immediately after a fresh in-place upgrade.
Also note there is a ~/.jenkins/cache directory where jar file versions may be. Don't suggest you play in there unless step above has been tried and then, if still failing, after you have stopped jenkins to rename/delete cache contents.
With further testing we can get this same error to occur with different versions of Jenkins. For an existing installation we are seeing this same issue when we update to Jenkins 1.562 ("incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue"). Whereas dropping in-place a lower Jenkins version such as 1.528 does not show this issue.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [translation] (JENKINS-22982) Copy-Paste Errors in German Translation Resource for LogRotator
dogfood commented on JENKINS-22982 Copy-Paste Errors in German Translation Resource for LogRotator Integrated in jenkins_main_trunk #3378 [FIXED JENKINS-22982] Copy-Paste Errors in German Translation Resource (Revision 87de5aa5f5ffdde884c9506e8ffd89c3a1f13351) Result = SUCCESS github : 87de5aa5f5ffdde884c9506e8ffd89c3a1f13351 Files : core/src/main/resources/hudson/tasks/LogRotator/config_de.properties This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix] (JENKINS-15673) InvalidClassException after modifying job matrix
Brian Murrell commented on JENKINS-15673 InvalidClassException after modifying job matrix I've just all of a sudden started seeing this on what was an otherwise working Jenkins installation as of a few days ago. I have not done any updates/upgrades of anything – Jenkins or plugins. This just started happening. Both my Jenkins server and build slaves are EL6 Linux running java-1.6.0-openjdk-1.6.0.0-5.1.13.3.el6_5 Any clues what the problem might be? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-21362) Multiple (User Defined) Global Templates
Alex Ouzounis commented on JENKINS-21362 Multiple (User Defined) Global Templates This is a really exciting proposition, I will try and have a look at the plugin and give you some feedback at some point. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-23006) Improve exception message when reading missing workspace files
Nick B created JENKINS-23006 Improve exception message when reading missing workspace files Issue Type: Improvement Affects Versions: current Assignee: Nick B Components: job-dsl-plugin Created: 13/May/14 6:33 PM Description: New to JobDSL, so please bear with me! When loading files from the workspace using readFileInWorkspace() or streamFileInWorkspace(), a missing file will throw an IllegalStateException (debates on that probably not in scope...) It would be very helpful to the end user to include the path to the missing file (I know because we spent a lot of time looking at the wrong section of our JobDSL code over the last couple of days). FWIW, there's also a typo in the message... Project: Jenkins Priority: Minor Reporter: Nick B This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-6817) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
Ian Norton commented on JENKINS-6817 FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel This is killing me, I get this 6 times a day but only on my windows slaves. The amount of resources I give to them makes no difference to the chance of failure (they are all quad core with 6Gb of RAM 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] [subversion] (JENKINS-23007) Subversion plugin 2.x cannot handle changelog computation with variables in SVN URLs
Daniel Beck created JENKINS-23007 Subversion plugin 2.x cannot handle changelog computation with variables in SVN URLs Issue Type: Bug Assignee: Unassigned Components: subversion Created: 13/May/14 7:13 PM Description: Another Subversion plugin 2.x auth failure for no good reason. Steps to reproduce 1. In Jenkins, define a variable 'BRANCH' with value 'trunk'. (E.g. in Configure System, or Folders Plus on folder level). 2. Create a job checking out the URL https://svnserver/svn/repo/$BRANCH/foo (assuming https://svnserver/svn/repo/trunk/foo exists). 3. Build the job. 4. Poll for SCM changes (/job/jobname/polling). Expected results No changes. Or changes. Whatever's correct. Actual results ERROR: Failed to check repository revision for https://svnserver/svn/repo/trunk/foo org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS /svn/repo/trunk/foo failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:384) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:180) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:148) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.run(SvnRemoteGetInfo.java:46) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.run(SvnRemoteGetInfo.java:31) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNWCClient.doInfo(SVNWCClient.java:2461) at hudson.scm.SubversionSCM.parseSvnInfo(SubversionSCM.java:1235) at hudson.scm.CompareAgainstBaselineCallable.call(CompareAgainstBaselineCallable.java:78) at hudson.scm.CompareAgainstBaselineCallable.call(CompareAgainstBaselineCallable.java:26) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source) Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorMa
[JIRA] [clang-scanbuild] (JENKINS-23008) "xcodebuild: error: option '-activetarget' is no longer supported" when using clang-scanbuild plugin on xcode 5.1.1
Colin Sauze created JENKINS-23008 "xcodebuild: error: option '-activetarget' is no longer supported" when using clang-scanbuild plugin on xcode 5.1.1 Issue Type: Bug Assignee: Josh Kennedy Attachments: jenkins clang-scanbuild error Components: clang-scanbuild Created: 13/May/14 7:14 PM Description: I'm getting an error "xcodebuild: error: option '-activetarget' is no longer supported" in the console output when trying to use the clang-scanbuild plugin while building an iOS application. I'm assuming that the latest version of Xcode has deprecated this option and that the plugin needs to be updated to no longer use it. Manually running scan-build from the command line without this option appears to work fine. I have attached the full error log as shown in the Jenkins console. Environment: Mac OSX 10.8.5, Xcode version 5.1.1, clang checker version 276, Jenkins version 1.554.1 (running on a Linux host, executing jobs on the Mac as a slave node) Project: Jenkins Labels: plugin Priority: Major Reporter: Colin Sauze This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-6817) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
Adam Daughterson commented on JENKINS-6817 FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel I've been able to "sort of" get around this by only sending IO and CPU heavy stuff to dedicated, powerful systems, reducing the number of executors on each slave to 1, reducing the number of threads to half the number of cores. Totally lame workaround, but "done at all" is better than the stupid stack dump. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [openid] (JENKINS-23009) [openid-plugin] Support 3 different email attributes for AX Extension
Nirmal Jonnalagedda created JENKINS-23009 [openid-plugin] Support 3 different email attributes for AX Extension Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: openid, plugin Created: 13/May/14 8:14 PM Description: The standard email attribute type URI for the AX extension is "http://axschema.org/contact/email". However, many of the OpenId providers do not support this standard attribute type URI but instead support one of the following: http://schema.openid.net/contact/email http://openid.net/schema/contact/email The Jenkins openid-plugin currently supports only "http://schema.openid.net/contact/email". For a better user experience, it is recommended to ask/support for all three email attributes. Project: Jenkins Priority: Major Reporter: Nirmal Jonnalagedda This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [openid] (JENKINS-23009) [openid-plugin] Support 3 different email attributes for AX Extension
Nirmal Jonnalagedda commented on JENKINS-23009 [openid-plugin] Support 3 different email attributes for AX Extension Link to the pull request made: https://github.com/jenkinsci/openid-plugin/pull/6 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy] (JENKINS-17171) Token macro expansion not working in Groovy plugin 1.13
vjuranek resolved JENKINS-17171 as Fixed Token macro expansion not working in Groovy plugin 1.13 fixed by PR #14, fixed version 1.18. Change By: vjuranek (13/May/14 8:22 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [exclusion] (JENKINS-23010) Exclusion-Plugin Control Panel doesn't update; doesn't report parameter values
Generic Ratslaugh created JENKINS-23010 Exclusion-Plugin Control Panel doesn't update; doesn't report parameter values Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: exclusion.jpg Components: exclusion Created: 13/May/14 8:40 PM Description: Three problems with the Exclusion-Plugin control panel (see attached image): 1) It reports parameter variable instead of the value that the parameter variable points to. 2) When I replaced the variable with a pure text parameter, the control panel did not update to reflect my changes - it still shows the old variable. 3) I couldn't enter or find anything in the "Resource name" section of the control panel and I could not release a resource (In the attached example, I set the job build parameter RT_IOBLOCK to 'A' for testing, and entered '$RT_IOBLOCK' in the Build Environment "Add resource to manage exclusion" section. The control panel should have shown the resource to be A, but instead showed '$RT_IOBLOCK'. I then changed the "Add resource to manage exclusion" to 'A' and ran the test. The control block should again show 'A', but has not changed.) BTW, this plugin is nonetheless great. Thanks. Environment: RHEL 6.5 x86-64 Fix Versions: current Project: Jenkins Labels: plugin Exclusion-plugin Priority: Minor Reporter: Generic Ratslaugh This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
