How do you handle multiple build requests

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

How do you handle multiple build requests

Ryan Feiock

Hello,

I have an application that takes about 15 min to build.  I have a repository trigger setup so that when a developer commits new code, it will kick off a new build.  I also have a lockable resource setup so that if multiple build requests come in within a few min of each other, I don’t have parallel builds trying to run at the same time (the build process can’t handle parallel builds).  However this creates a scenario where I am getting a whole bunch of builds queued up behind each other waiting for the previous builds to complete. 

 

What I want to do is have the first developer commit kick off a build.  If during that 15 min build process, 5 developers commit code, I want a second build to kick off after the first one is complete which would get latest, and take care of all 5 build requests.  What I don’t want is for 5 builds to get queued up and run one at a time.  Is there a way to do this?

 

Thanks,

Ryan

 


_______________________________________________
Anthill-pro mailing list
[hidden email]
http://lists.urbancode.com/mailman/listinfo/anthill-pro
Reply | Threaded
Open this post in threaded view
|

RE: How do you handle multiple build requests

Daniel Kirsch

Ryan,

 

Use the Quiet Period to wait a specified amount of time before kicking off the builds.  AHP will wait the time set and then check to see if there were any more repository changes and if so combine all the changes in the next build.

 

We use this with a 10 minute quiet period.

 

Regards,

 

Dan

 

Daniel Kirsch

Principal Software Development Engineer

Citrix Systems, Inc. – www.citrix.com

14 Crosby Drive

Bedford, MA 01730

781.301.9629 Office

781.301.0050 Fax

[hidden email]

 


From: [hidden email] [mailto:[hidden email]] On Behalf Of Ryan Feiock
Sent: Friday, December 19, 2008 4:11 PM
To: [hidden email]
Subject: [Anthill-pro] How do you handle multiple build requests

 

Hello,

I have an application that takes about 15 min to build.  I have a repository trigger setup so that when a developer commits new code, it will kick off a new build.  I also have a lockable resource setup so that if multiple build requests come in within a few min of each other, I don’t have parallel builds trying to run at the same time (the build process can’t handle parallel builds).  However this creates a scenario where I am getting a whole bunch of builds queued up behind each other waiting for the previous builds to complete. 

 

What I want to do is have the first developer commit kick off a build.  If during that 15 min build process, 5 developers commit code, I want a second build to kick off after the first one is complete which would get latest, and take care of all 5 build requests.  What I don’t want is for 5 builds to get queued up and run one at a time.  Is there a way to do this?

 

Thanks,

Ryan

 


_______________________________________________
Anthill-pro mailing list
[hidden email]
http://lists.urbancode.com/mailman/listinfo/anthill-pro
Reply | Threaded
Open this post in threaded view
|

RE: How do you handle multiple build requests

Mark_Melvin
In reply to this post by Ryan Feiock
Hey Dan,

Doesn't that mean all of your builds will then take a minimum of 10 minutes
(even if the build actually only takes a few seconds)?  I've seen the same
issue myself and knew that I could use the quiet period in this way, but
I'm worried about making all of my build processes take a long time.

Mark.
----------------------------------------------------------



-----[hidden email] wrote: -----


To: "AnthillPro user and support list." <[hidden email]>
From: "Daniel Kirsch" <[hidden email]>
Sent by: [hidden email]
Date: 12/22/2008 08:39AM
Subject: RE: [Anthill-pro] How do you handle multiple build requests


Ryan,

Use the Quiet Period to wait a specified amount of time before kicking off
the builds.  AHP will wait the time set and then check to see if there were
any more repository changes and if so combine all the changes in the next
build.

We use this with a 10 minute quiet period.

Regards,

Dan

Daniel Kirsch
Principal Software Development Engineer
Citrix Systems, Inc. – www.citrix.com
14 Crosby Drive
Bedford, MA 01730
781.301.9629 Office
781.301.0050 Fax
[hidden email]




From: [hidden email]
[mailto:[hidden email]] Sent: Friday, December 19,
2008 4:11 PM
To: [hidden email]
Subject: [Anthill-pro] How do you handle multiple build requests

Hello,
I have an application that takes about 15 min to build.  I have a
repository trigger setup so that when a developer commits new code, it will
kick off a new build.  I also have a lockable resource setup so that if
multiple build requests come in within a few min of each other, I don’t
have parallel builds trying to run at the same time (the build process
can’t handle parallel builds).  However this creates a scenario where I am
getting a whole bunch of builds queued up behind each other waiting for the
previous builds to complete.

What I want to do is have the first developer commit kick off a build.  If
during that 15 min build process, 5 developers commit code, I want a second
build to kick off after the first one is complete which would get latest,
and take care of all 5 build requests.  What I don’t want is for 5 builds
to get queued up and run one at a time.  Is there a way to do this?

Thanks,
Ryan

_______________________________________________
Anthill-pro mailing list
[hidden email]
http://lists.urbancode.com/mailman/listinfo/anthill-pro
_______________________________________________
Anthill-pro mailing list
[hidden email]
http://lists.urbancode.com/mailman/listinfo/anthill-pro
Reply | Threaded
Open this post in threaded view
|

Re: How do you handle multiple build requests

Ryan Smith-3-3
Ryan,

Which version are you using?  The latest release will merge repository
changes with builds that are waiting to obtain a lockable resource.


Ryan Smith

[hidden email] wrote:

> Hey Dan,
>
> Doesn't that mean all of your builds will then take a minimum of 10 minutes
> (even if the build actually only takes a few seconds)?  I've seen the same
> issue myself and knew that I could use the quiet period in this way, but
> I'm worried about making all of my build processes take a long time.
>
> Mark.
> ----------------------------------------------------------
>
>
>
> -----[hidden email] wrote: -----
>
>
> To: "AnthillPro user and support list." <[hidden email]>
> From: "Daniel Kirsch" <[hidden email]>
> Sent by: [hidden email]
> Date: 12/22/2008 08:39AM
> Subject: RE: [Anthill-pro] How do you handle multiple build requests
>
>
> Ryan,
>
> Use the Quiet Period to wait a specified amount of time before kicking off
> the builds.  AHP will wait the time set and then check to see if there were
> any more repository changes and if so combine all the changes in the next
> build.
>
> We use this with a 10 minute quiet period.
>
> Regards,
>
> Dan
>
> Daniel Kirsch
> Principal Software Development Engineer
> Citrix Systems, Inc. – www.citrix.com
> 14 Crosby Drive
> Bedford, MA 01730
> 781.301.9629 Office
> 781.301.0050 Fax
> [hidden email]
>
>
>
>
> From: [hidden email]
> [mailto:[hidden email]] Sent: Friday, December 19,
> 2008 4:11 PM
> To: [hidden email]
> Subject: [Anthill-pro] How do you handle multiple build requests
>
> Hello,
> I have an application that takes about 15 min to build.  I have a
> repository trigger setup so that when a developer commits new code, it will
> kick off a new build.  I also have a lockable resource setup so that if
> multiple build requests come in within a few min of each other, I don’t
> have parallel builds trying to run at the same time (the build process
> can’t handle parallel builds).  However this creates a scenario where I am
> getting a whole bunch of builds queued up behind each other waiting for the
> previous builds to complete.
>
> What I want to do is have the first developer commit kick off a build.  If
> during that 15 min build process, 5 developers commit code, I want a second
> build to kick off after the first one is complete which would get latest,
> and take care of all 5 build requests.  What I don’t want is for 5 builds
> to get queued up and run one at a time.  Is there a way to do this?
>
> Thanks,
> Ryan
>
> _______________________________________________
> Anthill-pro mailing list
> [hidden email]
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
> ------------------------------------------------------------------------
>
> _______________________________________________
> Anthill-pro mailing list
> [hidden email]
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>  
_______________________________________________
Anthill-pro mailing list
[hidden email]
http://lists.urbancode.com/mailman/listinfo/anthill-pro
Reply | Threaded
Open this post in threaded view
|

RE: How do you handle multiple build requests

Daniel Kirsch
In reply to this post by Mark_Melvin
Yes, it does.  Our builds take around 40 minutes, but with developers
across the country that may be checking in changes it seemed to work
best for us.  You can set the period for something shorter if it works
better for you.

Regards,
 
Dan

-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of
[hidden email]
Sent: Monday, December 22, 2008 12:26 PM
To: AnthillPro user and support list.
Subject: RE: [Anthill-pro] How do you handle multiple build requests

Hey Dan,

Doesn't that mean all of your builds will then take a minimum of 10
minutes
(even if the build actually only takes a few seconds)?  I've seen the
same
issue myself and knew that I could use the quiet period in this way, but
I'm worried about making all of my build processes take a long time.

Mark.
----------------------------------------------------------



-----[hidden email] wrote: -----


To: "AnthillPro user and support list."
<[hidden email]>
From: "Daniel Kirsch" <[hidden email]>
Sent by: [hidden email]
Date: 12/22/2008 08:39AM
Subject: RE: [Anthill-pro] How do you handle multiple build requests


Ryan,

Use the Quiet Period to wait a specified amount of time before kicking
off
the builds.  AHP will wait the time set and then check to see if there
were
any more repository changes and if so combine all the changes in the
next
build.

We use this with a 10 minute quiet period.

Regards,

Dan

Daniel Kirsch
Principal Software Development Engineer
Citrix Systems, Inc. - www.citrix.com
14 Crosby Drive
Bedford, MA 01730
781.301.9629 Office
781.301.0050 Fax
[hidden email]




From: [hidden email]
[mailto:[hidden email]] Sent: Friday, December
19,
2008 4:11 PM
To: [hidden email]
Subject: [Anthill-pro] How do you handle multiple build requests

Hello,
I have an application that takes about 15 min to build.  I have a
repository trigger setup so that when a developer commits new code, it
will
kick off a new build.  I also have a lockable resource setup so that if
multiple build requests come in within a few min of each other, I don't
have parallel builds trying to run at the same time (the build process
can't handle parallel builds).  However this creates a scenario where I
am
getting a whole bunch of builds queued up behind each other waiting for
the
previous builds to complete.

What I want to do is have the first developer commit kick off a build.
If
during that 15 min build process, 5 developers commit code, I want a
second
build to kick off after the first one is complete which would get
latest,
and take care of all 5 build requests.  What I don't want is for 5
builds
to get queued up and run one at a time.  Is there a way to do this?

Thanks,
Ryan

_______________________________________________
Anthill-pro mailing list
[hidden email]
http://lists.urbancode.com/mailman/listinfo/anthill-pro
_______________________________________________
Anthill-pro mailing list
[hidden email]
http://lists.urbancode.com/mailman/listinfo/anthill-pro
Reply | Threaded
Open this post in threaded view
|

Re: How do you handle multiple build requests

Ryan Feiock
In reply to this post by Ryan Feiock
Per Ryan Smith's question, I am running 3.5.3_14575.  I assume you mean 3.6?  Is there documentation on this process that I can look at?

Per everyone else's comments, I tried what Dan suggested, and it does cure my problem of the builds being added to the queue, but as Mark mentioned, it now means that when a developer commits code, it could take 15 min for the quiet period and then another 15 min for the code to compile.  This is not the worst thing that could happen, but if QA is waiting for a build, it is hard to make them wait that extra 15 min ;)  I am hoping that the new functionality Ryan mentions will do what I am looking for.


-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of [hidden email]
Sent: Monday, December 22, 2008 6:00 PM
To: [hidden email]
Subject: Anthill-pro Digest, Vol 59, Issue 21

Send Anthill-pro mailing list submissions to
        [hidden email]

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.urbancode.com/mailman/listinfo/anthill-pro
or, via email, send a message with subject or body 'help' to
        [hidden email]

You can reach the person managing the list at
        [hidden email]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Anthill-pro digest..."


Today's Topics:

   1. RE: How do you handle multiple build requests
      ([hidden email])
   2. Re: How do you handle multiple build requests (Ryan Smith)
   3. RE: How do you handle multiple build requests (Daniel Kirsch)
   4. Remote agent environment assignment - PersistenceException
      ([hidden email])
   5. Re: Remote agent environment assignment -
      PersistenceException ([hidden email])


----------------------------------------------------------------------

Message: 1
Date: Mon, 22 Dec 2008 10:26:22 -0700
From: [hidden email]
Subject: RE: [Anthill-pro] How do you handle multiple build requests
To: "AnthillPro user and support list."
        <[hidden email]>
Message-ID:
        <[hidden email]>
Content-Type: text/plain; charset=UTF-8

Hey Dan,

Doesn't that mean all of your builds will then take a minimum of 10 minutes
(even if the build actually only takes a few seconds)?  I've seen the same
issue myself and knew that I could use the quiet period in this way, but
I'm worried about making all of my build processes take a long time.

Mark.
----------------------------------------------------------



-----[hidden email] wrote: -----


To: "AnthillPro user and support list." <[hidden email]>
From: "Daniel Kirsch" <[hidden email]>
Sent by: [hidden email]
Date: 12/22/2008 08:39AM
Subject: RE: [Anthill-pro] How do you handle multiple build requests


Ryan,

Use the Quiet Period to wait a specified amount of time before kicking off
the builds.  AHP will wait the time set and then check to see if there were
any more repository changes and if so combine all the changes in the next
build.

We use this with a 10 minute quiet period.

Regards,

Dan

Daniel Kirsch
Principal Software Development Engineer
Citrix Systems, Inc. – www.citrix.com
14 Crosby Drive
Bedford, MA 01730
781.301.9629 Office
781.301.0050 Fax
[hidden email]




From: [hidden email]
[mailto:[hidden email]] Sent: Friday, December 19,
2008 4:11 PM
To: [hidden email]
Subject: [Anthill-pro] How do you handle multiple build requests

Hello,
I have an application that takes about 15 min to build.  I have a
repository trigger setup so that when a developer commits new code, it will
kick off a new build.  I also have a lockable resource setup so that if
multiple build requests come in within a few min of each other, I don’t
have parallel builds trying to run at the same time (the build process
can’t handle parallel builds).  However this creates a scenario where I am
getting a whole bunch of builds queued up behind each other waiting for the
previous builds to complete.

What I want to do is have the first developer commit kick off a build.  If
during that 15 min build process, 5 developers commit code, I want a second
build to kick off after the first one is complete which would get latest,
and take care of all 5 build requests.  What I don’t want is for 5 builds
to get queued up and run one at a time.  Is there a way to do this?

Thanks,
Ryan

_______________________________________________
Anthill-pro mailing list
[hidden email]
http://lists.urbancode.com/mailman/listinfo/anthill-pro

------------------------------

Message: 2
Date: Mon, 22 Dec 2008 13:00:10 -0500
From: Ryan Smith <[hidden email]>
Subject: Re: [Anthill-pro] How do you handle multiple build requests
To: "AnthillPro user and support list."
        <[hidden email]>
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=UTF-8; format=flowed

Ryan,

Which version are you using?  The latest release will merge repository
changes with builds that are waiting to obtain a lockable resource.


Ryan Smith

[hidden email] wrote:

> Hey Dan,
>
> Doesn't that mean all of your builds will then take a minimum of 10 minutes
> (even if the build actually only takes a few seconds)?  I've seen the same
> issue myself and knew that I could use the quiet period in this way, but
> I'm worried about making all of my build processes take a long time.
>
> Mark.
> ----------------------------------------------------------
>
>
>
> -----[hidden email] wrote: -----
>
>
> To: "AnthillPro user and support list." <[hidden email]>
> From: "Daniel Kirsch" <[hidden email]>
> Sent by: [hidden email]
> Date: 12/22/2008 08:39AM
> Subject: RE: [Anthill-pro] How do you handle multiple build requests
>
>
> Ryan,
>
> Use the Quiet Period to wait a specified amount of time before kicking off
> the builds.  AHP will wait the time set and then check to see if there were
> any more repository changes and if so combine all the changes in the next
> build.
>
> We use this with a 10 minute quiet period.
>
> Regards,
>
> Dan
>
> Daniel Kirsch
> Principal Software Development Engineer
> Citrix Systems, Inc. – www.citrix.com
> 14 Crosby Drive
> Bedford, MA 01730
> 781.301.9629 Office
> 781.301.0050 Fax
> [hidden email]
>
>
>
>
> From: [hidden email]
> [mailto:[hidden email]] Sent: Friday, December 19,
> 2008 4:11 PM
> To: [hidden email]
> Subject: [Anthill-pro] How do you handle multiple build requests
>
> Hello,
> I have an application that takes about 15 min to build.  I have a
> repository trigger setup so that when a developer commits new code, it will
> kick off a new build.  I also have a lockable resource setup so that if
> multiple build requests come in within a few min of each other, I don’t
> have parallel builds trying to run at the same time (the build process
> can’t handle parallel builds).  However this creates a scenario where I am
> getting a whole bunch of builds queued up behind each other waiting for the
> previous builds to complete.
>
> What I want to do is have the first developer commit kick off a build.  If
> during that 15 min build process, 5 developers commit code, I want a second
> build to kick off after the first one is complete which would get latest,
> and take care of all 5 build requests.  What I don’t want is for 5 builds
> to get queued up and run one at a time.  Is there a way to do this?
>
> Thanks,
> Ryan
>
> _______________________________________________
> Anthill-pro mailing list
> [hidden email]
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
> ------------------------------------------------------------------------
>
> _______________________________________________
> Anthill-pro mailing list
> [hidden email]
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>  

------------------------------

Message: 3
Date: Mon, 22 Dec 2008 13:04:17 -0500
From: "Daniel Kirsch" <[hidden email]>
Subject: RE: [Anthill-pro] How do you handle multiple build requests
To: "AnthillPro user and support list."
        <[hidden email]>
Message-ID:
        <[hidden email]>
Content-Type: text/plain; charset="us-ascii"

Yes, it does.  Our builds take around 40 minutes, but with developers
across the country that may be checking in changes it seemed to work
best for us.  You can set the period for something shorter if it works
better for you.

Regards,
 
Dan

-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of
[hidden email]
Sent: Monday, December 22, 2008 12:26 PM
To: AnthillPro user and support list.
Subject: RE: [Anthill-pro] How do you handle multiple build requests

Hey Dan,

Doesn't that mean all of your builds will then take a minimum of 10
minutes
(even if the build actually only takes a few seconds)?  I've seen the
same
issue myself and knew that I could use the quiet period in this way, but
I'm worried about making all of my build processes take a long time.

Mark.
----------------------------------------------------------



-----[hidden email] wrote: -----


To: "AnthillPro user and support list."
<[hidden email]>
From: "Daniel Kirsch" <[hidden email]>
Sent by: [hidden email]
Date: 12/22/2008 08:39AM
Subject: RE: [Anthill-pro] How do you handle multiple build requests


Ryan,

Use the Quiet Period to wait a specified amount of time before kicking
off
the builds.  AHP will wait the time set and then check to see if there
were
any more repository changes and if so combine all the changes in the
next
build.

We use this with a 10 minute quiet period.

Regards,

Dan

Daniel Kirsch
Principal Software Development Engineer
Citrix Systems, Inc. - www.citrix.com
14 Crosby Drive
Bedford, MA 01730
781.301.9629 Office
781.301.0050 Fax
[hidden email]




From: [hidden email]
[mailto:[hidden email]] Sent: Friday, December
19,
2008 4:11 PM
To: [hidden email]
Subject: [Anthill-pro] How do you handle multiple build requests

Hello,
I have an application that takes about 15 min to build.  I have a
repository trigger setup so that when a developer commits new code, it
will
kick off a new build.  I also have a lockable resource setup so that if
multiple build requests come in within a few min of each other, I don't
have parallel builds trying to run at the same time (the build process
can't handle parallel builds).  However this creates a scenario where I
am
getting a whole bunch of builds queued up behind each other waiting for
the
previous builds to complete.

What I want to do is have the first developer commit kick off a build.
If
during that 15 min build process, 5 developers commit code, I want a
second
build to kick off after the first one is complete which would get
latest,
and take care of all 5 build requests.  What I don't want is for 5
builds
to get queued up and run one at a time.  Is there a way to do this?

Thanks,
Ryan

_______________________________________________
Anthill-pro mailing list
[hidden email]
http://lists.urbancode.com/mailman/listinfo/anthill-pro


------------------------------

Message: 4
Date: Fri, 6 Feb 2009 14:49:56 -0800
From: [hidden email]
Subject: [Anthill-pro] Remote agent environment assignment -
        PersistenceException
To: [hidden email]
Message-ID:
        <[hidden email]>
       
Content-Type: text/plain; charset="us-ascii"

I have a remote agent i have installed and status is shown as online on
System -> Agents -> <Agent Name> screen. However when i try to assign an
environment to the remote agent i receive the following error?
I don't have this problem on my local agent configuration.

The agents and server version are 3.5.4_20812

com.urbancode.anthill3.domain.persistent.PersistenceRuntimeException:
com.urbancode.anthill3.domain.persistent.PersistenceException: Error
storing object in database
 
com.urbancode.anthill3.web.util.Conversation.unbind0(Conversation.java:187)
 com.urbancode.anthill3.web.util.Conversation.unbind(Conversation.java:49)
 
com.urbancode.anthill3.web.controller.ControllerServlet.doPost(ControllerServlet.java:462)
 javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
 javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
 
com.urbancode.anthill3.web.util.LicenseFilter.doFilter(LicenseFilter.java:78)
 
com.urbancode.anthill3.web.util.SecurityFilter.doFilter(SecurityFilter.java:132)
 
com.urbancode.anthill3.web.util.AuthorityFilter.doFilter(AuthorityFilter.java:67)
 
com.urbancode.anthill3.web.security.DisableSessionUrlFilter.doFilter(DisableSessionUrlFilter.java:127)


Any help would be much appreciated.

--Gurinder
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.urbancode.com/pipermail/anthill-pro/attachments/20090206/1a5583df/attachment.htm

------------------------------

Message: 5
Date: Fri, 6 Feb 2009 14:59:48 -0800
From: [hidden email]
Subject: Re: [Anthill-pro] Remote agent environment assignment -
        PersistenceException
To: "AnthillPro user and support list."
        <[hidden email]>
Message-ID:
        <[hidden email]>
       
Content-Type: text/plain; charset="us-ascii"

Skipped content of type multipart/alternative-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 145 bytes
Desc: not available
Url : http://lists.urbancode.com/pipermail/anthill-pro/attachments/20090206/429dfefd/attachment.gif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 145 bytes
Desc: not available
Url : http://lists.urbancode.com/pipermail/anthill-pro/attachments/20090206/429dfefd/attachment-0001.gif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1131 bytes
Desc: not available
Url : http://lists.urbancode.com/pipermail/anthill-pro/attachments/20090206/429dfefd/attachment-0002.gif

------------------------------

_______________________________________________
Anthill-pro mailing list
[hidden email]
http://lists.urbancode.com/mailman/listinfo/anthill-pro


End of Anthill-pro Digest, Vol 59, Issue 21
*******************************************

_______________________________________________
Anthill-pro mailing list
[hidden email]
http://lists.urbancode.com/mailman/listinfo/anthill-pro
Reply | Threaded
Open this post in threaded view
|

Re: Re: How do you handle multiple build requests

Ryan Smith-3-3
It is available in the 3.5.4_20812 on our site for download.


Ryan

Ryan Feiock wrote:

> Per Ryan Smith's question, I am running 3.5.3_14575.  I assume you mean 3.6?  Is there documentation on this process that I can look at?
>
> Per everyone else's comments, I tried what Dan suggested, and it does cure my problem of the builds being added to the queue, but as Mark mentioned, it now means that when a developer commits code, it could take 15 min for the quiet period and then another 15 min for the code to compile.  This is not the worst thing that could happen, but if QA is waiting for a build, it is hard to make them wait that extra 15 min ;)  I am hoping that the new functionality Ryan mentions will do what I am looking for.
>
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf Of [hidden email]
> Sent: Monday, December 22, 2008 6:00 PM
> To: [hidden email]
> Subject: Anthill-pro Digest, Vol 59, Issue 21
>
> Send Anthill-pro mailing list submissions to
> [hidden email]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
> or, via email, send a message with subject or body 'help' to
> [hidden email]
>
> You can reach the person managing the list at
> [hidden email]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Anthill-pro digest..."
>
>
> Today's Topics:
>
>    1. RE: How do you handle multiple build requests
>       ([hidden email])
>    2. Re: How do you handle multiple build requests (Ryan Smith)
>    3. RE: How do you handle multiple build requests (Daniel Kirsch)
>    4. Remote agent environment assignment - PersistenceException
>       ([hidden email])
>    5. Re: Remote agent environment assignment -
>       PersistenceException ([hidden email])
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 22 Dec 2008 10:26:22 -0700
> From: [hidden email]
> Subject: RE: [Anthill-pro] How do you handle multiple build requests
> To: "AnthillPro user and support list."
> <[hidden email]>
> Message-ID:
> <[hidden email]>
> Content-Type: text/plain; charset=UTF-8
>
> Hey Dan,
>
> Doesn't that mean all of your builds will then take a minimum of 10 minutes
> (even if the build actually only takes a few seconds)?  I've seen the same
> issue myself and knew that I could use the quiet period in this way, but
> I'm worried about making all of my build processes take a long time.
>
> Mark.
> ----------------------------------------------------------
>
>
>
> -----[hidden email] wrote: -----
>
>
> To: "AnthillPro user and support list." <[hidden email]>
> From: "Daniel Kirsch" <[hidden email]>
> Sent by: [hidden email]
> Date: 12/22/2008 08:39AM
> Subject: RE: [Anthill-pro] How do you handle multiple build requests
>
>
> Ryan,
>
> Use the Quiet Period to wait a specified amount of time before kicking off
> the builds.  AHP will wait the time set and then check to see if there were
> any more repository changes and if so combine all the changes in the next
> build.
>
> We use this with a 10 minute quiet period.
>
> Regards,
>
> Dan
>
> Daniel Kirsch
> Principal Software Development Engineer
> Citrix Systems, Inc. – www.citrix.com
> 14 Crosby Drive
> Bedford, MA 01730
> 781.301.9629 Office
> 781.301.0050 Fax
> [hidden email]
>
>
>
>
> From: [hidden email]
> [mailto:[hidden email]] Sent: Friday, December 19,
> 2008 4:11 PM
> To: [hidden email]
> Subject: [Anthill-pro] How do you handle multiple build requests
>
> Hello,
> I have an application that takes about 15 min to build.  I have a
> repository trigger setup so that when a developer commits new code, it will
> kick off a new build.  I also have a lockable resource setup so that if
> multiple build requests come in within a few min of each other, I don’t
> have parallel builds trying to run at the same time (the build process
> can’t handle parallel builds).  However this creates a scenario where I am
> getting a whole bunch of builds queued up behind each other waiting for the
> previous builds to complete.
>
> What I want to do is have the first developer commit kick off a build.  If
> during that 15 min build process, 5 developers commit code, I want a second
> build to kick off after the first one is complete which would get latest,
> and take care of all 5 build requests.  What I don’t want is for 5 builds
> to get queued up and run one at a time.  Is there a way to do this?
>
> Thanks,
> Ryan
>
> _______________________________________________
> Anthill-pro mailing list
> [hidden email]
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>
> ------------------------------
>
> Message: 2
> Date: Mon, 22 Dec 2008 13:00:10 -0500
> From: Ryan Smith <[hidden email]>
> Subject: Re: [Anthill-pro] How do you handle multiple build requests
> To: "AnthillPro user and support list."
> <[hidden email]>
> Message-ID: <[hidden email]>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> Ryan,
>
> Which version are you using?  The latest release will merge repository
> changes with builds that are waiting to obtain a lockable resource.
>
>
> Ryan Smith
>
> [hidden email] wrote:
>  
>> Hey Dan,
>>
>> Doesn't that mean all of your builds will then take a minimum of 10 minutes
>> (even if the build actually only takes a few seconds)?  I've seen the same
>> issue myself and knew that I could use the quiet period in this way, but
>> I'm worried about making all of my build processes take a long time.
>>
>> Mark.
>> ----------------------------------------------------------
>>
>>
>>
>> -----[hidden email] wrote: -----
>>
>>
>> To: "AnthillPro user and support list." <[hidden email]>
>> From: "Daniel Kirsch" <[hidden email]>
>> Sent by: [hidden email]
>> Date: 12/22/2008 08:39AM
>> Subject: RE: [Anthill-pro] How do you handle multiple build requests
>>
>>
>> Ryan,
>>
>> Use the Quiet Period to wait a specified amount of time before kicking off
>> the builds.  AHP will wait the time set and then check to see if there were
>> any more repository changes and if so combine all the changes in the next
>> build.
>>
>> We use this with a 10 minute quiet period.
>>
>> Regards,
>>
>> Dan
>>
>> Daniel Kirsch
>> Principal Software Development Engineer
>> Citrix Systems, Inc. – www.citrix.com
>> 14 Crosby Drive
>> Bedford, MA 01730
>> 781.301.9629 Office
>> 781.301.0050 Fax
>> [hidden email]
>>
>>
>>
>>
>> From: [hidden email]
>> [mailto:[hidden email]] Sent: Friday, December 19,
>> 2008 4:11 PM
>> To: [hidden email]
>> Subject: [Anthill-pro] How do you handle multiple build requests
>>
>> Hello,
>> I have an application that takes about 15 min to build.  I have a
>> repository trigger setup so that when a developer commits new code, it will
>> kick off a new build.  I also have a lockable resource setup so that if
>> multiple build requests come in within a few min of each other, I don’t
>> have parallel builds trying to run at the same time (the build process
>> can’t handle parallel builds).  However this creates a scenario where I am
>> getting a whole bunch of builds queued up behind each other waiting for the
>> previous builds to complete.
>>
>> What I want to do is have the first developer commit kick off a build.  If
>> during that 15 min build process, 5 developers commit code, I want a second
>> build to kick off after the first one is complete which would get latest,
>> and take care of all 5 build requests.  What I don’t want is for 5 builds
>> to get queued up and run one at a time.  Is there a way to do this?
>>
>> Thanks,
>> Ryan
>>
>> _______________________________________________
>> Anthill-pro mailing list
>> [hidden email]
>> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Anthill-pro mailing list
>> [hidden email]
>> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>>  
>>    
>
>
> ------------------------------
>
> Message: 3
> Date: Mon, 22 Dec 2008 13:04:17 -0500
> From: "Daniel Kirsch" <[hidden email]>
> Subject: RE: [Anthill-pro] How do you handle multiple build requests
> To: "AnthillPro user and support list."
> <[hidden email]>
> Message-ID:
> <[hidden email]>
> Content-Type: text/plain; charset="us-ascii"
>
> Yes, it does.  Our builds take around 40 minutes, but with developers
> across the country that may be checking in changes it seemed to work
> best for us.  You can set the period for something shorter if it works
> better for you.
>
> Regards,
>  
> Dan
>
> -----Original Message-----
> From: [hidden email]
> [mailto:[hidden email]] On Behalf Of
> [hidden email]
> Sent: Monday, December 22, 2008 12:26 PM
> To: AnthillPro user and support list.
> Subject: RE: [Anthill-pro] How do you handle multiple build requests
>
> Hey Dan,
>
> Doesn't that mean all of your builds will then take a minimum of 10
> minutes
> (even if the build actually only takes a few seconds)?  I've seen the
> same
> issue myself and knew that I could use the quiet period in this way, but
> I'm worried about making all of my build processes take a long time.
>
> Mark.
> ----------------------------------------------------------
>
>
>
> -----[hidden email] wrote: -----
>
>
> To: "AnthillPro user and support list."
> <[hidden email]>
> From: "Daniel Kirsch" <[hidden email]>
> Sent by: [hidden email]
> Date: 12/22/2008 08:39AM
> Subject: RE: [Anthill-pro] How do you handle multiple build requests
>
>
> Ryan,
>
> Use the Quiet Period to wait a specified amount of time before kicking
> off
> the builds.  AHP will wait the time set and then check to see if there
> were
> any more repository changes and if so combine all the changes in the
> next
> build.
>
> We use this with a 10 minute quiet period.
>
> Regards,
>
> Dan
>
> Daniel Kirsch
> Principal Software Development Engineer
> Citrix Systems, Inc. - www.citrix.com
> 14 Crosby Drive
> Bedford, MA 01730
> 781.301.9629 Office
> 781.301.0050 Fax
> [hidden email]
>
>
>
>
> From: [hidden email]
> [mailto:[hidden email]] Sent: Friday, December
> 19,
> 2008 4:11 PM
> To: [hidden email]
> Subject: [Anthill-pro] How do you handle multiple build requests
>
> Hello,
> I have an application that takes about 15 min to build.  I have a
> repository trigger setup so that when a developer commits new code, it
> will
> kick off a new build.  I also have a lockable resource setup so that if
> multiple build requests come in within a few min of each other, I don't
> have parallel builds trying to run at the same time (the build process
> can't handle parallel builds).  However this creates a scenario where I
> am
> getting a whole bunch of builds queued up behind each other waiting for
> the
> previous builds to complete.
>
> What I want to do is have the first developer commit kick off a build.
> If
> during that 15 min build process, 5 developers commit code, I want a
> second
> build to kick off after the first one is complete which would get
> latest,
> and take care of all 5 build requests.  What I don't want is for 5
> builds
> to get queued up and run one at a time.  Is there a way to do this?
>
> Thanks,
> Ryan
>
> _______________________________________________
> Anthill-pro mailing list
> [hidden email]
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 6 Feb 2009 14:49:56 -0800
> From: [hidden email]
> Subject: [Anthill-pro] Remote agent environment assignment -
> PersistenceException
> To: [hidden email]
> Message-ID:
> <[hidden email]>
>
> Content-Type: text/plain; charset="us-ascii"
>
> I have a remote agent i have installed and status is shown as online on
> System -> Agents -> <Agent Name> screen. However when i try to assign an
> environment to the remote agent i receive the following error?
> I don't have this problem on my local agent configuration.
>
> The agents and server version are 3.5.4_20812
>
> com.urbancode.anthill3.domain.persistent.PersistenceRuntimeException:
> com.urbancode.anthill3.domain.persistent.PersistenceException: Error
> storing object in database
>  
> com.urbancode.anthill3.web.util.Conversation.unbind0(Conversation.java:187)
>  com.urbancode.anthill3.web.util.Conversation.unbind(Conversation.java:49)
>  
> com.urbancode.anthill3.web.controller.ControllerServlet.doPost(ControllerServlet.java:462)
>  javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
>  javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
>  
> com.urbancode.anthill3.web.util.LicenseFilter.doFilter(LicenseFilter.java:78)
>  
> com.urbancode.anthill3.web.util.SecurityFilter.doFilter(SecurityFilter.java:132)
>  
> com.urbancode.anthill3.web.util.AuthorityFilter.doFilter(AuthorityFilter.java:67)
>  
> com.urbancode.anthill3.web.security.DisableSessionUrlFilter.doFilter(DisableSessionUrlFilter.java:127)
>
>
> Any help would be much appreciated.
>
> --Gurinder
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://lists.urbancode.com/pipermail/anthill-pro/attachments/20090206/1a5583df/attachment.htm
>
> ------------------------------
>
> Message: 5
> Date: Fri, 6 Feb 2009 14:59:48 -0800
> From: [hidden email]
> Subject: Re: [Anthill-pro] Remote agent environment assignment -
> PersistenceException
> To: "AnthillPro user and support list."
> <[hidden email]>
> Message-ID:
> <[hidden email]>
>
> Content-Type: text/plain; charset="us-ascii"
>
> Skipped content of type multipart/alternative-------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: image/gif
> Size: 145 bytes
> Desc: not available
> Url : http://lists.urbancode.com/pipermail/anthill-pro/attachments/20090206/429dfefd/attachment.gif
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: image/gif
> Size: 145 bytes
> Desc: not available
> Url : http://lists.urbancode.com/pipermail/anthill-pro/attachments/20090206/429dfefd/attachment-0001.gif
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: image/gif
> Size: 1131 bytes
> Desc: not available
> Url : http://lists.urbancode.com/pipermail/anthill-pro/attachments/20090206/429dfefd/attachment-0002.gif
>
> ------------------------------
>
> _______________________________________________
> Anthill-pro mailing list
> [hidden email]
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>
>
> End of Anthill-pro Digest, Vol 59, Issue 21
> *******************************************
>  
> ------------------------------------------------------------------------
>
> _______________________________________________
> Anthill-pro mailing list
> [hidden email]
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>  
_______________________________________________
Anthill-pro mailing list
[hidden email]
http://lists.urbancode.com/mailman/listinfo/anthill-pro
Reply | Threaded
Open this post in threaded view
|

RE: How do you handle multiple build requests

Ryan Feiock
In reply to this post by Ryan Feiock
Per Ryan Smith's suggestion, I downloaded version 3.5.4_20812, upgraded the server and agents, and sure enough the source control triggers are now performing as I want them to.  I have set the Quiet Period on all of my projects to 60 seconds, and once the build makes it past the  quiet period and starts building, any subsequent checkins are all queued up in a single build queue which is what I am looking for.  Thanks Ryan!


-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of [hidden email]
Sent: Monday, December 22, 2008 6:00 PM
To: [hidden email]
Subject: Anthill-pro Digest, Vol 59, Issue 21

Send Anthill-pro mailing list submissions to
        [hidden email]

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.urbancode.com/mailman/listinfo/anthill-pro
or, via email, send a message with subject or body 'help' to
        [hidden email]

You can reach the person managing the list at
        [hidden email]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Anthill-pro digest..."


Today's Topics:

   1. RE: How do you handle multiple build requests
      ([hidden email])
   2. Re: How do you handle multiple build requests (Ryan Smith)
   3. RE: How do you handle multiple build requests (Daniel Kirsch)
   4. Remote agent environment assignment - PersistenceException
      ([hidden email])
   5. Re: Remote agent environment assignment -
      PersistenceException ([hidden email])


----------------------------------------------------------------------

Message: 1
Date: Mon, 22 Dec 2008 10:26:22 -0700
From: [hidden email]
Subject: RE: [Anthill-pro] How do you handle multiple build requests
To: "AnthillPro user and support list."
        <[hidden email]>
Message-ID:
        <[hidden email]>
Content-Type: text/plain; charset=UTF-8

Hey Dan,

Doesn't that mean all of your builds will then take a minimum of 10 minutes
(even if the build actually only takes a few seconds)?  I've seen the same
issue myself and knew that I could use the quiet period in this way, but
I'm worried about making all of my build processes take a long time.

Mark.
----------------------------------------------------------



-----[hidden email] wrote: -----


To: "AnthillPro user and support list." <[hidden email]>
From: "Daniel Kirsch" <[hidden email]>
Sent by: [hidden email]
Date: 12/22/2008 08:39AM
Subject: RE: [Anthill-pro] How do you handle multiple build requests


Ryan,

Use the Quiet Period to wait a specified amount of time before kicking off
the builds.  AHP will wait the time set and then check to see if there were
any more repository changes and if so combine all the changes in the next
build.

We use this with a 10 minute quiet period.

Regards,

Dan

Daniel Kirsch
Principal Software Development Engineer
Citrix Systems, Inc. – www.citrix.com
14 Crosby Drive
Bedford, MA 01730
781.301.9629 Office
781.301.0050 Fax
[hidden email]




From: [hidden email]
[mailto:[hidden email]] Sent: Friday, December 19,
2008 4:11 PM
To: [hidden email]
Subject: [Anthill-pro] How do you handle multiple build requests

Hello,
I have an application that takes about 15 min to build.  I have a
repository trigger setup so that when a developer commits new code, it will
kick off a new build.  I also have a lockable resource setup so that if
multiple build requests come in within a few min of each other, I don’t
have parallel builds trying to run at the same time (the build process
can’t handle parallel builds).  However this creates a scenario where I am
getting a whole bunch of builds queued up behind each other waiting for the
previous builds to complete.

What I want to do is have the first developer commit kick off a build.  If
during that 15 min build process, 5 developers commit code, I want a second
build to kick off after the first one is complete which would get latest,
and take care of all 5 build requests.  What I don’t want is for 5 builds
to get queued up and run one at a time.  Is there a way to do this?

Thanks,
Ryan

_______________________________________________
Anthill-pro mailing list
[hidden email]
http://lists.urbancode.com/mailman/listinfo/anthill-pro

------------------------------

Message: 2
Date: Mon, 22 Dec 2008 13:00:10 -0500
From: Ryan Smith <[hidden email]>
Subject: Re: [Anthill-pro] How do you handle multiple build requests
To: "AnthillPro user and support list."
        <[hidden email]>
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=UTF-8; format=flowed

Ryan,

Which version are you using?  The latest release will merge repository
changes with builds that are waiting to obtain a lockable resource.


Ryan Smith

[hidden email] wrote:

> Hey Dan,
>
> Doesn't that mean all of your builds will then take a minimum of 10 minutes
> (even if the build actually only takes a few seconds)?  I've seen the same
> issue myself and knew that I could use the quiet period in this way, but
> I'm worried about making all of my build processes take a long time.
>
> Mark.
> ----------------------------------------------------------
>
>
>
> -----[hidden email] wrote: -----
>
>
> To: "AnthillPro user and support list." <[hidden email]>
> From: "Daniel Kirsch" <[hidden email]>
> Sent by: [hidden email]
> Date: 12/22/2008 08:39AM
> Subject: RE: [Anthill-pro] How do you handle multiple build requests
>
>
> Ryan,
>
> Use the Quiet Period to wait a specified amount of time before kicking off
> the builds.  AHP will wait the time set and then check to see if there were
> any more repository changes and if so combine all the changes in the next
> build.
>
> We use this with a 10 minute quiet period.
>
> Regards,
>
> Dan
>
> Daniel Kirsch
> Principal Software Development Engineer
> Citrix Systems, Inc. – www.citrix.com
> 14 Crosby Drive
> Bedford, MA 01730
> 781.301.9629 Office
> 781.301.0050 Fax
> [hidden email]
>
>
>
>
> From: [hidden email]
> [mailto:[hidden email]] Sent: Friday, December 19,
> 2008 4:11 PM
> To: [hidden email]
> Subject: [Anthill-pro] How do you handle multiple build requests
>
> Hello,
> I have an application that takes about 15 min to build.  I have a
> repository trigger setup so that when a developer commits new code, it will
> kick off a new build.  I also have a lockable resource setup so that if
> multiple build requests come in within a few min of each other, I don’t
> have parallel builds trying to run at the same time (the build process
> can’t handle parallel builds).  However this creates a scenario where I am
> getting a whole bunch of builds queued up behind each other waiting for the
> previous builds to complete.
>
> What I want to do is have the first developer commit kick off a build.  If
> during that 15 min build process, 5 developers commit code, I want a second
> build to kick off after the first one is complete which would get latest,
> and take care of all 5 build requests.  What I don’t want is for 5 builds
> to get queued up and run one at a time.  Is there a way to do this?
>
> Thanks,
> Ryan
>
> _______________________________________________
> Anthill-pro mailing list
> [hidden email]
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
> ------------------------------------------------------------------------
>
> _______________________________________________
> Anthill-pro mailing list
> [hidden email]
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>  

------------------------------

Message: 3
Date: Mon, 22 Dec 2008 13:04:17 -0500
From: "Daniel Kirsch" <[hidden email]>
Subject: RE: [Anthill-pro] How do you handle multiple build requests
To: "AnthillPro user and support list."
        <[hidden email]>
Message-ID:
        <[hidden email]>
Content-Type: text/plain; charset="us-ascii"

Yes, it does.  Our builds take around 40 minutes, but with developers
across the country that may be checking in changes it seemed to work
best for us.  You can set the period for something shorter if it works
better for you.

Regards,
 
Dan

-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of
[hidden email]
Sent: Monday, December 22, 2008 12:26 PM
To: AnthillPro user and support list.
Subject: RE: [Anthill-pro] How do you handle multiple build requests

Hey Dan,

Doesn't that mean all of your builds will then take a minimum of 10
minutes
(even if the build actually only takes a few seconds)?  I've seen the
same
issue myself and knew that I could use the quiet period in this way, but
I'm worried about making all of my build processes take a long time.

Mark.
----------------------------------------------------------



-----[hidden email] wrote: -----


To: "AnthillPro user and support list."
<[hidden email]>
From: "Daniel Kirsch" <[hidden email]>
Sent by: [hidden email]
Date: 12/22/2008 08:39AM
Subject: RE: [Anthill-pro] How do you handle multiple build requests


Ryan,

Use the Quiet Period to wait a specified amount of time before kicking
off
the builds.  AHP will wait the time set and then check to see if there
were
any more repository changes and if so combine all the changes in the
next
build.

We use this with a 10 minute quiet period.

Regards,

Dan

Daniel Kirsch
Principal Software Development Engineer
Citrix Systems, Inc. - www.citrix.com
14 Crosby Drive
Bedford, MA 01730
781.301.9629 Office
781.301.0050 Fax
[hidden email]




From: [hidden email]
[mailto:[hidden email]] Sent: Friday, December
19,
2008 4:11 PM
To: [hidden email]
Subject: [Anthill-pro] How do you handle multiple build requests

Hello,
I have an application that takes about 15 min to build.  I have a
repository trigger setup so that when a developer commits new code, it
will
kick off a new build.  I also have a lockable resource setup so that if
multiple build requests come in within a few min of each other, I don't
have parallel builds trying to run at the same time (the build process
can't handle parallel builds).  However this creates a scenario where I
am
getting a whole bunch of builds queued up behind each other waiting for
the
previous builds to complete.

What I want to do is have the first developer commit kick off a build.
If
during that 15 min build process, 5 developers commit code, I want a
second
build to kick off after the first one is complete which would get
latest,
and take care of all 5 build requests.  What I don't want is for 5
builds
to get queued up and run one at a time.  Is there a way to do this?

Thanks,
Ryan

_______________________________________________
Anthill-pro mailing list
[hidden email]
http://lists.urbancode.com/mailman/listinfo/anthill-pro


------------------------------

Message: 4
Date: Fri, 6 Feb 2009 14:49:56 -0800
From: [hidden email]
Subject: [Anthill-pro] Remote agent environment assignment -
        PersistenceException
To: [hidden email]
Message-ID:
        <[hidden email]>
       
Content-Type: text/plain; charset="us-ascii"

I have a remote agent i have installed and status is shown as online on
System -> Agents -> <Agent Name> screen. However when i try to assign an
environment to the remote agent i receive the following error?
I don't have this problem on my local agent configuration.

The agents and server version are 3.5.4_20812

com.urbancode.anthill3.domain.persistent.PersistenceRuntimeException:
com.urbancode.anthill3.domain.persistent.PersistenceException: Error
storing object in database
 
com.urbancode.anthill3.web.util.Conversation.unbind0(Conversation.java:187)
 com.urbancode.anthill3.web.util.Conversation.unbind(Conversation.java:49)
 
com.urbancode.anthill3.web.controller.ControllerServlet.doPost(ControllerServlet.java:462)
 javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
 javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
 
com.urbancode.anthill3.web.util.LicenseFilter.doFilter(LicenseFilter.java:78)
 
com.urbancode.anthill3.web.util.SecurityFilter.doFilter(SecurityFilter.java:132)
 
com.urbancode.anthill3.web.util.AuthorityFilter.doFilter(AuthorityFilter.java:67)
 
com.urbancode.anthill3.web.security.DisableSessionUrlFilter.doFilter(DisableSessionUrlFilter.java:127)


Any help would be much appreciated.

--Gurinder
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.urbancode.com/pipermail/anthill-pro/attachments/20090206/1a5583df/attachment.htm

------------------------------

Message: 5
Date: Fri, 6 Feb 2009 14:59:48 -0800
From: [hidden email]
Subject: Re: [Anthill-pro] Remote agent environment assignment -
        PersistenceException
To: "AnthillPro user and support list."
        <[hidden email]>
Message-ID:
        <[hidden email]>
       
Content-Type: text/plain; charset="us-ascii"

Skipped content of type multipart/alternative-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 145 bytes
Desc: not available
Url : http://lists.urbancode.com/pipermail/anthill-pro/attachments/20090206/429dfefd/attachment.gif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 145 bytes
Desc: not available
Url : http://lists.urbancode.com/pipermail/anthill-pro/attachments/20090206/429dfefd/attachment-0001.gif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1131 bytes
Desc: not available
Url : http://lists.urbancode.com/pipermail/anthill-pro/attachments/20090206/429dfefd/attachment-0002.gif

------------------------------

_______________________________________________
Anthill-pro mailing list
[hidden email]
http://lists.urbancode.com/mailman/listinfo/anthill-pro


End of Anthill-pro Digest, Vol 59, Issue 21
*******************************************

_______________________________________________
Anthill-pro mailing list
[hidden email]
http://lists.urbancode.com/mailman/listinfo/anthill-pro