Add GitLab on DC/OS blog post and tutorial. #831

ssk2 · 2016-09-16T02:03:40Z

No description provided.

grampelberg · 2016-09-16T15:14:00Z

src/blog/2016-09-16_gitlab-dcos.md

+lunr: true
+---
+
+We've been working with the team at GitLab for a few months now to bring GitLab as an easily installable package to DC/OS. This is a feature that many in the community have requested and we're happy to finally merge this package to the Universe and make it available for all!


This isn't part of DC/OS community, let's not use words like we. Maybe you can now use GitLab easily with DC/OS or something like that. Need to make sure the community is aware that this isn't a part of DC/OS but an application you run on top of it.

My affiliation is mentioned in the author tag, so "we" was intended to refer to Mesosphere. I will make this clearer.

grampelberg · 2016-09-16T15:15:15Z

src/blog/2016-09-16_gitlab-dcos.md

+
+Using GitLab on DC/OS now allows you to co-locate all of the tools you need for developers on one easy to manage cluster. Just as with any Universe package, you can robustly install several side by side instances of GitLab to provide segregated instances for each of your development teams. Alternatively, you can just as easily install GitLab in a highly available configuration that many teams use concurrently.
+
+In this post, we'll run through a quickstart installation of GitLab to show how straightforward it is to set up an end to end continuous delivery pipeline using GitLab to host both your code and Docker images, and Jenkins to run a job that builds a Docker image on DC/OS and deploys it to Marathon.


Please move all this into an actual tutorial. Discovery on blog posts and maintenance is a nightmare. Then you can link to the tutorial in docs and we'll bring it along and update every version.

grampelberg · 2016-09-16T15:15:31Z

src/blog/2016-09-16_gitlab-dcos.md

+
+# Prerequisites
+
+ DC/OS 1.8 or later


Please link to the installation docs here.

grampelberg · 2016-09-16T15:16:04Z

src/blog/2016-09-16_gitlab-dcos.md

+
+ DC/OS 1.8 or later
+
+ [Marathon-lb](https://dcos.io/docs/1.8/usage/service-discovery/marathon-lb/usage/) must be installed and running


Drop the domain.

grampelberg · 2016-09-16T15:16:07Z

src/blog/2016-09-16_gitlab-dcos.md

+
+ [Marathon-lb](https://dcos.io/docs/1.8/usage/service-discovery/marathon-lb/usage/) must be installed and running
+
+ [Jenkins](https://docs.mesosphere.com/1.8/usage/service-guides/jenkins/) must be installed and running


Drop the domain.

grampelberg · 2016-09-16T15:16:49Z

src/blog/2016-09-16_gitlab-dcos.md

+
+ An available hostname configured to point to the public agent(s) where Marathon-lb is running (e.g. `gitlab-test.mesosphere.com`)
+
+ Either set up appropriate certificates on each of your hosts, or configure each of your hosts to use your hostname (i.e. `gitlab-test.mesosphere.com`) as a [Docker insecure registry](https://docs.docker.com/registry/insecure/). You will need to do this for the Jenkins agent too using the [Advanced Configuration instructions](https://docs.mesosphere.com/1.8/usage/service-guides/jenkins/advanced-configuration/).


This is pretty confusing. Should it be a separate topic in administration?

grampelberg · 2016-09-16T15:17:27Z

src/blog/2016-09-16_gitlab-dcos.md

+
+<img src="/assets/images/blog/2016-09-16-gitlab/new-project.png" alt="New GitLab Project" /> *Create a New GitLab Project*
+
+1. Once this is done, clone the project to your local machine:


Syntax highlighting please.

grampelberg · 2016-09-16T15:18:05Z

src/blog/2016-09-16_gitlab-dcos.md

+
+1. Next, we'll create a simple Marathon application definition. Putting this into version control is good practice and makes it easy to implement and track changes to your application definition as the underlying application:
+
+    nano marathon.json


nano? really? also, syntax highlighting.

grampelberg · 2016-09-16T15:18:10Z

src/blog/2016-09-16_gitlab-dcos.md

+
+1. This will tell Marathon how to run our application. Paste the following into it, replacing the address to the Docker registry with your own:
+
+    {


Syntax highlighting please.

grampelberg · 2016-09-16T15:18:19Z

src/blog/2016-09-16_gitlab-dcos.md

+
+1. Finally, let's create a simple Jenkinsfile. This is a new way to programmatically define your builds that was released as part of [the Pipeline feature](https://jenkins.io/doc/pipeline/) of Jenkins 2.0. This will pull from the GitLab instance you've just set up, build the Docker image, push it to the GitLab registry, and then trigger a deployment using [the Marathon plugin](https://github.com/jenkinsci/marathon-plugin) for Jenkins:
+
+    nano Jenkinsfile


Syntax highlighting please.

grampelberg · 2016-09-16T15:18:36Z

src/blog/2016-09-16_gitlab-dcos.md

+
+1. Now that we've got our four files, add, commit and push them to the repository:
+
+    git add *


Syntax highlighting please.

grampelberg · 2016-09-16T15:19:09Z

src/blog/2016-09-16_gitlab-dcos.md

+Other resources:
+* [About GitLab](https://about.gitlab.com/about/)
+
+* [Deploy GitLab on DC/OS today](https://mesosphere.com/blog/2016/09/16/gitlab-dcos/) on the Mesosphere blog


What is this link for? Feels like we're crossing the streams.

PageRank mainly. Fine.

ashenden · 2016-10-04T22:13:04Z

Is this still up for review or are we good to go?

judithpatudith · 2016-10-24T20:59:18Z

Hey Guys, is anything happening with this post? If it goes up I'm happy to promote it on twitter etc.

ssk2 · 2016-10-24T21:06:55Z

Blocked on me @judithpatudith.

ssk2 · 2016-12-13T22:15:19Z

Superceded by dcos/examples#27

ssk2 added 2 commits September 15, 2016 19:05

Add GitLab on DC/OS blog post and tutorial.

48ef197

Typo fixes.

07e26da

grampelberg reviewed Sep 16, 2016

View reviewed changes

twk3 mentioned this pull request Nov 29, 2016

Update GitLab to version 8.14.1 mesosphere/universe#847

Merged

ssk2 closed this Dec 13, 2016

ashenden deleted the gitlab-blog-post branch December 22, 2016 18:19

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add GitLab on DC/OS blog post and tutorial. #831

Add GitLab on DC/OS blog post and tutorial. #831

ssk2 commented Sep 16, 2016

grampelberg Sep 16, 2016

ssk2 Sep 16, 2016

grampelberg Sep 16, 2016

ssk2 Sep 16, 2016

grampelberg Sep 16, 2016

ssk2 Sep 16, 2016

grampelberg Sep 16, 2016

grampelberg Sep 16, 2016

grampelberg Sep 16, 2016

grampelberg Sep 16, 2016

grampelberg Sep 16, 2016

grampelberg Sep 16, 2016

grampelberg Sep 16, 2016

grampelberg Sep 16, 2016

grampelberg Sep 16, 2016

ssk2 Sep 16, 2016

ashenden commented Oct 4, 2016

judithpatudith commented Oct 24, 2016

ssk2 commented Oct 24, 2016

ssk2 commented Dec 13, 2016


		Using GitLab on DC/OS now allows you to co-locate all of the tools you need for developers on one easy to manage cluster. Just as with any Universe package, you can robustly install several side by side instances of GitLab to provide segregated instances for each of your development teams. Alternatively, you can just as easily install GitLab in a highly available configuration that many teams use concurrently.

		In this post, we'll run through a quickstart installation of GitLab to show how straightforward it is to set up an end to end continuous delivery pipeline using GitLab to host both your code and Docker images, and Jenkins to run a job that builds a Docker image on DC/OS and deploys it to Marathon.


		+ DC/OS 1.8 or later

		+ [Marathon-lb](https://dcos.io/docs/1.8/usage/service-discovery/marathon-lb/usage/) must be installed and running


		+ [Marathon-lb](https://dcos.io/docs/1.8/usage/service-discovery/marathon-lb/usage/) must be installed and running

		+ [Jenkins](https://docs.mesosphere.com/1.8/usage/service-guides/jenkins/) must be installed and running


		+ An available hostname configured to point to the public agent(s) where Marathon-lb is running (e.g. `gitlab-test.mesosphere.com`)

		+ Either set up appropriate certificates on each of your hosts, or configure each of your hosts to use your hostname (i.e. `gitlab-test.mesosphere.com`) as a [Docker insecure registry](https://docs.docker.com/registry/insecure/). You will need to do this for the Jenkins agent too using the [Advanced Configuration instructions](https://docs.mesosphere.com/1.8/usage/service-guides/jenkins/advanced-configuration/).


		<img src="/assets/images/blog/2016-09-16-gitlab/new-project.png" alt="New GitLab Project" /> Create a New GitLab Project

		1. Once this is done, clone the project to your local machine:


		1. Next, we'll create a simple Marathon application definition. Putting this into version control is good practice and makes it easy to implement and track changes to your application definition as the underlying application:

		nano marathon.json


		1. This will tell Marathon how to run our application. Paste the following into it, replacing the address to the Docker registry with your own:

		{


		1. Finally, let's create a simple Jenkinsfile. This is a new way to programmatically define your builds that was released as part of [the Pipeline feature](https://jenkins.io/doc/pipeline/) of Jenkins 2.0. This will pull from the GitLab instance you've just set up, build the Docker image, push it to the GitLab registry, and then trigger a deployment using [the Marathon plugin](https://github.com/jenkinsci/marathon-plugin) for Jenkins:

		nano Jenkinsfile


		1. Now that we've got our four files, add, commit and push them to the repository:

		git add *

Add GitLab on DC/OS blog post and tutorial. #831

Add GitLab on DC/OS blog post and tutorial. #831

Conversation

ssk2 commented Sep 16, 2016

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

ashenden commented Oct 4, 2016

judithpatudith commented Oct 24, 2016

ssk2 commented Oct 24, 2016

ssk2 commented Dec 13, 2016