Yep. Expect I meant through the pipeline editing UI *OR* direct editing of the server's configuration XML. Sorry about my fat fingering :)
On Sun, Jul 3, 2016 at 8:29 AM John Test <[email protected]> wrote: > hi David, > > I think this answers my question > > "Configuration can be through the UI or direct editing of the server's > configuration XML" > > So if we just want to stick with Bash/Python, then we simply call it via > GoCD. > And it's possible we might have to do some configs via XML. > > Did I get that right? > > Thanks > > > On Sun, Jul 3, 2016 at 9:44 AM, David Rice <[email protected]> wrote: > >> Hi John - >> >> In terms of scripting or programming languages, you don't need to know >> anything. In fact, GoCD *cannot* be scripted. It can only be configured to >> execute your scripts and programs. (I'd suggest it's a good thing to keep >> your scripts decoupled from your CI/CD tool.) >> >> There are a few things in the UI that make invocation of Ant or Rake a >> little easier, but for the most part you will be configuring a "Custom >> Command" that instructs GoCD how to run your scripts. Configuration can >> be through the UI or direct editing of the server's configuration XML. 16.6 >> has experimental support for putting pipeline configuration in your source >> repositories. That should firm up over the next couple of releases. >> >> I'd highly recommend working through the reading and example in our Getting >> Started material <https://www.go.cd/getting-started/part-1/>. It will >> very quickly walk you through what working with GoCD will feel like. >> >> Hope that helps, >> David >> >> >> >> On Sat, Jul 2, 2016 at 8:50 PM John Test <[email protected]> wrote: >> >>> Thanks Arvind. >>> I was going through the documentation here: >>> https://docs.go.cd/current/configuration/quick_pipeline_setup.html >>> https://docs.go.cd/current/advanced_usage/command_repository.html >>> >>> I saw Ant being mentioned and commands. I wasn't clear what kind of >>> commands it is talking about. >>> Unless I overlooked, I didn't see it specifically mention "any installed >>> language" or Bash or Python. >>> >>> Since I am new to CI/CD, I am also trying to learn some of these >>> concepts. So I apologize for elementary questions. >>> >>> As an example, Jenkins pipeline requires Groovy. We can add shell >>> commands inside Groovy but the wrapper remains Groovy. >>> Is there something like this going on with GoCD? >>> >>> The question simply put: what do I need to know to build a pipeline with >>> GoCD? >>> Is this simply working with the WebUI point and click create stages and >>> inside those stages put any kind of code? >>> >>> >>> Thanks >>> >>> >>> >>> >>> On Thu, Jun 30, 2016 at 12:03 PM, Aravind SV <[email protected]> >>> wrote: >>> >>>> Hello! >>>> >>>> It depends on your definition of "scripting", but if you're looking to >>>> orchestrate existing scripts using GoCD, then yes, any of those should do. >>>> I'm curious about which documentation you read, and what made it unclear. >>>> For instance, in the Getting Started documentation, it mentions being able >>>> to use any commands when bringing up the task concept >>>> <https://www.go.cd/getting-started/part-1/#concept4>. If you can help >>>> with some information about the documentation you read, maybe we can >>>> improve it. >>>> >>>> If, by scripting, you mean using the APIs <https://api.go.cd/current/>, >>>> there are HTTP(s) endpoints and some wrappers (like gomatic >>>> <https://github.com/SpringerSBM/gomatic>, yagocd >>>> <https://github.com/grundic/yagocd>, py-gocd >>>> <https://github.com/gaqzi/py-gocd>) written and maintained by members >>>> of the GoCD community. >>>> >>>> Cheers, >>>> Aravind >>>> >>>> >>>> On Thu, Jun 30, 2016 at 11:41 AM, John Test <[email protected]> >>>> wrote: >>>> >>>>> Hello >>>>> >>>>> I am a little confused reading the docs its not clear what types of >>>>> scripting can I do with Go. >>>>> My team has standardized on Bash/Python/YAML. Can we use Go as per >>>>> this requirement? >>>>> >>>>> Thanks >>>>> John >>>>> >>>>> -- >>>>> 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. >>>>> >>>> >>>> -- >>>> 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/4_cqIot-EO0/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. >>> >> -- >> 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/4_cqIot-EO0/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. > -- 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.
