« first day (4951 days earlier)      last day (54 days later) » 

1:16 AM
I red that "benefits of using containers in your CI/CD pipeline include deploying applications easily to multiple operating systems and hardware platforms, deploying multiple versions of an application at the same time without interfering with one another, and creating a more reliable way to work with applications at any stage in the pipeline process."
Just to be clear, these are some of the benefits that may arise from using a CI/CD pipeline. For example someone could still be using a CI/CD pipeline even if there weren't using containers and were only concerned with one version and one operating system. Is this right, or am I misunderstanding?
 
 
12 hours later…
12:57 PM
That's correct. Containers in a CI/CD pipeline are an added benefit, not a strict requirement. You can certainly have a CI/CD workflow that doesn't utilize containerization, perhaps because it's not deemed necessary for the project's scale or complexity. CI/CD is really about continuous integration and continuous delivery or deployment. Containers are just a tool that can help make some aspects of CI/CD easier or more efficient, particularly when dealing with multiple environments or ...
versions, as you mentioned. But, like any tool, it's not always the right fit for every job. Some setups might be just fine with a simpler approach or have other means of managing different versions and operating systems. Don't just jump on the container bandwagon without considering if it's the best option for your specific needs.
 

« first day (4951 days earlier)      last day (54 days later) »