[Anthill-pro] Get Changelog Step
Eric Minick
etm at urbancode.com
Thu Jul 5 11:17:24 CDT 2007
Matthew,
If you look at the "get changelog" step, what is the status set to? I
think if the build has never reached that status, you will get that
message even if there are other builds.
Regards,
Eric
Mathew Joseph wrote:
> All,
>
> One of the generic jobs that we have configured has a "get changelog"
> step. However, on executing a workflow containing this job, the log for
> this job always indicates "First build life of project X. Get change log
> step skipped."
> This surely is not the first build life of the project. The option for
> get changelog does work for another project where we are using the
> specific "build" job as opposed to the "generic" job. What could be the
> problem? We are using AHP version 3.2.1.b112
> Mathew
>
>
>
>
>
> ________________________________
>
> From: anthill-pro-bounces at lists.urbancode.com
> [mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of Curtis
> Yanko
> Sent: Wednesday, 4 July 2007 12:26 a.m.
> To: anthill-pro at caladin.urbancode.com
> 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
>
More information about the Anthill-pro
mailing list