Difference between revisions of "Samba CI on gitlab"

(Expand gitlab CI page)
Line 1: Line 1:
 +
=Samba Team members=
 +
 
Samba Team members are encouraged to join the Samba Team organisation here:
 
Samba Team members are encouraged to join the Samba Team organisation here:
  
 
* [https://gitlab.com/samba-team/ gitlab CI for Samba team member]
 
* [https://gitlab.com/samba-team/ gitlab CI for Samba team member]
 +
 +
==How to join==
 +
 +
If you are a Samba Team member then you are entitled to access.  Just ask on the team list from your team e-mail with your gitlab username.
 +
 +
A fellow team member with *maintainer* rights can then add you a *developer* via this page:
 +
 
* [https://gitlab.com/groups/samba-team/-/group_members Samba team group members]
 
* [https://gitlab.com/groups/samba-team/-/group_members Samba team group members]
 +
 +
=Other Samba developers=
  
 
Our broader developer community is encouraged to apply to join a collaborative development repo here:
 
Our broader developer community is encouraged to apply to join a collaborative development repo here:
Line 8: Line 19:
 
* [https://gitlab.com/samba-team/devel/samba CI for Samba contributors]
 
* [https://gitlab.com/samba-team/devel/samba CI for Samba contributors]
  
Access is given to folks active on the mailing list with patches to submit, not just to Samba Team members.
+
==How to join==
 +
 
 +
Access is given to folks active on the mailing list with patches to submit, not just to Samba Team members.
  
If using that, please prefix branches with your username, and be nice. In return you get a full CI run using Samba Team provided resources running thanks to a credit in Rackspace's cloud.
+
Please write a mail to contributing@samba.org with details of your contribution history or plans and a Samba Team member with *maintainer* rights can then add you as a *developer* via this page:
 +
 
 +
* https://gitlab.com/samba-team/devel/samba/project_members
 +
 
 +
==Code of conduct==
 +
 
 +
If using that, please prefix branches with your username, and be nice. Don't overwrite the work of others. 
 +
 
 +
In return you get a full CI run using Samba Team provided resources running thanks to a credit in Rackspace's cloud.  That in turn makes it easier for Samba Team members doing [[CodeReview|Code Review]] as your patches will work first time, and they can see proof of that.
 +
 
 +
==CI Results==
 +
 
 +
A CI run is triggered after every push.  This makes finding issues early easy.  
  
 
CI results are here: [https://gitlab.com/samba-team/devel/samba/pipelines Pipelines]
 
CI results are here: [https://gitlab.com/samba-team/devel/samba/pipelines Pipelines]
  
Instructions how to run CI with your own gitlab runner can be found here: [[CI using Your own gitlab runner]].
+
=CI for personal GitLab forks=
 +
 
 +
Instructions how to run CI with your own GitLab runner can be found here: [[CI using Your own gitlab runner]]
 +
 
 +
This is helpful if you do not wish to share the repository with others (you have your own fork on gitlab).  However it requires your own build resources.

Revision as of 22:47, 4 July 2018

Samba Team members

Samba Team members are encouraged to join the Samba Team organisation here:

How to join

If you are a Samba Team member then you are entitled to access. Just ask on the team list from your team e-mail with your gitlab username.

A fellow team member with *maintainer* rights can then add you a *developer* via this page:

Other Samba developers

Our broader developer community is encouraged to apply to join a collaborative development repo here:

How to join

Access is given to folks active on the mailing list with patches to submit, not just to Samba Team members.

Please write a mail to contributing@samba.org with details of your contribution history or plans and a Samba Team member with *maintainer* rights can then add you as a *developer* via this page:

Code of conduct

If using that, please prefix branches with your username, and be nice. Don't overwrite the work of others.

In return you get a full CI run using Samba Team provided resources running thanks to a credit in Rackspace's cloud. That in turn makes it easier for Samba Team members doing Code Review as your patches will work first time, and they can see proof of that.

CI Results

A CI run is triggered after every push. This makes finding issues early easy.

CI results are here: Pipelines

CI for personal GitLab forks

Instructions how to run CI with your own GitLab runner can be found here: CI using Your own gitlab runner.

This is helpful if you do not wish to share the repository with others (you have your own fork on gitlab). However it requires your own build resources.