Closed chriskrycho closed 8 years ago
this isn't just windows, came here after investigating build failures for our heroku release
@novaugust interesting. I updated the title accordingly; does your error output show anything different than mine?
Was just lookig at that to compare. Answer: same stack
Anyone have a repro locally?
This is also failing for me on all my heroku deploys
@rwjblue yeah, figured it out.
Clone your ember project somewhere and delete its .git
folder
Without that, the path comes back null, et voila.
removing git folder worked for me as well locally
Why would this have changed between 1.1.2 and 1.1.3?
Got it. Fix incoming.
:+1:, this broke our heroku deploys as well. You are on top of everything @rwjblue.
Released v1.1.4
worked in heroku, thanks @rwjblue!
Works again using Docker, thanks @rwjblue!
This is a fun one. Since the 1.13 publication, builds started failing for us on our TeamCity server, but only there. We can't reproduce locally (on OS X 10.11.5 or Windows 10 Pro).
The call to
findRepo()
is returningnull
, and that error condition isn't being handled: it's just passing the result directly intopath.join
, here. Curiously, 1.13 didn't actually change anything around this—but something about shipping it did break the TC build.Our TeamCity box is running Windows Server 2008 and Git [will add shortly].
Here's the full stack trace: