canonical-ci-engineering team mailing list archive

[Evan Dandrea <evan.dandrea@xxxxxxxxxxxxx>]

Thanks for the thoughtful feedback, Francis.

On 16 December 2013 20:31, Francis Ginther
<francis.ginther@xxxxxxxxxxxxx> wrote:
> Here are some technical problems that immediately come to mind:
>  - We would be missing launchpad user integration. We would either
> need to replicate our users and teams in github or create a mapping
> between github and launchpad.

Where do we need Launchpad users beyond authentication? Github is an
OAuth provider, and Jenkins has a plugin for talking to it.

If we're talking about a project that has its team members already
configured in Github, do we really need to maintain a mapping of those
users to Launchpad users?

>  - Our workflow tools would need to be ported to talk to git and
> github. This includes things like lp:tarmac and lp:cupstream2distro.
> The git plugin appears to help here, but doesn't appear to do things
> like enforce review requirements and comment on reviews.

I don't think we'd need cupstream2distro here. We're talking about the
push notification server. As I understand it, the code wouldn't need
to live in the distro (or at least wouldn't have dependencies into the
distro). Did you have a different understanding?