A lone misconfigured CI build that doesn't thoroughly test before pushing (or perhaps missing a test) shouldn't be grounds for banning any and all CI/CD here.
Automation is dumb, you cant expect automation to test every single possibility, it does not have a brain and it can't use common sense. If a package installs, but for example, you forgot to copy the data over to the package, sure it will build, CI/CD will pass and this will be pushed to remote, but its still a dysfunctional package. You an not expect CI/CD to do all the work for you, devops is to aid you, not to replace your role.
I don't believe anyone is suggesting that CI/CD is completely disabled here, but the key topic of 'thoroughly testing, automatically' is probably the avenue to follow.
Don't get me wrong, CI/CD is amazing, I would be disappointed if it was banned. But, it needs to be used within moderation, there are a large amount of maintainers which will just CI/CD it and forget about the entire package, not test it, and when all goes wrong, they abandon the package because they are too busy to maintain it. I do not care what anyone says, this is not the right attitude to have to maintaining packages. If you don't care enough about your packages to ensure they work, then why you even a package maintainer?
I'd suggest that the package build in the original message simply gets another once-over to improve the robustness.
Ok, if this is such an amazing idea, why do you think TUs still bump the official packages manually? Test them? TU's devout a large amount of time to maintaining their packages, those of you who want to let a automation script do it all for you kinda kicks the TUs in the balls, you are trying to highlight that TUs are doing it all wrong, or thats how I feel from this, I personally think it is disregarding the time given by TUs. I get it we are all busy, but saying you MUST use CI/CD because you are too busy otherwise, makes TUs role seem p*ss easy. The AUR is like a training ground for future TUs, if you can't handle maintaining packages conforming to the packaging guidelines now, if you ever want to become TU, how would you cope? Bumping packages, and submitting a PR is what I suggest, it takes a lot of the manual work out of it, you then review the package, rebuild it mnaually, check the structure is correct, check it runs, check there is no dependencies missing, check the release notes for incompatibilities. WHERE is this all within a CI/CD task? Last time I checked the CI/CD tasks aren't human! Seriously guys, there is a reason that CI/CD isn't mass promoted by TU's, use it sparingly to do repetitive work, but it does not replace your job! -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev