3 ms·

There's easy transparency amongst multiple teams, without having accounts for the other teams on CircleCI or Jenkins. This is while the deploy is in flight, and

There's easy transparency amongst multiple teams, without having accounts for the other teams on CircleCI or Jenkins. This is while the deploy is in flight, and it can provide timestamped logs if there's an incident, and it could be useful for tracking history. It's also clear who kicked off the deploy.

cutemonster 6y ago
How do you configure who may deploy what, without having user accounts / groups in Jenkins / circleCI? Maybe those who can post to your deployment slack channel, can deploy? So you configure who-may-deploy via permissions in Slack instead?