Fork me on GitHub
#boot
<
2018-12-17
>
plexus14:12:44

is there a way to have a task exit with a non-zero exit code, without printing a stack trace?

plexus14:12:50

use case: I'm working on the Kaocha (test runner) boot task.When a test fails the exit code should be non-zero (so e.g. CI can detect the failure), but all error reporting is already done by the test runner.

alandipert17:12:36

System/exit?

alandipert17:12:46

that will ensure party over

alexyakushev20:12:00

We've been using boot-bin from https://github.com/boot-clj/boot-bin/pull/17 for quite some time, and it seems to be working fine.

alexyakushev20:12:19

Any chance to merge it back and release the new binary?

alandipert21:12:37

@alexyakushev that's good to hear, the original merge was pretty traumatic 😅

alandipert21:12:08

i can take a look and do some of my own testing, maybe we can think about merging next month or so? post-holidays at least

alexyakushev21:12:41

Sure, no rush, just a reminder that it's there 🙂

flyboarder21:12:55

@alexyakushev @alandipert this is great! I have been holding all my projects back at 2.7.2 would love to get on 2.8

alandipert21:12:40

@flyboarder have you been using boot-bin from that PR also?

flyboarder21:12:23

no not as of yet but 2.8 scares me - it didnt have a great launch

flyboarder21:12:54

@alandipert what are your thoughts on #722

alandipert21:12:40

@flyboarder doesn't seem like a problem technically, but i'm personally not cognizant of a larger trend to put build scripts in dot dirs

alandipert21:12:07

i thought that was more what you did for things that were "ancillary" like CI or IDE configs

alandipert21:12:04

oh hey, on the topic of releases and maintenance, is anyone interested in a rotation as maintainer? since i don't use boot for work anymore my time budget is extremely limited, but i could make myself available regularly for anyone who wanted to take a shot

alandipert21:12:56

@flyboarder if you signed up you could merge 722 and i couldn't stop you 😄

flyboarder21:12:30

@alandipert im ok with co-maintaining boot

alandipert21:12:40

re: making myself available, i was imagining i could meet with a maintainer 1-2x a month to review tickets/test things/discuss whatever

flyboarder21:12:43

I already do it for hoplon 😅

alandipert21:12:13

ha, it would almost be like they were the same thing again!

alandipert21:12:28

but in seriousness, your offer is much appreciated. the people of boot thank you

flyboarder21:12:09

I plan on getting around to the hoplon tickets again this holiday break as has been the trend of releasing new 7.x versions for new-year

alandipert21:12:48

maybe in january we could do a conference call or zoom or something, and discuss future direction for boot? and anyone with thoughts could hop on

flyboarder21:12:11

sounds good!

flyboarder21:12:43

just ping me when you want to set something up

alandipert21:12:03

i will! thanks again. very excited by this turn of events