Closed JoshRosen closed 9 years ago
+1 on this.
What if we created some kind of barebones API that Jenkins could call directly to set the PR status? Basically, we'd be replicating the Commit Status API that GitHub offers (but which we can't use).
Meh, we might as well just remove "AmplabJenkins" from the list of QA bots and only count messages from SparkQA; this is simpler and avoids introducing any new code in Spark itself.
Now that @amplabjenkins is also reporting statuses on our PRs, we should filter out its "build succeeded / build failed" messages so that the test outcome messages from our own script are viewable in the PR dashboard's tooltips.