[JIRA] [core] (JENKINS-29902) Unexpected executor death - java.lang.IllegalStateException: build already existed
Title: Message Title lata kopalle created an issue Jenkins / JENKINS-29902 Unexpected executor death - java.lang.IllegalStateException: build already existed Issue Type: Bug Assignee: Unassigned Attachments: odd_build_records_1.609.1.png, odd_build_records_1.609.1_builds_dir.png, odd_build_records_restart_thread.png, odd_build_records_set_build_number.png Components: core Created: 12/Aug/15 5:56 AM Environment: Jenkins 1.609.1 Master on RHEL 6.6, in in Tomcat 8. Priority: Major Reporter: lata kopalle Issue is seen after upgrading to 1.609.1 from 1.596.2. Issue is seen on freestyle projects (fixes in https://issues.jenkins-ci.org/browse/JENKINS-26582 relate to matrix project)
[JIRA] [core] (JENKINS-15627) Using MacOS slave in 1.487 - Can't connect to window server - not enough permissions
lata kopalle commented on JENKINS-15627 Using MacOS slave in 1.487 - Cant connect to window server - not enough permissions thanks for the workaround Andrey, it just saved our day. Our Jenkins version: 1.533, Master on windows. Issue seen with on Mac OS X 10.9 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] [envinject] (JENKINS-24406) 'Inject variables as a build step' resets slave's system path
lata kopalle created JENKINS-24406 Inject variables as a build step resets slaves system path Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: envinject Created: 25/Aug/14 10:18 AM Description: Using 'Inject variables as a build step', either through 'Properties File Path' or 'Properties Content', resets the system Path for subsequent build steps. Printing out the env before using this step matches the slave's system path variable, but after injecting variables as a build step, the new env printed shows a different path value, unsure where this new value is being set from, i couldn't map it to anything in our env, yet. The new path ofcourse messes with build environment. Environment: Jenkins Version: 1.532.1 EnvInject Plugin Version: 1.88 Slave: Windows 7 Master: RHEL 5.8 Project: Jenkins Priority: Major Reporter: lata kopalle This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [slave-setup] (JENKINS-22239) Doesn't create root folder when installing JNLP Windows Service
lata kopalle commented on JENKINS-22239 Doesnt create root folder when installing JNLP Windows Service yes, i hv a similar 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] [nodeofflinenotification] (JENKINS-20720) Jenkins fails to connect to slave via ssh after nodeofflinenotification plugin
lata kopalle created JENKINS-20720 Jenkins fails to connect to slave via ssh after nodeofflinenotification plugin Issue Type: Bug Assignee: Unassigned Components: nodeofflinenotification Created: 22/Nov/13 11:46 AM Description: Hi We could connect to our slaves via ssh smoothly, until we installed the nodeofflinenotification plugin. Once the plugin is installed, *the connection is not established, *there is no slave log at $JENKINS_HOME/logs/slaves/ created, *and a spinning wheel when trying to access the slave log from jenkins console, the log is not created anyway. There were a bunch of plugins that were installed on our instance since the last successful slave connect, the new plugin which is causing this failure to connect is the nodeofflinenotification v 1.0.3 https://wiki.jenkins-ci.org/display/JENKINS/Node+Offline+Notification+Plugin I've uninstalled the plugin and restarted our Jenkins, the slaves re-connect smoothly again. I've categorized this as a 'Major' priority not for the functionality of the plugin but for the time and effort it could result in in identifying why the slaves are not connecting via ssh. Thanks Lata Environment: Jenkins Master: Linux x86_64 Jenkins Slave: Linux x86_64 Jenkins Version: 1.509.3 (LTS) nodeofflinenotification Plugin: 1.0.3 java version: jdk1.6.0_32 Project: Jenkins Priority: Major Reporter: lata kopalle This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14401) Jenkins throws exception iv version colnumn plugin is disabled.
lata kopalle commented on JENKINS-14401 Jenkins throws exception iv version colnumn plugin is disabled. How do we resolve this, do you have a workaround, i don't mind enabling the plugin back, but not sure how to. I just hit this issue, and it's a blocker for us. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
