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

Would like the ability to create a changelog for jobs triggered by scripttrigger

    Details

    • Similar Issues:

      Description

      Using the ScriptTrigger plugin, I can run a script to decide whether to trigger a build.
      I would like the ability to create a changelog file so that I could display the reasons why the build was triggered.
      It's fine if the plugin just implements the parsing. I can create the xml file on my own.

        Attachments

          Activity

          Hide
          gbois Gregory Boissinot added a comment -

          Sure, it will be very convenient to have a change log as SCM for XTrigger plugins.
          However, you have already the build cause contains the polling log on the build main page.
          What do you mean about the ability to create the XML file?

          Show
          gbois Gregory Boissinot added a comment - Sure, it will be very convenient to have a change log as SCM for XTrigger plugins. However, you have already the build cause contains the polling log on the build main page. What do you mean about the ability to create the XML file?
          Hide
          rmyung Roger Myung added a comment -

          The polling log doesn't have user info, if you want to send emails.
          It also is not readable for users.

          I am referring to the changelog.xml file. Jenkins requires an implementation of ChangeLogParser and ChangeLogEntry to read the xml file. However, it does not require any specific way to create the xml file. This does not need to be done by the plugin.

          Show
          rmyung Roger Myung added a comment - The polling log doesn't have user info, if you want to send emails. It also is not readable for users. I am referring to the changelog.xml file. Jenkins requires an implementation of ChangeLogParser and ChangeLogEntry to read the xml file. However, it does not require any specific way to create the xml file. This does not need to be done by the plugin.
          Hide
          gbois Gregory Boissinot added a comment -

          For user info, it is a trigger for an environment (an external system without dedicated user). Therefore, there is no user info for a job scheduled by a XTrigger typology (such as ScriptTrigger).

          It seems there is no uniform way to generate the changelog.
          Do you have more information about this subject?

          Show
          gbois Gregory Boissinot added a comment - For user info, it is a trigger for an environment (an external system without dedicated user). Therefore, there is no user info for a job scheduled by a XTrigger typology (such as ScriptTrigger). It seems there is no uniform way to generate the changelog. Do you have more information about this subject?
          Hide
          gbois Gregory Boissinot added a comment -

          Roger,
          I come back to you again.
          Does it suits you to have a custom changelog (different from the SCM changelog)?
          The cons of this solution is to not have an uniform interface between differents builds for knowing the changeset.

          Show
          gbois Gregory Boissinot added a comment - Roger, I come back to you again. Does it suits you to have a custom changelog (different from the SCM changelog)? The cons of this solution is to not have an uniform interface between differents builds for knowing the changeset.
          Hide
          rmyung Roger Myung added a comment -

          Hi Gregory,
          I'm using the scripttrigger to do a Clearcase operation that I can't do via the plugins. I then run a query to get the change information. Currently, I'm turning the information into html and using the html publisher. However, the build will say "no changes".

          Show
          rmyung Roger Myung added a comment - Hi Gregory, I'm using the scripttrigger to do a Clearcase operation that I can't do via the plugins. I then run a query to get the change information. Currently, I'm turning the information into html and using the html publisher. However, the build will say "no changes".
          Hide
          chrisq Chris Q added a comment -

          I have the same need: I run a shell script via scripttrigger, that does some complicated git+svn+url deployment, the kind that is much easier to do out of jenkins (and kept as-is for legacy reasons as well, I don't have much choice)
          The possibility to set changelog.xml to a specific content during the continuous build would be great, so that I could fill it with the correct data I can know from out of jenkins easily ! I would have real data instead of a "no changes" messages, that is true from a jenkins point of view, but not in this kind of use-case.

          Such a new feature would be great

          Show
          chrisq Chris Q added a comment - I have the same need: I run a shell script via scripttrigger, that does some complicated git+svn+url deployment, the kind that is much easier to do out of jenkins (and kept as-is for legacy reasons as well, I don't have much choice) The possibility to set changelog.xml to a specific content during the continuous build would be great, so that I could fill it with the correct data I can know from out of jenkins easily ! I would have real data instead of a "no changes" messages, that is true from a jenkins point of view, but not in this kind of use-case. Such a new feature would be great
          Hide
          boomboom Steven Owens added a comment -

          It looks like this has been stagnant for some time. I think the feature would be great also.

          Show
          boomboom Steven Owens added a comment - It looks like this has been stagnant for some time. I think the feature would be great also.

            People

            • Assignee:
              gbois Gregory Boissinot
              Reporter:
              rmyung Roger Myung
            • Votes:
              4 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated: