Re: Anthill Build regardless Question

Josh,

The pagelets can be modified to alter the commands used to interact with 
subversion. The problem is more subtle. After the command to retrieve a 
change log is issued, no changes are detected by the part of the system 
that does the parsing.

With no changes the build system decides a build is not required and 
moves on to the next request in the queue. If you hacked the get 
changelog pagelet to get a wider set of changes, that might work but I 
think we filter out changes prior to build time because subversion tends 
to return too much information in change logs.

As for code changes, I would look at two approaches:
1) Change com.urbancode.anthill.BuildManager.*requiresBuild()* to always 
require the build.
2 )Change AnthillSchedule.run() to set the force build flag on its new 
build defnition. That would require putting a build definition on the 
build queue rather than just the project. For an example of that, see 
com.urbancode.anthill.web.admin.BuildProjectStepTwoServlet. This could 
be expanded to make that optional with a UI widget if you wanted to 
contribute it back.

There could be other options or more complications, but that's what I 
see after taking a quick look.

-- Eric

Claros, Josue (Mission Systems) wrote:

>Thanks Eric,
>
>Yes I would like for you to point me in the right direction when you
>have the time thank you very much.
>By the way...i was under the impression that I could modify the way
>anthillos works by modifying 
>The pagelets under /conf/profiles/Unix/unix_subversion ...guess theres
>more to it than I thought.
>I originally wanted anthillOS to do an update instead of a checkout if
>there was an existing repository because my svn repository is almost
>half a gig...so every time I build it takes over 2 hours to complete
>because it always checks out a fresh copy of the repository.
>My solution was to checkout the build folder and use svnant commands
>within my build script...and now I have this problem.
>
>Anyway your help would be greatly appreciated 
>Thanks,
>Josh
> 
>
>-----Original Message-----
>From: anthill-bounces-IWHQxnLZ/[email protected]
>[mailto:anthill-bounces-IWHQxnLZ/[email protected]] On Behalf Of Eric Minick
>Sent: Wednesday, February 07, 2007 9:55 AM
>To: Anthill user list
>Subject: Re: [Anthill] Anthill Build regardless Question
>
>Fair question. I just realized that the how to get the source is a bit
>hard to find.
>
>That page is here:
>http://www.anthillpro.com/html/products/anthillos/for-developers.html
>
>I can dig in to the code and point you in the right direction later this
>afternoon if you'd like (I've got to run to a meeting right now).
>
>-- Eric
>
>
>Claros, Josue (Mission Systems) wrote:
>
>  
>
>>Thanks Eric,
>>
>>Can you explain how to do option number 3 in detail. 
>>
>>Thanks,
>>Josh
>>
>>-----Original Message-----
>>From: anthill-bounces-IWHQxnLZ/[email protected]
>>[mailto:anthill-bounces-IWHQxnLZ/[email protected]] On Behalf Of Eric Minick
>>Sent: Tuesday, February 06, 2007 10:15 PM
>>To: Anthill user list
>>Subject: Re: [Anthill] Anthill Build regardless Question
>>
>>Josue,
>>
>>AnthillOS doesn't handle this situation particularly well. It's really 
>>designed to be doing the interaction with your core project. You do 
>>have a couple options though.
>>
>>1) Use a 'file system' repository. If your build script changes almost 
>>never, you could manually put that build script out to some location 
>>and just have AnthillOS run against that. The File System Repo doesn't 
>>detect changes, so it will always build.
>>
>>2) Check in bogus changes. If your SVN tasks could also check in a 
>>bogus change to a scratch file in the /mainfolder/build path, Anthill 
>>would see those changes on the next build and react to them.
>>
>>3) Grab the source, and change how schedules work. :)
>>
>>AnthillPro handles this quite nicely and if we get some time to revisit
>>    
>>
>
>  
>
>>AnthillOS, we might steal a feature from it and add a force build flag 
>>to schedules.
>>
>>-- Eric
>>
>>Claros, Josue (Mission Systems) wrote:
>>
>> 
>>
>>    
>>
>>>How do I configure anthill to build regardless of no updates being 
>>>made to the subversion repository on a timed schedule.
>>>
>>>The way I have my setup is... Anthill checks out /mainfolder/build 
>>>folder And the actual build.xml has svnant commands that either 
>>>checkout or update the repository Problem is....on a timed schedule 
>>>anthill will never do anything since the /mainfolder/build folder will
>>>   
>>>
>>>      
>>>
>> 
>>
>>    
>>
>>>rarely change
>>>
>>>Please help
>>>
>>>Thanks,
>>>Josh
>>>
>>>----------------------------------------------------------------------
>>>-
>>>-
>>>
>>>_______________________________________________
>>>Anthill mailing list
>>>Anthill-IWHQxnLZ/[email protected]
>>>http://lists.urbancode.com/mailman/listinfo/anthill
>>>
>>>
>>>   
>>>
>>>      
>>>
>>_______________________________________________
>>Anthill mailing list
>>Anthill-IWHQxnLZ/[email protected]
>>http://lists.urbancode.com/mailman/listinfo/anthill
>>_______________________________________________
>>Anthill mailing list
>>Anthill-IWHQxnLZ/[email protected]
>>http://lists.urbancode.com/mailman/listinfo/anthill
>> 
>>
>>    
>>
>
>_______________________________________________
>Anthill mailing list
>Anthill-IWHQxnLZ/[email protected]
>http://lists.urbancode.com/mailman/listinfo/anthill
>_______________________________________________
>Anthill mailing list
>Anthill-IWHQxnLZ/[email protected]
>http://lists.urbancode.com/mailman/listinfo/anthill
>  
>