[Anthill-pro] Cleanup Policies
Jason Schatz
jes at urbancode.com
Thu Jul 5 09:03:28 CDT 2007
Curtis,
The WorkDir script will create the same folder on each agent that it is
run on and will reuse that folder if it already exists for that agent.
Currently we do not support an update operation in subversion, or any
scm for that matter. However, I tested this on my machine and it looks
like performing the same checkout to a directory twice will first
perform a checkout and then do an update for each subsequent checkout.
This was added to subversion to allow users to be able to run the
checkout command again if their first checkout attempt failed.
Take a look at the logs of your svn checkout commands. Svn prefixes all
of its updates with
A Added
D Deleted
U Updated
C Conflict
G Merged
In a standard checkout all the files listed would have an A before
them. If any of your files lines have a different letter at the front
of them then the checkout is actually updating those files.
Let me know if you have any additional thoughts/questions.
Thanks,
Jason
Curtis Yanko wrote:
>
> One last question, what is the WorkDir script (not the name but the
> actual code) of the out-of-the-box experience. I didn't think it
> re-used a folder.
>
> If we're going to re-use a folder then it's a shame I can't also do a
> 'svn update' and save on network traffic for my larger projects.
>
> - Curtis Yanko
> UnitedHealth Group IT
> Mail Route: CT028-06SA
> Internet email: curt_yanko at uhc.com
> Office 860.702.9059
> Cell 860.729.8171
>
>
>
> *Curtis Yanko/CT/Unitedmail at Unitedmail*
> Sent by: anthill-pro-bounces at caladin.urbancode.com
>
> 07/03/2007 08:25 AM
> Please respond to
> anthill-pro at caladin.urbancode.com
>
>
>
> To
> anthill-pro at caladin.urbancode.com
> cc
>
> Subject
> Re: [Anthill-pro] Cleanup Policies
>
>
>
>
>
>
>
>
>
> Eric,
>
> Thanks, I also searched the archives and concluded that I misinterpreted
> your suggestion to Jeff Rogers on Non-Originating Workflows. We'll switch
> back now armed with this new perspective. Glad we're still small!
>
> - Curtis Yanko
> United Health Technologies
> Mail Route: CT028-06SA
> Internet email: curt_yanko at uhc.com
> Office 860.702.9059
> Cell 860.729.8171
>
>
>
>
> Eric Minick <etm at urbancode.com>
> Sent by: anthill-pro-bounces at caladin.urbancode.com
> 07/02/2007 04:08 PM
> Please respond to
> anthill-pro at caladin.urbancode.com
>
>
> To
> anthill-pro at caladin.urbancode.com
> cc
>
> Subject
> Re: [Anthill-pro] Cleanup Policies
>
>
>
>
>
>
> Curtis,
>
> I walked through some of the archives to see where we had told you to
> use a different working directory for every build life. I couldn't find
> it, but I imagine there might be a situation where its appropriate.
>
> For the standard case of running secondary workflows though, delivered
> artifacts are what its all about. You want to deliver everything that
> you will later use at the end of the build, and then reuse that
> workspace for the next build. At deployment or test time, you will
> normally use a "resolve my artifacts" step to pull back down the
> delivered artifacts so they can be worked on.
>
> As for the cleanup policies, my understanding is that if both Days and
> Count is present, Anthill will require a build to pass both boundaries
> before removing it. So if you have 7 days and 20 builds listed, you
> would see every build from the last 7 days. If that turned out to be
> only 15 builds, the next 5 most recent builds that achieved the given
> status would remain.
>
> Regards,
>
> Eric
>
> Curtis Yanko wrote:
> > Steve,
> >
> > We are in fact using a different working directory for every buildlife,
> > which I thought was desirable from a previous discussion on this
> listserv.
> > How else can I run a secondary workflows against a historical buildlife?
> > What will Clean Up steps do? ...just Derived Artifacts? Can I blow away
> > everything and do a re-build at some later point?
> >
> > My point on the 'Days' & 'Count' is just what you said, if I leave
> 'Days'
> > blank the cleanups never run! ...so I need to populate both if I want it
> > to work (or I suppose just Days but that's not what I want, I want count
> > based. Does Days trump Count?
> >
> > - Curtis Yanko
> > United Health Technologies
> > Mail Route: CT028-06SA
> > Internet email: curt_yanko at uhc.com
> > Office 860.702.9059
> > Cell 860.729.8171
> >
> >
> >
> >
> > "Steve Boone" <sbb at urbancode.com>
> > Sent by: anthill-pro-bounces at caladin.urbancode.com
> > 07/02/2007 02:59 PM
> > Please respond to
> > anthill-pro at caladin.urbancode.com
> >
> >
> > To
> > anthill-pro at caladin.urbancode.com
> > cc
> > anthill-pro at caladin.urbancode.com
> > Subject
> > Re: [Anthill-pro] Cleanup Policies
> >
> >
> >
> >
> >
> >
> > Curtis,
> >
> > If you are running out of space on an agent there is most likely two
> > causes. If you are using a different working directory for every
> project
> > you are building, this practice can take up a good portion of space,
> > especially if you are building a large number of projects. The second
> > cause
> > could be your codestation cache has grown out of control.
> >
> > If you are using a different working directory for each project, you
> will
> > need to create a cleanup step, and have it run after your build
> completes.
> > This will ensure that the files created are removed.
> >
> > If this is not the case, and you are using cleanup steps within your
> > projects, then odds are your codestation cache has grown rather large.
> > Check your ~/.codestation/cache directory to see if that is what is
> > consuming the majority of your space. If it is, you can delete the
> files
> > from there, and to prevent this from happening in the future you can
> turn
> > the agent caching off.
> >
> > To do this, edit the codestation.properties file located in
> > ~/.codestation/ If the file does not exist, go ahead and create it.
> > Add
> > the following line to the file.
> >
> > codstation.noCache=true
> >
> >
> > As for the Cleanup Policies, anytime they run, they will create a Misc.
> > Job
> > that you will see on the dashboard (much like an email notification, or
> > other Misc Job) if you are not seeing any Misc Jobs for cleanup, then
> they
> > most likely are not running. You do not need to set both the "Days" and
> > "Count" fields, the Days field can be left empty if you choose to keep
> the
> > buildlife indefinitely.
> >
> > Cleanup Policies only clean the server, it will clean up logs when
> > corresponding job traces are deleted, but it does not delete working
> > directories for jobs. If this is the functionality you are looking for,
> I
> > would suggest adding a cleanup step to your individual jobs as you find
> > necessary. You could also create a cleanup workflow, and set it to a
> > trigger and have it cleanup only when you felt it was appropriate.
> >
> > We hope to release version 3.2.2 this week (pending it's progress
> through
> > QA), this release will address the issues with codestation and
> > transferring
> > files between Windows and Linux/Unix.
> >
> > Hopefully this information will get you back on track, if you need any
> > assistance, feel free to contact us at support at urbancode.com
> >
> > Thank you,
> > Steve Boone
> >
> >
> >
> >
> > On 7/2/07, Curtis Yanko <curt_yanko at uhc.com> wrote:
> >
> >> All,
> >>
> >> One of my agents has quickly consumed it's available disk space so I am
> >> trying to get a handle on deleting build life's and cleanup policies.
> >>
> >> It seems that deleting them in the admin interface only removes them
> >>
> > from
> >
> >> the BMS. I also have had no luck with clean up policies, can't see them
> >> running nor confirm that any cleanups are taking place. One possible
> >>
> > item we
> >
> >> are exploring is that both 'Days' and 'Count' need to be populated
> where
> >>
> > as
> >
> >> I had only populated 'Count' thinking it was an OR situation.
> >>
> >> Do cleanup policies triggers cleanups on agents?
> >>
> >> I also have not heard any word on an updated build/release to address
> >> Windoze/*nix issues, please advise.
> >>
> >> - Curtis Yanko
> >> United Health Technologies
> >> Mail Route: CT028-06SA
> >> Internet email: curt_yanko at uhc.com
> >> Office 860.702.9059
> >> Cell 860.729.8171
> >>
> >>
> >> 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.
> >>
> >> _______________________________________________
> >> 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.
> >
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > 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.
>
>
>
> _______________________________________________
> 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.
>
> ------------------------------------------------------------------------
>
>
> Eric,
>
> Thanks, I also searched the archives and concluded that I
> misinterpreted your suggestion to Jeff Rogers on Non-Originating
> Workflows. We'll switch back now armed with this new perspective. Glad
> we're still small!
>
> - Curtis Yanko
> United Health Technologies
> Mail Route: CT028-06SA
> Internet email: curt_yanko at uhc.com
> Office 860.702.9059
> Cell 860.729.8171
>
>
>
> *Eric Minick <etm at urbancode.com>*
> Sent by: anthill-pro-bounces at caladin.urbancode.com
>
> 07/02/2007 04:08 PM
> Please respond to
> anthill-pro at caladin.urbancode.com
>
>
>
> To
> anthill-pro at caladin.urbancode.com
> cc
>
> Subject
> Re: [Anthill-pro] Cleanup Policies
>
>
>
>
>
>
>
>
>
> Curtis,
>
> I walked through some of the archives to see where we had told you to
> use a different working directory for every build life. I couldn't find
> it, but I imagine there might be a situation where its appropriate.
>
> For the standard case of running secondary workflows though, delivered
> artifacts are what its all about. You want to deliver everything that
> you will later use at the end of the build, and then reuse that
> workspace for the next build. At deployment or test time, you will
> normally use a "resolve my artifacts" step to pull back down the
> delivered artifacts so they can be worked on.
>
> As for the cleanup policies, my understanding is that if both Days and
> Count is present, Anthill will require a build to pass both boundaries
> before removing it. So if you have 7 days and 20 builds listed, you
> would see every build from the last 7 days. If that turned out to be
> only 15 builds, the next 5 most recent builds that achieved the given
> status would remain.
>
> Regards,
>
> Eric
>
> Curtis Yanko wrote:
> > Steve,
> >
> > We are in fact using a different working directory for every buildlife,
> > which I thought was desirable from a previous discussion on this
> listserv.
> > How else can I run a secondary workflows against a historical buildlife?
> > What will Clean Up steps do? ...just Derived Artifacts? Can I blow away
> > everything and do a re-build at some later point?
> >
> > My point on the 'Days' & 'Count' is just what you said, if I leave
> 'Days'
> > blank the cleanups never run! ...so I need to populate both if I want it
> > to work (or I suppose just Days but that's not what I want, I want count
> > based. Does Days trump Count?
> >
> > - Curtis Yanko
> > United Health Technologies
> > Mail Route: CT028-06SA
> > Internet email: curt_yanko at uhc.com
> > Office 860.702.9059
> > Cell 860.729.8171
> >
> >
> >
> >
> > "Steve Boone" <sbb at urbancode.com>
> > Sent by: anthill-pro-bounces at caladin.urbancode.com
> > 07/02/2007 02:59 PM
> > Please respond to
> > anthill-pro at caladin.urbancode.com
> >
> >
> > To
> > anthill-pro at caladin.urbancode.com
> > cc
> > anthill-pro at caladin.urbancode.com
> > Subject
> > Re: [Anthill-pro] Cleanup Policies
> >
> >
> >
> >
> >
> >
> > Curtis,
> >
> > If you are running out of space on an agent there is most likely two
> > causes. If you are using a different working directory for every
> project
> > you are building, this practice can take up a good portion of space,
> > especially if you are building a large number of projects. The second
> > cause
> > could be your codestation cache has grown out of control.
> >
> > If you are using a different working directory for each project, you
> will
> > need to create a cleanup step, and have it run after your build
> completes.
> > This will ensure that the files created are removed.
> >
> > If this is not the case, and you are using cleanup steps within your
> > projects, then odds are your codestation cache has grown rather large.
> > Check your ~/.codestation/cache directory to see if that is what is
> > consuming the majority of your space. If it is, you can delete the
> files
> > from there, and to prevent this from happening in the future you can
> turn
> > the agent caching off.
> >
> > To do this, edit the codestation.properties file located in
> > ~/.codestation/ If the file does not exist, go ahead and create it.
> > Add
> > the following line to the file.
> >
> > codstation.noCache=true
> >
> >
> > As for the Cleanup Policies, anytime they run, they will create a Misc.
> > Job
> > that you will see on the dashboard (much like an email notification, or
> > other Misc Job) if you are not seeing any Misc Jobs for cleanup,
> then they
> > most likely are not running. You do not need to set both the "Days" and
> > "Count" fields, the Days field can be left empty if you choose to
> keep the
> > buildlife indefinitely.
> >
> > Cleanup Policies only clean the server, it will clean up logs when
> > corresponding job traces are deleted, but it does not delete working
> > directories for jobs. If this is the functionality you are looking
> for, I
> > would suggest adding a cleanup step to your individual jobs as you find
> > necessary. You could also create a cleanup workflow, and set it to a
> > trigger and have it cleanup only when you felt it was appropriate.
> >
> > We hope to release version 3.2.2 this week (pending it's progress
> through
> > QA), this release will address the issues with codestation and
> > transferring
> > files between Windows and Linux/Unix.
> >
> > Hopefully this information will get you back on track, if you need any
> > assistance, feel free to contact us at support at urbancode.com
> >
> > Thank you,
> > Steve Boone
> >
> >
> >
> >
> > On 7/2/07, Curtis Yanko <curt_yanko at uhc.com> wrote:
> >
> >> All,
> >>
> >> One of my agents has quickly consumed it's available disk space so I am
> >> trying to get a handle on deleting build life's and cleanup policies.
> >>
> >> It seems that deleting them in the admin interface only removes them
> >>
> > from
> >
> >> the BMS. I also have had no luck with clean up policies, can't see them
> >> running nor confirm that any cleanups are taking place. One possible
> >>
> > item we
> >
> >> are exploring is that both 'Days' and 'Count' need to be populated
> where
> >>
> > as
> >
> >> I had only populated 'Count' thinking it was an OR situation.
> >>
> >> Do cleanup policies triggers cleanups on agents?
> >>
> >> I also have not heard any word on an updated build/release to address
> >> Windoze/*nix issues, please advise.
> >>
> >> - Curtis Yanko
> >> United Health Technologies
> >> Mail Route: CT028-06SA
> >> Internet email: curt_yanko at uhc.com
> >> Office 860.702.9059
> >> Cell 860.729.8171
> >>
> >>
> >> 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.
> >>
> >> _______________________________________________
> >> 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.
> >
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > 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.
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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