Full CI and How to use Samba's gitlab.com repos! (was: Re: gitlab seems the best Free Software home.)

[Andrew Bartlett]

On Wed, 2018-05-30 at 09:17 -0700, Jeremy Allison via samba-technical
wrote:
> On Wed, May 30, 2018 at 06:05:17PM +0200, David Disseldorp via samba-technical wrote:
> > Hi Jeremy,
> > 
> > On Wed, 30 May 2018 08:48:05 -0700, Jeremy Allison via samba-technical wrote:
> > 
> > > Just wanted to point out that the Gnome
> > > project just announced the completion of
> > > their migration to gitlab:
> > > 
> > > https://twitter.com/csoriano1618/status/1001501640623640577
> > > 
> > > So (IMHO of course) gitlab does seem the
> > > way forward for Samba as well.
> > 
> > As "the way forward", do you mean self-hosting the MIT licensed
> > Community Edition, or some other sort of setup?
> 
> Well I don't want to give up our infrastructure yet :-),
> but I was thinking of better integration with gitlab
> for occasional contributors.

This seems to be a good point to announce some things.

I gave instructions here for how to fork the official Samba Team mirror
on gitlab:
 https://lists.samba.org/archive/samba-technical/2018-May/127740.html

When you then push back to a branch in that fork, many of the tests run
in shared runners provided by GitLab.com.  This is a similar but not
matching set to those run in Travis-CI:

The missing tests (autobuild targets) compared to sn-devel on the two
platforms are

Travis CI
 - samba

GitHub shared runners
 - samba
 - samba-nt4
 - samba-fileserver
 - samba-ad-dc

Anybody at all can use this simply by creating an account (as below)
and forking Samba's primary mirror:
https://gitlab.com/samba-team/samba/forks/new

However there is GOOD NEWS!

I've set up a new shared repo, entitled "Upstream Samba Development". 
There I've set up the remaining tests, so if you push a branch there
the FULL set of tests are run, using 'private runners' on Rackspace to
fill in the gaps. 

https://gitlab.com/samba-team/devel/samba/

Members of the samba-team organisation on gitlab.com already have
access, but because this isn't our main repository (only the master and
release branches are protected and force-reset), we can also allow
others from our broader community to join. 

Between these options we have a good set of options to have gitlab be
both a major development platform for Samba Team members while also
providing great service and rapid feedback for external contributors.

Status on pipelines (CI) run in this repo is summarised here:

https://gitlab.com/samba-team/devel/samba/pipelines

I'll talk about this more during my talk at SambaXP.

Finally, to join:

https://gitlab.com -> Sign in/register (top right-hand corner)

Use either github/google/etc credentials or create an account.

Once in, click the profile icon in the top-right-hand corner to access
your profile

Click the pen to edit it.  Click SSH keys or go to 
https://gitlab.com/profile/keys

Add your SSH key.

To set up two-factor authentication go to:
https://gitlab.com/profile/account

Finally, tell me your username and I can add you to the samba-team
group or the samba-team/devel/samba repo as appropriate.

You can pull and push from the collaborative development repo using
this git URL:

git at gitlab.com:samba-team/devel/samba.git

eg 

git remote add gitlab.com-samba-devel git at gitlab.com:samba-team/devel/samba.git
git fetch gitlab.com-samba-devel

Please play nice and use branch-names starting with your username.

Thanks,

Andrew Bartlett
-- 
Andrew Bartlett                       http://samba.org/~abartlet/
Authentication Developer, Samba Team  http://samba.org
Samba Developer, Catalyst IT          http://catalyst.net.nz/services/samba