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

Allow environment variables in phing properties

    • Icon: New Feature New Feature
    • Resolution: Fixed
    • Icon: Major Major
    • phing-plugin
    • None
    • Jenkins 1.5

      I want to use the Jenkins build number as a phing property. But it is currently not possible to dynamically include the Jenkins build id into the Phing properties area. In the same way as the Jenkins SSH plugin has several environment variables available for substitution (see below), it would be super handy if this would be possible:

      build.id=$BUILD_NUMBER

      == For reference: SSH environment variables ===
      The following variables are available to shell scripts

      BUILD_NUMBER
      The current build number, such as "153"
      BUILD_ID
      The current build id, such as "2005-08-22_23-59-59" (YYYY-MM-DD_hh-mm-ss)
      JOB_NAME
      Name of the project of this build, such as "foo" or "foo/bar"
      BUILD_TAG
      String of "jenkins-${JOB_NAME}-${BUILD_NUMBER}". Convenient to put into a resource file, a jar file, etc for easier identification.
      EXECUTOR_NUMBER
      The unique number that identifies the current executor (among executors of the same machine) that's carrying out this build. This is the number you see in the "build executor status", except that the number starts from 0, not 1.
      NODE_NAME
      Name of the slave if the build is on a slave, or "master" if run on master
      NODE_LABELS
      Whitespace-separated list of labels that the node is assigned.
      WORKSPACE
      The absolute path of the directory assigned to the build as a workspace.
      JENKINS_HOME
      The absolute path of the directory assigned on the master node for Jenkins to store data.
      JENKINS_URL
      Full URL of Jenkins, like http://server:port/jenkins/
      BUILD_URL
      Full URL of this build, like http://server:port/jenkins/job/foo/15/
      JOB_URL
      Full URL of this job, like http://server:port/jenkins/job/foo/

          [JENKINS-16967] Allow environment variables in phing properties

          Code changed in jenkins
          User: Seiji Sogabe
          Path:
          src/main/java/hudson/plugins/phing/PhingBuilder.java
          http://jenkins-ci.org/commit/phing-plugin/720a99e5e4e9616d0a3e307068ea62d5b0dccaa0
          Log:
          [FIXED JENKINS-16967] Allow environment variables in phing properties


          You received this message because you are subscribed to the Google Groups "Jenkins Commits" group.
          To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscribe@googlegroups.com.
          For more options, visit https://groups.google.com/groups/opt_out.

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Seiji Sogabe Path: src/main/java/hudson/plugins/phing/PhingBuilder.java http://jenkins-ci.org/commit/phing-plugin/720a99e5e4e9616d0a3e307068ea62d5b0dccaa0 Log: [FIXED JENKINS-16967] Allow environment variables in phing properties – You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscribe@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out .

            sogabe sogabe
            erikstielstra Erik Stielstra
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: