The current build pipeline greps for errors only in the following cases:
findText regexp: '.*ERROR.*', fileSet: 'ftests/nuxeo-server-cmis-tests/**/log/server.log' findText regexp: '.*ERROR.*', fileSet: 'ftests/nuxeo-server-hotreload-tests/**/log/server.log' findText regexp: '.*ERROR.*', fileSet: 'ftests/nuxeo-server-tests/**/log/server.log' findText regexp: '.*ERROR.*', fileSet: 'ftests/nuxeo-jsf-to-web-ui-ftests/**/log/server.log'
Ideally we should grep for errors in packages functional tests too:
findText regexp: ".*ERROR.*", fileSet: "ftests/**/log/server.log"
The current behaviour might be linked to the fact that some errors, visible in packages ftests, should not make the build fail (after a grep on a nuxeo build artifacts, no error log was visible).
There are some attributes to the plugin to change the build result depending on logs found, all ERROR logs should be reported to the console in all cases.
- is related to
-
NXP-30137 Fix random ftest error log on NXAuditEventsService
- Resolved
-
NXP-30146 Fix random ftest error log on AuditStorageLogWriterPool
- Resolved
-
NXP-30155 Split functional test runs in tiers
- Resolved
-
NXP-29984 Migrate Runtime Contributions to XRegistry Annotations
- Resolved
- Is referenced in
- links to