We've seen what starting a manual pipeline looks like when covering the same topic for our Terraform CI pipeline. We'll cover the process again here in brief.
Just like our Terraform pipeline it won't trigger unless we're making changes to specific files. In the case of our application that means
*.go files. We're not making changes to such files in this case, so the pipeline won't run. That's why we're having to manually run the pipeline again.
Once we've written and committed our
.gitlab-ci.yml file we can trigger the pipeline in the GitLab CI UI.
- Navigate to the
http-cats/application/httpcatsrepository in the GitLab console
- Use the menu on the left to go to
Run pipelinein the top right of the screen
We can run straight from the
main as it's now called by default) branch and we don't need any additional variables.
What we'll see is our two stages that will
build an artefact (ZIP files containing the binary and the static files) and then
publish the artefact into the GitLab package repository.
At this point in time we know everything there is to explore the pipeline and see the results.
Let's now take a look in the package registry and review the results of the pipeline.