I think this is quite useful, and we should try incorporating some of these in GoCD itself. Personally, I've misconfigured agents and jobs many times, and something like this would be a great time-saver.
On Fri, Dec 28, 2018 at 10:15 PM Dmitry Ledentsov <[email protected]> wrote: > Hello all! > > This is my first post here. Here's a little holiday present > https://github.com/d-led/will_it_go_cd - flying tomatoes encouraged > I have found myself making stupid configuration mistakes a couple of > times, that cannot be universally validated against. > To guard myself and, hopefully, others, against such, I've written a small > GoCD XML configuration sanity check. > E.g. it shows which agent can potentially build which job, and which > agents are available to a certain job (the other direction). > If an agent will not be used, or a pipeline will never run, you should > clearly see it. It can also probably be used as a kind of environment audit. > New analyses, corrections of my misunderstandings and other faults welcome > Dmitry > > -- > 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. > -- Akshay Dewan Phone: +91 99201 57907 ThoughtWorks -- 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.
