Yes, after checking out whole glassfish module, now we can see the
checkins for the build duration after you click on the build number:
http://glassfishbuildtools.sun.com:8000/hudson/job/glassfish/build/2006-04-04_14-42-00/
If you click on "detail" link, following details can be seen, which
seems to be good..
http://glassfishbuildtools.sun.com:8000/hudson/job/glassfish/build/2006-04-04_14-42-00/changes#detail1
thanks
Dinesh
Kedar Mhaswade wrote:
> That beats me.
> I say that this is one of the *best* features
> of Tinberbox integration. An ability to give a script with
> *exact* set of commands that revert a failing checkin
> entirely. This is an essential tool in a build engineer's
> tool box, IMO.
>
> Even if it is a developer responsibility, we need to
> help developers by providing these basic facilities.
>
> Dinesh Patil wrote:
>
>> Hudson application is used just for build monitoring for getting the
>> status to developers about the state of the build and not build
>> debugging controlling the checkins :-) We haven't even used
>> Tinderbox command that you are suggesting (cvs update -j) for
>> reverting the changes, that still becomes manual and developers
>> responsibility to make sure it doesn't break the build, and if it
>> breaks, then developer to revert the changes that causing the problem.
>> Refer to the guidelines:
>> https://glassfish.dev.java.net/public/GuidelinesandConventions.html#Commit_Procedures
>>
>>
>> thanks
>> Dinesh
>>
>> Kedar Mhaswade wrote:
>>
>>> Thanks Dinesh, for the details.
>>>
>>> Just to confirm: Are you saying that if someone checks in 15 files in 4
>>> GF modules and that results in a build breakage, there is no easy way
>>> to know what/how to roll back? (If we do not do the rollback as an
>>> atomic
>>> operation, there might be more problems), other than going through
>>> the (often delayed) java.net e-mails and painfully finding out
>>> versions to revert?
>>>
>>> If yes, it is a limitation, especially for you :).
>>>
>>> Kedar
>>>
>>> Dinesh Patil wrote:
>>>
>>>> For reference, I have the blog on Glassfish build continuously on
>>>> Hudson application: *http://blog.sun.com/dpatil
>>>> *
>>>> In hudson, job configuration
>>>> http://glassfishbuildtools.sun.com:8000/hudson/job/glassfish
>>>> (/configure which is not accessible other than admin-role) we have
>>>> setup "module as glassfish/bootstrap" in "Source Code Management"
>>>> as checking out glassfish would be too long as it will checkout
>>>> unnecessary modules/source from java.net under glassfish modules.
>>>>
>>>> But the side effect of this is only checkins in glassfish/bootstrap
>>>> module are been detected by Hudson tool in "Changes" section of the
>>>> job, and not all GlassFish modules. We will need to see another
>>>> option to get this same functionality as Tinderbox, but currently
>>>> we have similar functionality in "Changes" section of the build
>>>> status, which shows integrations in "glassfish/bootstrap" module only.
>>>>
>>>> Source Code Management
>>>> None
>>>> CVS
>>>> CVSROOT *module glassfish/bootstrap*
>>>> branch CVS_RSH Use update If checked, Hudson will
>>>> use 'cvs update' whenever possible, making the build faster. But
>>>> this causes the artifacts from the previous build to remain when a
>>>> new build starts.
>>>> Subversion
>>>>
>>>> thanks
>>>> Dinesh
>>>>
>>>> Kedar Mhaswade wrote:
>>>>
>>>>> I was trying to understand (of course without reading the manual)
>>>>> the Hudson based builds of GlassFish at:
>>>>> http://glassfishbuildtools.sun.com:8000/hudson/job/glassfish/
>>>>>
>>>>> I could not locate where one should look for, if s/he is
>>>>> interested in finding out in *one* click a list of cvs update -j
>>>>> commands that undo the *entire* guilty checkin. (This is
>>>>> available on Tinderbox as a basic feature).
>>>>>
>>>>> Does anyone know?
>>>>>
>>>>> Thanks,
>>>>> Kedar
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>