Hello Joel, I would start from creating an issue in the bugtracker. Since you report an issue for the build parameter, it really makes sense to provide a configuration of your job. Variables injection may behave differently depending on job types and build steps.
Best regards, Oleg Nenashev суббота, 7 марта 2015 г., 1:41:14 UTC+3 пользователь Joel Collins написал: > > Let me start off by saying i'm way way over my head here, and apologies if > this is the wrong audience for this. > > > We're using jenkins with a custom built plugin, and that plugin recently > broke after an upgrade to 1.591 / 1.601 (could have been before that, I > hadn't upgraded beforehand in a few months) > > THe plugin runs a script to get 1 value for a parameter, and based on the > result of that script, a second drop down is populated. The plugin in on > github, and everything seems to work perfectly, the drop downs work fine > and the first environment variable (read by the second script) is set > correctly. HOWEVER, when the build is run, only the first environment > variable is visible to the build scripts, not the second. > > I narrowed it down to this method not being executed > > https://github.com/tekante/restricted-parameter-list/blob/master/src/main/java/com/phase2technology/jenkins/RestrictedStringDynamicParameterValue.java#L34 > > Keeping in mind that I can barely spell java, if anyone has > recommendations on where to go from here i'd really appreciate it. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/084e4645-1b05-462a-bdd7-72ed5e343225%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
