commit 5d5e93f6e19fb6d0008f0722eb2e24e0197fb481
tree 1010b6776bb58f8cf629d1b3d18c515960002dc7
parent fc9a2c5a37ad31aabffa1d0e9d836d6dd00b3e28
author Christophe Lyon <christophe.lyon@linaro.org> 2023-10-05 14:51:43 +0000
committer Christophe Lyon <christophe.lyon@linaro.org> 2023-10-24 12:27:33 +0000

    tcwg-base/home-data/group: Rename tcwg-build group into tcwg-build-group
    
    This group is only used by the tcwg-build user, when we run precommit
    testing, which we want isolated from other processes as much as
    possible.
    
    However, having UID == GID and group name == user name for that user
    implies that its default umask is 002 instead of 022 for other
    users. This results in bogus regression reports when (bogus) tests
    depend on file permissions, where our baseline used 022 as umask and
    the precommit tests use 002.
    
    The simplest workaround seems to rename tcwg-build group.
    
    Another possibility would have been to give tcwg-buidslave (the user
    we use for most CI) its dedicated group (and thus behave the same as
    tcwg-build), but this would imply the tedious process of running chgrp
    on all machines.
    
    Change-Id: Ice589dc30abf357036d37425e327593b083193b6


:100644 100644 d65db79e2f7c0b23e79db6452e92602ca1bc7670 e4166dad9bd4349b9fc381f5f03599e8fd3c7795 M	tcwg-base/home-data/group
:100644 100644 ebf5ba194d87bfb0a653e2554abcf52ea161ff8b d5a95bf5e71b4416f36879f0bfb6d1b636ba98dc M	tcwg-base/home-data/tcwg-build/README