Convert circleci config to 2.0.

[SuperQ]

No description provided.

[grobie]

Cool, I was waiting for the first one to move to ask "can you do that on all repos please" :D

[SuperQ]

@grobie hah! Yea, there's a bunch of stuff that's easier in 2.0 configs. But, as you can see, it's not working perfectly yet with docker mode. Not sure why. :-/

[sdurrheimer]

Nice, I was going to look at this.

[SuperQ]

@sdurrheimer promu crossbuild failed, not sure why.

[sdurrheimer]

@SuperQ Can you add a -v to promu crossbuild to see more debug informations ?

[SuperQ]

@grobie @matthiasr The test and build workflow steps now work reliably. The publish steps should work now as well, but we need to try cutting an actual release from master to test them end-to-end.

[matthiasr]

Let's cut an 0.16 beta then?

[SuperQ]

@matthiasr Yup, that's the plan, I want to cut it as rc0.

[matthiasr]

looks good!

[grobie]

So this config uses a lot more hardcoded names now, where we previously used template variables. This makes it a lot more cumbersome to keep our circle CI configs in sync between projects. Can you bring back the environment variables to reference the repo+organization names?

[SuperQ]

@grobie Based on the documentation I've read so far, the working_directory key doesn't interpret env vars. I can give it a try anyway.