Provides Jenkins integration with Apache Ivy.
This plugin automatically configures a build to trigger other builds based on dependency configuration via Apache Ivy.
Note: Support for Hudson has been dropped. Only Jenkins will be supported from now on.
Since Version 1.25 this plugin uses Ivy 2.4.0 internally (but it should work with Ivy 2.+ projects).
By using an Ivy project instead of a Freestyle project Jenkins can simplify the job configuration. It will auto-detect all the ivy modules you checked out, create builds for them, and automatically generate the upstream/downstream build triggers based on your Ivy dependencies.
- Click on the "New Job" link
- Enter a project name and choose "Build an Ivy project"
- Fill in your SCM details (you can choose to check out a single ivy module, or an entire branch of ivy modules)
- Choose the Ant version to build with and enter the targets you want run. Most of the options have sensible defaults so you only need to fill them in if your modules are set up differently than the default values expect. If you want to build each module as a separate job, expand the "Advanced" section and check "Build modules as separate jobs". If you are polling for changes from your SCM, you can also optionally choose to only build changed modules.
- Now on your Jenkins job page you will see a "Modules" link
- This will give you a view of all the discovered ivy modules you checked out (Note: you will need to build the project once before the modules show up)
- The upstream/downstream project build triggers will be automatically generated from the dependencies in your ivy files.
- If you chose to build the modules as separate jobs, then you can click on a module in the module view to see all the individual builds, SCM changes, artifacts, etc.
- If you want to run different targets on a certain module then you can override the default targets in the module configuration.
Upon building, it scans the ivy.xml and fills in the 'build other projects' setting, which results in output on the project page of which projects are upstream (depends on) and which are downstream (is a dependency).