The following plugin provides functionality available through Pipeline-compatible steps. Read more about how to integrate steps into your Pipeline in the Steps section of the Pipeline Syntax page.
For a list of other such plugins, see the Pipeline Steps Reference page.
$class: 'YouTrackProjectProperty'
siteName : String
pluginEnabled : boolean
commentsEnabled : boolean
commandsEnabled : boolean
Enabling makes it possible to execute commands from the VCS commit message. It is inspired by how YouTrack integrates with TeamCity, as described here. It does however not support batch commands.
In short after #issue-id
the rest of the line is interpreted as a command an sent to YouTrack. If the next line does not contain a # it will be considered as a comment to the command applied.
An extra option in this integration is to write !#issue-id command
and the command will be applied, but silently, that is, watchers of the issue will not be notified.
runAsEnabled : boolean
annotationsEnabled : boolean
linkVisibility : String
stateFieldName : String
fixedValues : String
silentCommands : boolean
silentLinks : boolean
executeProjectLimits : String
trackCommits : boolean
Enabling this will globally store the revision ids for the comment and use this to prevent commits being processed multiple times. This is useful if there is a job per branch. The commit ids processed will be stored in Jenkins, so if the jobs for each branch is on different Jenkins intances this will not work.
This option has to be checked for all jobs were the same commit can be in the changelog, i.e. if there is a development job and a production job, then the option has to be checked for both.
project : String
commentText : String
The text for the comment to send to YouTrack for linking back to this build. It defaults to the URL for the build and the revision id(s) for the change(s). Setting a text here overrides that.
The text is interpreted by the Groovy SimpleTemplateEngine, see http://groovy.codehaus.org/api/groovy/text/SimpleTemplateEngine.html .
There are two variables available: build and entries, where build is an object of type hudson.model.AbstractBuild
and entries is a list of hudson.scm.ChangeLogSet.Entry
objects. Therefore a template can be something like:
Related build: $build.absoluteUrl<% entries.each { %> [Change: ${it.commitId}|http://sourcecodebrowser?change=${it.commitId}] <% } %>
failureMode
NONE
, UNSTABLE
, FAILURE
commentTextSecure
The text for the comment to send to YouTrack for linking back to this build. It defaults to the URL for the build and the revision id(s) for the change(s). Setting a text here overrides that.
The text you enter is executed as a Groovy script
There are two variables available: build and entries, where build is an object of type hudson.model.AbstractBuild
and entries is a list of hudson.scm.ChangeLogSet.Entry
objects. Therefore a template can be something like:
def result = "" result += "Related build: $build.absoluteUrl\n" entries.each { result += "[Change: ${it.commitId}|http://sourcecodebrowser?change=${it.commitId}]\n" } result
script : String
sandbox : boolean
classpath
path : String
oldPath : String
(optional)
shouldBeApproved : boolean
(optional)
oldScript : String
(optional)
Please submit your feedback about this page through this quick form.
Alternatively, if you don't wish to complete the quick form, you can simply indicate if you found this page helpful?
See existing feedback here.