If your CI or your user in our maven repo stopped working, there’s a reasonable explanation.
We recently had a credentials leak there. As we have so many users there by now, it’s a little bit hard to keep track of things.
I disabled all the users that weren’t obvious why access is needed.
I did two things on each user:
- disabled UI access
- removed permissions
I will send an email for each one.
If you are affected your CI stopped working, please tell us here and the access will be immediately reenabled (but CI users won’t have UI access to jfrog). As releases should be done by CI, this is a must.
If you believe you have any reason to need personal permissions to certain repositories (and you are /dev/4 or /dev/5) just raise your hand, tell the repo and the reason, and it will be readily reenabled.
If you are not a /dev/4 and you need access, I will need a much better explanation why your release cannot be done via CI.