npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

nodejs-nightly-builder

v1.0.1

Published

An application to trigger nightly builds of Node.js for distribution at nodejs.org _if_ there is new code available on a given branch

Downloads

2

Readme

nodejs-nightly-builder

An application to trigger nightly builds of Node.js for distribution at nodejs.org if there is new code available on a given branch

Usage

$ nodejs-nightly-builder [--type <nightly|next-nightly>] --ref <git head ref> --config <config file> [--force]
  • type: nightly vs next-nightly is a remnant of io.js and not used in current Node.js builds, it is therefore optional and defaults to nightly.
  • ref: normally points to a git branch, e.g. heads/v6.x or heads/master
  • force: can force a build even if one is not strictly required
  • config: a config file for finding and authorising access to the appropriate GitHub repo via the GitHub API. The config file is in JSON format and must contain the following entries:
    • "githubOrg" (optional, defaults to "nodejs"): the GitHub org or user for the repository being checked
    • "githubRepo" (optional, defaults to "node"): the GitHub repository name being checked
    • "githubScheme" (optional, defaults to "https://github.com/"): the scheme for accessing the GitHub repository, including host and other components up to the "org/repo"
    • "githubAuthUser": the user for which the GitHub API is being accessed by
    • "githubAuthToken": the authentication token for accessing the API for the given user (e.g. obtained with https://github.com/rvagg/ghauth)
    • "jenkinsToken": the token entered in the Jenkins job for building distributables, required to authenticate API triggered access
    • "jenkinsJobUrl": URL of the job being accessed, as you would as a normal user, e.g. "https://ci.nodejs.org/job/node-release"
    • "jenkinsCrumbUrl": the Jenkins API endpoint for obtaining a crumb for bypassing XSS checks during API access, e.g. "https://ci.nodejs.org/crumbIssuer/api/json"

The GitHub API is used to check HEAD commits which is why an authentication token is required.

When run, nodejs-nightly-builder will first check whether a build is required. It does this by checking the file at https://nodejs.org/download/{type}/index.json, where type is provided on the commandline, e.g. https://nodejs.org/download/nightly/index.json. Nightly builds contain a commit sha that can be decoded from their version string. The HEAD commit is also pulled from GitHub for the ref (branch) provided on the commandline. If the latest build does not match the HEAD commit, a new nightly build is required. Nightly builds are triggered with Jenkins.


Managed under the governance of the Node.js Build Working Group.

Copyright (c) 2016 Node.js Foundation. All rights reserved.

Licensed under MIT, see the LICENSE.md file for details