The downvotes on your previous comment are probably because it is misplaced/out-of-context to the message you replied to. Yes containerizing builds builds makes sense, especially outside the java world, but has nothing to do with the complaints about missing built-in artifact store for CI jobs that you replied to. A containerized build would have to publish the artifact somewhere too.

E.g. in a jenkins setup one could have a build run on every commit, that creates an artifact that a downstream job can use, possibly pulling in other artifacts from other jobs as well, e.g. to run integration tests and only at the end of the pipeline would one want to publish the artifact to regular places, e.g. maven nexus or S3.