On Thu, May 7, 2020 at 1:47 PM Frederic Gurr < frederic.g...@eclipse-foundation.org> wrote:
> A job is already in place for this here: > https://ci.eclipse.org/simrel/job/simrel.oomph.repository-analyzer.test/ That's great. However, as far as I understand, it requires the whole build (thus cannot work on Gerrit submissions yet), doesn't it? Does this job have a way to notify the "culprit" projects? Or should we just review it manually and exclude projects that generate JUnit tests failures and then make it a constraint that any change that turns the ball from green to yellow should be reverted? Is there an option/switch to filter the JUnit test output? E.g. only > output the signed artifacts tests? If not, I can try to filter the XML > output with some bash magic. In Jenkins config, checking for test files with pattern "* Simple.validSignedArtifacts <https://ci.eclipse.org/simrel/job/simrel.oomph.repository-analyzer.test/202/testReport/junit/staging._2020_06/Simple/validSignedArtifacts_org_eclipse_linuxtools_binutils_source_6_0_0_202005052310/>*" could do the job.
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
