Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publish to forge.puppet.com #11

Closed
nbarrientos opened this issue Nov 19, 2020 · 6 comments
Closed

Publish to forge.puppet.com #11

nbarrientos opened this issue Nov 19, 2020 · 6 comments

Comments

@nbarrientos
Copy link
Collaborator

We could add the module to the Puppet forge. Make sure first that the metadata is correctly filled before doing it (I think that all data is consumed automatically from metadata.json).

@duritong
Copy link
Collaborator

I would only like to do it, if we can do the push directly out of travis-ci, so we only need to flip the module version

@nbarrientos
Copy link
Collaborator Author

Makes sense, publishing when tagging a version sounds reasonable.

https://docs.travis-ci.com/user/deployment/puppetforge/

Personally I've never used it.

@duritong
Copy link
Collaborator

Also relevant:

I added an encrypted token to my forge account to the .travis.yml - but still commented out. it is available here: #21

@traylenator
Copy link
Collaborator

I'll refresh the REFERENCE now before any publish is made.

@duritong
Copy link
Collaborator

duritong commented Dec 7, 2020

Depending on how #35 goes, this might become obsolete.

@duritong
Copy link
Collaborator

duritong commented Dec 7, 2020

obsolete

@duritong duritong closed this as completed Dec 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants