Continuous Delivery of Pulp 3 » History » Sprint/Milestone 3
daviddavis, 03/22/2018 09:06 PM
1 | 1 | dkliban@redhat.com | # Continuous Delivery of Pulp 3 |
---|---|---|---|
2 | |||
3 | 3 | daviddavis | The plan for continuous delivery of Pulp 3 is to gate every pull request for pulp\[0\] and pulp_file\[1\] repositories using tests including those provided by pulp-smash\[2\] and to publish new builds of pulpcore and pulp_file to PyPI once a week without human intervention. |
4 | |||
5 | ## Pull Requests |
||
6 | |||
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 | ## Releases |
||
21 | |||
22 | The following tests are used to check pulpcore releases: |
||
23 | |||
24 | - pulp-smash pulpcore tests |
||
25 | |||
26 | ## Plugins |
||
27 | |||
28 | Other than pulp_file, plugins will be responsible for providing their own set of continuous integration jobs. |
||
29 | 1 | dkliban@redhat.com | |
30 | \[0\] http://github.com/pulp/pulp/ |
||
31 | \[1\] http://github.com/pulp/pulp_file/ |
||
32 | \[2\] https://github.com/PulpQE/pulp-smash |