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

Build environment variables are not always correctly set for executing build steps.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • tfs-plugin
    • None
    • Currently running a build in Jenkins (1.546) using the TFS Plugin 3.1.1.
      Also in TFS plugin 4.1

      Configured TFS Plugin to use update only

      • Build Step 1: Execute Shell (Print out TFS_CHANGESET)
      • Build Step 2: Execute Maven Build (Maven 3.1.1)
      • Build Step 3: Execute Shell (rolling_label.sh ${WORKSPACE} ${BUILD_NUMBER} ${TFS_CHANGESET})

      The execution build step Nr. 3 fails from time to time by the cause that the TFS_CHANGESET variable has not been set which can't be cause within the build step 1 it will be correctly printed out to the jenkins console.

      The following is the output in case of a failure:

      [portal-HEAD] $ /usr/bin/bash -xe /temp/hudson1539801749356572417.sh
      + /build/label.sh /opt/build/xxxxx-HEAD 4855
      

      The following is the output in case of success:

      [Current build status] check if current [SUCCESS] is worse or equals then [SUCCESS] and better or equals then [SUCCESS]
      Run condition [Current build status] enabling perform for step [Execute shell]
      [xxxxx-HEAD] $ /usr/bin/bash -xe /temp/hudson7426258207171993715.sh
       + /build/label.sh /opt/build/xxxxx-HEAD 4856 173224
       Updated label xxxxxx_HEAD@$/CCB
       [WARNINGS] Parsing warnings in console log with parser Maven
      

      which shows that only the TFS_CHANGESET is not being set.

            dastahel David Staheli
            khmarbaise Karl-Heinz Marbaise
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: