Code Manager Setup/Environments

asked 2017-06-20 16:49:01 -0600

nwilkerson gravatar image

We currently manually promote code through environments each user has his own dev environment that he can pull test branches to. See below: Production Staging devuser1 devuser2

Its my understanding that Code manager will remove these and recreate an environment for every branch. Is this correct? Is there a way to restrict what branches it creates environments on? Is there a way to protect environments from being deleted?

Is there a way to integrate some automated testing to the Code Manager so that dev is automatically merged into staging if tests are passed?

-Nathan

edit retag flag offensive close merge delete