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

Deployment to Forge #185

Closed
petems opened this issue May 3, 2017 · 0 comments
Closed

Deployment to Forge #185

petems opened this issue May 3, 2017 · 0 comments
Labels
enhancement New feature or request

Comments

@petems
Copy link
Member

petems commented May 3, 2017

@arioch So we have a few choices for this:

One, we add something to the .travis.yml like this:

deploy:
  provider: puppetforge
  user: puppet
  password:
    secure: "KOhDZN2IcdlCbnz4i6wCbh1RXK/TZW7GTzxCwuM4wnSVTit/I9TpD2AdEIHCYg3D7V0BKYqvKhVl0zVlabinHltDf0l9FJ0ic9yfXF3M2gcvJtOKjn+Xm8rC+UDFeiaIByDjE6bc7/Ys0SBQq/yLXkjI+OShqhtdo26ZIXiPVGo="
  on:
    tags: true
    # all_branches is required to use tags
    all_branches: true
    # Only publish the build marked with "DEPLOY_TO_FORGE"
    condition: "$DEPLOY_TO_FORGE = yes"

This will auto deploy everytime a build is succesful and the tag is changed.

In the mean time, I might just ask you do do a 2.0.0 tag release soon because setting up the above will be a PITA in the short term (but much better in the long term! 😄 )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant