[
https://issues.apache.org/jira/browse/IGNITE-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14681787#comment-14681787
]
Artem Shutak commented on IGNITE-1217:
--------------------------------------
Comment to point 1.
Looks like it's not a good idea to use the plugin for Ignite. We have to many
builds for triggering, so the plugin adds lots of comments to pull requests. It
looks ugly. Example: https://github.com/apache/incubator-ignite/pull/12 (It's
fake pull-request).
> TC triggering by github pull-requests
> -------------------------------------
>
> Key: IGNITE-1217
> URL: https://issues.apache.org/jira/browse/IGNITE-1217
> Project: Ignite
> Issue Type: Task
> Reporter: Artem Shutak
> Assignee: Artem Shutak
> Attachments: master_19fb305_ignite-1217.patch,
> master_19fb305_ignite-1217.patch_
>
>
> Need to investigate possibility of auto triggering TC by pull requests.
> Expected approach
> - contributor creates fork of apache git repo mirror at github
> - working with oun fork, creates branches, commites, pushes
> - create a pull request with changes from own fork to apache ignite mirror on
> github
> - TC automatically trigger builds for the pull-request
> - if TC green then a commiter apply changes to apache git repo (not to mirror
> on github)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
