I'm trying to get a clearer picture of what level of ownership Java developers have over Docker and the deployment processes within their projects. Specifically, I'm interested in whether developers are responsible for writing and maintaining Dockerfiles, managing scripts that build and push Docker images, and creating deployment scripts (like Terraform, Bash, or GitHub Actions). Also, is working with these tools generally a smooth experience, or are there often issues like flakiness with Docker or CI systems? I'd love to hear how responsibilities are divided today, and whether Java developers wish to have more control over these workflows.
2 Answers
I believe development teams should take charge of how their applications are packaged. It’s crucial for us to externalize our configuration, ensuring we can read from environment variables and config files. Teams should generally manage deployment responsibilities themselves, with DevOps providing supporting tools to make this easier. Yes, there’s a learning curve, but with consistent Docker image production practices, deploying can be straightforward for everyone.
Absolutely! Developers know best what their apps need, so writing and maintaining Dockerfiles is essential. In our team, we create our pipeline scripts in GitLab CI, and while occasionally we run into external issues, overall, Docker and CI tools have been reliable. It's beneficial when development teams take ownership as it fosters better responsibility across the board.
Yes, I think that’s a common sentiment. Many devs shy away from engaging with tools like Terraform because they are more focused on application needs. However, being involved even partially helps solidify understanding and ownership.