[JIRA] [email-ext] (JENKINS-20692) Optionally show action in CHANGES token
Alex Earl commented on JENKINS-20692 Optionally show action in CHANGES token No, this fix won't be in until 2.38, which I am still doing some testing on and trying to get some more bug fixes into. 2.37.2.2 was a bug fix release for a specific purpose. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-20692) Optionally show action in CHANGES token
Simon Stassen commented on JENKINS-20692 Optionally show action in CHANGES token Hi Alex, not sure about the process... I just wanted to check if this fix should be in the latest 2.37.2.2 build? And if not, could this be included in the next build? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-20692) Optionally show action in CHANGES token
Alex Earl resolved JENKINS-20692 as Fixed Optionally show action in CHANGES token Added %a and %d for pathFormat option. Change By: Alex Earl (29/Jan/14 4:28 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-20692) Optionally show action in CHANGES token
SCM/JIRA link daemon commented on JENKINS-20692 Optionally show action in CHANGES token Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/plugins/content/ChangesSinceLastBuildContent.java src/test/java/hudson/plugins/emailext/plugins/content/ChangesSinceLastBuildContentTest.java http://jenkins-ci.org/commit/email-ext-plugin/6d57206bb4b541a6504d77b08ad7fcabcfe59790 Log: Fix JENKINS-20692 Added %a and %d to the pathFormat formatting options. %a will display the getName of the EditType %d will display the getDescription of the EditType If getAffectedFiles is not implemented by the SCM, then "Unknown" will be put displayed for each %a anf %d This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-20692) Optionally show action in CHANGES token
Alex Earl commented on JENKINS-20692 Optionally show action in CHANGES token According to the comment on getAffectedFiles, it's possible that an SCM might not implement getAffectedFiles "Noted: since this is a new interface, some of the SCMs may not have implemented this interface. The default implementation for this interface is throw UnsupportedOperationException" Would probably need a fallback to getAffectedPaths in the case of an UnsupportedOperationException. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-20692) Optionally show action in CHANGES token
Simon Stassen edited a comment on JENKINS-20692 Optionally show action in CHANGES token I see this is more complex than what I originally thought - the action attribute is not made available in hudson.scm.ChangeLogSet http://javadoc.jenkins-ci.org/hudson/scm/ChangeLogSet.Entry.html Could we use getAffectedFiles instead of getAffectedPaths, and optionally use getEditType? http://javadoc.jenkins-ci.org/hudson/scm/ChangeLogSet.AffectedFile.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-20692) Optionally show action in CHANGES token
Simon Stassen edited a comment on JENKINS-20692 Optionally show action in CHANGES token I see this is more complex than what I originally thought - the action attribute is not made available in hudson.scm.ChangeLogSet http://javadoc.jenkins-ci.org/hudson/scm/ChangeLogSet.Entry.html Could we use getAffectedFiles instead of getAffectedPaths, and optionally use getEditType? http://javadoc.jenkins-ci.org/hudson/scm/ChangeLogSet.AffectedFile.html#getEditType() This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-20692) Optionally show action in CHANGES token
Simon Stassen edited a comment on JENKINS-20692 Optionally show action in CHANGES token I see this is more complex than what I originally thought - the action attribute is not made available in hudson.scm.ChangeLogSet http://javadoc.jenkins-ci.org/hudson/scm/ChangeLogSet.Entry.html Could we use getAffectedFiles instead of getAffectedPaths, and optionally use getEditType? http://javadoc.jenkins-ci.org/hudson/scm/SubversionChangeLogSet.Path.html#getEditType() This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-20692) Optionally show action in CHANGES token
Simon Stassen commented on JENKINS-20692 Optionally show action in CHANGES token I see this is more complex than what I originally thought - the action attribute is not made available in hudson.scm.ChangeLogSet http://javadoc.jenkins-ci.org/hudson/scm/ChangeLogSet.Entry.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-20692) Optionally show action in CHANGES token
Simon Stassen
created JENKINS-20692
Optionally show action in CHANGES token
Issue Type:
Improvement
Assignee:
Alex Earl
Components:
email-ext
Created:
21/Nov/13 1:41 AM
Description:
Is it possible to use the action attribute, from the changelog.xml file to allow me to use something like this in Email-Ext:
${CHANGES, pathFormat="\t%a%p\n"
where %a is a new variable that can be either Added, Modified or Deleted (or maybe use + and -)
Project:
Jenkins
Priority:
Minor
Reporter:
Simon Stassen
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
