[
https://issues.apache.org/jira/browse/BUILDS-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14645889#comment-14645889
]
Ismael Juma commented on BUILDS-102:
------------------------------------
That sounds promising [~abayer]. Thanks for looking into this.
In the meantime, I'll test close/reopen PR as a workaround.
> Ability to trigger Jenkins rebuild for GitHub pull requests
> -----------------------------------------------------------
>
> Key: BUILDS-102
> URL: https://issues.apache.org/jira/browse/BUILDS-102
> Project: Infra Build Platform
> Issue Type: Improvement
> Components: Jenkins
> Reporter: Ismael Juma
> Assignee: Andrew Bayer
>
> It would be really useful to be able to trigger a Jenkins rebuild for a
> GitHub pull request when the build fails due to a transient problem (ie flaky
> tests and/or environmental issues). Despite our best efforts, it's hard to
> eliminate all flaky tests from the Kafka codebase (as some are fixed, new
> ones appear).
> This is supported by the open-source GitHub Pull Request Builder Plugin via
> comments in the pull request itself (e.g. "retest this please" to rebuild,
> "add to whitelist" to automatically build future pull requests from the
> submitter, etc.):
> https://wiki.jenkins-ci.org/display/JENKINS/GitHub+pull+request+builder+plugin
> Spark is using this with the AMPLab Jenkins instance:
> https://github.com/apache/spark/pull/7613
> https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38199/consoleFull
> The Apache Jenkins instance is using the Jenkins Enterprise GH PR plugin,
> which doesn't support this functionality (probably based on
> https://wiki.jenkins-ci.org/display/JENKINS/GitHub+Plugin) because the more
> featured one required privileges on the GitHub side that the Apache Infra
> team was not able to give at the time (as explained by [~abayer]).
> [~abayer] suggested that he would check if things have changed. The fact that
> Spark made it work is a good indicator. We also have the option of moving to
> a separate Jenkins instance (Confluent has offered theirs), but we would
> prefer to improve the Apache one as that benefits the other projects too.
> This was originally discussed in the following thread in the mailing list:
> https://mail-archives.apache.org/mod_mbox/www-builds/201507.mbox/%3CCAD5tkZYrrjp4%2BS7a7DBNMZsAXJozB8kopwgGC%3DOLO63aB-4mBg%40mail.gmail.com%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
