Continuous Delivery of Pulp 3 » History » Sprint/Milestone 5
bmbouter, 03/23/2018 07:02 PM
| 1 | 1 | dkliban@redhat.com | # Continuous Delivery of Pulp 3 |
|---|---|---|---|
| 2 | |||
| 3 | 5 | bmbouter | The plan for quality involves the continuous delivery of Pulp 3 where both unit and integration are run with each PR and prior to each release to PyPI. This will affect both pulpcore and pulp_file. Beta builds of pulpcore and pulp_file will be published to PyPI once a week without human intervention when pulp-smash and unit tests are passing. |
| 4 | 3 | daviddavis | |
| 5 | 5 | bmbouter | ## Pull Requests (100% Travis) |
| 6 | 3 | daviddavis | |
| 7 | The following tests are used to check pulpcore pull requests: |
||
| 8 | |||
| 9 | - unit tests |
||
| 10 | - pulp-smash pulpcore tests |
||
| 11 | - pep8 |
||
| 12 | - docs builder |
||
| 13 | - pulp-smash pulp_file tests (failures are allowed) |
||
| 14 | |||
| 15 | For pulp_file, the following jobs are used: |
||
| 16 | |||
| 17 | - pep8 |
||
| 18 | - pulp-smash pulp_file tests |
||
| 19 | |||
| 20 | 5 | bmbouter | ## Releases (100% Travis) |
| 21 | 3 | daviddavis | |
| 22 | The following tests are used to check pulpcore releases: |
||
| 23 | |||
| 24 | - pulp-smash pulpcore tests |
||
| 25 | 4 | daviddavis | - pulp-smash pulp_file tests |
| 26 | |||
| 27 | For pulp_file, we use the following tests: |
||
| 28 | |||
| 29 | - pulp-smash pulp_file tests |
||
| 30 | 3 | daviddavis | |
| 31 | ## Plugins |
||
| 32 | |||
| 33 | Other than pulp_file, plugins will be responsible for providing their own set of continuous integration jobs. |
||
| 34 | 1 | dkliban@redhat.com | |
| 35 | \[0\] http://github.com/pulp/pulp/ |
||
| 36 | \[1\] http://github.com/pulp/pulp_file/ |
||
| 37 | \[2\] https://github.com/PulpQE/pulp-smash |
.