From: "Anibal Limon" <anibal.limon@linaro.org>
To: kernelci@groups.io, info <info@kernelci.org>, milo@milo.name
Cc: Nicolas Dechesne <nicolas.dechesne@linaro.org>,
Anmar Oueja <anmar.oueja@linaro.org>,
Fathi Boudra <fathi.boudra@linaro.org>
Subject: Re: [kernelci] KernelCI API Auth Token
Date: Wed, 3 Oct 2018 11:16:01 -0500 [thread overview]
Message-ID: <CA+_AqivuXXgsHCNRn0mz752dojic61pLt--3pUL7bC3AnNDZdA@mail.gmail.com> (raw)
In-Reply-To: <CAJrz+7+WWpkhFasJwqUsrN+h4eyMenNwg28t18cuNt1ssLzzog@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 700 bytes --]
+ Milo
+ info at kernelci.org
On Wed, 3 Oct 2018 at 03:13, Milosz Wasilewski <milosz.wasilewski@linaro.org>
wrote:
> On Wed, 3 Oct 2018 at 01:37, Anibal Limon <anibal.limon@linaro.org> wrote:
> >
> > Hi,
> >
> > I want to access the KernelCI API to get information about the QCOMLT
> builds, I have a couple of questions,
> >
> > What is the process to get a KernelCI API auth token?
>
> I guess asking the ML is a good start. Back in the days when Milo was
> working on the code I got one directly from him. I'm not sure who is
> generating tokens these days.
>
> milosz
>
> >
> > Fathi, Anmar,
> > Do we have a KernelCI auth token available on LinaroCI?
> >
> > Regards,
> > Anibal
> >
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 1185 bytes --]
next prev parent reply other threads:[~2018-10-03 16:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 18:46 KernelCI API Auth Token anibal.limon
2018-10-02 18:54 ` Fathi Boudra
2018-10-03 8:13 ` [kernelci] " Milosz Wasilewski
2018-10-03 16:16 ` Anibal Limon [this message]
2018-10-16 20:29 ` Guillaume Tucker
2018-10-16 20:31 ` Anibal Limon
2018-10-23 15:44 ` Anibal Limon
2018-10-23 16:01 ` Guillaume Tucker
2018-10-23 16:57 ` Anibal Limon
2018-10-30 5:21 ` Guillaume Tucker
2018-10-30 5:45 ` Nicolas Dechesne
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=CA+_AqivuXXgsHCNRn0mz752dojic61pLt--3pUL7bC3AnNDZdA@mail.gmail.com \
--to=anibal.limon@linaro.org \
--cc=anmar.oueja@linaro.org \
--cc=fathi.boudra@linaro.org \
--cc=info@kernelci.org \
--cc=kernelci@groups.io \
--cc=milo@milo.name \
--cc=nicolas.dechesne@linaro.org \
/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.
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.