Hi Evans Ye :
I am not sure what you are trying to accomplish:
Is it that you like to save the image after a build ? Than all the files in .m2/repository and are already there and rebuild will not download all the software artifacts again?
In other words: Do you want to offer a full snapshot ready for bigtop-deploy to the world, where almost everything from source, dependencies to bigtop packages is contained within ?
And extending the idea ... creating a docker image with everything contained with only one gradle call.
- Building the bigtop-slave image (maybe pushing to dockerhub)
- Running the docker run "gradle apt/yum" command on the created image
- saving the result as bigtop-all and pushing to dockerhub
That may be nice for students.
I am not sure if I like it. Let me think about it.
If I misunderstood you, please elaborate in more detail.