I've used a modified version of the scripts found on
https://support.cloudbees.com/hc/en-us/articles/217630098-How-to-access-Changelogs-in-a-Pipeline-Job-
to great success by putting them as @NonCPS on the bottom of my declarative
pipeline. Just recently I have moved the script to a global library that is
now referenced in each corresponding job.
On Wednesday, July 26, 2017 at 10:56:01 AM UTC-5, Joaquin Henriquez wrote:
>
> Hi Guys
>
>
>
> Does somebody has an example on the currentBuild.ChangeSets?
>
> Jenkins 2.60.2
>
>
>
> On the Jelly emailext template (seems on the forEach changeSet.logs there
> is nothing).
>
> Do I need to put anything on the declarative script before? On my file it
> is under post,success
>
>
>
> <div class="content">
>
> <!-- CHANGE SET -->
>
> <j:set var="changeSet" value="${build.changeSets}" />
>
> <j:if test="${changeSet!=null}">
>
> <j:set var="hadChanges" value="false" />
>
> <a href="${rooturl}${build.url}/changes">
>
> <h1>Changes</h1>
>
> </a>
>
> <j:forEach var="cs" items="${changeSet.logs}" varStatus="loop">
>
> <j:set var="hadChanges" value="true" />
>
> <h2>${cs.msgAnnotated}</h2>
>
> <p>by <em>${cs.author}</em></p>
>
> <table>
>
> <j:forEach var="p" items="${cs.affectedFiles}">
>
> <tr>
>
> <td width="10%">${spc}${p.editType.name}</td>
>
> <td>
>
> <tt>${p.path}</tt>
>
> </td>
>
> </tr>
>
> </j:forEach>
>
> </table>
>
> </j:forEach>
>
> <j:if test="${!hadChanges}">
>
> <p>No Changes</p>
>
> </j:if>
>
> <br />
>
> </j:if>
>
> </div>
>
>
>
>
>
> <http://localhost/>
> *Changes <http://localhost/>*
>
>
>
> No Changes
>
>
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/53a9a81a-e8d3-4fc9-825e-80ad2f083db6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
