my use case is GitSCM (actually, GitRepositoryBrowser) to expand attributes based on Job.getEnvironment how would you handle this ?
Also, I don't understand why you consider back-references to be a bad thing. 2014-02-17 17:52 GMT+01:00 Jesse Glick <[email protected]>: > On Mon, Feb 17, 2014 at 11:42 AM, nicolas de loof > <[email protected]> wrote: > > from gitSCM I need job to compute environment and expand variables > > Most places where the job would be needed, it (or a build of it) is > already passed in as a method argument. If you are dealing with a case > where it is not, then that is what should be fixed, rather than having > the SCM hold a backreference. > > -- > 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]. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
