Build vs. Release

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

Build vs. Release

Frank Grimes
Hi All,

I'm trying to migrate to Hudson and was wondering if it were possible to have a separate "Release Now" button which could invoke a different Ant build target.

If this functionality doesn't yet exist, might I suggest the following possibilities?

1) It could simply be another option below the "Build Now" button that currently exists on the Job view
2) It could work similarly to the "Tag This Build" functionality. That way, it could be a kind of build promotion mechanism to go along with the tagging.

Thanks,

Frank Grimes


Be a better Heartthrob. Get better relationship answers from someone who knows.
Yahoo! Answers - Check it out.
Reply | Threaded
Open this post in threaded view
|

Re: Build vs. Release

CletusTSJY
Hey Grimey,

I've got my projects on three servers (two for testing, one for live releases) and made a different job for each one.  They all do the exact same thing except evoke different Ant targets.  It works pretty well using the "clone an existing job" feature.  So I just go to the "Live Deployment" job and click "Build now" and it runs the Ant task that builds and deploys to the live server.

Cameron

On 10/16/07, Frank Grimes <[hidden email]> wrote:
Hi All,

I'm trying to migrate to Hudson and was wondering if it were possible to have a separate "Release Now" button which could invoke a different Ant build target.

If this functionality doesn't yet exist, might I suggest the following possibilities?

1) It could simply be another option below the "Build Now" button that currently exists on the Job view
2) It could work similarly to the "Tag This Build" functionality. That way, it could be a kind of build promotion mechanism to go along with the tagging.

Thanks,

Frank Grimes


Be a better Heartthrob. <a href="http://us.rd.yahoo.com/evt=48255/*http://answers.yahoo.com/dir/_ylc=X3oDMTI5MGx2aThyBF9TAzIxMTU1MDAzNTIEX3MDMzk2NTQ1MTAzBHNlYwNCQUJwaWxsYXJfTklfMzYwBHNsawNQcm9kdWN0X3F1ZXN0aW9uX3BhZ2U-?link=list&amp;sid=396545433" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> Get better relationship answers from someone who knows.
Yahoo! Answers - Check it out.



--
Cameron Hinkle
Development Manager
Adaptavant
Cell: 503-998-9673
Reply | Threaded
Open this post in threaded view
|

Re: Build vs. Release

Frank Grimes
In reply to this post by Frank Grimes
Hi Cameron,

I was *really* hoping not to have to configure separate jobs to handle that!
It would introduce an explosion of maintenance overhead and make it far less intuitive to manage the lifecycle of our numerous internal projects.
I'd probably sooner dig into the code and figure out how to hack the functionality in myself.... still, maintaining a fork of Hudson isn't high on my list of things to do, either. :-)

Frank "Grimey" Grimes


----- Original Message ----
From: Cameron Hinkle <[hidden email]>
To: [hidden email]
Sent: Tuesday, October 16, 2007 2:19:36 PM
Subject: Re: Build vs. Release

Hey Grimey,

I've got my projects on three servers (two for testing, one for live releases) and made a different job for each one.  They all do the exact same thing except evoke different Ant targets.  It works pretty well using the "clone an existing job" feature.  So I just go to the "Live Deployment" job and click "Build now" and it runs the Ant task that builds and deploys to the live server.

Cameron

On 10/16/07, Frank Grimes <[hidden email]> wrote:
Hi All,

I'm trying to migrate to Hudson and was wondering if it were possible to have a separate "Release Now" button which could invoke a different Ant build target.

If this functionality doesn't yet exist, might I suggest the following possibilities?

1) It could simply be another option below the "Build Now" button that currently exists on the Job view
2) It could work similarly to the "Tag This Build" functionality. That way, it could be a kind of build promotion mechanism to go along with the tagging.

Thanks,

Frank Grimes


Be a better Heartthrob. Get better relationship answers from someone who knows.
Yahoo! Answers - Check it out.



--
Cameron Hinkle
Development Manager
Adaptavant
Cell: 503-998-9673



Be a better Heartthrob. Get better relationship answers from someone who knows.
Yahoo! Answers - Check it out.
Reply | Threaded
Open this post in threaded view
|

Re: Build vs. Release

Arnaud LACOUR
Frank,
  you could pretty easily implement that in a plugin that you deploy on your hudson instance.
that would save you the hassle of forking and would probably benefit other users out there if you host your plugin on hudson's java.net project.
cheers
-=arnaud=-

On 10/16/07, Frank Grimes <[hidden email]> wrote:
Hi Cameron,

I was *really* hoping not to have to configure separate jobs to handle that!
It would introduce an explosion of maintenance overhead and make it far less intuitive to manage the lifecycle of our numerous internal projects.
I'd probably sooner dig into the code and figure out how to hack the functionality in myself.... still, maintaining a fork of Hudson isn't high on my list of things to do, either. :-)

Frank "Grimey" Grimes



----- Original Message ----
From: Cameron Hinkle <[hidden email]>
To: [hidden email]
Sent: Tuesday, October 16, 2007 2:19:36 PM
Subject: Re: Build vs. Release

Hey Grimey,

I've got my projects on three servers (two for testing, one for live releases) and made a different job for each one.  They all do the exact same thing except evoke different Ant targets.  It works pretty well using the "clone an existing job" feature.  So I just go to the "Live Deployment" job and click "Build now" and it runs the Ant task that builds and deploys to the live server.

Cameron

On 10/16/07, Frank Grimes <[hidden email]> wrote:
Hi All,

I'm trying to migrate to Hudson and was wondering if it were possible to have a separate "Release Now" button which could invoke a different Ant build target.

If this functionality doesn't yet exist, might I suggest the following possibilities?

1) It could simply be another option below the "Build Now" button that currently exists on the Job view
2) It could work similarly to the "Tag This Build" functionality. That way, it could be a kind of build promotion mechanism to go along with the tagging.

Thanks,

Frank Grimes


Be a better Heartthrob. <a rel="nofollow" href="http://us.rd.yahoo.com/evt=48255/*http://answers.yahoo.com/dir/_ylc=X3oDMTI5MGx2aThyBF9TAzIxMTU1MDAzNTIEX3MDMzk2NTQ1MTAzBHNlYwNCQUJwaWxsYXJfTklfMzYwBHNsawNQcm9kdWN0X3F1ZXN0aW9uX3BhZ2U-?link=list&amp;sid=396545433" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> Get better relationship answers from someone who knows.
Yahoo! Answers - Check it out.



--
Cameron Hinkle
Development Manager
Adaptavant
Cell: 503-998-9673



Be a better Heartthrob. <a href="http://us.rd.yahoo.com/evt=48255/*http://answers.yahoo.com/dir/_ylc=X3oDMTI5MGx2aThyBF9TAzIxMTU1MDAzNTIEX3MDMzk2NTQ1MTAzBHNlYwNCQUJwaWxsYXJfTklfMzYwBHNsawNQcm9kdWN0X3F1ZXN0aW9uX3BhZ2U-?link=list&amp;sid=396545433" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> Get better relationship answers from someone who knows.
Yahoo! Answers - Check it out.

Reply | Threaded
Open this post in threaded view
|

Re: Build vs. Release

Frank Grimes
In reply to this post by Frank Grimes
Hi Arnaud,

I'll take a look at the plugin documentation and some samples...
If you could point me more specifically to a sample plugin that hooks into similar extension points that I would need, it would be much appreciated.

Otherwise, due to time constraints I may end up configuring duplicate projects and filtering them by view. i.e. separate Continuous Integration and Release tabs on the Hudson Dashboard.
It's far from ideal, but it should work.

Cheers,

Frank Grimes


----- Original Message ----
From: Arnaud LACOUR <[hidden email]>
To: [hidden email]
Sent: Tuesday, October 16, 2007 3:06:54 PM
Subject: Re: Build vs. Release

Frank,
  you could pretty easily implement that in a plugin that you deploy on your hudson instance.
that would save you the hassle of forking and would probably benefit other users out there if you host your plugin on hudson's java.net project.
cheers
-=arnaud=-

On 10/16/07, Frank Grimes <[hidden email]> wrote:
Hi Cameron,

I was *really* hoping not to have to configure separate jobs to handle that!
It would introduce an explosion of maintenance overhead and make it far less intuitive to manage the lifecycle of our numerous internal projects.
I'd probably sooner dig into the code and figure out how to hack the functionality in myself.... still, maintaining a fork of Hudson isn't high on my list of things to do, either. :-)

Frank "Grimey" Grimes



----- Original Message ----
From: Cameron Hinkle <[hidden email]>
To: [hidden email]
Sent: Tuesday, October 16, 2007 2:19:36 PM
Subject: Re: Build vs. Release

Hey Grimey,

I've got my projects on three servers (two for testing, one for live releases) and made a different job for each one.  They all do the exact same thing except evoke different Ant targets.  It works pretty well using the "clone an existing job" feature.  So I just go to the "Live Deployment" job and click "Build now" and it runs the Ant task that builds and deploys to the live server.

Cameron

On 10/16/07, Frank Grimes <[hidden email]> wrote:
Hi All,

I'm trying to migrate to Hudson and was wondering if it were possible to have a separate "Release Now" button which could invoke a different Ant build target.

If this functionality doesn't yet exist, might I suggest the following possibilities?

1) It could simply be another option below the "Build Now" button that currently exists on the Job view
2) It could work similarly to the "Tag This Build" functionality. That way, it could be a kind of build promotion mechanism to go along with the tagging.

Thanks,

Frank Grimes


Be a better Heartthrob. Get better relationship answers from someone who knows.
Yahoo! Answers - Check it out.



--
Cameron Hinkle
Development Manager
Adaptavant
Cell: 503-998-9673



Be a better Heartthrob. Get better relationship answers from someone who knows.
Yahoo! Answers - Check it out.




Yahoo! oneSearch: Finally, mobile search that gives answers, not web links.
Reply | Threaded
Open this post in threaded view
|

Re: Build vs. Release

Kohsuke Kawaguchi
Administrator
In reply to this post by Frank Grimes
2007/10/16, Frank Grimes <[hidden email]>:
> I'm trying to migrate to Hudson and was wondering if it were possible to
> have a separate "Release Now" button which could invoke a different Ant
> build target.

Yes. There's a "batch task" plugin in the works which lets you do
this. I should probably release this plugin, even though it still has
a lot of room for improvements.

> 1) It could simply be another option below the "Build Now" button that
> currently exists on the Job view
> 2) It could work similarly to the "Tag This Build" functionality. That way,
> it could be a kind of build promotion mechanism to go along with the
> tagging.

(2) is close to how the plugin works.

--
Kohsuke Kawaguchi

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

Reply | Threaded
Open this post in threaded view
|

RE: Re: Build vs. Release

Juhos, Pavol
Hi,

That's great news! We are also using Hudson for releasing our Maven2
project (let's call it BFLM). Our current setup looks like this:

We have a Hudson project BFLM that is doing the "continuous builds"
(i.e. is triggered by Subversion post-commit hook) and then we have
separate projects like BFLM-0.2, BFLM-0.2.1, BFLM-0.3, etc. for
individual releases.

When we want to release a new version of BFLM, say 0.3.1, we first run
"mvn release:prepare" from some development workstation (i.e. not from
Hudson) where maven-release-plugin asks for the new version. Then we
create a BFLM-0.3.1 project in Hudson (clone BFLM-0.3 in fact) and set
the SVN URL to point to the right tag (e.g.
svn://server/svn/tags/bflm-0.3.1). Next we run a single build of the
BFLM-0.3.1 project and disable further builds (it should run maven goal
"release:perform", but because of some problems we use "clean install"
instead).

This way we also have build artifacts from the released version easily
accessible through the BFLM-0.3.1 Hudson project.

I described our process to give inspiration to others and also to
receive some feedback if someone knows of a better way to do this. I
would be really happy to see some more direct support for our use case
in Hudson.

--
Pavol Juhos
[[hidden email]]

-----Original Message-----
From: [hidden email] [mailto:[hidden email]]
On Behalf Of Kohsuke Kawaguchi
Sent: Wednesday, October 17, 2007 06:59
To: [hidden email]
Subject: Re: Build vs. Release

2007/10/16, Frank Grimes <[hidden email]>:
> I'm trying to migrate to Hudson and was wondering if it were possible
to
> have a separate "Release Now" button which could invoke a different
Ant
> build target.

Yes. There's a "batch task" plugin in the works which lets you do
this. I should probably release this plugin, even though it still has
a lot of room for improvements.

> 1) It could simply be another option below the "Build Now" button that
> currently exists on the Job view
> 2) It could work similarly to the "Tag This Build" functionality. That
way,
> it could be a kind of build promotion mechanism to go along with the
> tagging.

(2) is close to how the plugin works.

--
Kohsuke Kawaguchi

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

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

Reply | Threaded
Open this post in threaded view
|

Re: Build vs. Release

Kohsuke Kawaguchi
Administrator
In reply to this post by Kohsuke Kawaguchi
Kohsuke Kawaguchi wrote:
>> 2) It could work similarly to the "Tag This Build" functionality. That way,
>> it could be a kind of build promotion mechanism to go along with the
>> tagging.
>
> (2) is close to how the plugin works.

I should mention that there's a separate build-promotion plugin in the
works, too.

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

RE: Re: Build vs. Release

tvworks
Is there an eta for the build-promotions and batch-task plugins?

-----Original Message-----
From: Kohsuke Kawaguchi [mailto:[hidden email]]
Sent: Wednesday, October 17, 2007 12:36 PM
To: [hidden email]
Subject: Re: Build vs. Release

Kohsuke Kawaguchi wrote:
>> 2) It could work similarly to the "Tag This Build" functionality.
That way,
>> it could be a kind of build promotion mechanism to go along with the
>> tagging.
>
> (2) is close to how the plugin works.

I should mention that there's a separate build-promotion plugin in the
works, too.

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

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

Reply | Threaded
Open this post in threaded view
|

Re: Re: Build vs. Release

Kohsuke Kawaguchi
Administrator
I'll try to post batch-task tomorrow.

build promotion plugin will take a bit longer, but I need it at my
work, so shouldn't take too long.

2007/10/17, Jason Chaffee <[hidden email]>:

> Is there an eta for the build-promotions and batch-task plugins?
>
> -----Original Message-----
> From: Kohsuke Kawaguchi [mailto:[hidden email]]
> Sent: Wednesday, October 17, 2007 12:36 PM
> To: [hidden email]
> Subject: Re: Build vs. Release
>
> Kohsuke Kawaguchi wrote:
> >> 2) It could work similarly to the "Tag This Build" functionality.
> That way,
> >> it could be a kind of build promotion mechanism to go along with the
> >> tagging.
> >
> > (2) is close to how the plugin works.
>
> I should mention that there's a separate build-promotion plugin in the
> works, too.
>
> --
> Kohsuke Kawaguchi
> Sun Microsystems                   [hidden email]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
Kohsuke Kawaguchi

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

Reply | Threaded
Open this post in threaded view
|

RE: Re: Build vs. Release

jblack
In reply to this post by Juhos, Pavol
Pavol,

That's a great idea.  I will try this same procedure at work and see if I can come up with any improvements.  Thanks for mentioning it.

BTW, what version of maven are you using?


Jeff

Juhos, Pavol wrote
Hi,

That's great news! We are also using Hudson for releasing our Maven2
project (let's call it BFLM). Our current setup looks like this:

We have a Hudson project BFLM that is doing the "continuous builds"
(i.e. is triggered by Subversion post-commit hook) and then we have
separate projects like BFLM-0.2, BFLM-0.2.1, BFLM-0.3, etc. for
individual releases.

When we want to release a new version of BFLM, say 0.3.1, we first run
"mvn release:prepare" from some development workstation (i.e. not from
Hudson) where maven-release-plugin asks for the new version. Then we
create a BFLM-0.3.1 project in Hudson (clone BFLM-0.3 in fact) and set
the SVN URL to point to the right tag (e.g.
svn://server/svn/tags/bflm-0.3.1). Next we run a single build of the
BFLM-0.3.1 project and disable further builds (it should run maven goal
"release:perform", but because of some problems we use "clean install"
instead).

This way we also have build artifacts from the released version easily
accessible through the BFLM-0.3.1 Hudson project.

I described our process to give inspiration to others and also to
receive some feedback if someone knows of a better way to do this. I
would be really happy to see some more direct support for our use case
in Hudson.

--
Pavol Juhos
[pjuhos@exstream.com]

-----Original Message-----
From: kohsuke.kawaguchi@gmail.com [mailto:kohsuke.kawaguchi@gmail.com]
On Behalf Of Kohsuke Kawaguchi
Sent: Wednesday, October 17, 2007 06:59
To: users@hudson.dev.java.net
Subject: Re: Build vs. Release

2007/10/16, Frank Grimes <frankgrimes97@yahoo.com>:
> I'm trying to migrate to Hudson and was wondering if it were possible
to
> have a separate "Release Now" button which could invoke a different
Ant
> build target.

Yes. There's a "batch task" plugin in the works which lets you do
this. I should probably release this plugin, even though it still has
a lot of room for improvements.

> 1) It could simply be another option below the "Build Now" button that
> currently exists on the Job view
> 2) It could work similarly to the "Tag This Build" functionality. That
way,
> it could be a kind of build promotion mechanism to go along with the
> tagging.

(2) is close to how the plugin works.

--
Kohsuke Kawaguchi

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@hudson.dev.java.net
For additional commands, e-mail: users-help@hudson.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@hudson.dev.java.net
For additional commands, e-mail: users-help@hudson.dev.java.net
Reply | Threaded
Open this post in threaded view
|

Re: Build vs. Release

Kohsuke Kawaguchi
Administrator
In reply to this post by Kohsuke Kawaguchi
Kohsuke Kawaguchi wrote:
> I'll try to post batch-task tomorrow.

Posted.

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Build vs. Release

Kohsuke Kawaguchi
Administrator
In reply to this post by Juhos, Pavol
Juhos, Pavol wrote:

> Hi,
>
> That's great news! We are also using Hudson for releasing our Maven2
> project (let's call it BFLM). Our current setup looks like this:
>
> We have a Hudson project BFLM that is doing the "continuous builds"
> (i.e. is triggered by Subversion post-commit hook) and then we have
> separate projects like BFLM-0.2, BFLM-0.2.1, BFLM-0.3, etc. for
> individual releases.
>
> When we want to release a new version of BFLM, say 0.3.1, we first run
> "mvn release:prepare" from some development workstation (i.e. not from
> Hudson) where maven-release-plugin asks for the new version. Then we
> create a BFLM-0.3.1 project in Hudson (clone BFLM-0.3 in fact) and set
> the SVN URL to point to the right tag (e.g.
> svn://server/svn/tags/bflm-0.3.1). Next we run a single build of the
> BFLM-0.3.1 project and disable further builds (it should run maven goal
> "release:perform", but because of some problems we use "clean install"
> instead).
>
> This way we also have build artifacts from the released version easily
> accessible through the BFLM-0.3.1 Hudson project.
>
> I described our process to give inspiration to others and also to
> receive some feedback if someone knows of a better way to do this. I
> would be really happy to see some more direct support for our use case
> in Hudson.
Thanks. I agree that a better support for Maven release plugin would be
useful. Something like a fire-and-forget "release" button would be very
cool (although I haven't thought about how that would work at all!)

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Build vs. Release

Merry Prankster
In reply to this post by Kohsuke Kawaguchi
Hi,

and thanks for sharing this plugin. However, I'm a bit confused regarding how to use it. I'm currently trying to use it to implement build promotion, i.e. functionality to mark earlier integration build to be a release build. It seems that Batch task-plugin only works on latest build's workspace, am I right? This is troublesome at least for my purposes as the build I want to promote may not be the latest one.

To me it seems Batch task-plugin is nothing like "Tag this build" functionality (which works on specific workspace, not latest) :D I really haven't checked from source code whether it would be feasible or simple, but I think this plugin would be much more usable if it could operate on selected workspace, not just on job-level.

//janne

kohsuke wrote
Kohsuke Kawaguchi wrote:
> I'll try to post batch-task tomorrow.

Posted.

--
Kohsuke Kawaguchi
Sun Microsystems                   kohsuke.kawaguchi@sun.com

 
Reply | Threaded
Open this post in threaded view
|

RE: Re: Build vs. Release

tvworks
I agree, it would be nice if you could run a batch task on a particular
build instead of just the latest build,  I would like to do the same
thing in promoting a build.

-----Original Message-----
From: Merry Prankster [mailto:[hidden email]]
Sent: Thursday, November 01, 2007 12:38 AM
To: [hidden email]
Subject: Re: Build vs. Release


Hi,

and thanks for sharing this plugin. However, I'm a bit confused
regarding
how to use it. I'm currently trying to use it to implement build
promotion,
i.e. functionality to mark earlier integration build to be a release
build.
It seems that Batch task-plugin only works on latest build's workspace,
am I
right? This is troublesome at least for my purposes as the build I want
to
promote may not be the latest one.

To me it seems Batch task-plugin is nothing like "Tag this build"
functionality (which works on specific workspace, not latest) :D I
really
haven't checked from source code whether it would be feasible or simple,
but
I think this plugin would be much more usable if it could operate on
selected workspace, not just on job-level.

//janne


kohsuke wrote:

>
> Kohsuke Kawaguchi wrote:
>> I'll try to post batch-task tomorrow.
>
> Posted.
>
> --
> Kohsuke Kawaguchi
> Sun Microsystems                   [hidden email]
>
>  
>

--
View this message in context:
http://www.nabble.com/Build-vs.-Release-tf4635837.html#a13524483
Sent from the Hudson users mailing list archive at Nabble.com.

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

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

Reply | Threaded
Open this post in threaded view
|

Re: Build vs. Release

Kohsuke Kawaguchi
Administrator
In reply to this post by Merry Prankster
Merry Prankster wrote:
> Hi,
>
> and thanks for sharing this plugin. However, I'm a bit confused regarding
> how to use it. I'm currently trying to use it to implement build promotion,
> i.e. functionality to mark earlier integration build to be a release build.
> It seems that Batch task-plugin only works on latest build's workspace, am I
> right? This is troublesome at least for my purposes as the build I want to
> promote may not be the latest one.

Ah, for that, I got the "promoted-builds" plugin in the pipe. It's
coming along, so stay tuned.

> To me it seems Batch task-plugin is nothing like "Tag this build"
> functionality (which works on specific workspace, not latest) :D I really
> haven't checked from source code whether it would be feasible or simple, but
> I think this plugin would be much more usable if it could operate on
> selected workspace, not just on job-level.

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Build vs. Release

Kohsuke Kawaguchi
Administrator
In reply to this post by tvworks
Jason Chaffee wrote:
> I agree, it would be nice if you could run a batch task on a particular
> build instead of just the latest build,  I would like to do the same
> thing in promoting a build.

The only problem is that this would require Hudson to save the entire
workspace indefinitely, which can be quite sizable.

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

RE: Re: Build vs. Release

tvworks
Yeah...makes sense.  I guess the build promotion plugin would be the
best solution.

-----Original Message-----
From: Kohsuke Kawaguchi [mailto:[hidden email]]
Sent: Friday, November 02, 2007 8:49 AM
To: [hidden email]
Subject: Re: Build vs. Release

Jason Chaffee wrote:
> I agree, it would be nice if you could run a batch task on a
particular
> build instead of just the latest build,  I would like to do the same
> thing in promoting a build.

The only problem is that this would require Hudson to save the entire
workspace indefinitely, which can be quite sizable.

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

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