On Thu, Mar 1, 2018 at 2:41 PM, Martín Ferrari <tin...@tincho.org> wrote:
> On 01/03/18 07:58, Michael Stapelberg wrote: > > I’m assuming you have read https://pkg-go.alioth.debian.org/ci.html > > already. If not, start there. > > I had read it, but it was good to read it again. > > > Instead of sharing the knowledge only on mailing list posts, I would > > strongly prefer to extend ci.html such that it makes sense to everyone > > and is easily discoverable. > > > > Could you pose a few specific questions, which I’ll try to answer > > through updates of ci.html? Thanks! > > I think the problem is that I don't know anything about Gitlab and its > CI infrastructure.. My main questions would be: > Thanks for the feedback. Have a look at https://docs.gitlab.com/ce/ci/quick_start/README.html please (I’ll add the link to ci.html). > > * Where does all this run? > The runner we’re using is installed on a machine at my place. I assume that as salsa usage grows, more shared runners (run by DSA/the salsa team?) will become available, and we can just switch our workload over to them. For the time being, using our own runner is a nice way to not step on anyone’s toes and ensure our resource usage doesn’t hurt anyone else. IIUC, the current shared runners should only be used for GitLab pages and the like. > * How does it communicate with gitlab? > https://forum.gitlab.com/t/how-does-communicate-gitlab-runners/7553 > * What kind of control do we have over it? > Not sure I follow. Can you make this question more specific? > > Sorry for the very basic questions.. > > -- > Martín Ferrari (Tincho) > -- Best regards, Michael
_______________________________________________ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
