Skip to content

Ignore CI failures for Ruby 2.4 and 2.5#2023

Merged
jeremyevans merged 2 commits into
rack:mainfrom
jeremyevans:ci-fail-24-25
Jan 19, 2023
Merged

Ignore CI failures for Ruby 2.4 and 2.5#2023
jeremyevans merged 2 commits into
rack:mainfrom
jeremyevans:ci-fail-24-25

Conversation

@jeremyevans

Copy link
Copy Markdown
Contributor

No description provided.

continue-on-error: ${{ startsWith(matrix.ruby, '2.4') || startsWith(matrix.ruby, '2.5') }}

- run: bundle exec rake
continue-on-error: ${{ startsWith(matrix.ruby, '2.4') || startsWith(matrix.ruby, '2.5') }}

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might just be easier to have a matrix variable called unsupported or experimental and write:

Suggested change
continue-on-error: ${{ startsWith(matrix.ruby, '2.4') || startsWith(matrix.ruby, '2.5') }}
continue-on-error: ${{ matrix.unsupported }}

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately, I don't know how to set new matrix variables in GitHub Actions, or whether it is possible to do so (where 2.4 and 2.5 could be marked as unsupported, and the other versions not). If it is possible, can you point me to the documentation for doing so?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You would remove the ruby versions from the ruby list and instead include them in the matrix with include (where you would set unsupported), example of that at https://github.com/sporkmonger/addressable/blob/1fdd676753fb2f44c9d7e0953c97c3e6becfb36a/.github/workflows/test.yml#L116-L118 (but there it called allow-failure instead of unsupported)

@ioquatix

ioquatix commented Jan 19, 2023

Copy link
Copy Markdown
Member

Thanks for your effort here.

As I said before, I'm on the fence regarding this. I'm slightly against technical debt for the sake of old versions: technical debt in this case being configuration or code specifically to deal with them.

@jeremyevans jeremyevans merged commit 35a8574 into rack:main Jan 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants