Fork me on GitHub
Chris Rosengren00:12:57

Ahh nevermind, it looks like having a hardcoded {:source-paths } stopped it scanning directories

👍 3

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: @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: 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.


Questions regarding CI, just want to verify I have understood things correctly 🙂. Let's say I would have 3 projects:

["invoicer" "myproject1" "myproject2"]
when running the tool, myproject1 and invoicer has changed and needs to be built. When it comes to CI - when the build completes for each project I create a new tag per project? git tag invoicer-XXX git tag myproject1-XXX


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 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 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 🙂

Aviv Kotek14:12:08

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 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
But we run CI for our entire monorepo, not just for specific subprojects, and so after each successful build, we force update the previous-build tag. I was sort of following Polylith's lead there because we generally want all updated apps to be deployed together across our cluster.

polylith 1

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 🙂

👍 1

So something I am not sure about, I have created a project which fails with file not found, I believe this is because it con not find a resource in one of the components should the resources be available to a project ? as we don't add paths to a project deps.edn file ? or should adding the component in the deps: key solve this ? Scratch that silly mistake, had -M in the :main-opts key so it was building -M -M and causing the error, thanks duckie

duckie 3