[Anthill-pro] Any anthill3 tutorials or guides?

[Curtis Yanko]

Getting documentation available is going to very important for me very 
soon. I need to be able to understand and communicate AH3 if I am to 
evangelize it.

- Curtis Yanko
United Health Technologies
Mail Route: CT028-07SA
Internet email: curt_yanko at uhc.com
Office 860.702.9059
Cell 860.729.8171




Maciej Zawadzki <mbz at urbancode.com> 
Sent by: anthill-pro-bounces at caladin.urbancode.com
08/16/2006 08:53 PM
Please respond to
anthill-pro at caladin.urbancode.com


To
anthill-pro at caladin.urbancode.com
cc

Subject
Re: [Anthill-pro] Any anthill3 tutorials or guides?






Simon,

There is a lot of functionality in Anthill3.  It can automate pretty
much any part of the lifecycle from build all the way to release.  It
can automate testing, deployment, etc.  We are still working on getting
flash tutorials put together.

To get a simple project configured in Anthill3 you need to go through
the following steps:

1. In Administration, under Repositories, create a repository of the
type that corresponds to your SCM.

2. In Administration, under Project, create a new project.

3. In that project configure the name, status group (use default for
now), Stamp Style Group (use default), Environment Group (use default),
Quiet Period type (use Change log Quiet Period), Quiet Period (set to 0
or 60 seconds).  And save.

4. Now configure a Source Config in the project.  This should be
relatively straight forward.  Let me know what SCM you use for more
specific help on this.

5.  You can skip artifacts sets for now.

6.  Configure a Stamping Strategy.  This is the piece that will assign a
build identifier (could be thought of as a Version) to your builds.
Click New, then select the Default Stamping Template; name it something
like "trunk-dev", and give it a version number such as 1 or 1.0.

7.  Create a Job Configuration.  Hit New, then select a Build Job
Config; save.  Then configure the project name, stamp style (select
DEV), should tag (set to never for now), should cleanup (set to no for
now), Change Log Start Status (set to success); then save.  Now go to
the Builders tab and add a builder (probably Ant builder).  Pretty much
everything is self explanatory except the Ant Configuration (set to
${env/ANT_HOME} and JVM Configuration (set to ${env/JAVA_HOME}.

8. create a new Activity configuration.  Select Simple activity.  Name
it and select the build job config in the drop down.  save.

9. create a new workflow.  select Originating workflow.  Name it, select
server group (build farm), notification scheme (default one), lockable
resource (none for now), source config (select the one you configured
earlier in step 4).  Stamp to DEV (select the stamping strategy you
created in step 6).  Save.  Now create a new Workflow Activity.  Select
the Activity Configuration you created in step 8.  Save.


Wasn't that easy :)  There are a lot of moving parts in Anthill3, but
they are all required in order to get the full power of the tool.

Before running a build, lets make sure that you have an agent installed
and configured.  Once you have installed an agent and have it running,
go to the System tab (we were just in the Administration tab).  In the
system tab hit Agents.  Your agent should be listed in the table
"available Agents".  Click the "Configure link" and provide a name for
the Agent and save.  The agent should now be in the "Active Agents"
table.  You can go to the "Current Activity" tab to make sure that the
agent is "Online".

Now, we can do the build.  Go to the Dashboard tab and then select your
project.  Once there, you will see a form in a table called "Manual
build".  select the workflow that you configured and then check the
"Force" box and hit next.  Since we don't have any parameters, hit the
"Build" button now.  You should see a message indicating that a build
request was created near the top of the screen.  And you should see a
build request in the "Recent BuildLife Requests" table.  If the source
config is not configured correctly, the build request will have an
error.  You can hit the Job link to see the steps that were performed
while servicing this request and then you can view the logs or output
for each step to see what went wrong -- if anything did.

Once the request is services, you will see a new BuildLife in the
"Recent BuildLife Activity" table.  You can click the BuildLife link to
see the BuildLife page -- it's pretty much the BOM (Bill of Materials)
for the build.  You can read more about BuildLifes at the urbancode 
website.

Let us know if you get stuck anywhere along the way.

Regards,

--Maciej




Au, Simon wrote:
> Hi,
>
> I am in the process up configuring Anthill3 for a prototype project.
> The setup is not trivial at all...in fact, its pretty confusing.  The
> quick guide from urbancode was not much help.  Are there more detailed
> guides?
>
> I am setting up this prototype to evaluate if my company should buy this
> tool.
>
> Thanks,
> Simon
_______________________________________________
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/20060817/1487d19e/attachment.htm