Align the develop and stable testing jobs #529

ekohl · 2025-01-08T19:20:43Z

This is a bit of an experiment to see if we can use the same jobs for testing develop and stable branches. It's inspired by #525.

Some differences we should discuss:

It still runs RuboCop on develop, but should we? it's not something we care about
It only builds the package for develop, but perhaps we can just build it for all
Build rotation: can we align on a week of builds and X builds? Not sure
Shall we drop the matrix building and align on a single Ruby version per release? Do we pick the oldest version?

In 70d9a45 the git_checkout function was removed but this remained. Fixes: 70d9a45 ("drop smart-proxy-pr-test and all non-packaging PR testing remains")

This inverses the relationship, but it makes it easier because we already have the source name because that's where we copy the artifacts from.

This attempts to align the stable testing job to the source release job as much as possible.

ekohl added 3 commits January 8, 2025 20:00

Fix instance of git_checkout

c6f9041

In 70d9a45 the git_checkout function was removed but this remained. Fixes: 70d9a45 ("drop smart-proxy-pr-test and all non-packaging PR testing remains")

Set trigger package release jobs instead of on source jobs

109e75b

This inverses the relationship, but it makes it easier because we already have the source name because that's where we copy the artifacts from.

Align the smart-proxy testing and source release jobs

b5030db

This attempts to align the stable testing job to the source release job as much as possible.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Align the develop and stable testing jobs #529

Align the develop and stable testing jobs #529

ekohl commented Jan 8, 2025

Align the develop and stable testing jobs #529

Are you sure you want to change the base?

Align the develop and stable testing jobs #529

Conversation

ekohl commented Jan 8, 2025