Continuous Integration with GitLab CI

Pete Johanson
In the not so distant past, a team's options for continuous integration tools was limited to complex, hard to maintain solutions such as Jenkins/Hudson, TeamCity, or to write your own tooling by hand. Since then, there have been a wealth of continuous integration tools to emerge on the market that simplify configuration and maintenance, while simultaneously offering powerful constructs for complex workflows that span build, testing, and deployment/release tasks. One such tool which strikes a fine balance of simplicity and power is GitLab CI/CD. This session will introduce attendees to the basics of adding GitLab CI/CD to a project, and then build upon those basics to explore features such as dependency caching, build artifacts, GitLab Pages, and additional docker integration. Going further, attendees will be introduced to various features designed to facilitate continuous delivery, including distinct environments, and git ref filtering. By then end of the session, attendees will have a solid grasp of GitLab CI/CD, and how to use it for automation of workflows and jobs for their projects.

[@istvanmalyar]

This video was crazy good and helpful, thank you very much!

[@calabrais]

Amazing! You explain everything so well.

[@attilaviniczai7215]

I can totally relate to that. Having to manage Jenkins separately from the codebase adds some serious overhead / instability. Especially when you would need verification for older release branches. With Jenkins this would mean keeping a set of verification jobs alive for all branches. It's amazing, and very comfortable how Gitlab's own CI solution manages this out-of-the-box.

[@gpprudhvi]

Awesome video! Everything needed at a single place

[@sprytnychomik]

Well done. On point from start to finish.

[@JG-nv1eb]

Excellent video! awsome!

[@ariasalmeida]

Thank you for this presentation

[@svenbreyvogel3445]

Really amazing, awesome!

[@frankdoerr1487]

Excellent stuff.

[@filipemateus9608]

Great content. Thanks

[@shabanakhatoon5977]

I simply love your explanations

[@mono0101mono]

Great video. It's save my time

[@DY-fn5iu]

how can I start a server in one runner and use that running server in other runners so I won't have to start a new server in every single runner?

[@Od253]

Nice video!

[@NeverCodeAlone]

Thx a lot.

[@twessels]

Very cool! What tool did you use to make the presentation? It seems to run in the browser

[@trishajohnson2684]

I'm thinking boomerang h2o water/atomic buttoned magnetic

[@raghupathym25]

Thanks for the video. How to deploy via cicd if machine is behind the windows bastion host. My aws instance is behind windows bastion. Is this task possible. Currently my cicd is deploying to dev environment(public IP), the requirement is to deploy to prod environment(privateIP)

[@jitendrachaudhary2819]

This video is pretty much understandable. Is there any way to get more knowledge about the CI/CD pipeline?

[@kaizoey]

Awesome bruh

[@varshatirumal7837]

how do we logon to Docker and where?

[@betterwithrum]

ok Gitlab-CI is pretty dope

[@mdfaizan4025]

gitlab.com/atinkapoor/gitlab-cicd/blob/master/.gitlab-ci.yml I have used this with small changes and it runs fine and get succeeded but when I check the server docker image is not available and no job is running

[@pawel_html5972]

good overview, but unfortunately NO real examples based on code + CI configuration.

[@HoitePrins]

This video is really amazing, great presentation. But ^please buy a microphone

[@mdfaizan4025]

How to deploy to an Amazon EC2 Instance using ssh or anything

[@idcmardelplata]

you can use the terraform image inside your gitlab-ci.yml and voila, it's much easier that way.

[@mdfaizan4025]

Thnx@@idcmardelplata

[@RH-zf3ki]

@@idcmardelplata any specific tutorial on this? Do you have any repo link example?

[@TheALEXiSounds]

Depends what you mean. Are you trying to deploy a new ec2 instance? Then probably you're looking for terraform + packer. Are you trying to update binaries / codebase inside the instance? Then ansible is the perfect solution for this. Write some ansible plays, and have your CD pipeline run them. Of course you can use ssh as well and run a set of commands.

[@remmasloff1303]

If you are speaking, why we need at the same time have a slide reading?

[@remmasloff1303]

And no live light spot on the commands text.... Dislike for unprofessional knowledge delivering.

[@SM-ok3sz]

libRary libRary… Not Lie Berry

[@blindpupil]

Shut up and take my money