Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge ui_rm_head into one workflow file using matrix #60

Open
thehejik opened this issue Feb 27, 2024 · 2 comments
Open

Merge ui_rm_head into one workflow file using matrix #60

thehejik opened this issue Feb 27, 2024 · 2 comments
Assignees
Labels
automation Add or update automation fleet-e2e-ci Improvements or additions to the CI framework

Comments

@thehejik
Copy link
Collaborator

thehejik commented Feb 27, 2024

It should be possible to merge all 3 head-2.x workflow files into one workflow file by using matrix, so far we are using just 2 various variables (rancher_version and upstream_cluster_version).

Also it shouldn't prevent us to use an extra variables if we need them let say for disabling specific tests for 2.9 by following this document https://docs.github.com/en/actions/using-jobs/using-a-matrix-for-your-jobs#example-expanding-configurations

Also update description of qase_run_id there and provide hint for possible values like 'auto'/'none'/existing_qase_id#).

@thehejik thehejik added automation Add or update automation fleet-e2e-ci Improvements or additions to the CI framework labels Feb 27, 2024
@thehejik thehejik self-assigned this Feb 27, 2024
@thehejik
Copy link
Collaborator Author

thehejik commented Mar 20, 2024

The change lives here main...matrix

But there is a problem with status badges which should be addressed first ideally without involving 3rd party action. The default gh badge supports only overall status for the entire workflow but not its sub-jobs.

I was thinking about involving gh-pages on this repo and using https://img.shields.io/badge/MYJOB-STATUS-green where I could dynamically generate a simple html with proper state of last main run.

Or similarly we could save ci results into last-results.json file on gh pages in our gh project after finishing main job on schedule and then use something like https://shields.io/badges/dynamic-json-badge

@thehejik
Copy link
Collaborator Author

Reverted due to problems with badges. We will have to find a better way than 40ants service.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation Add or update automation fleet-e2e-ci Improvements or additions to the CI framework
Projects
None yet
Development

No branches or pull requests

1 participant