Per-release changelog plugin

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

Per-release changelog plugin

Luis Pérez
Hi,

I'm just setting up Hudson in a software company, and one requirement
of the management process is that a changelog in a per-release basis
is available through Hudson.
However, our main jobs are building frequently (polling cvs every 5
minutes), so i'm almost finished a new plugin to dealt with this.

The plugin generates an alternative changelog file from the last
tagged build (This is our criteria for "a release", though it doesn't
mean a stable release, it can be just a intermediate build for quality
or testing purposes), and presents it through a Hudson action, showing
the changes and the range of builds comprising the "release".

I'm wondering if it could be useful for the community. What do you think?

Regards,

Luis Perez

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

Reply | Threaded
Open this post in threaded view
|

RE: Per-release changelog plugin

Adam Purkiss
I can see it being useful. From my own point of view however I have a serepate build job for a release so the changelog does exactly what you mention.




> Date: Mon, 16 Jun 2008 14:55:32 +0200

> From: [hidden email]
> To: [hidden email]
> Subject: Per-release changelog plugin
>
> Hi,
>
> I'm just setting up Hudson in a software company, and one requirement
> of the management process is that a changelog in a per-release basis
> is available through Hudson.
> However, our main jobs are building frequently (polling cvs every 5
> minutes), so i'm almost finished a new plugin to dealt with this.
>
> The plugin generates an alternative changelog file from the last
> tagged build (This is our criteria for "a release", though it doesn't
> mean a stable release, it can be just a intermediate build for quality
> or testing purposes), and presents it through a Hudson action, showing
> the changes and the range of builds comprising the "release".
>
> I'm wondering if it could be useful for the community. What do you think?
>
> Regards,
>
> Luis Perez
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


Reply | Threaded
Open this post in threaded view
|

Re: Per-release changelog plugin

Kohsuke Kawaguchi
Administrator
In reply to this post by Luis Pérez
Luis Pérez wrote:

> Hi,
>
> I'm just setting up Hudson in a software company, and one requirement
> of the management process is that a changelog in a per-release basis
> is available through Hudson.
> However, our main jobs are building frequently (polling cvs every 5
> minutes), so i'm almost finished a new plugin to dealt with this.
>
> The plugin generates an alternative changelog file from the last
> tagged build (This is our criteria for "a release", though it doesn't
> mean a stable release, it can be just a intermediate build for quality
> or testing purposes), and presents it through a Hudson action, showing
> the changes and the range of builds comprising the "release".
>
> I'm wondering if it could be useful for the community. What do you think?
Yes, please!

What's your java.net ID, so that I can add you as a committer?

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]


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

Re: Per-release changelog plugin

Erik Ramfelt
In reply to this post by Luis Pérez
On Mon, Jun 16, 2008 at 2:55 PM, Luis Pérez <[hidden email]> wrote:

> Hi,
>
> I'm just setting up Hudson in a software company, and one requirement
> of the management process is that a changelog in a per-release basis
> is available through Hudson.
> However, our main jobs are building frequently (polling cvs every 5
> minutes), so i'm almost finished a new plugin to dealt with this.
>
> The plugin generates an alternative changelog file from the last
> tagged build (This is our criteria for "a release", though it doesn't
> mean a stable release, it can be just a intermediate build for quality
> or testing purposes), and presents it through a Hudson action, showing
> the changes and the range of builds comprising the "release".

How do you tag builds? Do you use any of the SVN/CVS tagging
functionality? Is it possible to a build as a release through code, so
SCM plugins can hook into the plugin when they have implemented a
tagging functionality.


It would be useful if the builds could also be tagged through a link
on a build page, so it will work for those SCM that doesnt have
tagging functionality?


> I'm wondering if it could be useful for the community. What do you think?

Yes! Please share :D


//Erik

>
> Regards,
>
> Luis Perez
>
> ---------------------------------------------------------------------
> 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: Per-release changelog plugin

Luis Pérez
In reply to this post by Luis Pérez
> From: Kohsuke Kawaguchi <[hidden email]>
> To: [hidden email]
> Date: Mon, 16 Jun 2008 09:15:24 -0700
> Subject: Re: Per-release changelog plugin
> Luis Pérez wrote:
>
>    Hi,
>
>    I'm just setting up Hudson in a software company, and one requirement
>    of the management process is that a changelog in a per-release basis
>    is available through Hudson.
>    However, our main jobs are building frequently (polling cvs every 5
>    minutes), so i'm almost finished a new plugin to dealt with this.
>
>    The plugin generates an alternative changelog file from the last
>    tagged build (This is our criteria for "a release", though it doesn't
>    mean a stable release, it can be just a intermediate build for quality
>    or testing purposes), and presents it through a Hudson action, showing
>    the changes and the range of builds comprising the "release".
>
>    I'm wondering if it could be useful for the community. What do you think?
>
>
> Yes, please!
>
> What's your java.net ID, so that I can add you as a committer?
>
> --
> Kohsuke Kawaguchi
> Sun Microsystems                   [hidden email]

Hi,

Sorry, I've been very busy, and I could'n answer sooner :)

Mi java.net ID is laperez

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

Reply | Threaded
Open this post in threaded view
|

Re: Per-release changelog plugin

Luis Pérez
In reply to this post by Luis Pérez
> From: "Erik Ramfelt" <[hidden email]>
> To: [hidden email]
> Date: Tue, 17 Jun 2008 11:26:16 +0200
> Subject: Re: Per-release changelog plugin
> On Mon, Jun 16, 2008 at 2:55 PM, Luis Pérez <[hidden email]> wrote:
> > Hi,
> >
> > I'm just setting up Hudson in a software company, and one requirement
> > of the management process is that a changelog in a per-release basis
> > is available through Hudson.
> > However, our main jobs are building frequently (polling cvs every 5
> > minutes), so i'm almost finished a new plugin to dealt with this.
> >
> > The plugin generates an alternative changelog file from the last
> > tagged build (This is our criteria for "a release", though it doesn't
> > mean a stable release, it can be just a intermediate build for quality
> > or testing purposes), and presents it through a Hudson action, showing
> > the changes and the range of builds comprising the "release".
>
> How do you tag builds? Do you use any of the SVN/CVS tagging
> functionality? Is it possible to a build as a release through code, so
> SCM plugins can hook into the plugin when they have implemented a
> tagging functionality.

I rely in the current functionality of Hudson to Tag CVS/SVN. However,
my plugin currently only works for CVS, though I can work on it to
provide SVN support.

I'm a begginer with Hudson, so I'm not sure if the strategy to
implement the plugin was the best, so any suggestion will be
appreciated.

Basically, it is a publisher that generates a release-changelog.xml
file,  and binds an action that reads that file and generates a report
similar to the current changelog functionality (I found useful to show
dates in the changes too).
I couldn't find a way to reuse the code in the core to generate the
changelog xml file, so  I had to copy some parts of it.


> It would be useful if the builds could also be tagged through a link
> on a build page, so it will work for those SCM that doesnt have
> tagging functionality?
>
Unfortunately, as I said, the plugin relies in the SCM tagging functionality...

>
> > I'm wondering if it could be useful for the community. What do you think?
>
> Yes! Please share :D
>
>
> //Erik

Luis

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