action: update specs #32
Merged
Conversation
This file contains hidden or 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
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.
What
Use GitHub actions in addition to the
updateclito bump the json schemas created inecs-logging.It runs on a daily basis and create a Pull Request if new changes exist.
Create PRs with the description pointing to the original change in the ecs-logging, similarly done in #30
Why
Jenkins ecosystem at Elastic is deprecated, so let's use GH actions with
updatecli, so consumers can control what to do and when.Test
#31 was created based on these changes
Further details
The automation relied on Jenkins and projects were onboarded by having a configuration entry in https://github.com/elastic/ecs-logging/blob/main/.ci/.jenkins-loggers.yml