Commit Graph

4 Commits

Author SHA1 Message Date
Monty Taylor
a55f3fd1ca Ignore more things for the final artifact
We don't need tox or ci scripts in the collection, only in git.

Change-Id: Ie96dab9b7d9adac878e8c2e753a08f7ed794fc10
2020-03-26 15:22:14 -05:00
Monty Taylor
1553d34b02 Clean up minor build quibbles
collection build produces FILES.json and METADATA.json, so add them
to the .gitignore. Also, remove the version line from galaxy.yml.in
since it's generated.

Change-Id: I2ea0b04c8e56b3b7186ac2e9c475144340067636
2020-03-05 15:08:44 +00:00
Monty Taylor
e0200e9faf Fix license metadata
The galaxy upload rejects GPLv3 and requires a valid SPDX license
tag. The file headers list:

  GNU General Public License v3.0+ (see COPYING or https://www.gnu.org/licenses/gpl-3.0.txt)

which is a way of saying "3 or later" - so use that SPDX tag.

Also - the license headers refer to the file being COPYING, so
rename the file and update it in the galaxy metadata to match.

Change-Id: I6c82b49d7ce5ea8c9cde939d5d37ff54b969a598
2020-03-05 15:08:38 +00:00
Monty Taylor
5936a8f691 Add a tool to build collections with pbr
OpenStack in general uses git tags to drive versioning of artifacts.
This is important because of our code review driven workflow, since
patches don't necessarily land in a predictable sequence, so flows
requiring a version number in a file to be updated at a specific
time are problematic.

By having pbr generate the correct version number then putting that
into the galaxy.yml file, we can match the behavior without too much
undue burden.

Also ignore build_artifact directory.

Change-Id: Id02fee682fb5a4b6fd6dcb0644848e6d1269e19b
2020-02-27 08:20:43 -06:00