Setting HP_RUN_ID only works if the build is not parameterized. If it is parameterized, HP_RUN_ID does not get passed to subsequent Ant scripts.

      For it to work with parameterized builds also, you need to check for existing string parameters, merge in the new one, and replace the existing parameters.

      See the attached patch for a fix.

      thanks

          [JENKINS-34821] HP_RUN_ID not available in parameterized builds

          Fima - please have alook

          Tal Abramovich added a comment - Fima - please have alook

          Yafim Kazak added a comment -

          Yafim Kazak added a comment - Might be related to https://issues.jenkins-ci.org/browse/JENKINS-39654 orenpelzman - is it?

          John Gregg added a comment -

          I don't think these are the same. I can think of a couple of ways to test:

          For NON-parameterized builds, is HP_RUN_ID available after the build step completes without the security workaround in JENKINS-39654?

          For parameterized builds, is HP_RUN_ID available after the build step completes with the security workaround in JENKINS-39654?

          I think the two things are unrelated.

          thanks

          John Gregg added a comment - I don't think these are the same. I can think of a couple of ways to test: For NON-parameterized builds, is HP_RUN_ID available after the build step completes without the security workaround in JENKINS-39654 ? For parameterized builds, is HP_RUN_ID available after the build step completes with the security workaround in JENKINS-39654 ? I think the two things are unrelated. thanks

            bemh Hanan Bem
            john_gregg John Gregg
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: