ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitriy Setrakyan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-1217) TC triggering by github pull-requests
Date Mon, 10 Aug 2015 19:07:47 GMT

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

Dmitriy Setrakyan commented on IGNITE-1217:


I am seeing an individual email for every build sent to the dev list. There is no need to
send any emails to the dev list. The only thing we need is a link to the TeamCity build added
as a comment to the Jira ticket.

> 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