-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Bump plugins to get latest documentation changes #7993
Comments
The tooling we have right now (thanks, @ph!) has certain expectations about how the plugin version is written, and there are a handful of plugins that use a different versioning system than the rest of the plugins I'm going to try and fix that before moving forward on this. I'll keep this updated as I progress. |
The rest use |
@jsvd Can you take a look at some of these branches in the above comment? I'm going to spot check a few others. All plugins should now have a Next steps for me to do after the reviews are completed:
|
@jordansissel the test PR's look good, same for your version-bumper branch. One thing to note is that several plugins had their major versions bumped, and these will only be included in Logstash 6.0 For all of these it's necessary to branch off of the latest release tag and bump that branch. We can see the major versions of plugins used by 5.5.1 by running the command below in
From here we should be able to fetch the latest patch or minor release tag in each plugin repo, branch from there, and execute your bump_version |
@jsvd yeah I had that thought; thank you for verifying! I'm expecting this to be a bit of a battle given the docs changes may have landed only in the new majors, but I will find out soon. |
I'm pushing all the current changes to plugins now. Next step will be to do the same patch bumps on all plugin minor versions targeted for Logstash 5.6 |
For elastic/logstash#7993 [ci skip]
For elastic/logstash#7993 [ci skip]
For elastic/logstash#7993 [ci skip]
For elastic/logstash#7993 [ci skip]
For elastic/logstash#7993 [ci skip]
For elastic/logstash#7993 [ci skip]
For elastic/logstash#7993 [ci skip]
For elastic/logstash#7993 [ci skip]
For elastic/logstash#7993 [ci skip]
For elastic/logstash#7993 [ci skip]
For elastic/logstash#7993 [ci skip]
For elastic/logstash#7993 [ci skip]
For elastic/logstash#7993 [ci skip]
For elastic/logstash#7993 [ci skip]
For elastic/logstash#7993 [ci skip]
For elastic/logstash#7993 [ci skip]
Unresolvedlogstash-output-hipchat v4.0.3master is v4.0.3 and needs to be published. ❌ ❗️ I am going to skip this plugin. We should remove it from the docs until we resolve this? logstash-output-jms v3.0.1master is v3.0.2 and needs to be published ❌ Resolvedlogstash-output-rabbitmq v4.0.10asciidoc typo fix on
✅ Published logstash-output-rabbitmq-4.0.11-java.gem logstash-input-graphite v3.0.3This should be v3.0.4 but somehow it didn't get published in my last run. Jarvis won't publish it because the tests are failing on what seems like a flaky test - https://travis-ci.org/logstash-plugins/logstash-input-graphite/jobs/266105322 I'm having Jarvis ignore the test failure. ✅ published https://rubygems.org/gems/logstash-input-graphite/versions/3.0.4 logstash-output-datadog_metrics v3.0.1master is v3.0.2 and needs to be published. ✅ Published logstash-output-datadog_metrics-3.0.2.gem logstash-output-exec v3.1.1master is v3.1.2 and needs to be published. ✅ Published logstash-output-exec-3.1.2.gem logstash-output-lumberjack v3.1.3master is 3.1.5 and needs to be published ✅ Published logstash-output-lumberjack-3.1.5.gem logstash-filter-hashid v0.1.2logstash-mass_effect lists this as a plugin that is manually removed. I think this is correct and this plugin should not show up in the documentation. The Anyway, we don't have time really to decide and execute on removing hashid, so here are the next steps:
✅ Published logstash-filter-hashid-0.1.3.gem logstash-output-kafka v5.1.9needs an
✅ Published logstash-output-kafka-5.1.10.gem logstash-input-kafka v5.1.10This needs an
✅ Published logstash-input-kafka-5.1.11.gem |
related: elastic/logstash#7993 Fixes #146
Related: elastic/logstash#7993 Fixes #5
Next step is to remove the jms and hipchat outputs from the docs because these two plugins latest version's do not work in Logstash 5.x due to their depedencies requiring Ruby 2.x syntax. |
This is because the latest plugin versions (hipcat v4.0.3, jms v3.0.1) are incompatible with Logstash 5.x as they require ruby 2.0 or 2.1, and Logstash 5 uses JRuby 1.7 which is Ruby 1.9.3 Related elastic/logstash#7993
Currently blocked on:
|
Blocked on logstash-plugins/logstash-codec-rubydebug#1 |
Next steps:
|
Reasons: * The jms output cannot be installed under Logstash 5.6 because of a transitive dependency that requires Ruby >=2.1 * The hipchat output cannot be installed under Logstash 5.6 because of a transitive dependency that requires Ruby >=2.0 History here: elastic/logstash#7993 (comment)
PR to remove jms and hipchat outputs: elastic/logstash-docs#408 |
Reasons: * The jms output cannot be installed under Logstash 5.6 because of a transitive dependency that requires Ruby >=2.1 * The hipchat output cannot be installed under Logstash 5.6 because of a transitive dependency that requires Ruby >=2.0 History here: elastic/logstash#7993 (comment) Fixes #408
* Add WIP to fetch all plugin asciidoc. * Add --master flag for fetching master docs from plugins. Also fill in placeholders in docs like %VERSION%, etc * Add Gemfile * Add default-or-not check * Skip hipchat and jms outputs This is because the latest plugin versions (hipcat v4.0.3, jms v3.0.1) are incompatible with Logstash 5.x as they require ruby 2.0 or 2.1, and Logstash 5 uses JRuby 1.7 which is Ruby 1.9.3 Related elastic/logstash#7993 * Move skip settings to a yaml file * Make the settings yaml a flag.
I think this is resolved fully. Some related work pending getting the docs published, but all the preparation work (version bumps, etc) in this issue is complete. |
For elastic/logstash#7993 [ci skip]
We've made some documentation changes in most plugins, and in order for those docs changes to ship with 5.6.0, we need to release every plugin that's had a docs change.
We didn't notice this in time for the 5.5.0 release, and on release day, we (mostly @dedemorton's hard work) do a lot of contortions in order to get the docs updated. It was manual and difficult work.
This is a blocker for 5.6.0 because I'm not going through that pain again :)
The text was updated successfully, but these errors were encountered: