Tooling: GitLab SaaS
Environment: GitLab Pages
Estimated Time: 10 mins
A developer’s first instincts are to jump right in and start coding a change and seeing that change happen. In our case let’s start the process right and follow good change controls and branching processes. This will lead to an overall better quality product and will start adding to our DevOps metrics we will look at later in the process.
Create your first issue (or a few) and assign it to a milestone. You can use anything you like here, but if you need an example you can start with “Edit Hugo template base to current project details”
https://docs.gitlab.com/ee/user/project/issues/managing_issues.html
You should have something that looks like this.
Open your issue, and create a branch that ties back to your issue.
From here we jump to making our first change. This can be done through many editors like Visual Studio Code which we will look at later, but let’s jump right in and do it through GitLab’s online editor.
From here you can update the basic information to start to customize it for your personal site. Important: Change the base URL in the following.
Create a commit to the branch and review your code changes
Create your merge request.
Select Merge when the pipeline succeeds.
Close the merge request and open the CI/CD pipeline. Once it shows passed, you will be able to see your changes.
Wondering where your site it? Check out the Setting – Pages section and it will have your url listed.
https://jmgress.gitlab.io/tampadevops/
Connect with me on LinkedIn and let me know what you would like to see next… http://linkedin.com/in/jamesgress
Be First to Comment