Looks like it was the aborted flex-sdk build. Right now, many of our builds are dependent on the flex-sdk build, even the FlexJS builds. This is probably not a good thing, but I don't want to take the time right now to reconfigure our builds to use the "last good build" instead of the workspaces of other builds. If someone wants to take that on that would be great, although the simple solution for now is just to log in to Jenkins and manually restart the flex-sdk build (and cancel any jobs currently in the queue that are going to break because of a bad flex-sdk build). In fact, the flex-sdk build died again yesterday due to inability to access Git and I restarted it this morning.
-Alex On 6/27/17, 10:39 PM, "piotrz" <piotrzarzyck...@gmail.com> wrote: >Ahh! If that help - It probably was my fault, cause I was playing a bit >with >builds lately. > >I'm sorry about that! > >Piotr > > > >----- >Apache Flex PMC >piotrzarzyck...@gmail.com >-- >View this message in context: >https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle >x-development.2333347.n4.nabble.com%2FRe-Build-failed-in-Jenkins-flex-falc >on-1627-tp62646p62654.html&data=02%7C01%7C%7Cd34e7a0d25124cce8c6408d4bdea8 >4a8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636342262332481920&sdata= >O2cYv6y2p0T1QXB%2FAK5i2d3FV%2B22NLQLOyr0Bek5lYs%3D&reserved=0 >Sent from the Apache Flex Development mailing list archive at Nabble.com.
