[Anthill-pro] Workflow resources

Wed May 7 10:35:15 CDT 2008

I was referring to what you posted.

"Recursively clean up the working copy, removing locks resuming
unfinished operations. If you ever get a "working copy locked" error,
run this command to remove stale locks and get your working copy into
a usable state again."

Emerson, try using it.  If you don't like the results, then try using the
set working directory step, and setting it to clean.

On Wed, May 7, 2008 at 11:32 AM, emerson cargnin <echofloripa.yell at gmail.com>
wrote:

> Sorry, now you confused me.
>
> are you saying that "svn cleanup" command does more than a cleanup?
>
> "> But as it states, it does remove the working copy.  "
>
> sorry, what states what?
>
> In AHP it says:
> "SVN Cleanup    Perform Svn Cleanup"
>
>
> Svn clean up doesn't remove the working copy.
>
> http://svnbook.red-bean.com/en/1.1/re05.html
>
> For me, the problem in using the "Set Working  Directory step, and use
> the Clean option" is that my build workflow will run in different
> directories, depending if I'm running a build from a tag workflow or a
> trunk workflow, the three use variables of the tag or the
> trunk/branch...
>
> regards
> emerson
> On 07/05/2008, Steve Boone <sbb at urbancode.com> wrote:
> >
> > Right,
> >
> > It does more than just a simple cleanup of the code.
> >
> > But as it states, it does remove the working copy.
> >
> > If you only want to remove the working copy, and not do any of the other
> > functions that an SVN cleanup does, then you can use the Set Working
> > Directory step, and use the Clean option.
> >
> > On Wed, May 7, 2008 at 11:07 AM, emerson cargnin
> > <echofloripa.yell at gmail.com> wrote:
> > > alright, I thought svn cleanup would run a "svn cleanup", which
> > > doesn't remove anything.
> > >
> > > "Recursively clean up the working copy, removing locks resuming
> > > unfinished operations. If you ever get a "working copy locked" error,
> > > run this command to remove stale locks and get your working copy into
> > > a usable state again."
> > >
> > > Ok then, I will use this, but this name is quite confusing, as it
> > > means something totally different in svn.
> > >
> > >
> > >
> > >
> > > regards
> > > emerson
> > >
> > > On 07/05/2008, Steve Boone <sbb at urbancode.com> wrote:
> > > > Check your source steps, you are using SVN right? There is an SVN
> clean
> > up
> > > > step.
> > > >
> > > > On Wed, May 7, 2008 at 11:00 AM, emerson cargnin
> > > > <echofloripa.yell at gmail.com> wrote:
> > > > >
> > > > > On 07/05/2008, Steve Boone <sbb at urbancode.com> wrote:
> > > > >
> > > > > > Emerson,
> > > > > >
> > > > > > You can add a cleanup step to the end of your build, that would
> > clean up
> > > > > > your code for you.
> > > > > >
> > > > >
> > > > > Couldn't this part of the normal clean process? The one configured
> in
> > > > > the life-cycle model? It seems like it makes sense to have it done
> > > > > during the cleanup schedule...
> > > > >
> > > > >
> > > > > > If you were re-using your working directory, this wouldn't be an
> > issue
> > > > > > either because you can choose to do clean the directory every
> time
> > you
> > > > do a
> > > > > > checkout.
> > > > >
> > > > > I was, but I would get svn errors, as in the build from tag I get
> from
> > > > > different places...
> > > > >
> > > > >
> > > > > >
> > > > > > Essentially, the feature is there, its just how you choose to
> set it
> > up.
> > > > > >
> > > > > > If you are using different working directories for each build,
> and
> > not
> > > > using
> > > > > > a clean up step, then yes, you will have plenty of code laying
> > around.
> > > > > >
> > > > >
> > > > > I couldn't find a "clean up step". The only way i can think of is
> > > > > adding a "Set Working Directory" workflow and choose the "Clean
> > > > > Working Directory"
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > >
> > > > > > On Wed, May 7, 2008 at 10:42 AM, emerson cargnin
> > > > > > <echofloripa.yell at gmail.com> wrote:
> > > > > > > Steve
> > > > > > >
> > > > > > > Is there any reason for it to keep all things it checked out?
> > > > > > > For each branch, or cuild from a tag, it dowloads more than 80
> > mega in
> > > > > > > code, JSP's and other stuff used for deployment. After a few
> > builds it
> > > > > > > clutters the disk with things that can be checkout again if
> > needed...
> > > > > > >
> > > > > > > Wouldn't be a good idea to have it as a feature?
> > > > > > >
> > > > > > > regards
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > emerson
> > > > > > >
> > > > > > >
> > > > > > > On 07/05/2008, Steve Boone <sbb at urbancode.com> wrote:
> > > > > > > > That is correct, it only cleans up the artifacts.
> > > > > > > >
> > > > > > > > On Wed, May 7, 2008 at 10:38 AM, emerson cargnin
> > > > > > > > <echofloripa.yell at gmail.com> wrote:
> > > > > > > > > But not the source that was checkedout for that workflow
> run,
> > > > right?
> > > > > > > > > at least i had to remove it manually, as after deleting
> the
> > build
> > > > > > > > > life, the sources were still there.
> > > > > > > > >
> > > > > > > > > thanks
> > > > > > > > > emerson
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On 07/05/2008, Steve Boone <sbb at urbancode.com> wrote:
> > > > > > > > > > It deletes all the artifacts of the build.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Tue, May 6, 2008 at 7:16 AM, emerson cargnin
> > > > > > > > <echofloripa.yell at gmail.com>
> > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > When I delete a build life, shouldn't it also delete
> > > > everything it
> > > > > > > > used
> > > > > > > > > > for the build life?
> > > > > > > > > > > In my case they were all still there, even after
> removing
> > the
> > > > > > > > build-life.
> > > > > > > > > > >
> > > > > > > > > > > regards
> > > > > > > > > > > emerson
> > > > > > > > > > >
> > > > _______________________________________________
> > > > > > > > > > > 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
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > > 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
> > > > > >
> > > > > >
> > > > > _______________________________________________
> > > > > 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
> > >
> >
> >
> > _______________________________________________
> > 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.urbancode.com/pipermail/anthill-pro/attachments/20080507/4116f7f8/attachment.htm