In other git environments, I'm able to have the git server perform a post-receive githook to push user branches out to the puppetmaster:/etc/puppet/environments/branchname.
Stash githook support is different so I'm running into an issue where I have not seen any good examples of this workflow.
If you need to you can certainly use raw Git hooks on the Stash server. But otherwise, or in general, we recommend using our Repository Hooks:
Forgive the naive question - are you just looking to mirror the repository to your puppet environment?
My apologies - I'm not all that familar with exact mechanics of Puppet. Can/does puppet do polling/fetching to receive updates? Or will you need to push to the puppet servers from Stash? If the latter is the mirror plugin linked above enough or if not then why?
Sorry for the 20 questions, I just need to understand exactly what you're trying to do.
Thanks Alan, that helps.
One option would be to just use raw Git hooks, putting the SSH key on the filesystem somewhere. You could use the External Hooks plugin as a mechanism to launch the script if you want per-repository configuration.
Another option would be to send a webhook to the server, which listens on HTTP and then does the fetch that way.
Do any of those options sound appealing/useful?
There are the three input parameters listed on the marketplace page:
Specified executables will receive "$from_ref $to_ref $ref_name" lines on stdin (see "man githooks").
For the environmental variables, the best place is to go directly to the source:
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot