[Anthill-pro] Successful build question

Wed Sep 5 07:19:13 CDT 2007

Seems like a 80/20 violation to me and I'd question why the build steps 
are in flux so much? Shouldn't those variations be in the build script 
which are versioned?

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

"Mikal Todd" <mtodd at bravurasolutions.com> 
Sent by: anthill-pro-bounces at caladin.urbancode.com
09/04/2007 05:54 PM
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
RE: [Anthill-pro] Successful build question

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

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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.urbancode.com/pipermail/anthill-pro/attachments/20070905/86bc2f27/attachment.htm