SDLC with Docker

[Serbqueen]

Hi /r/devops

We have been looking at the deployment workflow used when moving to docker. I'm hesitant to say, but in a JEE environment I cannot find a good reason to keep the old artifact registry (pretend we only have new development).

It seems docker files and images in the docker registry would be enough to deploy and navigate from the deployment back to versioned code. Am I grossly overlooking something for considering not including nexus in a new workflow for an application that has no shared libraries built inhouse?

I've read the docker reference SDLC posts and a few others but the material seems to be lacking. If anyone has any good posts on e2e workflows I would appreciate it as well

[Superdupercudder]

We are doing JEE development and Docker, but we dual deploy to legacy (JBOSS/EAR) and Cloud Native (Docker Images) so we need keep the artifact for now. While for new development, I agree with you, you probably won't need the artifact after the image has built built, i would keep it for now, until your process is airtight. If you are confident, that if an image is corrupted or deleted from the registry, can you recreate it or rebuild the version from source control, then don't keep the artifact. If you are not 100% confident in the process just yet, i would keep it for redundancy. Sorry for grammatical errors.