[Anthill-pro] Custom Job Pre-Condition Scripts Failure Message?
Brian_Kelly at timeinc.com
Brian_Kelly at timeinc.com
Tue Oct 6 09:40:37 CDT 2009
We have a deployment process here which consists of two workflows/jobs:
1) Generate a report showing the changes a deployment will make to the
target system
2) Makes those changes to the target system only if the above step was
run on the target environment
The first workflow, if successful, will give the build life a status of
"<environment.shortname>.validated". For example "dev.validated".
I set up a Job Pre-Condition Script for th second workflow to only
return true if the build life has been validated for the target
environment:
return new Criteria() {
public boolean matches(Object obj) throws Exception {
return
BuildLifeLookup.getCurrent().hasStatus(StatusLookup.getStatusByName(Envi
ronmentLookup.getCurrent().getShortName() + ".validated"));
}
}
This works well but the only problem is the Workflow fails without
providing any indication as to why it failed.
How can I provide a message to the user like "This build life has not
been validated against the 'dev' environment. Please validate before
attempting to deploy." ?
-brian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.urbancode.com/pipermail/anthill-pro/attachments/20091006/59faa88f/attachment.htm
More information about the Anthill-pro
mailing list