Emily von Hoffmann ✨ · 2bb4c14e
--- a/source/posts/2017-06-06-whats-next-for-gitlab-ci.html.md 0 → 100644
+++ b/source/posts/2017-06-06-whats-next-for-gitlab-ci.html.md 0 → 100644
+
+## GitLab CI Is the Most Popular Next-Generation CI System
+
+Our commitment to seamless integration extends to CI. Integrated CI/CD is both more time and resource efficient than a set of distinct tools, and allows developers greater control over their build pipeline, so they can spot issues early and address them at a relatively low cost. Tighter integration between different stages of the development process makes it easier to cross-reference code, tests, and deployments while discussing them, allowing you to see the full context and iterate much more rapidly. We've heard from customers like [Ticketmaster](https://about.gitlab.com/2017/06/07/continous-integration-ticketmaster/) that adopting GitLab CI can transform the entire SDLC, in their case helping the Ticketmaster mobile development team deliver on the longstanding goal of weekly releases. As more and more companies look to embrace CI as part of their development methodology, having CI fully integrated into their overall SDLC solution will ensure these companies are able to realize the full potential of CI. You can read more about the benefits of integrated CI in our white paper, [Scaling Continuous Integration]().
+
+In his post on [building Heroku CI](https://blog.heroku.com/building-tools-for-developers-heroku-ci), Heroku’s Ike DeLorenzo noted that GitLab CI is “clearly the biggest mover in activity on Stack Overflow,” with more popularity than both Travis CI and Circle CI:
+
+![Image via Heroku blog](/images/blogimages/heroku-questions-chart.png){: .shadow}<br>
+
+While the use of Jenkins for CI is still higher than any other solution, we see more and more organizations moving from Jenkins, because upgrading their Jenkins server is a brittle process. The last two big things that GitLab CI lacked were scheduled builds (contributed to [GitLab 9.2](https://about.gitlab.com/2017/05/22/gitlab-9-2-released/)) and cross-project builds, which are scheduled for GitLab 9.3 to be released on June 22. 
+
+## Auto DevOps Is Next
+
+We remain [hard at work](https://gitlab.com/gitlab-org/gitlab-ce/issues/32639) continuing to make the [idea to production](https://about.gitlab.com/handbook/product/i2p-demo/) flow even better. [Our direction](https://about.gitlab.com/direction/) is to fully automate DevOps with the concept of [Auto DevOps](https://gitlab.com/gitlab-org/gitlab-ee/issues/2517). In a cloud-native world, developers have many projects, and it doesn't make sense to have to set up their tools for every one of them. With help from the wider community we'll ensure that everything works out of the box, from code quality metrics to Review Apps, and from metrics to autoscaling.
+
+Watch our Head of Product Mark Pundsack demonstrate our Auto DevOps vision, including Auto Build, Auto CI, Auto Code Climate, Auto Deploy, and Auto Monitoring: [update copy to be more descriptive once demo is done]
--- a/source/posts/2017-06-06-whats-next-for-gitlab-ci.html.md
+++ b/source/posts/2017-06-06-whats-next-for-gitlab-ci.html.md

 ![Image via Heroku blog](/images/blogimages/heroku-questions-chart.png){: .shadow}<br>

-While the use of Jenkins for CI is still higher than any other solution, we see more and more organizations moving from Jenkins, because upgrading their Jenkins server is a brittle process. The last two big things that GitLab CI lacked were scheduled builds (contributed to [GitLab 9.2](https://about.gitlab.com/2017/05/22/gitlab-9-2-released/)) and cross-project builds, which are scheduled for GitLab 9.3 to be released on June 22.
+While the use of Jenkins for CI is still higher than any other solution, we see more and more organizations moving from Jenkins, because upgrading their Jenkins server is a brittle process. The last two big things that GitLab CI lacked were scheduled builds (contributed to [GitLab 9.2](https://about.gitlab.com/2017/05/22/gitlab-9-2-released/)) and cross-project builds (released in [GitLab 9.3 on June 22](https://about.gitlab.com/2017/06/22/gitlab-9-3-released/)).

 ## Auto DevOps Is Next

-We remain [hard at work on delivering more of idea to production](https://gitlab.com/gitlab-org/gitlab-ce/issues/32639) continuing to make the flow even better. [Our direction](https://about.gitlab.com/direction/) is to fully automate DevOps with the concept of [Auto DevOps](https://gitlab.com/gitlab-org/gitlab-ee/issues/2517). In a cloud-native world, developers have many projects, and it doesn't make sense to have to set up their tools for every one of them. With help from the wider community we'll ensure that everything works out of the box, from code quality metrics to Review Apps, and from metrics to autoscaling.
+We want to [deliver more of idea to production](https://gitlab.com/gitlab-org/gitlab-ce/issues/32639) and continue to make the flow even better. [Our direction](https://about.gitlab.com/direction/) is to fully automate DevOps with the concept of [Auto DevOps](https://gitlab.com/gitlab-org/gitlab-ee/issues/2517). In a cloud-native world, developers have many projects, and it doesn't make sense to have to set up their tools for every one of them. With help from the wider community we'll ensure that everything works out of the box, from code quality metrics to Review Apps, and from metrics to autoscaling.

 Watch our Head of Product Mark Pundsack demonstrate our Auto DevOps vision, including Auto Create, Auto Build, Auto CI, Auto Deploy, Auto Code Quality, Auto Review Apps: