3 ms·

Looks interesting, * I use one namespace per env (staging, prod, etc), is this supported or must I go with the default (slightly wacky) staging and prod releas

Looks interesting, * I use one namespace per env (staging, prod, etc), is this supported or must I go with the default (slightly wacky) staging and prod releases side-by-side in the same namespace? * How are bugfix releases handled? If I pushed 1.2.0 to staging, and want to hotfix the prod release 1.1.0 with 1.1.1 (a common bugfix flow), can I promote releases from the hotfix branch? * Is there a permission model? Does it bottom out to GitHub permissions for each env repository? E.g. can I have a smaller set of users approved to promote releases to production?

jstrachan 9y ago
Each environment is in a separate namespaces. You can add/edit/delete the Environments to use whatever namespaces you wish to use. Promotion is either automatic or manual. By default Staging is automatic and production is manual. You can manually promote any version to any environment whenever you wish: http://jenkins-x.io/developing/promote/ http://jenkins-x.io/developing/promote/ For promotions we're delegating to the git repository for RBAC; so you can setup whatever roles you want for who is allowed to approve promotions & if you need code reviews etc