Commit 4c0720c4 authored by French, Robert's avatar French, Robert
Browse files

Use h2's so that it renders well on Gitlab also

parent 51ff7f5c
......@@ -11,8 +11,6 @@
---
# Continuous Integration with Gitlab Runners
## Some Definitions
* **Pipeline** - a set of batch jobs which must succeed for your push to get a green checkmark.
......@@ -20,8 +18,6 @@
---
# Continuous Integration with Gitlab Runners
## How to get a Green Light
1. If a build fails, then the whole pipeline fails.
1. If a pipeline fails, then your push gets a red X.
......@@ -31,8 +27,6 @@ Let's look at the [pipeline definition]() from the [Inspirational Quote Generato
---
# Continuous Integration with Gitlab Runners
## Configuring runners in your project
* I will walk through configuring a new runner on my Fedora Linux desktop unless I get bitten by the Live Demo gremlins.
......@@ -40,8 +34,6 @@ Let's look at the [pipeline definition]() from the [Inspirational Quote Generato
---
# Continuous Integration with Gitlab Runners
## Testing on multiple platforms
* If the above runner was configured successfully, *and* we add a new build definition to our pipeline, we will be able to test our application simultaneously on both Mac OS X and Redhat Linux.
......@@ -49,25 +41,18 @@ Let's look at the [pipeline definition]() from the [Inspirational Quote Generato
---
# Continuous Integration with Gitlab Runners
## Pro Tip: Force Merge Requests to pass Tests
At this point I will show how to configure your GitLab repo so that Merge Requests must pass before they can be merged -- this can help you enforce quality control in your project, and is arguably the most useful aspect of Continuous Integration.
---
# Continuous Integration with Gitlab Runners
### Double Pro Tip Bonus: Protect Master from Pushes
## Double Pro Tip Bonus: Protect Master from Pushes
You can further protect your repo from un-tested code by removing everyone's ability to push directly to master. This means that all changes must be submitted as Merge Requests. This may be a bit more obnoxious, especially for single person projects, but it ensures that nothing can get into master without passing CI first. See GitLab's [Docs on Protected Branches](https://docs.gitlab.com/ee/user/project/protected_branches.html)
---
# Continuous Integration with Gitlab Runners
## But wait there's more!
* Automatically build executables for different platforms
......@@ -80,7 +65,6 @@ You can further protect your repo from un-tested code by removing everyone's abi
## Questions?
---
# Git It Together!
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment