|
|
In reply to this post by JIRA noreply@jenkins-ci.org
 |
|
|
|
|
Change By:
|
Daniel Beck
(20/Sep/12 7:54 AM)
|
|
Summary:
|
Allow
Add variable resolution to
"additional groovy class path"
to reference workspace
|
|
Description:
|
Some of my Groovy postbuild scripts are rather long due to rather complex information gathering and presentation, and I'd like to store them in SVN to get a proper version history. It'd be great if that version would be recorded alongside everything else about the build.
Currently it's only possible to specify a full absolute path as "additional groovy class path". There is no variable substitution for e.g. {{$WORKSPACE}}
or Jenkins/node level environment variables
, and relative paths don't resolve within the workspace. As I'm trying to get rid of absolute paths as much as possible (tool auto installation, working in workspace only, etc.), this is a step backwards.
Please add this feature to allow storing scripts in SVN and having them check out to e.g. {{$WORKSPACE/gpb}}
or {{$GROOVY_POSTBUILD_SCRIPTS}} (defined for each node)
and record the revision information for them there.
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
|
Locked
Major
On further thought, using $WORKSPACE breaks in a master/slave scenario, as postbuild is executed on the master. But variable resolution would still allow the global definition of an environment variable such as GROOVY_POSTBUILD_SCRIPTS_DIR and reusing that in the individual jobs – an improvement upon the current situation.