Move logstash release information to .ci
#17924
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
Consumers of this information are already cloning the `.ci` repo. They subsequently curl logstash for this information. Moving to `.ci` reduces steps and removes the need to track this across information in active streams of logstash.
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
|
This pull request does not have a backport label. Could you fix it @donoghuc? 🙏
|
donoghuc
added
the
backport-active-all
|
💚 Build Succeeded
|
|
@Mergifyio backport 8.17 8.18 8.19 9.0 9.1 |
✅ Backports have been created
|
mergify bot
pushed a commit
that referenced
this pull request
Aug 8, 2025
Consumers of this information are already cloning the `.ci` repo. They subsequently curl logstash for this information. Moving to `.ci` reduces steps and removes the need to track this across information in active streams of logstash. (cherry picked from commit 95a0466) # Conflicts: # ci/logstash_releases.json
mergify bot
pushed a commit
that referenced
this pull request
Aug 8, 2025
Consumers of this information are already cloning the `.ci` repo. They subsequently curl logstash for this information. Moving to `.ci` reduces steps and removes the need to track this across information in active streams of logstash. (cherry picked from commit 95a0466) # Conflicts: # ci/logstash_releases.json
mergify bot
pushed a commit
that referenced
this pull request
Aug 8, 2025
Consumers of this information are already cloning the `.ci` repo. They subsequently curl logstash for this information. Moving to `.ci` reduces steps and removes the need to track this across information in active streams of logstash. (cherry picked from commit 95a0466) # Conflicts: # ci/logstash_releases.json
mergify bot
pushed a commit
that referenced
this pull request
Aug 8, 2025
Consumers of this information are already cloning the `.ci` repo. They subsequently curl logstash for this information. Moving to `.ci` reduces steps and removes the need to track this across information in active streams of logstash. (cherry picked from commit 95a0466) # Conflicts: # ci/logstash_releases.json
mergify bot
pushed a commit
that referenced
this pull request
Aug 8, 2025
Consumers of this information are already cloning the `.ci` repo. They subsequently curl logstash for this information. Moving to `.ci` reduces steps and removes the need to track this across information in active streams of logstash. (cherry picked from commit 95a0466) # Conflicts: # ci/logstash_releases.json
yaauie
reviewed
Aug 8, 2025
There was a problem hiding this comment.
🎉
It's great to have all of this finally self-contained in .ci.
donoghuc
added a commit
that referenced
this pull request
Aug 8, 2025
…17938) * Move logstash release information to `.ci` (#17924) Consumers of this information are already cloning the `.ci` repo. They subsequently curl logstash for this information. Moving to `.ci` reduces steps and removes the need to track this across information in active streams of logstash. (cherry picked from commit 95a0466) # Conflicts: # ci/logstash_releases.json * Remove logstash_releases.json --------- Co-authored-by: Cas Donoghue <[email protected]>
donoghuc
added a commit
that referenced
this pull request
Aug 8, 2025
…17939) * Move logstash release information to `.ci` (#17924) Consumers of this information are already cloning the `.ci` repo. They subsequently curl logstash for this information. Moving to `.ci` reduces steps and removes the need to track this across information in active streams of logstash. (cherry picked from commit 95a0466) # Conflicts: # ci/logstash_releases.json * Remove logstash_releases.json --------- Co-authored-by: Cas Donoghue <[email protected]>
donoghuc
added a commit
that referenced
this pull request
Aug 8, 2025
…17940) * Move logstash release information to `.ci` (#17924) Consumers of this information are already cloning the `.ci` repo. They subsequently curl logstash for this information. Moving to `.ci` reduces steps and removes the need to track this across information in active streams of logstash. (cherry picked from commit 95a0466) # Conflicts: # ci/logstash_releases.json * Remove logstash_releases.json --------- Co-authored-by: Cas Donoghue <[email protected]>
donoghuc
added a commit
that referenced
this pull request
Aug 8, 2025
…17942) * Move logstash release information to `.ci` (#17924) Consumers of this information are already cloning the `.ci` repo. They subsequently curl logstash for this information. Moving to `.ci` reduces steps and removes the need to track this across information in active streams of logstash. (cherry picked from commit 95a0466) # Conflicts: # ci/logstash_releases.json * Remove logstash_releases.json --------- Co-authored-by: Cas Donoghue <[email protected]>
donoghuc
added a commit
that referenced
this pull request
Aug 8, 2025
…17941) * Move logstash release information to `.ci` (#17924) Consumers of this information are already cloning the `.ci` repo. They subsequently curl logstash for this information. Moving to `.ci` reduces steps and removes the need to track this across information in active streams of logstash. (cherry picked from commit 95a0466) # Conflicts: # ci/logstash_releases.json * Remove logstash_releases.json --------- Co-authored-by: Cas Donoghue <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Consumers of this information are already cloning the
.cirepo. They subsequently curl logstash for this information. Moving to.cireduces steps and removes the need to track this across information in active streams of logstash.Issue described in https://github.com/elastic/ingest-dev/issues/4773