Project

Profile

Help

Task #4784

closed

Create a tool for generating Travis config for plugins

Added by dkliban@redhat.com about 5 years ago. Updated almost 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
Actions #1

Updated by dkliban@redhat.com about 5 years ago

  • Description updated (diff)
Actions #2

Updated by amacdona@redhat.com about 5 years ago

+1, this will be helpful. Since has a lot more arguments, it probably makes sense to uses jinja or something instead of python string substitution.

Actions #3

Updated by bmbouter about 5 years ago

+1 we should do this. The bindings are hugely valuable, but the cost of adding each of these features to each repo is too high. This tool will bring that back into something we can afford to do for all bindings for all plugins!

Actions #4

Updated by dkliban@redhat.com about 5 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to dkliban@redhat.com
Actions #5

Updated by dkliban@redhat.com about 5 years ago

What about adding even more options:

test_mariadb
test_python_client

??

Actions #6

Updated by bmbouter about 5 years ago

wrote:

What about adding even more options:

test_mariadb
test_python_client

??

The test_mariadb definitly makes sense, and I think should be True by default. Also the test_docs (already in the ticket) should default to true also. Basically all the testing should default to true.

test_python_client I could take or leave at the moment. I do think we'll have it one way or another over time. So I would say +0 to that.

Also to confirm, this will use the Ansible installer to handle all the installation right? If so, we can find all those "switch plugin X to Travis" and use those when we apply the tooling.

Actions #7

Updated by dkliban@redhat.com about 5 years ago

Also to confirm, this will use the Ansible installer to handle all the installation right? If so, we can find all those "switch plugin X to Travis" and use those when we apply the tooling.

Yes, it will use ansible-pulp to deploy the pulpcore with the plugin.

Actions #8

Updated by dkliban@redhat.com about 5 years ago

  • Blocks Task #4572: Switch Travis installer to use Ansbile roles added
Actions #9

Updated by dkliban@redhat.com about 5 years ago

  • Blocks Task #4571: Switch Travis installer to use Ansbile roles added
Actions #10

Updated by dkliban@redhat.com about 5 years ago

  • Blocks Task #4574: Switch Travis installer to use Ansbile roles added
Actions #11

Updated by dkliban@redhat.com about 5 years ago

  • Status changed from ASSIGNED to POST

Added by dkliban@redhat.com about 5 years ago

Revision a457e645 | View on GitHub

Problem: no way to update Travis config for plugin

Solution: add a script for generating travis configs

This patch introduces a new script that plugin writers can use to generate Travis configs for their projects.

fixes: #4784 https://pulp.plan.io/issues/4784

Actions #12

Updated by dkliban@redhat.com about 5 years ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100
Actions #13

Updated by bmbouter over 4 years ago

  • Sprint/Milestone set to 3.0.0
Actions #14

Updated by bmbouter over 4 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Also available in: Atom PDF