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.
getLastChangesPublisher
: Get Last Changes Publishersince
PREVIOUS_REVISION
, LAST_SUCCESSFUL_BUILD
, LAST_TAG
format
LINE
, SIDE
matching
NONE
, LINE
, WORD
showFiles : boolean
synchronisedScroll : boolean
matchWordsThreshold : String
matchingMaxComparisons : String
specificRevision : String
vcsDir : String
specificBuild : String
publishLastChanges
: publish the changespublisher
class com.github.jenkins.lastchanges.pipeline.LastChangesPublisherScript
lastChanges
: Publish Last ChangesShows build last changes via rich VCS diff between revisions using Diff2Html.
This plugin expects a .git or .svn folder on your job workspace.
After job execution the plugin will generate a html diff from current
and a previous
revision.
Note that the previous revision
can be:
A provided revision
id;
Revision of Last successful build
;
Revision of anspecific build
;
Revision of Last tag
;
|
By default previous revision is current revision -1. |
|
You can use parameters in SpecificRevision . In case of git, expressions like HEAD^^ can be used. |
To get most from this plugin use periodically SCM pooling to Trigger your Build, more details here.
since
(optional)
PREVIOUS_REVISION
, LAST_SUCCESSFUL_BUILD
, LAST_TAG
format
(optional)
LINE
, SIDE
matching
(optional)
NONE
, LINE
, WORD
showFiles : boolean
(optional)
synchronisedScroll : boolean
(optional)
matchWordsThreshold : String
(optional)
matchingMaxComparisons : String
(optional)
specificRevision : String
(optional)
vcsDir : String
(optional)
specificBuild : 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.