Project

Profile

Help

Task #4784

closed

Create a tool for generating Travis config for plugins

Added by dkliban@redhat.com over 5 years ago. Updated over 4 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Plugin Template
Sprint:
Quarter:

Description

The plugin_template bootstrap script generates some Travis configs for the plugin. However, over time we have found that these configs change and require the plugin writer to manually update. As a result of this task, the plugin writer will have a script that is called generate_plugin_travis_config. It will take the following arguments:

plugin app_label (string) - the label used to find plugin repo directory and in template substitution
test_docs (boolean) - if true, Travis will test running 'make html' in the docs directory
deploy_to_pypi (boolean) - if yes, Travis will deploy to PyPI when a tag is pushed
deploy_client_to_pypi (boolean) - if yes, Travis will deploy the Python client library to PyPI when a tag is pushed
deploy_client_to_rubygems (boolean). - if yes, Travis will deploy the Ruby client library to rubygems.org

The plugin writer will still need to provide the credentials for PyPI and Rubygems.org, but the rest will be handled by this script.


Related issues

Blocks Container Support - Task #4572: Switch Travis installer to use Ansbile rolesCLOSED - CURRENTRELEASEdkliban@redhat.com

Actions
Blocks Ansible Plugin - Task #4571: Switch Travis installer to use Ansbile rolesCLOSED - CURRENTRELEASEbmbouter

Actions
Blocks RPM Support - Task #4574: Switch Travis installer to use Ansbile rolesCLOSED - CURRENTRELEASEdkliban@redhat.com

Actions

Also available in: Atom PDF