Add the plugins command to Jarvis
#76
Closed
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
This add a new command to jarvis that allow you to get the status of the build for the default plugins that we ship with Logstash and it will periodically yield in the #logstash channel to tell us to look after them. You can trigger the query manually like this: ``` @jarvis plugins Jarvis Oops, We have currently *14* plugins jobs failing :sadbazpanda: Failures for branch: *master* logstash-codec-edn, logstash-codec-edn_lines, logstash-codec-es_bulk, logstash-codec-graphite, logstash-codec-json_lines, logstash-codec-multiline, logstash-codec-plain, logstash-filter-kv, logstash-filter-mutate, logstash-filter-split, logstash-filter-xml, logstash-output-elasticsearch, logstash-output-null, logstash-output-statsd ``` It will fetch the following file https://github.com/elastic/logstash/blob/master/rakelib/plugins-metadata.json to get the list of plugins. It can check more than one branch for some plugins, you will have to make a PR to this repository and add your plugin and the additional branch to check to the `plugins_config.yml` file. like this: ``` logstash-output-elasticsearch: - "6.x" ``` This was motivated by logstash-plugins/logstash-input-beats#203 and needed for the migration to jruby 9k
ph
commented
May 25, 2017
| location = "logstash-plugins/#{plugin_name}" | ||
| repo = ::Travis::Repository.find(location) | ||
| branches = branch_to_monitor(plugin_name) | ||
| status[plugin_name] = branches.each_with_object({}) { |branch, hsh| hsh[branch] = repo.branches[branch].passed? } |
There was a problem hiding this comment.
When you use passed? at the build level it will ignore jobs marked as allowed to fails (like for the feature/9000), But you can check status per job.
elasticsearch-bot
pushed a commit
that referenced
this pull request
May 26, 2017
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.
This add a new command to jarvis that allow you to get the status of the
build for the default plugins that we ship with Logstash and it will
periodically yield in the #logstash channel to tell us to look after them.
You can trigger the query manually like this:
It will fetch the following file https://github.com/elastic/logstash/blob/master/rakelib/plugins-metadata.json to get the list of plugins.
It can check more than one branch for some plugins, you will have
to make a PR to this repository and add your plugin and the additional
branch to check to the
plugins_config.ymlfile. like this:This was motivated by logstash-plugins/logstash-input-beats#203
and needed for the migration to jruby 9k