[Anthill-pro] Workflow resources

[emerson cargnin]

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
>
>