taskotron

Clone
Source Code
GIT

#279 Taskotron EOL date
Closed: Fixed 4 years ago by kparal. Opened 5 years ago by kparal.

Closed: Fixed
Reopen Issue

It looks like Fedora Infra move plans have been finalized:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/NWIUHXC26DJK3R3NBWDJWZNUTHSO52U6/

We need to figure when when exactly we are going to sunset Taskotron, so that we can announce it in advance.

@tflink You probably know best whom to talk to. Could you please figure out the best date for Taskotron EOL? If you're busy, that's fine, I'll talk to infra, just let me know. Thanks!

Hey @tflink, I just want to make sure you've seen this ticket. Have you? Will you take it or should I? Thanks.

Sorry, keep forgetting to respond here. I'll bring it up at the infra meeting this week and start making announcements.

It came up yesterday in the FESCO meeting that there has been a lack of communication and there are plenty of Fedora folks who aren't aware of what's planned.

@tflink Hey, are there any updates to this? Have you picked the EOL date with the help of infra? Thanks.

@tflink ping again

The conclusion of the infra meeting was that we could pick a date.

The only thing kinda holding us back is rpmdeplint. I was hoping to just take the taskotron task and run it in Jenkins but I'm running into problems there due to the way that things are scheduled - I've not been able to figure out a way to schedule it the same way.

I'm hesitant to put much time into this as there's a replacement coming soon from inside redhat so it's a toss up between the amount of time saved by turning stuff off vs. the amount of time spent re-inventing the wheel that is already being re-invented. I don't have a specific date for the replacement other than "before flock" which is too late. I'll poke at a few things today and maybe I can get some rpmdeplint thing running in Jenkins with less work than I think.

Let's not hold the announcement because of rpmdeplint. We can easily say we're looking into options and we'll post another blog once we figure it out. People should assume it's probably going away at least temporarily.

So let's pick Taskotron EOL date and announce it. It would be easier if I knew the date when our servers are supposed to go down. But because I don't... I propose 30.4. Does it sound OK?

@tflink Unless you or somebody else yells in this ticket and stops me, I'll simply post the EOL announcement on Monday. I'll not spend a month deciding on a date.

That date makes sense to me. I'll get the announcement out today but if I don't, feel free to do it on Monday

Did we ever make a decision on whether to do emails to devel-announce@, a blog post on the community blog or both?

This is my draft announcement. I'm going to start looking into whether a community blog post is possible:

This is something that has been coming for quite a while now
and while it was discussed among QA and Infra but there hasn't been
enough communication with the rest of Fedora. For that, I apologize.

Taskotron has been in maintenance-only mode for a couple of years now
pending a replacement of some kind. That replacement has taken longer
to materialize than originally planned but the servers which run
Taskotron are almost out of warranty and will not be moving to the new
datacenter with the rest of Fedora's infrastructure.

Given all of this, we have decided that 2020-04-30 will be the day that
Taskotron will be turned off so that we're not trying to turn stuff off
in the middle of the infra move later this summer.


--------------------------------
Is anything replacing Taskotron?
--------------------------------

In the short term, there is a Jenkins instance which is running
rpminspect and rpmdeplint. Rpminspect includes tests which are
effectively the same as rpmlint and rpmgrill, effectively retiring
those tests.

We already have rpminspect results going into production resultsdb
and showing up in Bodhi. I'm still working on the last parts of the
rpmdeplint test in that Jenkins instance and expect to have that
finished in the next week or so.

In the longer term, there is a new solution coming from the Fedora CI
folk which they will be deploying before Flock. I expect they will have
more details in the near future.

---------------------
What about ResultsDB?
---------------------

ResultsDB is part of Taskotron but it is used by other bits like Bodhi
and Greenwave. The discussion around where ResultsDB will live going
forward and who will be responsible for the deployment is still ongoing
but ResultsDB will not be turned off as part of this EOL process.

Suggestions for changes or bits that I missed would be welcome

Did we ever make a decision on whether to do emails to devel-announce@, a blog post on the community blog or both?

I'd do devel-announce, test-announce and fedora planet (both regular and QA subplanet). I'm not sure about community blog, I had the notion that it was more directed towards our users than contributors. And it will need to go through some process probably taking days. But I certainly don't object, I just don't think it's absolutely necessary to post it there.

Suggestions for changes or bits that I missed would be welcome

I'd probably add another section (as the first one), something like "What does it mean for me?". And there I'd explain that this mainly affects package maintainers who want to see test results on their new package builds/proposed updates. The results are (still) visible in Bodhi under "Automated tests" tab, and include the following tests: rpmlint, rpmgrill, python-versions, abicheck and rpmdeplint. Only those are Taskotron checks, no other results will be affected by Taskotron EOL (i.e. OpenQA and Fedora CI results stay). Those mentioned tests will no longer be run and so the results will no longer be visible there. We try to move some of those tests to new systems, no guarantees, see the next section.

I'm not sure if you want to promise rpmdeplint to be up and running in a week (the text sounds like that), I wouldn't include a timeline at all. But that's your call, I don't know how far you are in this. Rpmdeplint is half broken and it can break more any time, so it's not a win-win situation even if we manage to run it elsewhere.

Did we ever make a decision on whether to do emails to devel-announce@, a blog post on the community blog or both?

I'd do devel-announce, test-announce and fedora planet (both regular and QA subplanet). I'm not sure about community blog, I had the notion that it was more directed towards our users than contributors. And it will need to go through some process probably taking days. But I certainly don't object, I just don't think it's absolutely necessary to post it there.

I just figured it might make sense as I remembered the CPE announcement showing up there but I'm not really attached to the idea

Suggestions for changes or bits that I missed would be welcome

I'd probably add another section (as the first one), something like "What does it mean for me?". And there I'd explain that this mainly affects package maintainers who want to see test results on their new package builds/proposed updates. The results are (still) visible in Bodhi under "Automated tests" tab, and include the following tests: rpmlint, rpmgrill, python-versions, abicheck and rpmdeplint. Only those are Taskotron checks, no other results will be affected by Taskotron EOL (i.e. OpenQA and Fedora CI results stay). Those mentioned tests will no longer be run and so the results will no longer be visible there. We try to move some of those tests to new systems, no guarantees, see the next section.

That makes sense, I'll add it

I'm not sure if you want to promise rpmdeplint to be up and running in a week (the text sounds like that), I wouldn't include a timeline at all. But that's your call, I don't know how far you are in this. Rpmdeplint is half broken and it can break more any time, so it's not a win-win situation even if we manage to run it elsewhere.

Oof, I thought that rpmdeplint was in a better place than it used to be. Thanks for the heads up and I'll be removing my pseudo-promise from the announcement

Email has been sent to devel-announce@ and test-announce@

Thanks a lot. Can you please also publish to the planets? Just to cover most of the important channels. We can then close this ticket.
Edited 4 years ago by kparal

I have prepared a short blogpost that I'll publish tomorrow, saying that Taskotron is now EOL.
Edited 4 years ago by kparal

Metadata Update from @kparal:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
4 years ago

Log in to comment on this ticket.

Metadata

infra

None
None
Critical
Powered by Pagure 5.14.1
Documentation • File an Issue • About • SSH Hostkey/Fingerprint
© Red Hat, Inc. and others.