fix: report GitHub Check before the cache #30372
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kuisathaverat
added
ci
Team:Automation
botelastic
bot
added
needs_team
|
This pull request does not have a backport label. Could you fix it @kuisathaverat? 🙏
NOTE: |
mergify
bot
added
the
backport-skip
kuisathaverat
added
backport-7.17
v1v
approved these changes
Feb 14, 2022
mdelapenya
approved these changes
Feb 14, 2022
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
|
/test |
mergify bot
pushed a commit
that referenced
this pull request
Feb 14, 2022
(cherry picked from commit f7ddf9f)
mergify bot
pushed a commit
that referenced
this pull request
Feb 14, 2022
(cherry picked from commit f7ddf9f)
mergify bot
pushed a commit
that referenced
this pull request
Feb 14, 2022
(cherry picked from commit f7ddf9f)
v1v
added a commit
to v1v/beats
that referenced
this pull request
Feb 21, 2022
…into feature/use-with-kind-k8s-env * 'feature/use-with-kind-k8s-env' of github.com:v1v/beats: (52 commits) ci: home is declared within withBeatsEnv ci: use withKindEnv step ci: use getBranchesFromAliases and support next-patch-8 (elastic#30400) Update fields.yml (elastic#29609) Heartbeat: fix browser metrics and trace mappings (elastic#30258) Apply light edits to 8.0 changelog (elastic#30351) packetbeat/beater: make sure Npcap installation runs before interfaces are needed (elastic#30396) Add a ring-buffer reporter to libbeat (elastic#28750) Osquerybeat: Add install verification for osquerybeat (elastic#30388) update windows matrix support (elastic#30373) Refactor of metricbeat process-gathering metrics and system/process (elastic#30076) adjust next changelog wording (elastic#30371) [Metricbeat] azure: move event report into loop validDim loop (elastic#29945) fix: report GitHub Check before the cache (elastic#30372) Add support for non-unique keys in Kafka output headers (elastic#30369) ci: 6 major branch reached EOL (elastic#30357) reduce Elastic Agent shut down time by stopping processes concurrently (elastic#29650) [Filebeat] Add message to register encode/decode debug logs (elastic#30271) [libbeat] kafka message header support (elastic#29940) Heartbeat: set duration to zero for syntax errors (elastic#30227) ...
kuisathaverat
added a commit
that referenced
this pull request
Mar 7, 2022
(cherry picked from commit f7ddf9f) Co-authored-by: Ivan Fernandez Calvo <[email protected]>
kuisathaverat
added a commit
that referenced
this pull request
Mar 7, 2022
(cherry picked from commit f7ddf9f) Co-authored-by: Ivan Fernandez Calvo <[email protected]>
kuisathaverat
added a commit
that referenced
this pull request
Mar 14, 2022
(cherry picked from commit f7ddf9f) Co-authored-by: Ivan Fernandez Calvo <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When the lint stage is not reported for some reason and the CI success you can not merge the PR because the lint check is required. Due to we have a cache in place the stage is never reported as a GitHub check if there are no changes in code. By changing the order of the GitHub check, it is always returned.