https://github.com/jenkinsci/ivy-plugin

Jenkins ivy plugin
https://github.com/jenkinsci/ivy-plugin

adopt-this-plugin

Last synced: 5 days ago
JSON representation

Jenkins ivy plugin

• Host: GitHub
• URL: https://github.com/jenkinsci/ivy-plugin
• Owner: jenkinsci
• License: mit
• Created: 2010-12-13T05:42:36.000Z (about 14 years ago)
• Default Branch: master
• Last Pushed: 2024-12-01T21:10:36.000Z (21 days ago)
• Last Synced: 2024-12-01T22:21:50.676Z (21 days ago)
• Topics: adopt-this-plugin
• Language: Java
• Homepage: https://plugins.jenkins.io/ivy/
• Size: 1020 KB
• Stars: 16
• Watchers: 99
• Forks: 43
• Open Issues: 3
• Metadata Files:
  • Readme: README.md
  • Changelog: CHANGELOG.md
  • License: LICENSE-2.0.txt
  • Codeowners: .github/CODEOWNERS

Awesome Lists containing this project

README

        
# Ivy Plugin

Provides Jenkins integration with [Apache Ivy](http://ant.apache.org/ivy/).

This plugin automatically configures a build to trigger other builds

based on dependency configuration via [Apache Ivy](http://ant.apache.org/ivy).

## Supported versions

Since Version 2.6 this plugin uses Ivy 2.5.2 internally.

## Creating an Ivy Project (added in version 1.0)

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.

1.  Click on the "New Job" link

    ![](docs/images/new-job.png)

2.  Enter a project name and choose "Build an Ivy project"

    ![](docs/images/new-ivy-project.png)

3.  Fill in your SCM details (you can choose to check out a single ivy

    module, or an entire branch of ivy modules)

4.  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.

    ![](docs/images/ivy-project-configuration.png)

5.  Now on your Jenkins job page you will see a "Modules" link

    ![](docs/images/modules.png)

6.  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)

    ![](docs/images/modules-view.png)

7.  The upstream/downstream project build triggers will be automatically

    generated from the dependencies in your ivy files.

    ![](docs/images/upstream-downstream.png)

8.  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.

9.  If you want to run different targets on a certain module then you

    can override the default targets in the module configuration.

    ![](docs/images/ivy-module-configuration.png)

## Build Trigger Configuration (for Freestyle Projects)

![](docs/images/hudson_ivy_build_trigger.png)

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).

![](docs/images/hudson_ivy_-_project_associations.png)