On Mon, 30 May 2011 10:40:00 +0200, Zygmunt Krynicki
wrote:
> > So we need a way of storing tokens. The easiest thing to do would be to
> > store a token for a (username, host) pair, so you'd run a command like:
>
> IMHO that should be python-keyring. Let's not reinvent .netrc again.
Sure. I
On Mon, 30 May 2011 17:30:53 +0200, Zygmunt Krynicki
wrote:
> W dniu 30.05.2011 16:35, Christian Robottom Reis pisze:
>
> > Storing a default (on first use, maybe?) seems sensible:
> >
> > lava-tool submit-job --farm $myfarm
> > Storing https://mwhud...@validation.linaro.org in ~/.lava
W dniu 30.05.2011 19:04, Alexander Sack pisze:
I prefer the ability to explicitly register shortnames for farms like
I proposed further above.
We can also have a shortname "default" or so that would be used if you
don't provide a --farm short-name ;).
+1
Was there any argument against havi
On Mon, May 30, 2011 at 07:04:46PM +0200, Alexander Sack wrote:
> I prefer the ability to explicitly register shortnames for farms like
> I proposed further above.
What does this give you that shell aliases don't? If nothing but
convenience, then it's probably just a nice-to-have.
--
Christian Ro
On Mon, May 30, 2011 at 4:35 PM, Christian Robottom Reis
wrote:
> On Mon, May 30, 2011 at 10:40:00AM +0200, Zygmunt Krynicki wrote:
>> $ lava-tool submit-job --farm https://mwhud...@validation.linaro.org
>> test.json --token
>> Token for mwhud...@validation.linaro.org: ***
>>
>> >So we nee
On Mon, May 30, 2011 at 05:30:53PM +0200, Zygmunt Krynicki wrote:
> > lava-tool submit-job --farm $myfarm
> > Storing https://mwhud...@validation.linaro.org in ~/.lava/default
>
> You obviously meant to say:
>
> Storing https://mwhud...@validation.linaro.org in
> ~/.config/lava/settings.c
W dniu 30.05.2011 16:35, Christian Robottom Reis pisze:
Storing a default (on first use, maybe?) seems sensible:
lava-tool submit-job --farm $myfarm
Storing https://mwhud...@validation.linaro.org in ~/.lava/default
You obviously meant to say:
Storing https://mwhud...@validation.lin
On Mon, May 30, 2011 at 10:40:00AM +0200, Zygmunt Krynicki wrote:
> $ lava-tool submit-job --farm https://mwhud...@validation.linaro.org
> test.json --token
> Token for mwhud...@validation.linaro.org: ***
>
> >So we need a way of storing tokens. The easiest thing to do would be to
> >stor
W dniu 30.05.2011 06:54, Michael Hudson-Doyle pisze:
Hi all,
$ lava-tool submit-job --farm https://mwhudson:$to...@validation.linaro.org
test.json
This could then remember, bzr style, that it's is the farm you want to
talk to. Unlike bzr the knowledge would be global (per user) so it would
On Mon, May 30, 2011 at 6:54 AM, Michael Hudson-Doyle
wrote:
> Hi all,
>
> I'm working on the infrastructure that will underlie the scheduler
> command line api. Â Zygmunt and I have the technical side understood I
> think, but what I want to think aloud about is how the command line
> should work
On Mon, May 30, 2011 at 11:57 AM, Paul Larson wrote:
> I think the long form of specifying the server is not terrible for now.
> After all, aliases would make it a non-issue anyway. Pulling from an
> environment variable should be simple, and iirc has already been done for
> lc-tool. I think it'
I think the long form of specifying the server is not terrible for now.
After all, aliases would make it a non-issue anyway. Pulling from an
environment variable should be simple, and iirc has already been done for
lc-tool. I think it's unlikely though, that one would commonly submit to
moreb tha
Hi all,
I'm working on the infrastructure that will underlie the scheduler
command line api. Zygmunt and I have the technical side understood I
think, but what I want to think aloud about is how the command line
should work for a user. In particular, I wonder how much state the
command line tool
13 matches
Mail list logo
