On 08/08/2014 11:54 PM, Ryan Hsu wrote:
> Thanks very much Anita. According to the Gerrit documentation [1], there is a
> command to set the http password for a given account. It does require
> administrator privileges though.
>
> set-account [--full-name ] [--active|--inactive] \
>
Thanks very much Anita. According to the Gerrit documentation [1], there is a
command to set the http password for a given account. It does require
administrator privileges though.
set-account [--full-name ] [--active|--inactive] \
[--add-email ] [--delete-email | ALL] \
On 08/06/2014 06:18 PM, Steven Kath wrote:
> Hello openstack-infra,
>
> Here at Brocade, we have a handful of Openstack Third-party CI service
> accounts.
>
> We recently had a personnel change and will need to do a refresh of our
> credentials (ex abundanti cautela). Presumably we'll need to g
On 08/08/2014 02:53 PM, jswar...@linux.vnet.ibm.com wrote:
>
> I'm unable to retrigger the turbo-hipster verification job on a change
> ("recheck migrations" comment retriggers Jenkins but not turbo-hipster)
> and I sent an e-mail to rc...@rcbops.com two days ago and still have not
> received a re
On 08/08/2014 11:57 AM, Ryan Hsu wrote:
> Hi All,
>
> Does anyone know if it’s possible to set up an http password for a 3rd party
> CI account? We are looking to use some of the Gerrit REST API operations that
> require authentication but according to this page [1], our account needs to
> have
Hi All,
Does anyone know if it’s possible to set up an http password for a 3rd party CI
account? We are looking to use some of the Gerrit REST API operations that
require authentication but according to this page [1], our account needs to
have a Gerrit http password set up. As far as I know, ou
On 08/08/2014 09:37 AM, Andreas Jaeger wrote:
> What kind of timeout do you mean? A timeout to reach the OpenStack
> infrastructure or a timeout in one of the tests?
Not sure. I think in the infrastructure.
> For the former, one low-tech solution would be to create a bug that you
> could referenc
On 08/08/2014 09:18 AM, Christian Berendt wrote:
> Does it makes sense to introduce a separate command to trigger rechecks
> caused by a timeout to be able to separate them? E.g. "recheck timeout".
What kind of timeout do you mean? A timeout to reach the OpenStack
infrastructure or a timeout in on
Does it makes sense to introduce a separate command to trigger rechecks
caused by a timeout to be able to separate them? E.g. "recheck timeout".
Christian.
--
Christian Berendt
Cloud Computing Solution Architect
Mail: bere...@b1-systems.de
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / htt
