Re: Gitlab merge requests
ср, 15 янв. 2020 г., 12:03 Tim Rühsen : > On 1/15/20 9:24 AM, Nikos Mavrogiannopoulos wrote: > > On Wed, Jan 15, 2020 at 7:18 AM Niels Möller > wrote: > > > >>> If they are you should be able to see them in Settings -> CI/CD -> > Runners. > >> > >> I've now had a look. There's a section for "Group runners", which is > >> empty. No mention of "shared runners". There's a link to "Install a > >> GitLab runner" (with various kinds of binaries, no mention of sources), > >> and a big button "Install Runner on Kubernetes". > > > > So there aren't any :) > > Niels, since you set up your own instance of Gitlab, you can't access > the Gitlab.com runners (it's a free service for customers only). > > So you can set up your own "machines" (bare metal, vm or container) and > install [1] on them. This gives you runners for your own CI - every > merge request and every push will automatically be built and tested. > Another option would be to switch to gitlab.com (and use free CI runners) and use git.lysator.liu.se as a backup/mirror. ___ nettle-bugs mailing list nettle-bugs@lists.lysator.liu.se http://lists.lysator.liu.se/mailman/listinfo/nettle-bugs
Re: Gitlab merge requests
On 1/15/20 9:24 AM, Nikos Mavrogiannopoulos wrote: > On Wed, Jan 15, 2020 at 7:18 AM Niels Möller wrote: > >>> If they are you should be able to see them in Settings -> CI/CD -> Runners. >> >> I've now had a look. There's a section for "Group runners", which is >> empty. No mention of "shared runners". There's a link to "Install a >> GitLab runner" (with various kinds of binaries, no mention of sources), >> and a big button "Install Runner on Kubernetes". > > So there aren't any :) Niels, since you set up your own instance of Gitlab, you can't access the Gitlab.com runners (it's a free service for customers only). So you can set up your own "machines" (bare metal, vm or container) and install [1] on them. This gives you runners for your own CI - every merge request and every push will automatically be built and tested. Sorry that I am not into the details, thus can't give you detailed instructions. [1] https://docs.gitlab.com/runner/install/ Regards, Tim signature.asc Description: OpenPGP digital signature ___ nettle-bugs mailing list nettle-bugs@lists.lysator.liu.se http://lists.lysator.liu.se/mailman/listinfo/nettle-bugs
Re: Gitlab merge requests
On Wed, Jan 15, 2020 at 7:18 AM Niels Möller wrote: > > If they are you should be able to see them in Settings -> CI/CD -> Runners. > > I've now had a look. There's a section for "Group runners", which is > empty. No mention of "shared runners". There's a link to "Install a > GitLab runner" (with various kinds of binaries, no mention of sources), > and a big button "Install Runner on Kubernetes". So there aren't any :) ___ nettle-bugs mailing list nettle-bugs@lists.lysator.liu.se http://lists.lysator.liu.se/mailman/listinfo/nettle-bugs
Re: Gitlab merge requests
Nikos Mavrogiannopoulos writes: > On Tue, Jan 14, 2020 at 1:26 PM Niels Möller wrote: >> >> Nikos Mavrogiannopoulos writes: >> >> > That's great. Does git.lysator.liu.se support shared runners for CI? >> >> I'm not sure what "shared runners" mean. I'm not aware of any nearby >> machines running ci jobs for git.lysator.liu.se. > > If they are you should be able to see them in Settings -> CI/CD -> Runners. I've now had a look. There's a section for "Group runners", which is empty. No mention of "shared runners". There's a link to "Install a GitLab runner" (with various kinds of binaries, no mention of sources), and a big button "Install Runner on Kubernetes". Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid 368C6677. Internet email is subject to wholesale government surveillance. ___ nettle-bugs mailing list nettle-bugs@lists.lysator.liu.se http://lists.lysator.liu.se/mailman/listinfo/nettle-bugs
Re: Gitlab merge requests
On Tue, Jan 14, 2020 at 1:26 PM Niels Möller wrote: > > Nikos Mavrogiannopoulos writes: > > > That's great. Does git.lysator.liu.se support shared runners for CI? > > I'm not sure what "shared runners" mean. I'm not aware of any nearby > machines running ci jobs for git.lysator.liu.se. If they are you should be able to see them in Settings -> CI/CD -> Runners. > And the machines > running ci jobs for the gitlab mirror, do they belong to gitlab, or > have you set them up? The runners are from gitlab.com. regards, Nikos ___ nettle-bugs mailing list nettle-bugs@lists.lysator.liu.se http://lists.lysator.liu.se/mailman/listinfo/nettle-bugs
Re: Gitlab merge requests
Nikos Mavrogiannopoulos writes: > That's great. Does git.lysator.liu.se support shared runners for CI? I'm not sure what "shared runners" mean. I'm not aware of any nearby machines running ci jobs for git.lysator.liu.se. And the machines running ci jobs for the gitlab mirror, do they belong to gitlab, or have you set them up? Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid 368C6677. Internet email is subject to wholesale government surveillance. ___ nettle-bugs mailing list nettle-bugs@lists.lysator.liu.se http://lists.lysator.liu.se/mailman/listinfo/nettle-bugs
Re: Gitlab merge requests
That's great. Does git.lysator.liu.se support shared runners for CI? That will allow checking the MR status on CI, and eliminate the need for mirroring in gitlab and running the CI there. regards, Nikos On Sat, Jan 11, 2020 at 10:20 AM Niels Möller wrote: > > Hi, > > After some off-list discussions and encouragement, I've reenabled the > "merge request" feature on git.lysator.liu.se/nettle. > > I don't know yet precisely how I will want to use it, but feel free to > create merge requests if you think that helps us keep track of ongoing > work. For the time being, please also write to the mailinglist whenever > some action is done or desired on a merge request. > > I intend the mailinglist to remain the main forum for discussing new > features and implementation choices, while detailed patch review might > gradually move to the web interface. > > Advice on how to use and configure gitlab is welcome. > > Regards, > /Niels > > -- > Niels Möller. PGP-encrypted email is preferred. Keyid 368C6677. > Internet email is subject to wholesale government surveillance. > > ___ > nettle-bugs mailing list > nettle-bugs@lists.lysator.liu.se > http://lists.lysator.liu.se/mailman/listinfo/nettle-bugs ___ nettle-bugs mailing list nettle-bugs@lists.lysator.liu.se http://lists.lysator.liu.se/mailman/listinfo/nettle-bugs
Re: Gitlab merge requests
Dmitry Eremin-Solenikov writes: > I've tried registering with @gmai.com address. > I've received "Email is not from an allowed domain." error during > registration. I asked the sysadm. gmail had been put on the signup blacklist, because up to now it was used only by a few hundred spam accounts. Should be fixed now. Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid 368C6677. Internet email is subject to wholesale government surveillance. ___ nettle-bugs mailing list nettle-bugs@lists.lysator.liu.se http://lists.lysator.liu.se/mailman/listinfo/nettle-bugs
Re: Gitlab merge requests
Hello, сб, 11 янв. 2020 г. в 12:20, Niels Möller : > > Hi, > > After some off-list discussions and encouragement, I've reenabled the > "merge request" feature on git.lysator.liu.se/nettle. Great! > I don't know yet precisely how I will want to use it, but feel free to > create merge requests if you think that helps us keep track of ongoing > work. For the time being, please also write to the mailinglist whenever > some action is done or desired on a merge request. > > I intend the mailinglist to remain the main forum for discussing new > features and implementation choices, while detailed patch review might > gradually move to the web interface. Great idea, let's try it! > Advice on how to use and configure gitlab is welcome. I've tried registering with @gmai.com address. I've received "Email is not from an allowed domain." error during registration. -- With best wishes Dmitry ___ nettle-bugs mailing list nettle-bugs@lists.lysator.liu.se http://lists.lysator.liu.se/mailman/listinfo/nettle-bugs
