Sidehistorik
...
The environments from above is not the only ones, in many (large) setups we can have several others:
| System | Formål | Hvem kan deploye her | Purpose | Who can deploy here? | The good and bad stuffGode/dårlige ting | |||
|---|---|---|---|---|---|---|---|---|
| UAT | User Acceptance Test | Sysadmin (Evt. Developer ved DevOps)And/or Developer if DevOps is used) | A known/controlled environment - few and controlled changes that has be have been performed in Stage. | |||||
| integration | Speciel integrations tests, typically with 3rd party systems outside our control. Import/Export/Syncronising | Sysadmin (And/or Developer if DevOps is used) | A known/controlled environment - few and controlled changes that has be have been performed in Stage. | Kendt miljø under Change kontrol. Få eller ingen ændringer og skal til enhver tid matche Stage miljøet | integration | Test omkring integrationer med andre systemer, f.eks import/export/synkronisering | Sysadmin (Evt. Developer ved DevOps) | Kendt miljø under Change kontrol. Få eller ingen ændringer og skal til enhver tid matche Stage miljøet |
DevOps
DevOps og Continues Delivery koncepterne bryder lidt med den traditionelle Udvikler and Continues Delivery concepts extending the traditional concepts of the traditional Developer vs. Sysadmin tanke, idet at man ofte antager at Sysadmins blot kan deploye, mens udviklere ikke kan arbejde (overhovedet) i Stage eller Produktionsmiljøerthinking, where a common stage is that Sysadmins deploys, while Developers does not interact with Stage- or Production-environments.
Dette er ikke nødvendigvis koliderende tankegange, men man bør overvejer og implementere lidt anderledes regler og godkendelsesprocedurer, da jeg (belært af små 10 år på Sysadmin siden) må erkende:
...