{"id":242,"date":"2018-12-03T10:38:00","date_gmt":"2018-12-03T10:38:00","guid":{"rendered":""},"modified":"2019-07-03T13:08:00","modified_gmt":"2019-07-03T13:08:00","slug":"gitlab-ci-with-nexus","status":"publish","type":"post","link":"https:\/\/opstree.com\/blog\/2018\/12\/03\/gitlab-ci-with-nexus\/","title":{"rendered":"Gitlab-CI with Nexus"},"content":{"rendered":"
\n
\n
<\/a><\/div>\n
<\/div>\n
<\/div>\n

Recently I was asked to set up a CI- Pipeline for a Spring based application.
\nI said “piece of cake”, as I have already worked on jenkins pipeline, and knew about maven so that won’t be a problem. But there was a hitch, “pipeline of Gitlab CI<\/i>“. I said “no problem, I’ll learn about it<\/i>” with a Ninja Spirit.
\nSo for starters what is gitlab-ci pipeline. For those who have already work on Jenkins and maven, they know about the CI workflow of  Building a code , testing the code, packaging, and deploy it using maven. You can add other goals too, depending upon the requirement.
\nThe CI process in GitLab CI is defined within a file in the code repository itself using a YAML configuration syntax.
\nThe work is then dispatched to machines called runners, which are easy to set up and can be provisioned on many different operating systems. When configuring runners, you can choose between different executors like Docker, shell, VirtualBox, or Kubernetes to determine how the tasks are carried out.<\/p>\n

<\/div>\n
<\/div>\n

What we are going to do?<\/b>
\nWe will be establishing a CI\/CD pipeline using gitlab-ci and deploying artifacts to NEXUS Repository.<\/p>\n

<\/div>\n
<\/div>\n
<\/div>\n
<\/div>\n
<\/div>\n
<\/div>\n
<\/a><\/div>\n

Resources Used:<\/p>\n

    \n
  1. Gitlab server, I’m using gitlab<\/a> to host my code.  <\/b> <\/li>\n
  2. Runner server, It could be vagrant or an ec2 instance. <\/b><\/li>\n
  3. Nexus Server, It could be vagrant or an ec2 instance.\n
    <\/div>\n

     Before going further, let’s get aware of few terminologies. <\/li>\n<\/ol>\n