does anyone have a good tutorial for boot setup?

Best way to check if a resource has been updated & wether to run a task? Timestamp in an atom?

@cjhowe https://github.com/magomimmo/modern-cljs

@minikomi common pattern is to store the fileset of the previous invocation and compare files’ checksums

thanks!

@minikomi my mind goes to boot-sass as a potential example of doing this

thanks, will look it up boot -garden was a good example of tracking when namespaces change, using ns-tracker, but was trying to find a good resources-change example.

https://github.com/boot-clj/boot/wiki/Running-Boot-on-CI-systems#circleci-v2 mentions that the "inotify watch limits" are solved. However I'm still seeing them occasionally. I'm optimistically hoping I'm doing something wrong I have tweaked the template slightly). Any suggestions?

@juhoteperi looks like you wrote the v2 info.

I have not seen any inotify problems with that configuration

Hmm, odd. Something to keep an eye on I guess... it seems to happen sporadically. So it could be something else. j/w, but did you need to add apk update && apk add git openssh to get circleci to quit complaining about checkout?

no

Cljsjs is using debian base instead of alpine (so no apk)

Cljsjs has already ran at least hundreds of builds with new configuration and previously every 25 build or something like that failed due to inotify limit

ah, okay. I started from the example verbatim.

You can try clojure:boot-2.7.1 instead of clojure:boot-2.7.1-alpine

I'm running alpine version in Jenkins but Git checkout is running outside of docker container there

makes sense that the debian image would have git/ssh already, and alpine would definitely not.

I'll take a look at using the debian image, see if that helps at all.

Hmm yes, perhaps it will be good idea to change the example as in CircleCI one always wants to have git available

https://github.com/docker-library/openjdk/blob/415b0cc42d91ef5d70597d8a24d942967728242b/8-jdk/Dockerfile#L7 https://github.com/docker-library/openjdk/blob/415b0cc42d91ef5d70597d8a24d942967728242b/8-jdk/alpine/Dockerfile#L7 No Git ot anything available: https://hub.docker.com/_/alpine/

I mean, apk update && apk add git openssh works. Is the lightness worth the extra line in config (and does it offset the cost?)

No, using existing image, even if larger, is probably faster than having to install new software

Debian image is anyway cached at Circle servers

yeah, I was just checking if they cached the image.

is there a way to run boot tasks in parallel?

I think there's something called multiboot hanging around somewhere. Might be lying though.

https://github.com/boot-clj/boot/blob/master/boot/core/src/boot/parallel.clj @plexus might be useful?

yes, seems runcommands is what I was looking for

That is to commands parallel, not tasks

good enough for what I need I think, we're trying to run two watch tasks without having to start two jvm processes

Or well, tasks, but you have to provide tasks as strings... I don't see what is the reason behind that

apparently because it runs boot-in-boot, i.e. in a separate pod (I'm just saying words here that I read somewhere ;))

Ah true.

I remember writting parallel higher order function, which runs given task functions parallel, but I'm not sure where that is.

You can always "cheat" and use (future (boot …)) right?

It depends, if you want single fileset and pipeline, then no

oh neat, runcommands works on the existing fileset. I expected it to run on a new one for some reason.

so apparently somewhere here had already tried runcommands, and it crashed the JVM due to concurrent modifications in boot's tmp directories

giving this a try

(deftask multi-task []
  (let [tasks [(future (boot (...)))
               (future (boot (...)))]]
    (run! deref tasks)))

Tasks should return the middleware function.

But you can just declare multi-task as normal function instead of task

yes @plexus runcommands is the way to run tasks in parallel, but of course that does not protect from concurrency issues

so you have to implement your own locking/compare and swap if some resource is shared

Is there a way to safely cache ClojureScript compilation results in CI, so that the next time CI runs, it happens faster?