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

Notify Build Start events not resolving Environment Variables

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      It appears that the plugin does not correctly replace environment variables when it sends out "started" messages.  For example, ${COMMIT_BRANCH} is not resolved for the started message, but it is on success:

      Feature Branch Build - #1095 Started by changes from Daniel Kirkdorffer (6 file(s) changed) (Open)
      Branch: ${COMMIT_BRANCH}
      Feature Branch Build - #1095 Success after 2 min 34 sec (Open)
      No Tests found.
      Branch: EPC-648_Ordering_Filters

      This seems like a bug to me.  I can't see why the plugin wouldn't know the COMMIT_BRANCH when it sends out the "started" message.

      We are using version 2.2 of the plugin against Jenkins 2.32.2.

        Attachments

          Activity

          dankirkd Daniel Kirkdorffer created issue -
          dankirkd Daniel Kirkdorffer made changes -
          Field Original Value New Value
          Description It appears that the plugin does not correctly replace environment variables when it sends out "started" messages.  For example, $\{COMMIT_BRANCH} is not resolved for the started message, but it is on success:
          |{{Feature Branch Build - #}}{{1095}} {{Started by changes from Daniel Kirkdorffer (}}{{6}} {{file(s) changed) (Open)}}
          {{Branch: $\{COMMIT_BRANCH}}}|

          |{{Feature Branch Build - #}}{{1095}} {{Success after }}{{2}} {{min }}{{34}} {{sec (Open)}}
          {{No Tests found.}}
          {{Branch: EPC-648_Ordering_Filters}}|

           This seems like a bug to me.  I can't see why the plugin wouldn't know the COMMIT_BRANCH when it sends out the "started" message.
          It appears that the plugin does not correctly replace environment variables when it sends out "started" messages.  For example, $\{COMMIT_BRANCH} is not resolved for the started message, but it is on success:
          |{{Feature Branch Build - #}}{{1095}} {{Started by changes from Daniel Kirkdorffer (}}{{6}} {{file(s) changed) (Open)}}
           {{Branch: $\{COMMIT_BRANCH}}}|
          |{{Feature Branch Build - #}}{{1095}} {{Success after}}{{{{ }}{{2}} {{min }}{{34}} {{sec}} (Open)}}
           {{No Tests found.}}
           {{Branch: EPC-648_Ordering_Filters}}|

           This seems like a bug to me.  I can't see why the plugin wouldn't know the COMMIT_BRANCH when it sends out the "started" message.
          dankirkd Daniel Kirkdorffer made changes -
          Description It appears that the plugin does not correctly replace environment variables when it sends out "started" messages.  For example, $\{COMMIT_BRANCH} is not resolved for the started message, but it is on success:
          |{{Feature Branch Build - #}}{{1095}} {{Started by changes from Daniel Kirkdorffer (}}{{6}} {{file(s) changed) (Open)}}
           {{Branch: $\{COMMIT_BRANCH}}}|
          |{{Feature Branch Build - #}}{{1095}} {{Success after}}{{{{ }}{{2}} {{min }}{{34}} {{sec}} (Open)}}
           {{No Tests found.}}
           {{Branch: EPC-648_Ordering_Filters}}|

           This seems like a bug to me.  I can't see why the plugin wouldn't know the COMMIT_BRANCH when it sends out the "started" message.
          It appears that the plugin does not correctly replace environment variables when it sends out "started" messages.  For example, $\{COMMIT_BRANCH} is not resolved for the started message, but it is on success:
          {code:java}
          Feature Branch Build - #1095 Started by changes from Daniel Kirkdorffer (6 file(s) changed) (Open)
          Branch: ${COMMIT_BRANCH}{code}
           
          {code:java}
          Feature Branch Build - #1095 Success after 2 min 34 sec (Open)
          No Tests found.
          Branch: EPC-648_Ordering_Filters{code}
          This seems like a bug to me.  I can't see why the plugin wouldn't know the COMMIT_BRANCH when it sends out the "started" message.
          dankirkd Daniel Kirkdorffer made changes -
          Description It appears that the plugin does not correctly replace environment variables when it sends out "started" messages.  For example, $\{COMMIT_BRANCH} is not resolved for the started message, but it is on success:
          {code:java}
          Feature Branch Build - #1095 Started by changes from Daniel Kirkdorffer (6 file(s) changed) (Open)
          Branch: ${COMMIT_BRANCH}{code}
           
          {code:java}
          Feature Branch Build - #1095 Success after 2 min 34 sec (Open)
          No Tests found.
          Branch: EPC-648_Ordering_Filters{code}
          This seems like a bug to me.  I can't see why the plugin wouldn't know the COMMIT_BRANCH when it sends out the "started" message.
          It appears that the plugin does not correctly replace environment variables when it sends out "started" messages.  For example, $\{COMMIT_BRANCH} is not resolved for the started message, but it is on success:
          {code:java}
          Feature Branch Build - #1095 Started by changes from Daniel Kirkdorffer (6 file(s) changed) (Open)
          Branch: ${COMMIT_BRANCH}{code}
          {code:java}
          Feature Branch Build - #1095 Success after 2 min 34 sec (Open)
          No Tests found.
          Branch: EPC-648_Ordering_Filters{code}
          This seems like a bug to me.  I can't see why the plugin wouldn't know the COMMIT_BRANCH when it sends out the "started" message.
          dankirkd Daniel Kirkdorffer made changes -
          Description It appears that the plugin does not correctly replace environment variables when it sends out "started" messages.  For example, $\{COMMIT_BRANCH} is not resolved for the started message, but it is on success:
          {code:java}
          Feature Branch Build - #1095 Started by changes from Daniel Kirkdorffer (6 file(s) changed) (Open)
          Branch: ${COMMIT_BRANCH}{code}
          {code:java}
          Feature Branch Build - #1095 Success after 2 min 34 sec (Open)
          No Tests found.
          Branch: EPC-648_Ordering_Filters{code}
          This seems like a bug to me.  I can't see why the plugin wouldn't know the COMMIT_BRANCH when it sends out the "started" message.
          It appears that the plugin does not correctly replace environment variables when it sends out "started" messages.  For example, $\{COMMIT_BRANCH} is not resolved for the started message, but it is on success:
          {code:java}
          Feature Branch Build - #1095 Started by changes from Daniel Kirkdorffer (6 file(s) changed) (Open)
          Branch: ${COMMIT_BRANCH}{code}
          {code:java}
          Feature Branch Build - #1095 Success after 2 min 34 sec (Open)
          No Tests found.
          Branch: EPC-648_Ordering_Filters{code}
          This seems like a bug to me.  I can't see why the plugin wouldn't know the COMMIT_BRANCH when it sends out the "started" message.

          We are using version 2.2 of the plugin against Jenkins 2.32.2.
          timja Tim Jacomb made changes -
          Issue Type Bug [ 1 ] Improvement [ 4 ]
          timja Tim Jacomb made changes -
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Fixed but Unreleased [ 10203 ]
          timja Tim Jacomb made changes -
          Status Fixed but Unreleased [ 10203 ] Closed [ 6 ]

            People

            Assignee:
            kmadel Kurt Madel
            Reporter:
            dankirkd Daniel Kirkdorffer
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: