Fork me on GitHub
#boot
<
2017-05-06
>
pseud10:05:38

@flyboarder simply adding a shutdown hook doesn't seem to cut it, I assume (given the namespace in which add-shutdown-hook! resides) that I'll have to perhaps make a pod ?

pseud10:05:10

And in more general terms, if anyone has an example of making a new pod with shutdown hooks (and what the hell that actually even implies), I'd be grateful

flyboarder15:05:49

@pseud checkout the boot-nodejs serve task, uses shutdown hooks to kill rogue nodejs threads

flyboarder16:05:54

⚠️ boot-semver now supports Continuous Deployment v1.5.0 ⚠️ https://github.com/degree9/boot-semver

richiardiandrea19:05:57

@flyboarder awesome that you can push snapshots like this, but is it pushing on every file change?

flyboarder19:05:21

in that case yes!

flyboarder19:05:17

I dont recommend it, but the goal was to solve the repeated use of the version task in pipelines

flyboarder19:05:53

there is now an internal atom used to track the version

richiardiandrea19:05:59

Is it possible to do it ? A conditional watch it is not possible but you could maybe read meta from the version file

richiardiandrea19:05:27

The push task needs to do that

flyboarder19:05:43

yep, pom and push have been patched and replaced

flyboarder19:05:52

via replace-task!

flyboarder19:05:01

they also track the new atom

richiardiandrea19:05:29

I guess it would be a great addition

flyboarder19:05:52

im not sure it is, I think the correct way to store mutative data is in the env map

richiardiandrea19:05:50

Uhm in any case I like the idea of auto pushing