Purge on Passed only?
On-line help "System variables reference", in the latest version of
Build Forge: BF_STATUS Current status of a job, used internally to categorize jobs and display their state. BF_STATUS is not logged. However, BF_CALLER_STATUS appears in the logs of chained projects. It's easy to have a step in a library that purges the job if the current build status is Passed or Warning, as long as all previous steps halt on fail and there's no ".buildstatus Failed". That is, in such a case, if it reaches the step at all, it can't be a Failed build. But I want a step that purges a job if the current build status is Passed only. I want to keep it if it's Warning. My test seems to indicate that BF_STATUS is seen as an undefined variable. The library is already a chain and a pain in the neck. Is there a way I can do this without having the chain call a chain, look at BF_CALLER_STATUS, and somehow (but how?) pass that info back to the caller so it knows to do the purge? -- Tim McDaniel, tmcd@panix.com |
2 answers
|
In playing with this, I had a case when a step's pass chain completed
with a Warning status (due to the Log Filter). However, the parent project reported Passed status for the step and for the project. Is there any way that I could propagate a Warning status from a pass chain to cause a Warning status in the caller? -- Tim McDaniel, tmcd@panix.com |
Hi Tim,
I'm curious if you've thought about using a Build Class to handle the purging of jobs instead of adding it into your project. You could set your project to use a Build Class that has the 'Which' attribute set to 'Only Passed'. If you don't put the Build Class on a schedule, it will run based off the system configuration parameter 'Purge Check Time'. The default for 'Purge Check Time' is 15 minutes. bju |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.