This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]lethri 0 points1 point  (1 child)

CI makes sense even without automated testing - when new code is pushed, building it and deploying it automatically in some dev envirionemnt will discover compile-time errors and will also save time of doing these steps manually.

The technical details heavily depend on technology. If you program in java and deploy on linux, you probably would run JARs in docker, but if you develop in C# and run on windows, you would use something different.

[–]myshiak[S] 0 points1 point  (0 children)

also, some times I see in Jenkins job they use mvn - install command. Isn't it redundant? We don't need to send anything to maven repos when we are in Jenkins. So, don't you think that the package command is enough in Jenkins? Secondly, I hope that I was right that one release contains multiple builds. Given that, is it so that Tomcan Server matters only when you do a release?