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

Backport (v1.16): Refine CI (#4380) #4428

Merged
merged 2 commits into from Mar 11, 2024
Merged

Backport (v1.16): Refine CI (#4380) #4428

merged 2 commits into from Mar 11, 2024

Conversation

daipom
Copy link
Contributor

@daipom daipom commented Mar 11, 2024

Refine CI settings:

* Unify CI settings for each platforms to one file
* Don't run CI for Ruby head on each push/pull_request event
    * Because Ruby head is continually changed and not released
      yet, running CI one shot isn't so meaningful.
    * Instead run it regularly on every Sunday.
* Add TESTOPT=-v to all platfroms
    * It's useful to investigate when a test is stalled.
* Remove a hack for Ruby 3.0 on Windows
    * It seems no longer needed.

Signed-off-by: Takuro Ashie <ashie@clear-code.com>
@kenhys
Copy link
Contributor

kenhys commented Mar 11, 2024

Should we use .yaml instead of .yml for consistency in fluent/fluentd?

@daipom
Copy link
Contributor Author

daipom commented Mar 11, 2024

Should we use .yaml instead of .yml for consistency in fluent/fluentd?

Thanks for

We can backport this later as well.

because Ruby head is never supported on v1.16, and it seems wrong
to use schedule trigger outside of the default branch (master).

Signed-off-by: Daijiro Fukuda <fukuda@clear-code.com>
Co-authored-by: Takuro Ashie <ashie@clear-code.com>
@ashie ashie merged commit 30602a5 into v1.16 Mar 11, 2024
13 of 16 checks passed
@ashie ashie deleted the v1.16-backport-4380 branch March 11, 2024 04:07
@daipom
Copy link
Contributor Author

daipom commented Mar 11, 2024

Thanks!

@daipom
Copy link
Contributor Author

daipom commented Mar 11, 2024

Need to backport some commits to fix Ruby 3.3 tests. I'm doing.

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.

None yet

3 participants