Nice to hear! I never used eastwood before so I didn’t have an answer. It’s good that we have an answer now!

Indeed :source-paths are inferred, and therefore best left unconfigured: https://github.com/jonase/eastwood/tree/a983a04045ac9e0c4540693eade5a2e47193fc3c#depsedn @U2BDZ9JG3 what would be a great place to document Eastwood+Poly setup? Can contribute words or a PR

I guess the best is to add it to this page: https://app.gitbook.com/o/-LAhrWK-mSHRqiTNUTDP/s/-Mj2L4VeP3frziYOoQWC/architecture/development However, I’m not sure if you can suggest edits to that page right away. @U1G0HH87L Do you now if it’s possible to contribute gitbook?

Yes, it’s possible.

or I might just build it all in one go and use the release tag. Hmm. Going back to the hammock.

this is certainly an area I am interested in, currently migrating a project but its a single project at the moment but as soon as I start splitting knowing how to build and deploy individual projects using github actions will be on my radar, so will keep an eye on any replies anyone got an example github action by any chance ?

@UU67HFS2X we are in the same boat. I am looking at setting up CI for a polylith repo with future multiple projects using github actions right now.

You can do in both ways. Either you can have a single stable tag and only deploy changed projects since the last stable tag, or you can create a tag for each project and use it. Polylith repository uses the first approach, a single release tag, where we tag once but only deploy the changed projects. You can have a look at Polylith’s own https://github.com/polyfy/polylith/blob/master/build.clj to see how its done. I noticed the CI & Deployment documentation is a little bit out of date. I updated it and you can see the updated version https://github.com/polyfy/polylith/blob/ci-and-deployment-update/doc/ci-and-deployment.md. This documents explains the CircleCI configuration that we have in the Polylith repo.

Thanks for adding some extra information, be handy when I get to that point 🙂

I made a simple git workflow on clojure-polylith-realworld-example-app project, for some reason "clojure -A:poly test :project" doesn't run any test, while the "check" command seem to work, will look on it abit later, but https://github.com/akotek/clojure-polylith-realworld-example-app/blob/master/.github/workflows/pull_request.yml might help you out @UU67HFS2X Run clojure -A:poly test :project WARNING: Implicit use of clojure.main with options is deprecated, use -M Execution time: 0 seconds

We run this command in CI:

clojure -M:poly test since:previous-build

If we were building and deploying applications separately, we'd probably tag separately too and narrow the test to just that tag and just that project (although I have not attempted that).

Trying this in github actions for some reason returns [] locally it seems to work for some reason which prevents me putting in a conditional 😕

clojure -M:poly ws get:changes:changed-or-affected-projects

@UU67HFS2X Since you're pulling fresh from GH, there will be no changed files: it will all look in sync with GH.

Adding since:previous-release argument should give the changes since the tagged point in git.

okay thanks for the tip 🙂