diff --git a/source/contribute.html.erb b/source/contribute.html.erb index 3a55e2ea3d..f49f461dea 100644 --- a/source/contribute.html.erb +++ b/source/contribute.html.erb @@ -143,7 +143,7 @@ meta_keywords: "GoCD, continuous delivery, continuous delivery software, continu

How to get help

If you need any help getting started or get stuck along the way, you can talk to us on Gitter or on the Github or on the main discussion forum. We are happy to help and answer any questions.

diff --git a/source/partials/_footer.erb b/source/partials/_footer.erb index 3fe343291a..9244f3beb8 100644 --- a/source/partials/_footer.erb +++ b/source/partials/_footer.erb @@ -8,7 +8,7 @@
  • - + Chat with us diff --git a/source/posts/2015-12-22-gocd-in-2016.html.markdown.erb b/source/posts/2015-12-22-gocd-in-2016.html.markdown.erb index 72d16255fd..429f44906d 100644 --- a/source/posts/2015-12-22-gocd-in-2016.html.markdown.erb +++ b/source/posts/2015-12-22-gocd-in-2016.html.markdown.erb @@ -88,8 +88,8 @@ In 2016, GoCD and the ecosystem around it should change to make this possible and though changing everything in the application is probably a multi-year effort, the already-mentioned changes to the API have been making this easier to do, since the frontend and the backend are more clearly separated. If you have -good UI/UX skills and are willing to help, just join us on the [developers' -Gitter channel](https://gitter.im/gocd/gocd) and let us know! +good UI/UX skills and are willing to help, just join us on [GitHub +discussions](https://github.com/gocd/gocd/discussions) and let us know! ## Better support for clouds and containers diff --git a/source/posts/2017-02-16-migrating-snapci-to-gocd.html.markdown.erb b/source/posts/2017-02-16-migrating-snapci-to-gocd.html.markdown.erb index 8a21a6d763..7da5b42e6c 100644 --- a/source/posts/2017-02-16-migrating-snapci-to-gocd.html.markdown.erb +++ b/source/posts/2017-02-16-migrating-snapci-to-gocd.html.markdown.erb @@ -23,21 +23,21 @@ This post intends to serve as reference for anyone comparing GoCD to Snap CI (or Here is the obligatory comparison table. Read on ahead for our opinions. -| Features | Snap CI | GoCD | -|-----------------------------------------|-----------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Pricing | Free for public repositories. Starting at $30 for private repositories | Free, open source for all users | -| Platform | Hosted software as a service | Run on your own servers, on-premise or on the cloud | -| Source Control | Github integration | GoCD is universal (not platform or tool specific) and extensible through plugins | -| Pipeline | Built with pipelines at the core | Built with pipelines at the core | -| Pipeline Dependencies | Some support for fan-in and fan-out pipelines capabilities | First class support for fan-in/fan-out (to chain multiple pipelines) and value stream map.

    GoCD works great when it comes to modeling and visualizing workflows spanning across multiple repositories and pipelines. | -| Configuration | Configuration via UI | Configuration via source code, API and UI | -| Language Support | Ruby/JRuby, Python, Node.js/io.js, PHP, Java, Groovy/Gradle, Scala/SBT, Clojure/Leiningen, C/C++, Android | GoCD will execute tests and perform deployments written using any languages or frameworks | -| Operating System | CentOS, Ubuntu | Windows, Mac OSX and Linux (Debian/Ubuntu CentOS/RedHat) | -| Docker Support | Out of the box support for docker | Users are required to setup and configure docker on GoCD agents | -| Test Parallelization | Test parallelization up to 5 workers | Test parallelization and flexibility to scale from one machine to many machines using multiple GoCD agents | -| Branch Tracking | Automatic branch tracking and pull request integration | [Plugin](https://gocd.org/plugins) support | -| Support | First class professional support for all users | Community based support for all users
    1. [Google Group](https://groups.google.com/g/go-cd)
    2. [Gitter Chat](https://gitter.im/gocd/gocd) for code contributors

    [Professional support](https://www.thoughtworks.com//) for paid GoCD users | -| API | APIs to trigger pipelines and get pipeline history | [Rich API](https://api.gocd.org/current) to configure GoCD, trigger pipelines and get read historical data from GoCD | +| Features | Snap CI | GoCD | +|-----------------------------------------|-----------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Pricing | Free for public repositories. Starting at $30 for private repositories | Free, open source for all users | +| Platform | Hosted software as a service | Run on your own servers, on-premise or on the cloud | +| Source Control | Github integration | GoCD is universal (not platform or tool specific) and extensible through plugins | +| Pipeline | Built with pipelines at the core | Built with pipelines at the core | +| Pipeline Dependencies | Some support for fan-in and fan-out pipelines capabilities | First class support for fan-in/fan-out (to chain multiple pipelines) and value stream map.

    GoCD works great when it comes to modeling and visualizing workflows spanning across multiple repositories and pipelines. | +| Configuration | Configuration via UI | Configuration via source code, API and UI | +| Language Support | Ruby/JRuby, Python, Node.js/io.js, PHP, Java, Groovy/Gradle, Scala/SBT, Clojure/Leiningen, C/C++, Android | GoCD will execute tests and perform deployments written using any languages or frameworks | +| Operating System | CentOS, Ubuntu | Windows, Mac OSX and Linux (Debian/Ubuntu CentOS/RedHat) | +| Docker Support | Out of the box support for docker | Users are required to setup and configure docker on GoCD agents | +| Test Parallelization | Test parallelization up to 5 workers | Test parallelization and flexibility to scale from one machine to many machines using multiple GoCD agents | +| Branch Tracking | Automatic branch tracking and pull request integration | [Plugin](https://gocd.org/plugins) support | +| Support | First class professional support for all users | Community based support for all users
    1. [Google Group](https://groups.google.com/g/go-cd)
    2. [Github Discussions](https://github.com/gocd/gocd/discussions) for code contributors

    [Professional support](https://www.thoughtworks.com//) for paid GoCD users | +| API | APIs to trigger pipelines and get pipeline history | [Rich API](https://api.gocd.org/current) to configure GoCD, trigger pipelines and get read historical data from GoCD | ## What does this really mean for me? Is GoCD the tool for me? {#is-gocd-for-me} diff --git a/source/posts/2018-07-24-gocd-usage-analytics.html.markdown.erb b/source/posts/2018-07-24-gocd-usage-analytics.html.markdown.erb index 25e0bbc8a3..2162a75f03 100644 --- a/source/posts/2018-07-24-gocd-usage-analytics.html.markdown.erb +++ b/source/posts/2018-07-24-gocd-usage-analytics.html.markdown.erb @@ -66,7 +66,7 @@ You can absolutely turn this off, if you’d like. The toggle to turn off the da GoCD usage analytics -If you have any questions or would like more clarity about how and why we collect this information, chat with us on our [gitter channel](https://gitter.im/gocd/gocd) or join our [discussion forum](https://groups.google.com/g/go-cd). +If you have any questions or would like more clarity about how and why we collect this information, chat with us on our [discussion forum](https://groups.google.com/g/go-cd).