Skip to content
This repository has been archived by the owner on Jan 9, 2023. It is now read-only.

[RFE] Allow Jenkins CI job to show result of testing from more than just one slave #11

Closed
iankko opened this issue Feb 21, 2016 · 5 comments
Assignees

Comments

@iankko
Copy link

iankko commented Feb 21, 2016

The scap-security-guide-pull-requests Jenkins CI job has been configured to run all pull requests checks in parallel on all three of the following systems:

  • el6 to verify OVAL-5.10 content is produced properly (mainly wrt to make validate targets),
  • el7 to verify OVAL-5.11 content is produced properly (mainly wrt to make validate targets), and
  • fedora23 to verify:
    • OVAL-5.11 content is produced properly (mainly wrt to make validate targets), but
    • also verify the ShellCheck executable won't report some regression on the syntax of provided remediation scripts

The example PR on which all three tests have been performed is the following one:
    [1] ComplianceAsCode/content#1048

The issue is having look at All checks have passed section there's only 1 successful check report, not 3.

Since we need the scap-security-guide-pull-requests jenkins CI job to:

  • pass only if the specific PR has passed on all three nodes,
  • fail otherwise,

the All checks have passed section should be enhanced to list all three test results.

@ybznek You think this would be possible to implement?

Thanks, Jan.

@jan-cerny
Copy link
Member

@ybznek Do you think it would be beneficial also for openscap pull requests?

@ybznek
Copy link
Contributor

ybznek commented Feb 23, 2016

@jan-cerny I don't think so.
We have every week https://jenkins.open-scap.org/job/openscap-maint-RUN-ON-ALL/33/ what test it on all slaves.

We don't have so many pull requests now, and we don't often break something only on one system.

@mpreisler
Copy link
Member

@ybznek Hasn't this already been implemented?

@ybznek
Copy link
Contributor

ybznek commented Aug 3, 2016

@mpreisler I think so.

@ybznek ybznek closed this as completed Aug 3, 2016
@iankko
Copy link
Author

iankko commented Aug 3, 2016

Agree. This is available already. Thanks for that, Zbynek! (assuming it has saved us a lot of SSG build process fixes already).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants