[apparmor] test git repo

[Steve Beattie]

[Resending as apparently mailman decided to eat the first copy.
 Apologies if you receive multiple copies.]

On Sat, Sep 30, 2017 at 07:23:47AM -0500, Goldwyn Rodrigues wrote:
> On 09/26/2017 03:26 PM, Steve Beattie wrote:
> > I've made available a test apparmor git repository at
> > 
> >   https://code.launchpad.net/~sbeattie/apparmor/+git/apparmor
> > 
> > You can git clone it via
> > 
> >   git clone https://git.launchpad.net/~sbeattie/apparmor/+git/apparmor
> > 
> > Please feel free to take check out it, as I'd like to cut over
> > permanently to git in the next day or two.
> > 
> > I have not yet done the work to make the tarball generation work with
> > git and the .bzrignore needs to be converted to .gitignore, but
> > otherwise the tree should be complete.
> > 
> > Please let me know if you see any issues with the repo. Thanks!
> 
> Would this be the final location of the repository?

No. In the shortest of terms, when we officially cut over, it would appear at

  https://code.launchpad.net/~apparmor-dev/apparmor/+git/apparmor

with the shortname for the repo at

  https://git.launchpad.net/apparmor

(an alias for
https://git.launchpad.net/~apparmor-dev/apparmor/+git/apparmor)

> I was thinking of putting it in github[1] and using travis-ci[2]
> for continuous integration. [The repo does not have to be under my
> name. It is just the repo I used for bzr->git bridge.] I am not done
> with the travis as yet.
> 
> [1] https://github.com/goldwynr/apparmor
> [2] https://travis-ci.org/goldwynr/apparmor

Beyond the immediate conversion landing location, I'm supportive
of moving code-hosting and merge requests to github or gitlab and
the integrated CI environments that they enable. The whole point
of converting to git is to make it easier for people to contribute,
and choice of code hosting location affects that.

> And yes, it will provide mail notifications for pending pull requests
> and failed builds which could be directed to mailing lists.

To be fair, we currently have some automated builds in launchpad
that send failures to this list; I just don't moderate them through
because they are currently failing due to build bit rot issues (though
there's a legitimate build/test failure that occurs in libapparmor
on trunk and 2.11, which is what's blocking me from releasing a 2.11
maintenance release).

But the lack of email notifications from launchpad on git commits
is an issue, one that I was promised would have been addressed by
now. It can be worked around by having a commit hook that pushes to
a web service that would send out the email notification, but that
strikes me as an excessive hoop to jump through.

Thanks!

-- 
Steve Beattie
<sbeattie at ubuntu.com>
http://NxNW.org/~steve/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/apparmor/attachments/20171002/73100270/attachment.sig>