This is an example of a golang-based monorepo. It has the following features:
- Only build the services or cmds that are modified in a commit;
- Build all services and/or cmds that are affected by changes in common codes (i.e.
- Build all services and/or cmds that are affected by changes in
At the moment, CI is setup to use Go 1.14[.x] with
GOFLAGS=-mod=vendor environment variables enabled during build. See sample dockerfile for more details.
How does it work
During CircleCI builds, build.sh iterates the updated files within the commit range (
CIRCLE_COMPARE_URL environment variable in CircleCI) or the modified files within a single commit (when the value is not a valid range), excluding hidden files,
vendor folders. It will then try to walk up the directory path until it can find a Makefile (excluding root Makefile). Once found, the root Makefile will include that Makefile and call the
custom rule as target, thus, initiating the build.
When the changes belong to either
vendor, the script will then try to determine the services (and cmds) that have dependencies using the
go list command. All dependent services will then be built using the same process described above.
services/- Basically, long running services.
cmd/- CLI-based tools that are not long running.
pkg/- Shared codes, or libraries common across the repo.
vendor/- Third party codes from different vendors.
Although we have this structure, there is no limitation into where should you put your services/cmds. Any subdirectory structure is fine as long as a Makefile is provided.
How to add a service/cmd
A reference template named samplesvc is provided. Basically, these are the things that you need to do:
- Create a new directory for your service under
services/or tool under
cmd/. You may copy the samplesvc contents to your new directory.
- Update the dockerfile inside your new service directory. Note that during build, this dockerfile is copied to the root directory (to be able to access
- Update the Makefile with your own values. You need to at least update the
MODULEvariable with your service name. The only required rule is the
custompart so you may need to change that as well (i.e. name of the dockerfile used in
- [Optional] Update the deploy.sh script for your deployment needs.
PR's are welcome!
- Make it work without the
vendorfolder as well