Stories from the amazing world of release-monitoring.org #9

I woke up to the cold morning in my tower. The sun shone brightly on the sky, but the stone of the tower was cold as it takes some time to make it warm. Everything was already prepared for today’s journey. I sat at my table and started going through some reports from workers. I still had some time til the traveler arrived. So I started reading the reports …

Anitya

Anitya has a new home

Because of the small interest outside of the Fedora universe and being the only project outside fedora-infra consortium (GitHub organization), that is handled by Conclave of Mages (CPE Team), this same Conclave decided to move it from release-monitoring consortium to fedora-infra consortium. This move is done and Anitya is now here.

Anitya 0.18.0 released

Anitya 0.18.0 was released on 13th January and for week it was tested in the purgatory (staging). This version is now live and available for entities (users), who can enjoy new features and fixes:

  • We will no longer tolerate intruders without proper documentation (Automatically delete projects, that are incorrectly setup and reach error threshold)
  • We don’t need whole projects history from GitHub realm anymore (Use and store cursor to latest commit for GitHub projects)
  • Nothing is stuck at our door anymore when retrieving messages from other realms (Check service has timeout option now to prevent infinite loop)
  • Abstract Positive Intuition (API) now supports various kind of thoughts (Filters in APIv2 are now case insensitive)
  • When entities try to enter Anitya, they are no longer redirected back to the door (Current page is no longer forgotten on login)

This is only a small list of changes, to see full list look at the Book of Releases.

The-new-hotness

Dist-git realm integration

We are working on better integration between dist-git realm and release-monitoring.org. Recently we replaced Great Oraculum (scm-requests pagure repository) with direct communication with the-new-hotness. This is much more convenient for entities and it allows us to get rid of the Great Oraculum, when we no longer needs their service.

The next thing that is currently work in progress is possibility to interact with dist-git realm directly. This will be done with the help of Packit. With it we will be able to propose changes directly to dist-git and skipping Bugzilla realm. Bugzilla will be still used as a realm that will notify ever vigilant guards (package maintainers) about anything new.

Internal struggle with Anitya

Some time ago I was contacted by another mage from our conclave that something is wrong with the realm of release-monitoring.org. Messengers were stuck in front of the-new-hotness and nobody opened the door to them. Only one was taken inside, but immediately thrown outside and because he wanted to keep his place in line, he went back to stand in front of the doors.

I started asking around what is happening (checking the logs of the-new-hotness) and it seemed to me that the messenger, who was always in front of the queue, had something wrong with the message. I followed the clues in the reports and after while I found out that this message requires the-new-hotness to contact Anitya and trigger a new check for any news, which failed and the-new-hotness thrown out the messenger and spend some time recovering from the issue (openshift pod was restarted). But because the messenger was always first and others were not allowed in, the queue was getting bigger and bigger.

I teleported myself to Anitya island and looked at the specific project, which was checked for news. And I found out that the project is using a new feature introduced in 0.17.0. This feature allows entities (users) to specify what they want to check in GitHub universe. If they want to check any news (tags) or just certified news (releases). But not every project in GitHub universe makes certified news nice (no version in name of the release) and because Anitya wasn’t able to understand this nonsense it just thrown error back to the-new-hotness.

I fixed this quickly by changing configuration of the project. After the change the messenger went through without any issue and the queue was processed one by one. This was a temporal fix, because this could happen in any other project that is trying to check certified news. The solid fix is part of Anitya 0.18.0, so this shouldn’t happen anymore.

Post scriptum

This is all for now from the world of release-monitoring.org. Do you like this world and want to join our conclave of mages? Seek me (mkonecny) in the magical yellow pages (IRC freenode #fedora-apps) and ask how can you help. Or visit the Bugcronomicon (GitHub issues on Anitya or the-new-hotness) directly and pick something to work on.

Categories: Infrastructure

1 Comment

  1. Thanks for allthe great work!

Comments are closed.

Copyright © 2020 Fedora Community Blog

Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 International License.

Theme by Anders NorenUp ↑