Hi everyone,

I have a working Jenkins setup (ver 2.23), with *Pipeline jobs* that use 
*Subversion 
(SVN) *to build and test various software components.
Jobs are triggered by polling SCM changes.
Most jobs use the same SVN tree, with different include/exclude filters for 
each job.
I also have a working *JIRA *configuration, and JIRA annotation seem to 
work OK (Jenkins detects mentions of JIRA keys in commit notes and displays 
them as links to JIRA items)

Now I want to add a JIRA comment to related items, probably using 
a JiraIssueUpdater, as described 
in 
https://github.com/jenkinsci/jira-plugin/blob/master/COMPATIBILITY.md#jiraissueupdater-usage-example
However the documentation gives only a partial snippet, specific to GIT 
(unfortunately I use SVN).
I'm also not sure how the object passed to JiraIssueUpdater should be used 
in an earlier "SVN checkout" step...
* Should I create a new SVN object, just for the JiraIssueUpdater step, or 
should I reuse the same object of the SVN checkout?
* If I should reuse the object, how should it be defined for SVN checkout?
* If not, how do I specify related filters (include/exclude), credentials 
etc. for the newly created "SVN" object?

The Jenkins "Snippet Generator" does not work for JIRA steps (creates a 
useless Groovy code).
I'm not a Groovy expert, and so far used mostly the "Snippet Generator" to 
create my Groovy scripts for builds.

Can anybody help me out?

-- 
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/bf85b996-e8fc-4ce7-9733-e8f743a7065c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to