workflows: Dynamically detect fedora versions for test matrix #157
Conversation
anoopcs9
force-pushed
the
workflows-detect-fedora-versions
branch
6 times, most recently
from
380927f to
46e7061
Compare
|
But we still need to update Mergify configuration 😐 . Can we get rid of that too? |
|
Instead of labeling the jobs with the version number call them |
|
Or are you suggesting to dump mergify entirely? I would not be opposed but I want an equivalent workflow (via actions?) and I don't know if we want to take that on now. |
Perfect, thanks.
Nah.. |
anoopcs9
force-pushed
the
workflows-detect-fedora-versions
branch
from
d668f6e to
4ccc409
Compare
|
I will merge this later today, but I will wait a couple of hours for any additional feedback, but this needs to be merged manually anyway because of the changes to the mergify config. |
|
@Mergifyio rebase |
Instead of updating the versions during each fedora release we could automatically filter out the recent versions from publically available json data for fedora releases. In addition to that we rename fedora test jobs to symbolically represent the supported releases of fedora. This is done in an attempt to reduce the need for updating mergify configuration during each fedora release. Signed-off-by: Anoop C S <[email protected]>
Use the newly introduced symbolic names, fedora-latest and fedora-previous, replacing the hard coded release version specific test jobs to avoid updating the configuration for each fedora release. Signed-off-by: Anoop C S <[email protected]>
✅ Branch has been successfully rebased |
anoopcs9
force-pushed
the
workflows-detect-fedora-versions
branch
from
4ccc409 to
89da51c
Compare
3 participants
Instead of updating the versions during each fedora release we could automatically filter out the recent versions from publically available json data for fedora releases. We also take this opportunity to rename the corresponding test jobs to avoid updating the mergify configuration for every fedora release.
fixes #145