XCTORY-1 Add unit tests to improve coverage
XCTORY-2 Add project creation and edition to the web UI
XCTORY-3 Add SCM integration
XCTORY-4 Improve Web UI
XCTORY-5 Authentication and Authorization
XCTORY-6 Add unit test to the web UI
XCTORY-7 Add form validation (client-side and server-side)
XCTORY-8 Review and document concurency
XCTORY-9 review agent and jobs model
XCTORY-10 SCM Polling
XCTORY-11 review publishing architecture
XCTORY-12 JUnit reports
XCTORY-13 push is not working properly
XCTORY-14 use cometd as push mechanism
XCTORY-15 log auto update fix and improvement
XCTORY-16 Easy SCM URL configuration
XCTORY-17 deal with SCM authentication without displaying password in the SCM URL
XCTORY-18 change logs
XCTORY-19 remote agents
XCTORY-20 failure recovery
XCTORY-21 improve job distribution strategy
XCTORY-22 advanced job result sharing
XCTORY-23 user management UI
XCTORY-24 fine grain authorization based adaptation of UI
XCTORY-25 improve notifications
XCTORY-26 review concept of project: introduce job plan
XCTORY-27 search job plans
XCTORY-28 differential reporting
XCTORY-29 compilation report
XCTORY-30 workspace report
XCTORY-31 artifacts report
XCTORY-32 emma report
XCTORY-33 checkstyle report
XCTORY-34 PMD report
XCTORY-35 Findbugs report
XCTORY-36 javadoc report
XCTORY-37 replay job
XCTORY-38 label job
XCTORY-39 improve job progress bar
XCTORY-40 handle job dependencies
XCTORY-41 improve annotation results UI
XCTORY-42 Use Ivy to detect job dependencies
Created by: xavier
on: 7/18/07
Updated by: xavier
on: 9/21/07
Assigned to: xavier

Job dependencies handling has been recently implemented, but still requires a manual setup. Being able to reuse external project metadata would be very nice.

Using Ivy for this purpose is well suited, since it handles both Ivy format and pom files (maven 2 format).
XCTORY-43 Improve annotation differential reporting
XCTORY-44 Review job plan page
XCTORY-45 Add summary tab to job page
XCTORY-46 Use change logs to fill in why and who fields in jobs
XCTORY-47 Add SCM logs to job logs
XCTORY-48 job activity
XCTORY-49 Improve change log details
XCTORY-50 Add inline documentation
XCTORY-51 Add success and failing time
XCTORY-52 Modularize xooctory

Enter new issue

[XCTORY-42] Use Ivy to detect job dependencies edit

Comments

xavier (9/21/07)

It’s now possible to use Ivy to detect dependencies and trigger jobs accordingly.

To do so you need to add an IvyResource (in the what) to all your plans involved in Ivy dependencies (either as dependencies or modules depending on dependencies). Then you add an ivy-dependency-trigger to the triggers of the module depending on dependencies (adding such a trigger on a module with an ivy resource but without dependencies doesn’t hurt though).

For the moment it’s not possible to configure the ivy settings, but it doesn’t really matter since the revisions used are those from the SCM ivy file, which usually do not have revision, and thus Ivy dependency trigger will only work with latest.integration dependencies. To improve that, we should detect Ivy publication and use the published version to detect if a job trigger is required. In this case configuring settings would be necessary in case of custom version matcher.

The Ivy resource will also later be used as a true resource, able to resolve dependencies when preparing the job. This will allow better job dispatching, taking into account job dependencies, including third party libraries. But it’s another subject…