array of identical Jenkins jobs, redundant code – how to replace using a "super-feature"?
We do have like 10 Jenkins jobs here, and they all call the same batch script, always with the Jenkins job name as parameter in order to give the batch script an opportunity to decide who is who. I knew that kind of redundancy is bad, but I don't know a better approach yet. I don't think a usual parameterized Jenkins jobs solves it, but maybe I am missing the magic trick. Do you what I mean resp. what I need? I need your advice. ~j -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/56734179-e037-4d4e-b766-2370aaef6425%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How to extend $PATH used by Jenkins?
Have a look at the "Build Environment" section, particularly at "Properties Content"! You can make use of environment variables there, and you can assign values to environment variables, but only once per variable. But you can do things like this: PATH1=$HOME/bin:$PATH > PATH=$HOME/shell:$PATH1 Have a look at the online help! (-> "?") On Tuesday, 10 November 2015 22:58:22 UTC+1, Daniel Anechitoaie wrote: > > Hi, > > I have some stuff installed in /opt/ > > How can I add this to $PATH so that it's visible in Jenkins? > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c4f622a6-f47d-4c01-b3c5-ce4b09a2e45a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Jenkins Plugin Manager: "This plug cannot be enabled / It has one or more dependencies" – but the dependencies cannot be fulfilled
Hi there! I am experiencing the same problem as described by philm88 here: http://echelog.com/logs/browse/jenkins/1444600800 In my case no restoring of a backup is involved, and I don't think that particular issue is related. In the installed plugins page, the enabled box is ticked, but greyed out. > Hovering over them says "This plugin cannot be enabled. It has one more > disabled dependencies " Of those dependencies listed, they're greyed > out unticked and hovering on those says "This plugin cannot be disabled, It > has one more enabled dependants" > Which I don't really understand...the 'Enabled' boxes are greyed out > unticked, but it says the plugin cannot be disabled. And no, we can not enable the dependencies first: all of the plugins are either greyed out enabled, or greyed out disabled; I > can't change any of them. The dependencies look "a little circular" to me. I am not sure, whether that is seriously related. Thanks in advance! ~J P.S. I am sorry I also posted this issue erroneously on "Jenkins Developers". -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1edda12e-216f-4974-92f6-e6bbecbe02eb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
