With this blog post we’d like to continue with the idea of openly communicating changes in Packit. Since most of the developers use Packit as the GitHub App (which uses code from this repository - Packit Service), this blog will be about changes in all the parts, i.e. the GitHub App, the Packit Service and Packit itself.
At the moment the workflow is that one of us manually triggers production container image build at the end of a week. This image is then automatically deployed into our production instance of the service over a weekend (Sun/Mon night) so that everyone can start a week with all the amazing stuff we added the previous week. In case an issue makes it through our staging instance into production uncaught, we can easily rollback on Monday. The same person also writes down what’s changed in Packit (service/app) since previous deployment.
Previous post is almost half a year old so we won’t list all the changes since then, but only since last deployment, i.e. since end of December.
Previous deployment was running packit-0.7.1.
We haven’t released a newer version since then, but in the service we install Packit from the Git repository (we have a separate
stable git branch for our production deployment).
From the most visible changes, Packit now:
Changes not visible to end users: