In the Fedora RelEng Tools Backlog meeting, we were discussing various AutoCloud tickets, which are all kind of in a state of flux since the future of AutoCloud is unknown. I would like to get an answer from the WG what the ongoing commitment is there and if these work items are things that RelEng should care about.
Metadata Update from @maxamillion: - Issue tagged with: meeting
I updated @katec last night on IRC but here is an update.
The automated testing is blocked on the fedimg refactor, though I have already worked on the autocloud and autocloudrepoter for the AMI testing bits.
Apart from the automated testing, no new features will be added to Autocloud. Though I will keep managing the infrastructure for Autocloud. The plan was to move the 2WA to taskotron. Also, the automated testing part should eventually move down to taskotron.
Discussed in the Atomic Working group meeting today:
While autocloud has served us well in the past we don't have anyone working on new features for it and if it were to need serious maintainence we'd probably have trouble managing it. The Fedora CI pipeline (from the Fedora CI objective) should provide feature parity with Autocloud in the future and we should leverage that pipeline as soon as it does. This can eventually become our authoritative source of test results.
Taiga Epic updated accordingly.
closing this ticket.
Metadata Update from @dustymabe: - Issue untagged with: meeting - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.