[Issue 745] New - build trigger on all dependencies for maven2 projects

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[Issue 745] New - build trigger on all dependencies for maven2 projects

eirikma
https://hudson.dev.java.net/issues/show_bug.cgi?id=745
                 Issue #|745
                 Summary|build trigger on all dependencies for maven2 projects
               Component|hudson
                 Version|current
                Platform|All
              OS/Version|All
                     URL|
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|ENHANCEMENT
                Priority|P3
            Subcomponent|maven2
             Assigned to|issues@hudson
             Reported by|eirikma






------- Additional comments from [hidden email] Mon Aug 20 10:15:30 +0000 2007 -------
Maven2 modules should have an option to monitor updates of dependencies as build
trigger. Currently only modules that build in the same hudson-instance are able
to trigger a rebuild of downstream modules. It could be usefull to have a
rebuild triggered by a new version of any dependency.

URL monitor as suggested in issue 744 could be used to implement this.

Dependencies could be collected from the previous build. They don't change that
often, and, if SCM build trigging is used as well, committed updates of
dependencies in pom.xml would normally trigger a build anyway.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Issue 745] build trigger on all dependencies for maven2 projects

kohsuke-djn
https://hudson.dev.java.net/issues/show_bug.cgi?id=745






------- Additional comments from [hidden email] Tue Aug 21 00:54:15 +0000 2007 -------
So I guess the idea here is that we occasionally download maven-metadata.xml for
the snapshot dependencies and check the timestamp of the latest snapshot?

Oh, and I guess we could also do the same for the release dependency.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[Issue 745] build trigger on all dependencies for maven2 projects

eirikma
In reply to this post by eirikma
https://hudson.dev.java.net/issues/show_bug.cgi?id=745



User eirikma changed the following:

                What    |Old value                 |New value
================================================================================
                Priority|P3                        |P4
--------------------------------------------------------------------------------




------- Additional comments from [hidden email] Tue Aug 21 09:20:17 +0000 2007 -------
Well, I lowered the pri on this one, as it is more of a nice-to-have feature. I
don't know about maven-metadata, The idea was to piggyback on top of http url
monitoring (issue 744).

The idea is that Hudson tracks all the dependencies for maven projects, and is
even able to tell the fingerprint and originating build number for dependencies
that are built by the same hudson instance. The other dependencies are only
reported to be 'outside hudson'. These could be tracked for change and used as
build triggers pretty much 'automagically', just like builds of depending
modules do inside hudson.

For those dependencies that are 'inside hudson' (e.g. inside _this_ hudson),
build-trigging of dependent modules work very well, at least for all development
on head. Seems like managing various versions/branches of the same module
confuses hudson, so we use separate hudson-instances for projects that have
branched some modules. Naturally, in a large organization this leads to
dependencies on modules built on other instances (or with cruise / cnuum, as
some projects still use).

Once tracking of http urls as build trigger is in place (as of issue 744), maven
modules could actually monitor all dependencies as build triggers. Hudson knows
what 'outside hudson' dependencies each module has (from last build), and http
urls can easily be constructed against the repositories used by the module. I
assume hudson is able to find the repositories used in each maven module. Then
it could construct urls automatically for outside-hudson dependencies and try
these against the repositories. I assume a running hudson instance is able to
'learn' which files that are in which repositories (404 from the others).

This feature would be a convenience over manually configuring http monitor urls
for all external dependencies, and should adapt to changes in dependencies by
itself.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]