(I don't have a direct tool - but its an interesting conceptual problem) You would ordinarily want an intermediate system for this, either something custom - or a CI system like Jenkins (and perhaps Travis CI does this as well) where you would put your 'publish' logic.
The problem of course, being - when do you push? Ordinarily this would only occur with a new tag (and only if the tag is valid) ... so as long as you could capture a tag change perhaps and publish on that you might be okay. This kind of special handling might need something custom - but looks like Github supports HTTP POST requests, so you could right something yourself. Of course - you need to have a way of falling back to a poll type of system, or some manual method ... as notifies aren't perfect. If your receiver is down, or if github doesn't send the notify for some reason then you need a fallback. Jenkins CI can poll, but again - you really need a system that supports 'publishing on tag' not publishing on every change :-). ken. On Thu, Apr 12, 2012 at 3:56 PM, Dennis Hoppe <dennis.ho...@debian-solutions.de> wrote: > Hello, > > i am managing my Puppet modules with GitHub and today i discovered the > GitHub Service Hooks. Does anybody know if it is possible to use a > GitHub Service Hook to push the lates *.tar.gz into PuppetForge? > > Regards, Dennis > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
