The Package¶

Once the pipeline has finished we can actually see the results in the package repository and even download it!

Using the menu on the left in the GitLab UI select Packages & Registeries then Package Registry. If you've been following along precisely, you'll see a registry called httpcats - click this. You'll get a UI like this:

Along the top we can see the name of our registry - httpcats - followed by some information the registry itself:

• Generic - this refers to the type of the registry. We're just using a generic package registry which can hold anything
• 28.66 MiB - this is the total size of the repository
• httpcats is the name repository it belongs to
• master - the branch from which the latest package was built

Under this we have the Detail tab which gives us a history of what happened on this regustry followed, finally, by the packages themselves.

If we click on a package name - httpcats.zip - we can download this artefact and see/check what our pipeline is producing. If you click the downwards facing arrow to the left you'll drop down some information about the SHA-256 hash. This is used to check the integrity of the package after you download it (you can test this by generating a SHA-256 hash locally and checking they match.)

We also have other information like the package's size and when it was created.

Selecting the three dots to the far right of each packagfe we're presented with a simple menu that allows us to delete the package.

Next¶

We should now look at triggering our application pipeline when the code is changed. We know this is going to work, but let's run through the process anyway and trigger a new package.

In the future, as the book evolves, we're going to grow the application's complexity so this pipeline and its processes will get more complex too.