packit: Build COPR for main commits #1365
Conversation
|
@lachmanfrantisek, @lbarcziova : I'm a bit confused here. This already triggered rpm-build:main-build-copr* tasks, but this PR didn't land yet. Shouldn't this only trigger after a PR lands? I did set |
|
@martinpitt I think the problem here is that the source branch of this PR is named |
|
@lbarcziova Erk, right; If that's a regexp, I just make it tighter. TIL! |
martinpitt
force-pushed
the
main-build-copr
branch
from
7ca8bb0 to
c798ca8
Compare
|
@lbarcziova Yes, that was it -- with this change I don't get the copr jobs any more. That said, this error was actually useful, as the build failed. I'll revert back to the "broken" version again to fix the build first. |
martinpitt
force-pushed
the
main-build-copr
branch
from
c798ca8 to
669b9fd
Compare
|
COPR build succeeded, so switching back to the tight and correct Update: I deleted that COPR build, as I don't want to clutter it with test builds which were not actually from main. |
Build every commit into main into https://copr.fedorainfracloud.org/coprs/g/cockpit/main-builds/ We will use that for cross-project testing (e.g. running cockpit-podman's tests in podman upstream PRs). Users can also install that to test bug fixes and new features after they landed, but before they got released.
martinpitt
force-pushed
the
main-build-copr
branch
from
669b9fd to
bc478e9
Compare
|
Cool, I got a build! 👍 |
Build every commit into main into
https://copr.fedorainfracloud.org/coprs/g/cockpit/main-builds/
We will use that for cross-project testing (e.g. running cockpit-podman's tests in podman upstream PRs). Users can also install that to test bug fixes and new features after they landed, but before they got released.
See cockpit-project/cockpit#19117 (comment) for the plan.