From: Ted Zlatanov <tzz@lifelogs.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: EMBA (Emacs Gitlab CI build server) is now available
Date: Mon, 31 Dec 2018 18:05:30 +0000 [thread overview]
Message-ID: <wonpk1w5.fsf@lifelogs.com> (raw)
In-Reply-To: <8736qdbn0k.fsf@gmx.de> (Michael Albinus's message of "Mon, 31 Dec 2018 18:54:03 +0100")
On Mon, 31 Dec 2018 18:54:03 +0100 Michael Albinus <michael.albinus@gmx.de> wrote:
>> You can access EMBA at https://emba.gnu.org
>>
>> It will build Emacs commits on some pre-defined branches like master and
>> emacs-26.
>>
>> If you need a signup invite, please contact me (for now).
MA> Looks like I need an account. But why is it password based? I'd prefer a
MA> public key, or a certificate.
Gitlab, the software EMBA uses, supports passwords and 2FA. I don't know
if it supports others.
MA> I also believe, that account-free access shall be possible to check test
MA> run results.
I agree, but I don't think the server is ready for full public access.
I've allowed your signup, at least for now.
Ted
next prev parent reply other threads:[~2018-12-31 18:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-31 16:29 EMBA (Emacs Gitlab CI build server) is now available Ted Zlatanov
2018-12-31 17:54 ` Michael Albinus
2018-12-31 18:05 ` Ted Zlatanov [this message]
2019-01-01 12:08 ` Michael Albinus
2019-01-01 14:56 ` Ted Zlatanov
2019-01-01 16:51 ` Michael Albinus
2019-01-02 15:05 ` Justin Joseph Kaipada
2019-01-02 15:17 ` Michael Albinus
2019-01-04 11:52 ` Michael Albinus
2019-01-05 8:01 ` Toon Claes
2019-01-30 8:53 ` EMBA (Emacs Gitlab CI build server) is now *public* available Toon Claes
2019-01-30 9:46 ` Robert Pluim
2019-01-30 10:00 ` Michael Albinus
2019-01-30 11:23 ` Toon Claes
2019-01-30 12:13 ` Michael Albinus
2019-01-30 20:39 ` Ted Zlatanov
2019-02-05 12:50 ` Robert Pluim
2019-02-05 12:55 ` Michael Albinus
2019-02-05 14:58 ` Robert Pluim
2019-02-05 15:42 ` Ted Zlatanov
2019-02-05 15:50 ` Robert Pluim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=wonpk1w5.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.