On Tue, Apr 29, 2014 at 5:28 PM, Stephen Connolly
<stephen.alan.conno...@gmail.com> wrote:
> Basically if you can't trust your build machines, you have some issues.
>
> If you can't trust the code you are building, you have worse issues.
>
> The current block on releasing the literate plugin is providing a good
> isolation for pull request builds so that drive-by pull requests on GitHub
> don't crash your server... As soon as I get that in place I will push the
> pull request code to literate so people can use it. Would be irresponsible
> to push the pull request support into literate without such protections.
This may be a stretch, but would it be feasible to make something like
a literate 'deployment scheduler" where you could have some
high-level, human readable description of what things to deploy to
what groups of nodes at specific times? Then mash that up against
the maintenance schedule for the targets, users authorized to override
the schedule, and some node/artifact specific code to do the work and
spin up the jobs?
I haven't found a good cross-platform tool to do deployments in
closely-controlled environments. Jenkins doesn't seem quite right
either but it gets the cross-platform part right and could probably
handle a bunch of nodes with connect-on-demand ssh.
--
Les Mikesell
lesmikes...@gmail.com
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
