Re: Recalculate change log based on deleting builds

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Recalculate change log based on deleting builds

Kohsuke Kawaguchi-2
Paul Mendelson wrote:
> Have any users request the ability to have the hudson build # be the
> same as the latest SVN commit # in the build?

Yes, I've heard about this request before.

The immediate question is what happens if your first build failed and
you manually triggered another build from the same SVN revision #. You'd
need something like #15, #15.1, #15.2, ... ? Hudson's current
implementation uses int for build numbers, so doing this needs some changes.

And then there's a question of how to handle a project with multiple
modules.


But I think this is a reasonable request. I mean, it just seems so much
more convenient because you can easily relate builds to changes, even
without looking at Hudson build records.

(Note that Hudson does remember what builds correspond to what SVN
revisions already. I presume you already know that, but just in case.)

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

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

Re: Recalculate change log based on deleting builds

Marty Lamb-2
Kohsuke Kawaguchi wrote:
> Paul Mendelson wrote:
>
>> Have any users request the ability to have the hudson build # be the
>> same as the latest SVN commit # in the build?
>
>
> Yes, I've heard about this request before.

That's funny - I just signed up for the mailing list today to request
this.  As you point out, though, repeated builds of the same revision
raise questions.

> But I think this is a reasonable request. I mean, it just seems so much
> more convenient because you can easily relate builds to changes, even
> without looking at Hudson build records.

That's the key issue for me - relating a build to the revision.  My
build script embeds the svnversion # in its artifacts, but I still need
to be able to find the right builds in hudson's history.

How about simply modifying the Build History sidebar to include the
revision number, say, right after the build number?  In my case, builds
for revisions 1783-1785 might look something like:

------------------------------------------
| Build History                  (trend) |
------------------------------------------
| *  #6 (1785)   Feb 13, 2007 3:00:07 PM |
| *  #5 (1784)   Feb 13, 2007 2:48:13 PM |
| *  #4 (1783)   Feb 13, 2007 2:14:46 PM |
|                   ...                  |
------------------------------------------

I haven't looked at any of the code yet (just downloaded today and ran
for the first time on my project, but it looks like I'll be using it for
a while :)  It seems this would be easy to do.

At least, this would satisfy *my* needs.  I don't know about the others
that have asked for it.

- Marty
--
Marty Lamb
Martian Software, Inc.
mlamb at martiansoftware dot com

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

Reply | Threaded
Open this post in threaded view
|

Re: Recalculate change log based on deleting builds

Kohsuke Kawaguchi-2
Marty Lamb wrote:

> Kohsuke Kawaguchi wrote:
>> Paul Mendelson wrote:
>>
>>> Have any users request the ability to have the hudson build # be the
>>> same as the latest SVN commit # in the build?
>>
>>
>> Yes, I've heard about this request before.
>
> That's funny - I just signed up for the mailing list today to request
> this.  As you point out, though, repeated builds of the same revision
> raise questions.
>
>> But I think this is a reasonable request. I mean, it just seems so much
>> more convenient because you can easily relate builds to changes, even
>> without looking at Hudson build records.
>
> That's the key issue for me - relating a build to the revision.  My
> build script embeds the svnversion # in its artifacts, but I still need
> to be able to find the right builds in hudson's history.
>
> How about simply modifying the Build History sidebar to include the
> revision number, say, right after the build number?  In my case, builds
> for revisions 1783-1785 might look something like:
>
> ------------------------------------------
> | Build History                  (trend) |
> ------------------------------------------
> | *  #6 (1785)   Feb 13, 2007 3:00:07 PM |
> | *  #5 (1784)   Feb 13, 2007 2:48:13 PM |
> | *  #4 (1783)   Feb 13, 2007 2:14:46 PM |
> |                   ...                  |
> ------------------------------------------
>
> I haven't looked at any of the code yet (just downloaded today and ran
> for the first time on my project, but it looks like I'll be using it for
> a while :)  It seems this would be easy to do.
>
> At least, this would satisfy *my* needs.  I don't know about the others
> that have asked for it.
We can certainly do this, and this is a lot easier than making the build
number the repository revision number.

My question is, doesn't existing project "changes" page already do this?


--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

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

Re: Recalculate change log based on deleting builds

Renaud Bruyeron-2
Kohsuke Kawaguchi wrote:

> Marty Lamb wrote:
>> Kohsuke Kawaguchi wrote:
>>> Paul Mendelson wrote:
>>>
>>>> Have any users request the ability to have the hudson build # be
>>>> the same as the latest SVN commit # in the build?
>>>
>>>
>>> Yes, I've heard about this request before.
>>
>> That's funny - I just signed up for the mailing list today to request
>> this.  As you point out, though, repeated builds of the same revision
>> raise questions.
>>
>>> But I think this is a reasonable request. I mean, it just seems so
>>> much more convenient because you can easily relate builds to
>>> changes, even without looking at Hudson build records.
>>
>> That's the key issue for me - relating a build to the revision.  My
>> build script embeds the svnversion # in its artifacts, but I still
>> need to be able to find the right builds in hudson's history.
>>
>> How about simply modifying the Build History sidebar to include the
>> revision number, say, right after the build number?  In my case,
>> builds for revisions 1783-1785 might look something like:
>>
>> ------------------------------------------
>> | Build History                  (trend) |
>> ------------------------------------------
>> | *  #6 (1785)   Feb 13, 2007 3:00:07 PM |
>> | *  #5 (1784)   Feb 13, 2007 2:48:13 PM |
>> | *  #4 (1783)   Feb 13, 2007 2:14:46 PM |
>> |                   ...                  |
>> ------------------------------------------
>>
>> I haven't looked at any of the code yet (just downloaded today and
>> ran for the first time on my project, but it looks like I'll be using
>> it for a while :)  It seems this would be easy to do.
>>
>> At least, this would satisfy *my* needs.  I don't know about the
>> others that have asked for it.
>
> We can certainly do this, and this is a lot easier than making the
> build number the repository revision number.
How do you handle projects for which the revision number does not change?
One example that immediately springs to mind is SVN projects with
externals (I think they were called modules in CVS-speak), for which the
parent project can be a simple stub that (almost) never changes...

 - Renaud

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

Reply | Threaded
Open this post in threaded view
|

Re: Recalculate change log based on deleting builds

pmendelson
In reply to this post by Kohsuke Kawaguchi-2
I like the idea of being able to see the subversion version next to the build number as suggested.  My personal goal is to make my ant tasks less subversion aware as I let hudson control the process.  To that end I would benefit from hudson setting a BUILD_VERSIONING_VERSION variable that would have the subversion (or some other versioning system's build number)

Kohsuke Kawaguchi-2 wrote
Marty Lamb wrote:
> Kohsuke Kawaguchi wrote:
>> Paul Mendelson wrote:
>>
>>> Have any users request the ability to have the hudson build # be the
>>> same as the latest SVN commit # in the build?
>>
>>
>> Yes, I've heard about this request before.
>
> That's funny - I just signed up for the mailing list today to request
> this.  As you point out, though, repeated builds of the same revision
> raise questions.
>
>> But I think this is a reasonable request. I mean, it just seems so much
>> more convenient because you can easily relate builds to changes, even
>> without looking at Hudson build records.
>
> That's the key issue for me - relating a build to the revision.  My
> build script embeds the svnversion # in its artifacts, but I still need
> to be able to find the right builds in hudson's history.
>
> How about simply modifying the Build History sidebar to include the
> revision number, say, right after the build number?  In my case, builds
> for revisions 1783-1785 might look something like:
>
> ------------------------------------------
> | Build History                  (trend) |
> ------------------------------------------
> | *  #6 (1785)   Feb 13, 2007 3:00:07 PM |
> | *  #5 (1784)   Feb 13, 2007 2:48:13 PM |
> | *  #4 (1783)   Feb 13, 2007 2:14:46 PM |
> |                   ...                  |
> ------------------------------------------
>
> I haven't looked at any of the code yet (just downloaded today and ran
> for the first time on my project, but it looks like I'll be using it for
> a while :)  It seems this would be easy to do.
>
> At least, this would satisfy *my* needs.  I don't know about the others
> that have asked for it.

We can certainly do this, and this is a lot easier than making the build
number the repository revision number.

My question is, doesn't existing project "changes" page already do this?


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

 
Reply | Threaded
Open this post in threaded view
|

Re: Recalculate change log based on deleting builds

Marty Lamb-2
In reply to this post by Kohsuke Kawaguchi-2
Kohsuke Kawaguchi wrote:
> Marty Lamb wrote:
>> Kohsuke Kawaguchi wrote:
>>> Paul Mendelson wrote:
>>>
>>>> Have any users request the ability to have the hudson build # be the
>>>> same as the latest SVN commit # in the build?
>>>
>>>
>>> Yes, I've heard about this request before.

[snip]

>> ------------------------------------------
>> | Build History                  (trend) |
>> ------------------------------------------
>> | *  #6 (1785)   Feb 13, 2007 3:00:07 PM |
>> | *  #5 (1784)   Feb 13, 2007 2:48:13 PM |
>> | *  #4 (1783)   Feb 13, 2007 2:14:46 PM |
>> |                   ...                  |
>> ------------------------------------------

[snip]

> My question is, doesn't existing project "changes" page already do this?

Not that I can see.  It shows the hudson build # and time, but not the
repository revision number.  I *can* drill in to the build detail and
see the revision there, but it's hard to find a build for a specific
revision by drilling in to each build.  Having the revision # next to
the hudson build # would still be helpful for me as it would allow me to
go directly to the revision I want.

Of course, that's approaching the realm of using hudson as a build
archive, but if all the info is there anyway...

- Marty

--
Marty Lamb
Martian Software, Inc.
mlamb at martiansoftware dot com


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

Reply | Threaded
Open this post in threaded view
|

Re: Recalculate change log based on deleting builds

Kohsuke Kawaguchi-2
Marty Lamb wrote:
>> My question is, doesn't existing project "changes" page already do this?
>
> Not that I can see.  It shows the hudson build # and time, but not the
> repository revision number.  I *can* drill in to the build detail and
> see the revision there, but it's hard to find a build for a specific
> revision by drilling in to each build.  Having the revision # next to
> the hudson build # would still be helpful for me as it would allow me to
> go directly to the revision I want.

OK, would you be happy if that "changes" page list the revision number
along side the build number, in the same page?

> Of course, that's approaching the realm of using hudson as a build
> archive, but if all the info is there anyway...

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

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

Re: Recalculate change log based on deleting builds

Kohsuke Kawaguchi-2
In reply to this post by Renaud Bruyeron-2
Renaud Bruyeron wrote:
>> We can certainly do this, and this is a lot easier than making the
>> build number the repository revision number.
> How do you handle projects for which the revision number does not change?
> One example that immediately springs to mind is SVN projects with
> externals (I think they were called modules in CVS-speak), for which the
> parent project can be a simple stub that (almost) never changes...

svn:external support needs some real improvement (there's a bug filed
for this.) But this is a good point. There's also a multi-module
subversion setting, too.

I'm inclined not to add this information in the build history. I think
the build number and SVN revision numbers look too alike and confusing.

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

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

Re: Recalculate change log based on deleting builds

Marty Lamb-2
Kohsuke Kawaguchi wrote:
> I'm inclined not to add this information in the build history. I think
> the build number and SVN revision numbers look too alike and confusing.

That's certainly true.  Your suggestion of using the project changes
page allows hudson to display the info in an unambiguous way.

- Marty
--
Marty Lamb
Martian Software, Inc.
mlamb at maryi


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