Hi, yes, I can confirm that behaviour. Taking a closer look at the log shows that any build wrappers that inject e.g. Environment vars are not running at this early stage. My guess is, that the assumption was that these wrappers are instantiated in the Jenkinsfile, so that they are not yet known.
Wether this is a good assumption in all use-cases is an open question. Björn Am Dienstag, 5. April 2016 09:47:50 UTC+2 schrieb [email protected]: > > Hi, > > Mode: Pipeline script from SCM > > > I tried to change working example to take a TAG as String parameter > and to use *${TAG}* for the Branch using the Pipeline job in Jenkins 2.x > When trying this I get this: > > > git rev-parse origin/${TAG}^{commit} # timeout=10 > > git rev-parse ${TAG}^{commit} # timeout=10 > ERROR: Couldn't find any revision to build. Verify the repository and branch > configuration for this job. > > > It looks to me that the variable TAG is not evaluated. Using "master" instead > of "${TAG}" works fine. > > > Bug? I guess so. > > > Kind Regards, > > Thomas > > > PS: I tried to register at Jenkins JIRA but it's a nightmare. Either the > captcha popup appears > after hours, or it timeouts or I get null pointer exception after submitting > or whatever. > > After 20 minutes I gave up. So don't ask me to write a ticket please ;) > > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/d17e3fc6-ec63-4a41-b941-18806bb38b64%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
