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

Jenkins environment variables are not evaluated

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: text-finder-plugin
    • Labels:
      None
    • Environment:
      Jenkins 2.263.4
      Text-Finder 1.15
      Freestyle projects are used
    • Similar Issues:

      Description

      The environment variables provided by Jenkins itself like e.g. $BUILD_TAG or $BUILD_NO are no evaluated by the plugin and are processed as plain test. For example:

      • Assuming that this is the fifth build. / $BUILD_NO is evaluated to 5
      • The Maven plugin will evaluated the command "clean install l Maven$BUILD_NUMBER.log" and store the maven log file with the filename "Maven-5.log".
      • Archiving the build artefacts with "Maven-$BUILD_NUMBER.log" will archive the file "Maven-5.log".
      • Using the text finder to find a pattern in "Maven-$BUILD_NUMBER.log" prints "[Text Finder] File set 'Maven-$BUILD_NUMBER.log' is empty"

      Nominal behaviour: Using the text finder to find a pattern in "Maven-%BUILD_NUMBER.log" checks the file Maven-5.log for the specified pattern.

        Attachments

          Activity

          Hide
          basil Basil Crow added a comment -

          Hey Christoph, I would love to see this feature implemented. Pull requests are welcome!

          Show
          basil Basil Crow added a comment - Hey Christoph , I would love to see this feature implemented. Pull requests are welcome!

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            exojack Christoph
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: