-
Notifications
You must be signed in to change notification settings - Fork 18
Release artifact build
command
#116
Comments
for #116, for the stuff in the tarball (releases/v1.0.0.tar.gz), what should the name of the top level dir be if there is one? ie, when v1.0.0.tar.gz is extracted, what would 'some_dir' be below (if there is a top level dir)?
|
existing traditional role content archives as created by github end up with names like "ansible-role-nginx-2.5.0/" github download url: https://github.com/geerlingguy/ansible-role-nginx/archive/2.5.0.tar.gz
|
For existing multi-content repos something like 'testing.ansible_testing_content' ends up "ansible-testing-content-1.3.0" github url: https://github.com/atestuseraccount/ansible-testing-content/archive/1.3.0.tar.gz tar contents:
|
#130 has a good chunk of this feature. |
We've been given the green light to move forward with Artifact Build and Import Proposal
In support of that, Mazer needs to have a
build
command that does the following, as taken directly from the proposal:From within the root of the project (the Collection or repository directory), the user runs the
mazer build
command to create a build artifact, which does the following:galaxy.yml
, the collection level meta data filegalaxy.yml
, including the version information.The text was updated successfully, but these errors were encountered: