GitLab is awesome. If you want a truly private GitHub-like service, there is no better.
Of course, you have to do a little more house keeping than you would if you went with it's hosted equivalents. But for me, a geeky-geek who likes doing a little sys-admin and stuff every once in a while, that's a very small price to pay for all the features and functionality it provides.
However, time is precious. And a few dollars per month out of your wallet for a paid service may well better suit your needs.
Why should you invest your valuable time in learning yet another new system?
Why should you add yet another piece of tech to your list of maintenance chores?
Would it be worth it to you?
All valid questions which will be answered in this series.
We're going to look at how to install not only GitLab, but the server that it runs on.
We'll look at adding a new repository to your shiny new GitLab install, and
git push'ing' our first commit.
We can cram all that into the first video. It's not complicated. Really.
5 minutes? Bam, done.
From there we're going to look at how you can get GitLab to run your test suite whenever code hits your GitLab server. To do that, we're going to let GitLab CI test, build, and deploy our code. A Symfony 2 project, of course.
Honestly, I think GitLab is amazing. I cannot speak highly enough of the level of quality that they are giving away for free in their Community Edition.
It's not going to be for everyone.
But maybe it's for you.
|1||Zero To GitLab in 5 Minutes||05:02|
|2||Continuously Integrate All The Things||05:10|
|3||GitLab CI Runner Tutorial||03:04|
|4||GitLab Reset Password||01:42|
|5||Updating GitLab and GitLab CI||04:52|
|7||GitLab CI Backup||04:20|
|8||PHP Continuous Integration with GitLab CI||08:08|
|9||How To Use VirtualBox as a GitLab CI Test Runner||06:02|
|10||Running Selenium with Docker During VirtualBox Test Runs||09:02|
If you have found this course helpful, please share it.