[JIRA] [ssh-slaves-plugin] (JENKINS-30561) Unable to launch slave using SSH
Title: Message Title Derk-Jan Hartman edited a comment on JENKINS-30561 Re: Unable to launch slave using SSH Yes, this is because your default java on your node is running java 1.6. The error could be handled a bit better however.. I mean "[09/21/15 13:34:41] [SSH] java -version returned 1.6.0_22." it's already checking the version. Might as well do something with it :) I also installed Java 7 locally on that machine and switched javaPath (an option that is under the advanced button btw). I wanted to keep the actual jobs on that single node compiling with Java 6, specifically because it's doing checks on backwards compatibility. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-plugin] (JENKINS-30561) Unable to launch slave using SSH
Title: Message Title Derk-Jan Hartman commented on JENKINS-30561 Re: Unable to launch slave using SSH Yes, this is because your default java on your node is running java 1.6. The error could be handled a bit better however.. I mean "[09/21/15 13:34:41] [SSH] java -version returned 1.6.0_22." it's already checking the version. Might as well do something with it Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodejs-plugin] (JENKINS-27845) Support auto install on Mac OS X
Derk-Jan Hartman commented on JENKINS-27845 Support auto install on Mac OS X Yeah I also have some problems. I was trying to do some global npm packages install, after the auto installed node, in this case `grunt-cli gulp-cli` and it simply fails to execute and find stuff. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-plugin] (JENKINS-27620) SCM polling broken for servers with variable in path
Derk-Jan Hartman commented on JENKINS-27620 SCM polling broken for servers with variable in path My issue seems duplicate with JENKINS-22542 Downgrading to 2.4.5 indeed made polling work again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodejs-plugin] (JENKINS-27845) Support auto install on Mac OS X
Derk-Jan Hartman created JENKINS-27845 Support auto install on Mac OS X Issue Type: Improvement Assignee: Unassigned Components: nodejs-plugin Created: 08/Apr/15 12:55 PM Description: The documentation of the plugin notes that auto installation for mac and windows is currently not support. I would love to hear what was blocking this to make it work. Then I might even be motivated to look into fixing it Project: Jenkins Priority: Minor Reporter: Derk-Jan Hartman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-plugin] (JENKINS-27620) SCM polling broken for servers with variable in path
Derk-Jan Hartman commented on JENKINS-27620 SCM polling broken for servers with variable in path Actually, now that i'm looking a bit further, it seem that the real problem is that SCM polling isn't able to find the credentials anymore. This information is in the SCM polling log, and not in the Jenkins master log. Manually triggering the build, SVN has no problem finding the credentials. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-plugin] (JENKINS-27620) SCM polling broken for servers with variable in path
Derk-Jan Hartman commented on JENKINS-27620 SCM polling broken for servers with variable in path This is highly likely yes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pollscm-plugin] (JENKINS-27620) SCM polling broken for servers with variable in path
Derk-Jan Hartman created JENKINS-27620 SCM polling broken for servers with variable in path Issue Type: Bug Assignee: Vincent Latombe Components: pollscm-plugin Created: 26/Mar/15 10:41 AM Description: SCM polling broke for me after updating to: 1.605 Before this i was running 1.591 The log shows: no revision found corresponding to svn://$SVN_SERVER/path; known: [svn://my.servername.com/path] And it simply never triggered any of the builds for that reason. Apparently something changed in how or when the SCM paths get expanded. Regardless of the change, isn't the fallback of triggering a build in case of "no revision found corresponding", a safer fallback strategy ? Project: Jenkins Priority: Minor Reporter: Derk-Jan Hartman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-24686) scm-sync-configuration fails if job name contains a whitespace
Derk-Jan Hartman commented on JENKINS-24686 scm-sync-configuration fails if job name contains a whitespace me three ! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-21257) up link of downstream job from multiconfig job is going nowhere
Derk-Jan Hartman resolved JENKINS-21257 as Fixed up link of downstream job from multiconfig job is going nowhere Change By: Derk-Jan Hartman (01/Apr/14 7:59 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21257) up link of downstream job from multiconfig job is going nowhere
Derk-Jan Hartman updated JENKINS-21257 up link of downstream job from multiconfig job is going nowhere Change By: Derk-Jan Hartman (07/Jan/14 4:16 PM) Priority: Major Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21257) up link of downstream job from multiconfig job is going nowhere
Derk-Jan Hartman created JENKINS-21257 up link of downstream job from multiconfig job is going nowhere Issue Type: Bug Assignee: Unassigned Components: core Created: 07/Jan/14 4:13 PM Description: In the UI of the downstream job of a multiconfiguration job, in the top left there is a link named "up". This link points to http://server/job and results in a 404: "Problem accessing /job/. Reason: Not Found" So the UI for: http://server/job/multiconfig-job/label=aLabel I would expect it to link to: http://server/job/multiconfig-job But it links to http://server/job/ Environment: 1.546 Project: Jenkins Priority: Major Reporter: Derk-Jan Hartman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [core] (JENKINS-18410) Use RunAction2 from TestResultAction
Derk-Jan Hartman commented on JENKINS-18410 Use RunAction2 from TestResultAction The fix to the fix didn't make it to 1.546 it seems, causing both 1.545 and 1.546 to fail jobs in the aggregate test results phase with the NPE listed in the previous comments. The workaround for this is to explicitly set the names of the jobs that you want aggregated in your job configuration or to remove the entire aggregate task from the job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
