We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
With the proposal in #7183 to make the choice impactful I think we will need to provide an aggregated view of the plugin states.
I suggest when a build is successful or fails we trigger a webhook on Jarvis, the bot will periodically report something like this.
fails on master: {link to the failling build} fails on jruby-9k: { link to the failling build1}, { link to the failling build2}
The text was updated successfully, but these errors were encountered:
Done in elastic/jarvis#76
Sorry, something went wrong.
ph
No branches or pull requests
With the proposal in #7183 to make the choice impactful I think we will need to provide an aggregated view of the plugin states.
I suggest when a build is successful or fails we trigger a webhook on Jarvis, the bot will periodically report something like this.
The text was updated successfully, but these errors were encountered: