On Sat, Jun 6, 2015 at 10:23 PM, Varnau, Steve (Trafodion)
<[email protected]> wrote:
> Comment below...
A few comments of my own:
>> So, folks would comment on code up in github and CI running on Apache
>> servers would pull from github? JIRA would also carry comments on
>> patches and design?
>>
>> This will split the comment history across two systems.
>
> Apache Infra provides integration with github, such that all the github
> pull-request
> activity is mirrored back to JIRA. Jira is the system of record.
The workflow is pretty nice. Really the only thing you can NOT do is to
use 'merge PR' button on the GH UI.
> Github provides a
> better code-review interface than Jira, so it is convenient to make code
> review comments there. Apache/Spark and other projects use similar process.
Some folks prefer Reviewboard which is available for ASF projects at:
http://reviews.apache.org
Some developers swear by its side-by-side diff UI for reviews.
> The Apache CI system does not have any RedHat/Centos systems as far as we can
> tell,
I highly recommend using Docker containers. There's absolutely nothing
that a Docker
container can't do for your build AND it doesn't require you to setup
slaves in any
special way whatsoever.
> One key is that each pull-request in github should have a JIRA-ID in the
> title.
You don't actually need it. But it helps. Basically, try to make
receiving PRs into
your project as simple as possible -- that's your gateway to community growth.
To Stack's point -- Spark offers a good example of how tooling can help solve
99% of these integrations issues. Here's the dashboard (available in Spark GH)
that Spark folks use to pull it all together:
https://spark-prs.appspot.com/
it strikes me as a rather nice tool.
Thanks,
Roman.
