Source: medium.com
Containerize your DevOps WorkflowCategory: Software, Business, Microsoft, Kubernetes, Docker, Infrastructure, Jenkins, containerization, github, automation, artificial-intelligence
The developer saying “Its works on my machine” no longer valid with the arrival of the container and the Docker technology. The real world shipping container’s owner considers it content and not about how it going to ship to the right destination.
And also use of container provide the path to the developer and IT team to work more closely and collaborate, unlike traditional DevOps process.
Main change in the conventional DevOps workflow when adopting Docker technology is it delivers from build to Docker environments (Production, Staging and QA) Docker image instead of the source code package and integration of the Docker registry (Azure Container Registry, Docker Hub, private Docker Trusted Registry or any other Docker registry) to the DevOps workflow.
From the starting step of the DevOps workflow, Docker technology and container do their involvement till to the last step.
And also use of container provide the path to the developer and IT team to work more closely and collaborate, unlike traditional DevOps process.
Main change in the conventional DevOps workflow when adopting Docker technology is it delivers from build to Docker environments (Production, Staging and QA) Docker image instead of the source code package and integration of the Docker registry (Azure Container Registry, Docker Hub, private Docker Trusted Registry or any other Docker registry) to the DevOps workflow.
From the starting step of the DevOps workflow, Docker technology and container do their involvement till to the last step.
Related Articles
Community Partners
DevOps Careers