XTrigger Plugin

Skip to end of metadata
Go to start of metadata

Plugin Information

Plugin ID xtrigger Changes In Latest Release
Since Latest Release
Latest Release
Latest Release Date
Required Core
Dependencies
0.54
May 08, 2013
1.461
ivytrigger (version:0.26)
buildresult-trigger (version:0.10)
urltrigger (version:0.31)
fstrigger (version:0.34)
scripttrigger (version:0.28)
Source Code
Issue Tracking
Maintainer(s)
GitHub
Open Issues
Gregory Boissinot (id: gbois)
Usage Installations 2013-Apr 399
2013-May 408
2013-Jun 443
2013-Jul 447
2013-Aug 439
2013-Sep 470
2013-Oct 514
2013-Nov 500
2013-Dec 498
2014-Jan 553
2014-Feb 538
2014-Mar 569


The XTrigger plugin makes it possible to monitor different environments (filesystem, jobs result, url response, binary repository and so on) and triggers a build if there is at least one change between two checks.
The plugin is intended to dev, QA and Ops users.

Features

The plug-in provides an aggregation of the following plugins for the Jenkins update center:

If you download and install the XTrigger from the update center, all the above plugins will be downloaded and installed automatically.
Additionally, all these plugins will be displayed in the log at startup.

In all cases, you can combine the usage of these plugins. For example, in a same job, IvyTrigger Plugin and ScriptTrigger Plugin can be activated.

Use cases

A pipeline

A first Jenkins job monitors developers commits from a SCM. A new build (application build + unit tests) is scheduled if changes are detected. The first job produces build outputs (logs, artifacts stored in repository and so on).
Note: This job can be also detected by a trigger stored in the SCM (if the chosen SCM provides this feature).

A second job monitors these build outputs and the job is scheduled if changes are detected between 2 checks.
Note: In the below diagram, build outputs are stored in a file-system. However, you can use any kind of resources. XTrigger plugin enables you to configure a poll for any kind of environment.

This configuration makes it possible to avoid having an hard-coded dependency between Jenkins jobs (upstream and downstream jobs).
The second job is scheduled by a condition applied to an external resource (filesystem, build results, url response, ...)

Automate your CI processes with external components from sub-contractors

How to automate this typical use case is:

  • sub-contractors develop externals components or libraries
  • you build applications on these external components
  • On development phase, you want to retrieve a recent version (often the last) and build (compile+test) your applications with these latest components versions.

Solution:
You often share between you and them, a binary repository (managed for example by one of the following tools: Sonatype Nexus, JFrog Artifactory, Apache Archiva, ...).

XTrigger plugin enables you to trigger jobs when a dependency library in the binary repository has changed
In the Java world, dependency management can expressed for example with Ivy or Maven.

Example

  • Sub-contractors develop and share a component A
  • You develop an application B. And B has dependency on A at compile time.
  • In your dependency management descriptor of B, you express that you want the latest version of a branch
    (e.g. in Maven: e.g. 2.0-SNAPSHOT and in Ivy 2.+ or the latest from a status)
  • Sub-contractors push their new versions
  • Your Jenkins infrastructure with your dedicated job on B poll if there are new versions of A in the shared binary repository.

Note: In the above use case, your Jenkins instances are not shared: you have a dedicated Jenkins instance and sub-contractors can have their
Jenkins instances.
Note: XTRigger provides also a typology through the buildresult-trigger plugin (aka Job trigger) to achieve the same thing in the case you have a shared Jenkins instance).

Changelog

Release 0.54

* Update to URLTrigger Plugin 0.31
* Update to ScriptTrigger Plugin 0.28
* Update to FSTrigger Plugin 0.36
* Update to BuildResultTrigger Plugin 0.10
* Update to IvyTrigger Plugin 0.26

Release 0.53

* Update to URLTrigger Plugin 0.24

Release 0.52

* Update to ScriptTrigger Plugin 0.21

Release 0.51

* Update to URLTrigger Plugin 0.23

Release 0.50

* Update to URLTrigger Plugin 0.21

Release 0.49

* Update to FSTrigger Plugin 0.33
* Update to BuildResultTrigger Plugin 0.8

Release 0.48

* Update to ScriptTrigger Plugin 0.20
* Update to URLTrigger Plugin 0.20
* Update to IvyTrigger Plugin 0.22
* Update to FSTrigger Plugin 0.32

Release 0.47

* Update to URLTrigger Plugin 0.19

Release 0.46

* Update to ScriptTrigger Plugin 0.19
* Update to URLTrigger Plugin 0.18

Release 0.45

* Update to IvyTrigger Plugin 0.21

Release 0.44

* Update to ScriptTrigger Plugin 0.18

Release 0.43

* Update to BuildResultTrigger Plugin 0.7

Release 0.42

* Update to IvyTrigger Plugin 0.20

Release 0.41

* Update to ScriptTrigger Plugin 0.17

Release 0.40

* Update to URLTrigger Plugin 0.16

Release 0.39

* Update to BuildResultTrigger Plugin 0.6

Release 0.38

* Update to IvyTrigger Plugin 0.19
* Update to ScriptTrigger Plugin 0.16

Release 0.37

* Update to IvyTrigger Plugin 0.18

Release 0.36

* Update to FSTrigger Plugin 0.30

Release 0.35

* Update to IvyTrigger Plugin 0.16
* Update to URLTrigger Plugin 0.15

Release 0.34

* Update to FSTrigger Plugin 0.29

Release 0.33

* Update to xtrigger-lib 0.8
** Fix issue #12888 - Would like to have fstrigger show what file changed in the build cause
* Update to FSTrigger Plugin 0.28
* Update to IvyTrigger Plugin 0.14
* Update to URLTrigger Plugin 0.14
* Update to ScriptTrigger Plugin 0.15
* Update to BuildResultTrigger Plugin 0.5

Release 0.32

* Update to FSTrigger Plugin 0.27

Release 0.31

* Update to IvyTrigger Plugin 0.13
* Update to URLTrigger Plugin 0.13

Release 0.30

* Update to IvyTrigger Plugin 0.12

Release 0.29

* Update to IvyTrigger Plugin 0.11

Release 0.28

* Update to FSTrigger Plugin 0.26
* Update to IvyTrigger Plugin 0.10
* Update to URLTrigger Plugin 0.11
* Update to ScriptTrigger Plugin 0.14
* Update to xtrigger-lib 0.7
** Fix polling node choice
** Add actions

Release 0.27

* Update to FSTrigger Plugin 0.24

Release 0.26

* Update to FSTrigger Plugin 0.23

Release 0.25

* Update to IvyTrigger Plugin 0.9

Release 0.24

* Update to IvyTrigger Plugin 0.8

Release 0.23

* Update to FSTrigger Plugin 0.21
* Update to IvyTrigger Plugin 0.7
* Update to URLTrigger Plugin 0.10

Release 0.22

* Update to ScriptTrigger Plugin 0.13
* Update to FSTrigger Plugin 0.20
* Update to IvyTrigger Plugin 0.6
* Update to URLTrigger Plugin 0.9

Release 0.21

* Update to ScriptTrigger Plugin 0.12
* Update to FSTrigger Plugin 0.18
* Update to IvyTrigger Plugin 0.5
* Update to URLTrigger Plugin 0.8

Release 0.20

* Update to ScriptTrigger Plugin 0.11.1

Release 0.19

* Update to ScriptTrigger Plugin 0.11

Release 0.18

* Update to ScriptTrigger Plugin 0.10

Release 0.17

* Update to FSTrigger Plugin 0.17

Release 0.16

* Update to FSTrigger Plugin 0.16

Release 0.15

* Update to IvyTrigger Plugin 0.4

Release 0.14

* Updated to URLTrigger Plugin 0.7

Release 0.13

* Update to URLTrigger Plugin 0.6

Release 0.12

* Update to ScriptTrigger Plugin 0.9

Release 0.11

* Update to ScriptTrigger Plugin 0.8
* Update to IvyTrigger Plugin 0.3

Release 0.10

* Update to FSTrigger Plugin 0.15
* Update to BuildResultTrigger Plugin 0.4
* Build for 1.409 (compatible with LTS)

Release 0.9

* Update to FSTrigger Plugin 0.14

Release 0.8

* Update to FSTrigger Plugin 0.13

Release 0.7

* Update to FSTrigger Plugin 0.12

Release 0.6

* Update to URLTrigger Plugin 0.5.1

Release 0.5

* Update to BuildResultTrigger Plugin 0.3

Release 0.4

* Update to URLTrigger Plugin 0.5
* Update to FSTrigger Plugin 0.11
* Update to ScriptTrigger Plugin 0.7

Release 0.3

* Update to URLTrigger Plugin 0.4.2
* Update to BuildResultTrigger Plugin 0.2

Release 0.2

* Update to ScriptTrigger Plugin 0.6
* Add a dependency to the BuildResultTrigger

Release 0.1

* Initial release

Labels

Edit
plugin-trigger plugin-trigger Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Add Comment