3 ms·
They're addressing the lack of service accounts, targeted for 13.1: https://gitlab.com/gitlab-org/gitlab/-/issues/6883 https://gitlab.com/gitlab-org/gitlab/-/i
by rifelpet 6y ago
They're addressing the lack of service accounts, targeted for 13.1:
https://gitlab.com/gitlab-org/gitlab/-/issues/6883 https://gitlab.com/gitlab-org/gitlab/-/issues/6883
- sytse 6y agoYep, we want to charge only for people, not bots. Sorry it took a while to resolve this, it was complex.
- orf 6y agoI’m really glad you’ve reached this decision, but I’m still not happy with being asked “why are these automation tasks costing us $XXX” per year during our last recent license license update. Until this epic is completed you are charging people full-seat price for automation users which, because of the poorly-scoped token permissions, require multiple “user” accounts to implement securely. An automation utility in no way delivers the same value as a full time developer and it really shook me to know that this is how you have historically valued bots. It runs counter to everything that you publicise.