# Making our CI/CD Pipeline
### Config File
To create our pipeline, we must first create a `.gitlab-ci.yml` file and specify it to our project requirements (Place this in your project root)
[Templates](https://docs.gitlab.com/ee/ci/examples/)
[Syntax Reference](https://docs.gitlab.com/ee/ci/yaml/)
{% code title=".gitlab-ci.yml" %}
```yaml
image: golang:1.22
stages:
- test
- build
build:
stage: build
script:
- "go build -o calculator"
- "./calculator"
test:
stage: test
script:
- "go test"
```
{% endcode %}
Paste the code then push it to your repository
```bash
> git add .\.gitlab-ci.yml
> git commit -m "Created GO Pipeline"
> git push
```
We can now view our pipeline from the repository, under **Build -> Pipeline -> Pipeline Number**
### **Viewing our deployed pipeline**
Successful Build
{% hint style="warning" %}
**Issues Faced**
Spent the better part of an hour debugging and figured out that you need to create a runner as root cause of docker permissions. Alternatively, you can add yourself to the docker group - although it's easier just to use sudo
{% endhint %}
### Testing for Failures
Just like in [simple-calculator-project](https://blog.securescape.cc/offensive-security/red-team/offensive-development/offensive-devops/gitlab/simple-calculator-project "mention"), we can test for failures by changing the values slightly
First, we'll create a separate branch to mimic a real project, then change the test values from there
Creating a new branch with VS Code
Editing calculator_test.go
Push your changes then wait for the pipeline to finish running
Failure Test
We can now fix it back and create a merge request to main. Merge requests will trigger a pipeline job to check for errors before letting you merge (depending on your project settings)
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://blog.securescape.cc/offensive-security/red-team/offensive-development/offensive-devops/gitlab/making-our-ci-cd-pipeline.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
