Age | Commit message (Collapse) | Author |
|
Change-Id: I3a3342e8275db1d841e284a8881c3e201e4adcce
|
|
Crowd access error should not be fatal, as even if Crowd is down, it makes
no sense to deny users e.g. globally configured read access. However, make
error message even more visible, and add warning letting know that Crowd
access controls are inactive.
Change-Id: Ie5beff6055a03d96bf8a751079b54ff985db6aaf
|
|
https://bugs.linaro.org/show_bug.cgi?id=1692 reports an incident when SSH'ing
via gitolite user produced "Non-successful response from Crowd." message, and
it wasn't at all clear what component produced it. Make it obvious now.
Change-Id: Ic9dfb1941e557bfb13bf579f379887a8ff5b76f7
|
|
Andy wins
Change-Id: Ic3329d4c71c63cdc53860b4d44f79a1c13d8ce3b
|
|
Current state causes a cron email every time the script is run even when
it does nothing at all. Irritating :)
Change-Id: I4d8dbb7f55a4bb14c0f9e7dd476b1547625ddda5
|
|
Wrapper for the python LDAP library which uses config from local ldap.conf
or override LDAP_CONF in the environment
Command line credentials are now ignored.
grok-slave-keys:
use the linaro_ldap library to greatly simplify the script
gitolite-tools/gitolite-keys:
use the linaro_ldap library, remove logging and config parsing for
simplicity
Change-Id: I002efbc1f7d47d3120855038aa1c5cc3d8292c98
|
|
https://git.linaro.org/infrastructure/gitolite-tools.git
Change-Id: I0fb00522af449da5ed7950d4d286e15b4ed20c08
|