Details
-
Task
-
Status: Open (View Workflow)
-
Critical
-
Resolution: Unresolved
-
None
-
None
Description
We must have at least some install tests in branch protection.
At least one deb and one rpm.
Currently MariaDB installation from packages is completely broken for 3 days and nobody sees that
Attachments
Issue Links
- is part of
-
MDEV-33073 always green buildbot
-
- Stalled
-
Activity
Field | Original Value | New Value |
---|---|---|
Link | This issue is part of MDEV-33073 [ MDEV-33073 ] |
Component/s | Buildbot [ 18503 ] |
Summary | install tests in branch protection | Install tests in branch protection |
Workflow | MariaDB v4 [ 184490 ] | MariaDB Foundation v1 [ 188207 ] |
Labels | foundation |
serg adding an install test to protected branches will most likely add an overhead of at least 20 mins. The reson for this is the following: for each push, we trigger source file creation. This build triggers build + MTR, that in turn trigger packages creation that finally triggers install. Is this acceptable? Theoretically, we can trigger a package creation build directly, but install will still be triggered after.