Project

Profile

Help

Continuous Delivery of Pulp 3 » History » Sprint/Milestone 4

daviddavis, 03/22/2018 09:44 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 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