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

Skip CI when dev_docs or .mdx files are changed #133087

Merged
merged 1 commit into from
May 30, 2022
Merged

Skip CI when dev_docs or .mdx files are changed #133087

merged 1 commit into from
May 30, 2022

Conversation

jportner
Copy link
Contributor

I noticed that CI appears to be broken on the 8.0 branch which is preventing #132944 from merging.
However, that PR contains only docs changes and it shouldn't be triggering the kibana-ci actions anyway.

I updated the Buildkite config to skip CI when dev docs and/or MDX files are changed.

Note that this config was changed recently (in #132461), so backports for this PR will run into merge conflicts and will need to be manually fixed.

@jportner
Copy link
Contributor Author

jportner commented May 29, 2022

Two questions for reviewers:

1. Should we backport this farther back than 7.17 (maybe as far back as 7.13?) EDIT: it looks like the Buildkite PR pipeline was first introduced in 7.14 (#112029), so I think we can backport this PR that far back.

"always_require_ci_on_changed": [
"^docs/developer/plugin-list.asciidoc$",
"/plugins/[^/]+/readme\\.(md|asciidoc)$"
]

2. Should I change this to always require CI on readme.mdx files as well? I'm not sure that I understand the reasoning for always requiring CI when README files are changed.

@jportner jportner added release_note:skip Skip the PR/issue when compiling release notes v7.14.0 v7.15.0 v7.16.0 labels May 29, 2022
@jportner jportner changed the title Skip CI when .dev_docs or .mdx files are changed Skip CI when dev_docs or .mdx files are changed May 29, 2022
@brianseeders
Copy link
Contributor

Changes to this file are effectively applied to all branches, so it doesn't need to be backported at all.

@mistic
Copy link
Member

mistic commented May 30, 2022

@jportner regarding your question 2, .mdx dev_docs files built differently so we don't need to add them there.

@jportner jportner merged commit 086a895 into main May 30, 2022
@jportner jportner deleted the skip-ci branch May 30, 2022 13:15
jbudz added a commit that referenced this pull request Oct 17, 2024
Currently CI is not run on pull requests with `dev_docs` only changes.  

This was implemented in #133087,
where at the time we were not running any validation. Validation was
later added in #149991, but the
skip criteria was not updated.

This removes the skip criteria, allowing our validation checks to run on
all `dev_docs` changes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:skip This commit does not require backporting release_note:skip Skip the PR/issue when compiling release notes v8.4.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants