2024-07-17 11:17 CEST, Florent 'Skia' Jacquet: > Le 17/07/2024 à 11:07, Simon Chopin a écrit : > > > > (disclaimer: the claims below could be wrong, I'm basing this on vague > > memories of my time before being a Core Dev) > > > > IIRC, things are not that simple: you're subject to the same ACLs as if > > you were running autopkgtests in the archive. In particular, you can > > have upload rights to the PPA but not in the archive, in which case > > your request would be rejected. > > > > I think there's also a problem if the package doesn't exist in the > > archive or doesn't have autopkgtests there? > > I think you're absolutely right there, sorry for the oversight. > > For the case where there are no tests results yet, we can force that with > `run-autopkgtest` on the infra, because if I'm correct, the test is only > done on the `request.cgi` end-point, when sending test from the web URL. But > that check is only done for packages in the archive, and doesn't apply for > PPA (at least according to what I understand of the code). > > As for the ACL, what people sometimes do is send us a bunch of URLs to click > on. I've personally done that in the past, so don't hesitate to ping me with > a list of link, and I can click on them. >
My use case does involves packages that are not in the archive yet. How can I proceed with that constraint? Or is using the infra for packages not in the archive not a supported usecase, and I should keep to run them locally? Thanks. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
