Hi Support Team,
my ContinuaCI build process has some stages which are not essential to the build process itself; they are only ‘nice to have’. For example:
- the new binaries are copied to a local installation of the software to always have the most recent version on the build server
- check-in after build
These actions could fail because of
- access rights (sometimes the copy action cannot update the files because of user rights / different NTFS file owner) or because a programm to be replaced is currently running
- merge conflicts when checking-in
These situations should not lead to a failed build, because it can be fixed after build. Therefore I surrounded them with try/except.
It would be nice to be able to mark such stages as somewhat like ‘warning’=yellow instead of ‘success’=green for a better recognition of additional tasks required after build.
Would you mind to consider this to be implemented in future releases?
Best regards
Michael
Hi Micheal,
Yes, we have had another request for this. It is currently on our to-do list. I’ll increase the priority.
Hi Micheal,
do you now in which release this will be included?
For our build process it will be a very nice feature. Helpful would also be the possibility to set a State failed (red) but run the next state anyway.
Regards
Marcel
Hi Marcel,
We don’t have a timeframe for this, but thank you for your request which has been noted.
Hi there,
I’m playing around with the trial version and found the same issue. For some steps I would like to have a warning only.
Maybe there is a work around? I only use calls to external programs and monitor the results for key words.
Best regards
Bernd
Hi Bernd,
We introduced experimental support for showing warnings in version v1.8.1.229. This is currently disabled by default and can be enabled by setting the Server property Server.AllViews.ShowStageWarnings to True. You can then edit the Server property Actions.Messages.WarningPatterns to define text or patterns to match against the action output and pick up as warnings. Any feedback on this new feature is welcome.
You can also send warning messages from an external program (run from a Continua CI action) by writing a custom log message to standard output.
e.g.
@@continua[message value=‘This will be logged as a warning’ status=‘warning’ ]