Skip to content

Latest dist (2.0.1) is missing ARM6 builds #1656

Description

@fspoettel

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

Activity

  1. added
    buildIssues and PRs related to Node.js builds or CI infrastructure.
    on May 8, 2015
  2. imyller commented on May 8, 2015

    @imyller
    Member

    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.

  3. targos commented on May 8, 2015

    @targos
    Member

    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?

  4. imyller commented on May 8, 2015

    @imyller
    Member

    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.

  5. Fishrock123 commented on May 8, 2015

    @Fishrock123
    Contributor

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

  6. Fishrock123 commented on May 8, 2015

    @Fishrock123
    Contributor

    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

  7. rvagg commented on May 8, 2015

    @rvagg
    Member

    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.

  8. fspoettel commented on May 8, 2015

    @fspoettel
    Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    buildIssues and PRs related to Node.js builds or CI infrastructure.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions