idea: build "profiles"

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

idea: build "profiles"

Ravi Luthra
While I know there is the capability to copy a project in Hudson, it would be nice to factor out all configuration to a build profile.

The concept would be similar to how Maven inheritance works. To inherit build schedule, number of builds to keep, etc... would be a nice way to modify all builds at once. I keep finding myself going into each configure screen and changing something like that every now and then.

If that is too complex, maybe provide a way to select multiple projects and apply a set of properties to all the configuration files.

And if that is too complex, maybe just some documentation on how to push a groovy command that iterates through the projects, changes a property and saves the project.

Just an idea. I know you get these all the time.

Thanks!

Ravi

Reply | Threaded
Open this post in threaded view
|

Re: idea: build "profiles"

Kohsuke Kawaguchi
Administrator

Thanks for the feedback.

There are several existing RFEs that touch what you are describing.
Issue #22 is about defining a global default log rotation policy (and I
find it desirable because every so often someone forgets to set that and
eats all the disk space.)

Another related change I'm making right now is to support the "build
matrix". Often my test projects need to run with combinations of various
different axes (JDK version, platform, etc), and I wanted to control
them all from a single configuration. This might be related to what you
are saying.

I think inheritance is hard to do right, especially in GUI.

Documenting how to do this from scripting console is a good idea too
(but probably easier approach is to change config.xml files.)


Ravi Luthra wrote:

> While I know there is the capability to copy a project in Hudson, it would
> be nice to factor out all configuration to a build profile.
>
> The concept would be similar to how Maven inheritance works. To inherit
> build schedule, number of builds to keep, etc... would be a nice way to
> modify all builds at once. I keep finding myself going into each configure
> screen and changing something like that every now and then.
>
> If that is too complex, maybe provide a way to select multiple projects and
> apply a set of properties to all the configuration files.
>
> And if that is too complex, maybe just some documentation on how to push a
> groovy command that iterates through the projects, changes a property and
> saves the project.
>
> Just an idea. I know you get these all the time.
>
> Thanks!
>
> Ravi
>

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment