Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-15210

Add variable resolution to "additional groovy class path"

    XMLWordPrintable

Details

    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.

      Attachments

        Issue Links

          Activity

            People

              jglick Jesse Glick
              danielbeck Daniel Beck
              Votes:
              6 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: