[JIRA] [core] (JENKINS-9665) Variables used as node labes are not expanded in parameterized builds
ggi reopened JENKINS-9665 Variables used as node labes are not expanded in parameterized builds Hi, I think that the proposals are workarounds for specific situations, but I think the issue is still not resolved, since can not be used variables in label parameters. In my case I don't found the way to with those workarounds, I have to send the job to a label (not node) depending of the parameters which are called the job. I have solved it with another workaround: using the "Parameterized Trigger Plugin" inside this call, using the option of pass parameters from a properties file and inside this option, use the option "Don't trigger if any files are missing" So depending the the properties files that I create or delete in a previous shell script, I control which jobs runs, and each job has a fixed label. Still all of these are complex workarounds because can not be used variables in label parameters. So if this can be fixed would the good solution. Regards, Gorka Change By: ggi (05/Nov/14 3:25 PM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7744) Aborting job fails to kill processes started during cancel action
gck commented on JENKINS-7744 Aborting job fails to kill processes started during cancel action I can't reproduce the problem any more with 1.583. Looking into the code I touched in my patch from 4 years ago I can see that a lot of stuff have changed. It could be that the bug has been fixed by 550678074ebeae884cf98850c4032141a936fe09. No sure though. Since I can't find a recipe to reproduce anymore I would not regard my patch as anyhow useful. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-7746) Killing processes on Mac OS X/64bit VM does not work
gck commented on JENKINS-7746 Killing processes on Mac OS X/64bit VM does not work I've just checked with 1.583 and there it seems to work, both with 32bit and 64bit VM. So I guess the issue has been fixed in the meanwhile. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [managed-scripts] (JENKINS-20964) Option of disable the call to a managed script
ggi closed JENKINS-20964 as Not A Defect Option of disable the call to a managed script Hi Dominik, Totally agree with you. It is more interesting to be implemented in core and available for any build step. I do a search in the issues of jenkins and found it already reported: https://issues.jenkins-ci.org/browse/JENKINS-4819 So i'm closing this thread. Regards Change By: ggi (21/Jul/14 8:24 AM) Status: Open Closed Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
