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

Grails Plugin - You can't use build.job.name=${env['JOB_NAME']} in the 'properties' box.

    XMLWordPrintable

Details

    Description

      Replacements such as build.job.name=${env['JOB_NAME']} work fine on the 'targets' line, but not in the properties box at the bottom.

      This makes configuring a parameterised build pretty ugly!

      Attachments

        Activity

          Code changed in jenkins
          User: kiy0taka
          Path:
          src/main/java/com/g2one/hudson/grails/GrailsBuilder.java
          src/test/java/com/g2one/hudson/grails/GrailsBuilderIntegrationTest.java
          http://jenkins-ci.org/commit/grails-plugin/41bc755378429754a99b37e9357053c3b57a0b71
          Log:
          eval properties. (JENKINS-7750)

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: kiy0taka Path: src/main/java/com/g2one/hudson/grails/GrailsBuilder.java src/test/java/com/g2one/hudson/grails/GrailsBuilderIntegrationTest.java http://jenkins-ci.org/commit/grails-plugin/41bc755378429754a99b37e9357053c3b57a0b71 Log: eval properties. ( JENKINS-7750 )
          alxndrsn Alex Anderson added a comment - Think this is fixed by https://github.com/jenkinsci/grails-plugin/pull/6

          nudge. We hit this today as well. Tried using $WORKSPACE to define the grails.work.dir. No go. Had to downgrade to 1.5 as well to get all the standard Jenkins env variables back. This to me seems like a blocker.

          hardwickj James Hardwick added a comment - nudge . We hit this today as well. Tried using $WORKSPACE to define the grails.work.dir. No go. Had to downgrade to 1.5 as well to get all the standard Jenkins env variables back. This to me seems like a blocker.
          tomdew Tom Dunstan added a comment -

          Downgrading to 1.5 seems to have fixed it, but not sure at what point after that the bug has been introduced, as we hadn't kept up to date with the latest plugin versions for a while.

          tomdew Tom Dunstan added a comment - Downgrading to 1.5 seems to have fixed it, but not sure at what point after that the bug has been introduced, as we hadn't kept up to date with the latest plugin versions for a while.
          tomdew Tom Dunstan added a comment -

          This has also broken using variables in the server.port, grails.project.work.dir etc fields, and breaks, among other things, using a randomised port via the port allocator plugin, which we use to run multiple builds on the same host.

          tomdew Tom Dunstan added a comment - This has also broken using variables in the server.port, grails.project.work.dir etc fields, and breaks, among other things, using a randomised port via the port allocator plugin, which we use to run multiple builds on the same host.

          People

            jeffg2one jeffg2one
            wirah wirah
            Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated: