[Anthill-pro] Successful build question
Mikal Todd
mtodd at bravurasolutions.com
Tue Sep 4 20:34:59 CDT 2007
Eric,
Thanks for the prompt reply.
In a nutshell we are trying to ensure our build is completely portable,
so we even bundle Ant and the JDT in SVN and then use a shell scripted
invoker through AHP.
You are completely correct, we are trying to match the build
configuration against the source code - so that in a few years of
various versions we can make an effort to reproduce the artifacts.
We're almost there with the JDT and Ant, and the build files themselves
are held in SVN. Really all that is left are the steps and labels.
The snapshot stuff you provide will solve the problem in the interim -
many thanks.
Mikal Todd
Build and Release Manager
Bravura Solutions Limited
Level 1, 95 Hurstmere Road
Takapuna, Auckland Tel + 64 9 921 1268
Mobile +64 21 971 116
Fax + 64 9 489 6172
www.bravurasolutions.com.au
This mail message (and attachments) may contain information that is
confidential to Bravura Solutions. If you are not the intended recipient
you cannot use, distribute or copy the message or attachments. In such
case, please notify the sender by return email immediately and erase all
copies of the message and attachments. Regardless of content, this
e-mail shall not operate to bind Bravura Solutions to any order or other
contract unless pursuant to explicit written agreement expressly
permitting the use of e-mail for such purpose.
-----Original Message-----
From: anthill-pro-bounces at lists.urbancode.com
[mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of Eric
Minick
Sent: Wednesday, 5 September 2007 12:38 p.m.
To: AnthillPro user and support list.
Subject: Re: [Anthill-pro] Successful build question
Mikal,
This is something we've been looking at doing since very early in the
Anthill3 design effort. It's always been a bit hard to justify from a
delivered functionality to difficulty to implement ratio. A big part of
this, is that I don't think we really understand the common use cases
and how to best accommodate them.
There's some work in place that moves in this direction though. There's
a script that takes the project configuration and stores it as a report
against the build as a report. In a pinch, that would allow you to
import the project fresh, and run the old configuration.
http://bugs.urbancode.com/browse/AHPSCRIPTS-9
I suppose the more general question is what you mean by a "recent build
configuration" and "old source code". Are we trying to match the build
configuration to how it was when the source came into being? Are you
looking to run last month's source code against last week's
configuration?
Regards,
Eric
Mikal Todd wrote:
> Having now been using AHP in anger for a few months with lots and lots
> of builds running through it would be nice if the ability to detect
> changes was also hooked through to the build steps themselves.
>
> So
>
> - You change the build steps and AHP recognizes a change has occurred
> and hence does not need to force.
>
> - This leads onto a killer feature that we think we'll really need.
Can
> we have some kind of versioning of the builds steps, so that they are
> linked against a version?
>
> One problem we have is that the build process is constantly under
> refinement, and even though we take great care to make our generic
jobs
> portable it is still difficult to run a recent build configuration
> against old source code. Since of course the build steps may differ
> throughout product development
>
> IMHO this is something that would seriously differentiate AHP from the
> slow, but growing list of competitors...
>
> Mikal Todd
> Build and Release Manager
> Bravura Solutions Limited
> Level 1, 95 Hurstmere Road
>
> www.bravurasolutions.com.au
>
>
> This mail message (and attachments) may contain information that is
> confidential to Bravura Solutions. If you are not the intended
recipient
> you cannot use, distribute or copy the message or attachments. In such
> case, please notify the sender by return email immediately and erase
all
> copies of the message and attachments. Regardless of content, this
> e-mail shall not operate to bind Bravura Solutions to any order or
other
> contract unless pursuant to explicit written agreement expressly
> permitting the use of e-mail for such purpose.
>
> -----Original Message-----
> From: anthill-pro-bounces at lists.urbancode.com
> [mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of Eric
> Minick
> Sent: Wednesday, 5 September 2007 3:19 a.m.
> To: AnthillPro user and support list.
> Subject: Re: [Anthill-pro] Successful build question
>
> Nir,
>
> The change log may indeed be for "since the latest successful" but the
> determination of whether a build needs to happen is going to be
changes
> since the last build. Some people are on 5 minute build loops. Without
> this distinction, if someone breaks the build at midnight Friday.
They'd
>
> have hundreds of failed builds in the morning on Monday.
>
> So the assumption is that if the code didn't change, the build
shouldn't
>
> happen. This doesn't account for system glitches or configuration
> errors, but it's the best guess we can have Anthill make.
>
> Regards,
>
> Eric
>
> Silgi, Nir wrote:
>
>> That is true, there is no new source code but the previous source
code
>> get didn't build! (because of configuration problems rather than
>>
> source
>
>> problems)
>>
>> It is reasonable that in this case, I wouldn't need to force it.
>>
>> The Changelog should be from the last successful build.
>>
>>
>>
>>
>>
>>
>>
>> ________________________________
>>
>> From: anthill-pro-bounces at lists.urbancode.com
>> [mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of Curtis
>> Yanko
>> Sent: Tuesday, September 04, 2007 5:57 PM
>> To: AnthillPro user and support list.
>> Subject: Re: [Anthill-pro] Successful build question
>>
>>
>>
>>
>> It says 'no new build life needed, because there isn't new source
code
>> so you'd have to 'force' it
>>
>> Curt Yanko
>> UnitedHealth Group IT
>> Computer Services - AIS
>> Source->Build->Deploy
>> curt_yanko at uhc.com
>>
>> 450 Columbus Blvd
>> CT028-06SA
>> Hartford, CT 06103
>> ph: 860.881.2050
>>
>> http://www.linkedin.com/in/curtyanko
>> <http://www.linkedin.com/in/curtyanko>
>>
>>
>>
>>
>>
>>
>>
>>
>> "Silgi, Nir" <nsilgi at shopping.com>
>> Sent by: anthill-pro-bounces at caladin.urbancode.com
>>
>> 09/04/2007 10:54 AM
>>
>> Please respond to
>> "AnthillPro user and support list."
>>
> <anthill-pro at caladin.urbancode.com>
>
>> To
>>
>> "AnthillPro user and support list."
>>
> <anthill-pro at caladin.urbancode.com>
>
>> cc
>>
>>
>>
>> Subject
>>
>> [Anthill-pro] Successful build question
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> When is a successful build accounted as one for the next build's
>>
> source
>
>> check purpose?
>>
>> In other words:
>> If have a build that failed in the builder step, but in the next step
>>
> it
>
>> published the Changelog, does it count as a successful build? I'm
>>
> asking
>
>> because if I run it again, it says "No new build life is needed"
>>
>> Thanks,
>> Nir Silgi | eBay, Inc. | CM & Release Engineer, Shopping.com | Tel:
>>
> +972
>
>> (9) 8921008 | Cell: +972 (52) 6649051 | nsilgi at ebay.com
>> <mailto:nsilgi at ebay.com> | <skype:nirsilgi?chat>
>>
>>
>>
>>
>>
>>
>>
>>
>
<http://775146.sigclick.mailinfo.com/sigclick/0F060400/06074B00/0801094D
>
>> /0118111217.jpg> _______________________________________________
>> Anthill-pro mailing list
>> Anthill-pro at lists.urbancode.com
>> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>>
>>
>>
>> This e-mail, including attachments, may include confidential and/or
>> proprietary information, and may be used only by the person or entity
>>
> to
>
>> which it is addressed. If the reader of this e-mail is not the
>>
> intended
>
>> recipient or his or her authorized agent, the reader is hereby
>>
> notified
>
>> that any dissemination, distribution or copying of this e-mail is
>> prohibited. If you have received this e-mail in error, please notify
>>
> the
>
>> sender by replying to this message and delete this e-mail
immediately.
>>
>>
>>
>>
>>
>>
>
<http://775146.sigclick.mailinfo.com/sigclick/06010408/07014E01/01060845
>
>> /0001619372.jpg>
>>
>>
>>
>>
>
------------------------------------------------------------------------
>
>> _______________________________________________
>> Anthill-pro mailing list
>> Anthill-pro at lists.urbancode.com
>> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>>
>>
> _______________________________________________
> Anthill-pro mailing list
> Anthill-pro at lists.urbancode.com
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
> _______________________________________________
> Anthill-pro mailing list
> Anthill-pro at lists.urbancode.com
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>
>
_______________________________________________
Anthill-pro mailing list
Anthill-pro at lists.urbancode.com
http://lists.urbancode.com/mailman/listinfo/anthill-pro
More information about the Anthill-pro
mailing list