John Muczynski created JENKINS-12733:
----------------------------------------
Summary: MARK keyword in addition to ERROR, WARNING, and INFO
Key: JENKINS-12733
URL: https://issues.jenkins-ci.org/browse/JENKINS-12733
Project: Jenkins
Issue Type: New Feature
Components: log-parser
Reporter: John Muczynski
Assignee: rgoren
Priority: Minor
Sure would be nice if ... the log-parser would have a MARK keyword in addition
to ERROR, WARNING, and INFO.
My thought is that the MARK keyword would transfer a significant message into
the
Edit Build Information
for the job. That way every build that fails with something like
/SVNException: svn: Unknown error/ could be flagged. Sure would help track
down instabilities with jobs or with Jenkins.
For added bonus points, you could also add a RESTART_BUILD keyword that would
also cause the build to be retried/restarted. That's what I manually do with
the unknown SVN errors.
Just a thought. By the way, the log-parser is the greatest thing since sliced
bread.
-John
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
