Latest dist (2.0.1) is missing ARM6 builds

[fspoettel]

The latest dist is missing ARM6 builds, previously available until 2.0.0

[imyller]

Looks like they were built ok:

https://jenkins-iojs.nodesource.com/job/iojs+release/63/nodes=iojs-raspbian-wheezy-pi1/

And copied to staging just fine:

+ scp -p iojs-v2.0.1-linux-armv6l.tar.gz iojs-www:staging/release/v2.0.1/iojs-v2.0.1-linux-armv6l.tar.gz
+ scp -p iojs-v2.0.1-linux-armv6l.tar.xz iojs-www:staging/release/v2.0.1/iojs-v2.0.1-linux-armv6l.tar.xz
+ ssh iojs-www touch staging/release/v2.0.1/iojs-v2.0.1-linux-armv6l.tar.gz.done staging/release/v2.0.1/iojs-v2.0.1-linux-armv6l.tar.xz.done

But never ended up in the dist

I think @rvagg can fix this.

[targos]

The ARMv6 build takes much more time than the others and this one was just finished 90m ago.
Would it possible to have an automatic upload to the website when a build is successful?

[imyller]

We do not know how staging -> dist happens. It might be a scheduled job that takes places in hour or two after noticing iojs-v2.0.1-linux-armv6l.tar.gz.done flag file .. and this issue will be resolved.

.. or it could be manual process.

[Fishrock123]

Yeah, they just haven't been verified/signed and staged yet.

[Fishrock123]

We do not know how staging -> dist happens. It might be a scheduled job that takes places in hour or two after noticing iojs-v2.0.1-linux-armv6l.tar.gz.done flag file .. and this issue will be resolved.

.. or it could be manual process.

Actually, it's documented in doc/releases.md. It's manual. See:

https://github.com/iojs/io.js/blob/master/doc/releases.md#10-promote-and-sign-the-release-builds

[rvagg]

You just have to be a bit more patient with armv6 builds, the promotion process is manual and these builds take longer than the rest so they don't get done in the same batch - in this case I was busy and then simply forgot.

In future, feel free to ping the person responsible for the particular release if you see that the armv6 build has finished in Jenkins and is not in the public folder, it's likely that they haven't been paying close attention.

Also, you can download binaries straight from Jenkins if you want, they are the same files that get promoted and signed.

[fspoettel]

@rvagg @Fishrock123 Thanks for the clearup and the link to the docs, much appreciated! 🍻