Reading this blog post truly made my day! It’s so cool that the vision I had for Polylith, also works in practice! So thanks @U04V70XH6 for sharing this to the community!

And works at scale!

I should send you an updated ws.edn file. I'll try to remember next week when I'm back at work.

I totally agree with Joakim! It made my day :dancer:

Awesome blog post

Nice one!

poly test :dev :all will run all the tests, in the context of the development project.

Tests are always run in the context of a project -- either development or one of the projects.

By default, it runs only from the non-`development` projects, so if there are no projects, it won't run any tests. That's why you need to specify :dev to trigger development project testing.

HTH @U028BUU1P3R

(your :dev alias has dependencies on all five components yes?)

poly test :dev :all doesn't seem to find anything to run, so maybe not? I've got all the bricks' src and resources directories specified as :dev extra-paths in the workspace deps.edn, is there another way to depend on them?

The test paths are under the :test alias.

Ah, you have paths not deps and :local/root? Are you using Cursive?

I'm using emacs, but hopefully once this is working I can share it with coworkers who do use Cursive.

You may need :all-bricks in addition to what I posted.

poly test :dev :all :all-bricks should do it.

I'm sorry you have to use the paths approach, that's a pain 😞

I know, I'm rooting for cursive to catch up, the local/root way seems much nicer : )

And that worked, thanks 👍

The :local/root deps approach saves you from duplicating all the bricks' library deps into the :dev alias. That can get to be a real issue as your project grows. Pester the #C0744GXCJ folks about it 🙂

I'm now subscribed to https://github.com/cursive-ide/cursive/issues/2554, it looks like there's a potential solution that just hasn't risen high enough on the priority queue yet

The last Sean article has an example of how to do that: https://corfield.org/blog/2022/12/07/deps-edn-monorepo-10/, I think it is in the end of the article.

I recommend using babashka for finding out which projects has changed and https://github.com/GoogleContainerTools/jib to build the images. Use that combo previously and it was great

thanks both for the feedback. will look into that

don't see a lot of benefits for jib in our case. will keep an eye out for the future.

@U05094X3J: I saw the changed-projects fn and looks like it is what I was looking for. Will try it out, thanks again