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 fedora28 testing container, run container tests in parallel #86

Merged
merged 1 commit into from
Sep 12, 2018

Conversation

dirgim
Copy link
Collaborator

@dirgim dirgim commented Sep 12, 2018

This adds the fedora28 testing container to the contra-env-setup CI.
The container contains a fix for a libvirt bug that occurs when first starting the minishift VM, running fix-minishift.sh in the pipeline resolves the issue.
Jenkinsfile has been updated to run tests on both centos7 and fedora28 in parallel.
JUnit archiving has been added, and the test logs have corresponding prefixes for each container.

This adds the fedora28 testing container to the contra-env-setup CI.
The container contains a fix for a libvirt bug that occurs when first starting the minishift VM, running fix-minishift.sh resolves the issue.
Jenkinsfile has been updated to run tests on both centos7 and fedora28 in parallel.
JUnit archiving has been added, and the test logs have corresponding prefixes for each container.

ed:   test/config/Dockerfiles/contra-env-setup-test-c7/prepare_and_test.sh
Copy link
Member

@arilivigni arilivigni left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM
One question is there logic specific about the containers that are currently in the sample project. Does this need to be more general? Is it only for key services like Jenkins? Will we need something specific for the influxdb and grafana or the next things?

@dirgim
Copy link
Collaborator Author

dirgim commented Sep 12, 2018

Currently it's just (as much as it's possible) generically checking for the jenkins master and slave because that's expected to be included in every use case. I would include any specific tests into a separate CI pipeline that's testing the sample project specifically.

@arilivigni
Copy link
Member

[merge]

@dirgim
Copy link
Collaborator Author

dirgim commented Sep 12, 2018

Yeah, I'll have to add a merge job with image rebuilds.

@arilivigni arilivigni merged commit 0721d15 into CentOS-PaaS-SIG:master Sep 12, 2018
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

Successfully merging this pull request may close these issues.

None yet

2 participants