[Issue 673] New - SCM "catch up" feature

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

[Issue 673] New - SCM "catch up" feature

al_xipe
https://hudson.dev.java.net/issues/show_bug.cgi?id=673
                 Issue #|673
                 Summary|SCM "catch up" feature
               Component|hudson
                 Version|current
                Platform|All
              OS/Version|All
                     URL|
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|FEATURE
                Priority|P3
            Subcomponent|subversion
             Assigned to|issues@hudson
             Reported by|al_xipe






------- Additional comments from [hidden email] Tue Jul 24 17:09:04 +0000 2007 -------
My idea of this feature would be that hudson provide a mode where, instead of
just updating the workspace to the tip (latest repository revision) it would try
to catch up by updating to the next revision and run the target until it reaches
the tip.

Right now I do this manually from an ant wrapper script but integrating it in
hudson allows for fine grained identification of regressions. This is especially
important when a project get at a stage where performance improvements are the
focus.

for example, on our project, we do continuous performance testing so that the
impact of every commit is assessed by SLAMD jobs.

the principle is pretty simple but I don't know how difficult it would be to
implement.
Here's how I do it manually.
1. get workspace revision
2. get repository revision
3. if workspace revision < repository revision then trigger build

put that in a loop and you're set.

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

Reply | Threaded
Open this post in threaded view
|

[Issue 673] SCM "catch up" feature

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






------- Additional comments from [hidden email] Wed Jul 25 01:38:14 +0000 2007 -------
I think you can do this by writing a plugin and extending SubversionSCM and
registering it as a new SCM implementation.

The modified SubversionSCM could check the revision used in the last build, then
check the head revision in the server, and uses lastRev+1 to check out. If
lastRev+1 < serverRev, you can schedule another build right there.

You are doing this with Subversion, right? This doesn't make sense with CVS.

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

Reply | Threaded
Open this post in threaded view
|

[Issue 673] SCM "catch up" feature

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






------- Additional comments from [hidden email] Wed Jul 25 15:09:59 +0000 2007 -------
yes, that's with subversion. I'll add that plugin on my todo list then.

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