Closed gold2718 closed 11 months ago
Fine by me. Julie, since you added those tests, do you want to change the CI tests so that they only run for NCAR/ccpp-framework?
I've hacked at this for a day without success, so maybe someone who is more familiar with Travis CI can take a look at it.
Is this still an issue? We are using github actions nowadays, and those run fine everywhere. I do recommend however to change
to
on:
pull_request:
paths-ignore:
- 'doc/**'
- '**.md'
- '.github/ISSUE_TEMPLATE/*'
- '.gitignore'
(or whatever the exact exclusion list should be)
@mkavulich @peverwhee @dustinswales
@climbfuji I think we can close this In #494 this is changed to trigger on PRs. Do we need to add paths-ignore?
paths-ignore just means that you don't run CI tests if you are only changing documentation (it still runs doxygen etc), README.md
etc. Whatever you list there. Makes sense, or?
Gotcha. Then yes, lets add these exclusions to #494, and reference this Issue?
Sounds good to me
On Sep 14, 2023, at 2:01 PM, Dustin Swales @.***> wrote:
Gotcha. Then yes, lets add these exclusions to #494 https://github.com/NCAR/ccpp-framework/pull/494, and reference this Issue?
— Reply to this email directly, view it on GitHub https://github.com/NCAR/ccpp-framework/issues/401#issuecomment-1720063440, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB5C2RNE4P3KZ4V7MLXBPADX2NPA7ANCNFSM5C53A4GA. You are receiving this because you were mentioned.
Currently, the Travis CI workflow is run in any fork on any push. I feel this should be restricted to the main repo (NCAR/ccpp-framework), especially since git encourages frequent commits and currently a failure sends email to several (not involved for a fork push) parties. @climbfuji, @JulieSchramm, Thoughts?