Actions
Task #6150
closed
plugin-template needs to let plugins add new Travis services
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
CI/CD, Plugin Template
Sprint:
Quarter:
Description
pulp-2to3-migration had to resort to manually modifying .travis.yml:
services:
- postgresql
- redis-server
- docker
# This line manually added until the plugin-template makes this configurable.
- mongodb
Because the services list was non-configurable.
2 ways of doing this:
- Make the entire service list a variable. This is more flexible, but makes it more likely to be out-of-date in the future (and thus CI fails) when other parts of the travis template start needing new services.
- Create a variable list of services that get appended to the normal list of services. The only downside is that we might have plugin devs might specify service foo, but it later becomes a fixed service, and gets listed 2x. Duplicates might break Travis, but we could also deduplicate it in Python logic.
Actions
.
Task: plugin-template needs to let plugins add new Travis services
Solution: Create a variable list of services that get appended to the normal list of services.
This approach makes things easy for plugin devs, and prevents them from overlooking adding new services that the rest of the template needs, and running into CI failure because of it.
The only downside is that we might have plugin devs might specify service foo, but it later becomes a fixed service, and gets listed 2x. Duplicates might break Travis, but we could also deduplicate it in Python logic.
fixes: #6150