Laura Barcziová

> Also installability tmt plan should be [this one](https://github.com/fedora-ci/installability-pipeline/blob/master/installability.fmf) actually. Regarding the link to install-and-verify.sh link That one is also linked in the description (the repo). When implementing this, consider...

Besides the issues mentioned in the previous comments, we would also need to think of a mechanism of allowlisting that the particular upstream repo can create the new Copr projects...

hi @lsm5 , we have just discussed with @nforro that this should be in the end possible with just setting the `preserve_project: true` in the configuration, sorry for the confusion....

Hi! Thanks for creating this. The option of migrating most of the content, e.g., to our docs and just linking in comments sounds the most suitable to us. (The already...

As for the trigger naming, some proposals are also in #1806.

Might be the same issue as #2014

We have concluded that for now, we do not want to support this (there is e.g. `fedpkg srpm` for this). So within this issue, we can: - [ ] implement...

> Not always a failed job is marked as a failed celery task. I think this is correct behaviour, because the task successfully finishes. > To automatically detect this kind...

Hi, and thanks for the issue! As for the reported time, what would be the expected value for you? The time for running the RPM build itself? Time from submission...

thanks @lsm5 @edsantiago for clarification! > I just think it's important to report semi-constant times, not times spent waiting for a slot (which could be seconds, minutes, hours). agreed, going...