• Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Minor Minor
    • jabber-plugin
    • None

      The format of the build notification message is currently along the lines of:

      Project Changeset Verification build (17): SUCCESS in 1 min 14 sec:
                       http://hudson/job/Changeset%20Verification/17/
      

      Even if the build has parameters associated with it, it would be nice if the bot printed out the build parameters in the message as well, i.e.

      Project Changeset Verification build (17): SUCCESS in 1 min 14 sec:
                       http://hudson/job/Changeset%20Verification/17/  change=123 patch=2
      

          [JENKINS-6142] Print build parameters when notifiying

          kutzi added a comment -

          You mean parameters from the parametrized trigger plugin?

          kutzi added a comment - You mean parameters from the parametrized trigger plugin?

          R. Tyler Croy added a comment -

          I'm not sure what the parameterized trigger plugin does, I'm assuming it uses the built in support for build parameters though.

          I was referring to the standard build parameters option for jobs

          R. Tyler Croy added a comment - I'm not sure what the parameterized trigger plugin does, I'm assuming it uses the built in support for build parameters though. I was referring to the standard build parameters option for jobs

          kutzi added a comment -

          Oh, I had always thought that build parameters are not a part of hudson core, but only of the parametrized trigger plugin. Obviously, I was wrong.

          kutzi added a comment - Oh, I had always thought that build parameters are not a part of hudson core, but only of the parametrized trigger plugin. Obviously, I was wrong.

          kutzi added a comment -

          I'm trying to understand what you need the paramters for.
          I mean, you can always view the used parameters on the build's page.

          I don't want to make the output of the bot too verbose and there could be quite a lot parameters associated to a job.

          kutzi added a comment - I'm trying to understand what you need the paramters for. I mean, you can always view the used parameters on the build's page. I don't want to make the output of the bot too verbose and there could be quite a lot parameters associated to a job.

          derekjchoi added a comment -

          I think it's a matter of convenience though. Similar to the console output request, this one is equally as important. Suppose you work with an offshore team and they are building a release while you are sleeping and and you really want to know what version they are pushing out. I really dont want to wake up, click on a link in IM, and then parameters (that's 2 extra clicks). I just want to pick up the phone and see it on the screen immediately and put it back down. It's just like the whole Jabber initiative around hudson right? It was created for better convenience and allows us to receive notifications in a better manner than sifting through emails. If we have to click into links and navigate through a browser, it defeats the purpose of the Jabber plugin.

          You are right though, there is a workaround so it is a nice to have. I for one would certainly appreciate it

          derekjchoi added a comment - I think it's a matter of convenience though. Similar to the console output request, this one is equally as important. Suppose you work with an offshore team and they are building a release while you are sleeping and and you really want to know what version they are pushing out. I really dont want to wake up, click on a link in IM, and then parameters (that's 2 extra clicks). I just want to pick up the phone and see it on the screen immediately and put it back down. It's just like the whole Jabber initiative around hudson right? It was created for better convenience and allows us to receive notifications in a better manner than sifting through emails. If we have to click into links and navigate through a browser, it defeats the purpose of the Jabber plugin. You are right though, there is a workaround so it is a nice to have. I for one would certainly appreciate it

            Unassigned Unassigned
            rtyler R. Tyler Croy
            Votes:
            2 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: