Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a job to verify all slaves will boot up #11

Open
pcarney8 opened this issue Apr 12, 2019 · 0 comments
Open

Add a job to verify all slaves will boot up #11

pcarney8 opened this issue Apr 12, 2019 · 0 comments

Comments

@pcarney8
Copy link
Contributor

Mentioned in the rht-labs/labs-ci-cd meetup, we need to verify all jenkins-slaves will boot up with our instance of Jenkins that we use for labs-ci-cd.

I would like to propose that we do that here, since this is the Jenkins configuration for the rht-labs instance of Jenkins.

@springdo what'd you think? It would be separate from the CI setup for containers-quickstarts

@etsauer and I had discussed where the s2i-config would live for all of the jenkins bits in containers-quickstarts which is a challenge because of the inception loops there.

But IMO I think this is the place that we add the job of booting up all the slave instances. similar to your multi-branch. It then wouldn't be inception looping in the labs-ci-cd repo.

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

No branches or pull requests

1 participant