ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Artem Shutak (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-1217) TC triggering by github pull-requests
Date Tue, 11 Aug 2015 13:18:45 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14681784#comment-14681784

Artem Shutak commented on IGNITE-1217:

Currently, everyone can fork Mirror of Apache Ignite on GitHub (https://github.com/apache/incubator-ignite),
works with own fork (create branches, commit, pull changes at fork) and then creates a pull-request
to Mirror of Apache Ignite on GitHub (all changes should be done in one commit as in patch-way
approach). Then test TC builds will triggered automatically. Results can be found by branch
filtering by pattern <pull-request-number>/merge. "Merge" suffix here means pull-request
merged with master branch (if pull-request at master branch).


1. I tried to use TC plugin for github to see TC result at pull-request. But the plugin works
in unexpected way and add comments not only to pull-requests. Example: https://github.com/apache/incubator-ignite/commit/ae11e9b5aa9af4d0d58e2a16dd3a3331969961df#commitcomment-12635375.

2. I'm looking for a simple way to add information about new pull-request to associated jira.
The better way to use existing Jira plugin for it - DVCS plugin (https://confluence.atlassian.com/display/BITBUCKET/Linking+Bitbucket+and+GitHub+accounts+to+JIRA).
But I need both: Jira administration rights to configure the plugin and GitHub password for
"apache" user.

> 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

View raw message