>
> And for "binding variables" I mean what are the variables I can use in
> pipeline scripts, i.e., currentBuild is a binding Variable (when I try to
> use a non defined variable, for example, project, the error I get is
> undefined Binding Variable).
I answer myself: ${MY_JENKINS_URL}/pipeline-syntax/globals
This is a begining... But I don't know how can I modify the description of
the project, for example, because I have no idea about getting the Project
reference. I know I can disable "*Use the groovy sandbox*", but I think
this is not a great idea.
El viernes, 26 de agosto de 2016, 9:06:58 (UTC+2), Ramón Rial escribió:
>
> Thank you, Jesse.
>
> I have designed a hierarchical structure for the projects in my Jenkins,
> so I can autogenerate many information to write to the Jenkins project in
> any moment, based on the fullName of that structure (and other files, of
> course).
>
> I have a collection of groovy scripts that parses that information, and
> assign and/or fixes missing data (scm url's, ownership, folder and project
> descriptions...) to the project.
> But there is some work that should be done at "build time", because the
> data needed is inside of the files in the scm repository, so I need to do a
> checkout first, and then I can read the filename (for example, the node
> description of pom.xml, or the version).
>
> And with pipeline I don't know how to:
>
> * Get the full name of the project (getFullName(), I use the Folders
> plugin).
> * Change the description of a project.
> * Get the Ownership plugin of a project.
>
> And son on.
>
> And for "binding variables" I mean what are the variables I can use in
> pipeline scripts, i.e., currentBuild is a binding Variable (when I try to
> use a non defined variable, for example, project, the error I get is
> undefined Binding Variable).
>
> So, where can I find documentation about pipeline that says something like
> "You can use the currentBuild variable in pipeline scripts to...".
>
> Thank you for your help.
>
> El jueves, 25 de agosto de 2016, 19:53:58 (UTC+2), Jesse Glick escribió:
>>
>> On Thu, Aug 25, 2016 at 1:49 PM, Ramón Rial <[email protected]> wrote:
>> > With Pipeline I have the currentBuild, but this is an instance of
>> > org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper, and the
>> > method build() is private and getRawBuild is not allowed in secured
>> > environments.
>> >
>> > How can I get the project corresponding to currentBuild?
>>
>> A whitelisted equivalent to `.rawBuild.parent` would need to be added,
>> plus whatever information you wanted to get from _that_. But anyway
>>
>> > Is any list of the binding variables passed to the pipeline scripts?
>>
>> What do you mean by “the binding variables”? If you stated your goal
>> up front it might be easier to help you.
>>
>
--
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/23f68876-ede8-4e63-ac1e-4a214f172c70%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
