Executing a process in a directory always adds that directory to the fileset about boot-exec HOT 9 CLOSED

In your example you are using the current directory as the execution location for boot exec. This is where your error is, that directory should be a temporary location made with something like (tmp-dir!).

from boot-exec.

I understand, but there are some commands you have to run outside of a tempdir. For example, git commands must run in the repo root. It's what boot-semgit is doing e.g. here https://github.com/degree9/boot-semgit/blob/master/src/degree9/boot_semgit.clj#L16

So right now, using one of those git tasks adds your whole repo to the fileset. I could also report that as a bug in boot-semgit, but there's no way to fix it there without some change in boot-exec to make it not add-resource the current directory.

from boot-exec.

Try the version currently in master, i think this will need to be solved in semgit tho.

from boot-exec.

I was using 0.4.0, compared to that master only includes some readme-related commits, so I don't think that'll help.

Anyway, if this is intended behaviour I'll just write some tasks that use clj-jgit instead of exec'ing the binary. I'll close this issue.

from boot-exec.

The new version has an include option which should solve your problem, I'll do a push to clojars today. Also I'd be willing to accept jgit PR's for boot-semgit.

from boot-exec.

Thanks for adding the option, but I think you haven't pushed it to github? The newest commit here is still 06d27dd.

from boot-exec.

@svdm sorry it was in my personal repo, flyboarder/boot-exec I have merged it in here, can you take a look?

from boot-exec.

Thanks, it works fine. You could opt to make include enabled by default, so as not to break backwards compatibility (doesn't make a difference for me, but I guess someone might be relying on it).

I did look into jgit, but any interaction with the remote that requires authentication is a major hassle, because you can't rely on git handling things (so you have to explicitly connect to a running ssh-agent, else fall back, etc etc). That's probably why clj-jgit doesn't offer any bindings for e.g. pushing. So right now calling the binary is by far the more practical way to make it Just Work.

from boot-exec.

This should now be solved.

from boot-exec.