Merge ~powersj/cloud-init:create-centos-tests into cloud-init:master
| Status: | Merged |
|---|---|
| Merged at revision: | ee324391bcb436b1d3a1c44951aa1aa673005cf6 |
| Proposed branch: | ~powersj/cloud-init:create-centos-tests |
| Merge into: | cloud-init:master |
| Diff against target: |
276 lines (+264/-0) 2 files modified
tools/run-centos (+215/-0) tools/setup-centos (+49/-0) |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Server Team CI bot | continuous-integration | Approve on 2017-06-08 | |
| Ryan Harper | 2017-06-01 | Needs Fixing on 2017-06-07 | |
|
Review via email:
|
|||
Commit Message
tools: add centos scripts to build and test
* Creates centos 6 or 7 lxd container
* Sets http_proxy variable for yum if set locally
* Creates centos user
* Push local tree
* Tar's up working directory
* Pushes to container and untars
* Installs pip and yum dependencies
* As user centos it can then based on flags:
* runs unittests
* run ./packages/brpm
* run ./packages/brpm --srpm
* artifact the built *.rpm
Description of the Change
Read for review
| Scott Moser (smoser) wrote : | # |
i use 'newscript' to create scripts once they start needing options.
make sure you use it with '--spaces'
| Joshua Powers (powersj) wrote : | # |
@smoser: thanks for the template!
@rharper: responses below two big points:
1) Knowning when network is up is a better solution than the sleep. May try to see if cloud-init is finished if cloud-init is in the images or some other solution.
2) Knowing when we need to use the proxy. When this is run in the test env. we need to have the proxy set for yum to work properly.
PASSED: Continuous integration, rev:83e1b54a03f
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
Click here to trigger a rebuild:
https:/
- 950151f... by Joshua Powers on 2017-06-07
| Joshua Powers (powersj) wrote : | # |
Updated to use getnet to check if the network is up, removed extra sleeps, and added missing args.
Don't use make-tarball because we need the .git directory when we push into the container. When we are in the container doing the build, the build command itself will run the make-tarball command and needs the git log and values to know what version to call the tarball.
PASSED: Continuous integration, rev:950151f10a7
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
Click here to trigger a rebuild:
https:/
- d7a80bb... by Joshua Powers on 2017-06-08
| Joshua Powers (powersj) wrote : | # |
Now, new and improved with smoser's fixes
PASSED: Continuous integration, rev:d7a80bb0e34
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
Click here to trigger a rebuild:
https:/


PASSED: Continuous integration, rev:192b444b89b 6c6c5ab0377b9a2 509e5bb8076929 /jenkins. ubuntu. com/server/ job/cloud- init-ci/ 448/ /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=metal- amd64/448 /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=metal- arm64/448 /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=metal- ppc64el/ 448 /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=metal- s390x/448 /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=vm- i386/448
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
Click here to trigger a rebuild: /jenkins. ubuntu. com/server/ job/cloud- init-ci/ 448/rebuild
https:/