Yes, I could do that, but I disagree with your characterization of the request.
GoCD claims to be a CI/CD tool. While there are definitely classes of apps that don't need anything other than a single server on which to build and run its integration tests, there are just as certainly classes of apps where that is not sufficient. And, I can't think of any apps right now where deployment simply means "run build script on remote server". So, I don't feel like what I'm asking for is "random admin tasks", rather I feel like it's an integral part of handling the deployment and, in many cases, integration testing of an app. If not, what differentiates a CI/CD system from a build server? On Fri, Nov 4, 2016 at 1:34 PM Jason Whittington < [email protected]> wrote: > You would not need to write a material. You could set up code independent > of GoCD that runs on a schedule (e.g. a cron job) and query infrastructure. > This job could trigger some kind of cleanup pipeline via the GoCD pipeline > scheduling API. > > I don't really know that I recommend it though -- GoCD is best at "moving > bits through environments" not "random admin tasks". I think you might be > happier if you just set up a cron job that queries the infrastructures and > tears it down as needed and just keep the CI/CD tool out of it. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "go-cd" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/go-cd/SD9YlLPqIkQ/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
