Some of the Node.js Build ARM resources: 3 generations of Raspberry Pi and other ARMv7 & ARM64 hardware
# Node.js Build Working Group Chat with us on [Slack][1]. ## Purpose The Node.js Build Working Group maintains and controls infrastructure used for continuous integration (CI), releases, benchmarks, web hosting (of [nodejs.org][node] and other Node.js web properties) and more. Our mission is to provide Node.js Project and libuv with solid computing infrastructure in order to improve the quality of the software itself by targeting correctness, speed and compatibility and to ensure streamlined delivery of binaries and source code to end-users. This repository contains information used to set up and maintain the various pieces of Node.js Project infrastructure managed by the Build Working Group. It is intended to be open and transparent, if you see any relevant information missing please open an issue. If you are interested in joining, please read [GOVERNANCE.md][] to understand the process and reasoning we use for granting access to the resources we manage. ## Build WG Members * [@abmusse](https://github.com/abmusse) - Abdirahim Musse * [@AshCripps](https://github.com/AshCripps) - Ash Cripps * [@joaocgreis](https://github.com/joaocgreis) - João Reis * [@joyeecheung](https://github.com/joyeecheung) - Joyee Cheung * [@mhdawson](https://github.com/mhdawson) - Michael Dawson * [@MoLow](https://github.com/MoLow) - Moshe Atlow * [@node-forward-build](https://github.com/node-forward-build) - node-forward build infrastructure * [@richardlau](https://github.com/richardlau) - Richard Lau * [@rvagg](https://github.com/rvagg) - Rod Vagg * [@ryanaslett](https://github.com/ryanaslett) - Ryan Aslett * [@StefanStojanovic](https://github.com/StefanStojanovic) - Stefan Stojanovic * [@sxa](https://github.com/sxa) - Stewart X Addison * [@targos](https://github.com/targos) - Michaël Zasso * [@UlisesGascon](https://github.com/UlisesGascon) - Ulises Gascón Above list is manually synced with the [gpg member list](https://github.com/nodejs-private/secrets/tree/master/build/test/.gpg). ### Infra Admins * [@joaocgreis](https://github.com/joaocgreis) - João Reis * [@mhdawson](https://github.com/mhdawson) - Michael Dawson * [@MoLow](https://github.com/MoLow) - Moshe Atlow * [@richardlau](https://github.com/richardlau) - Richard Lau * [@rvagg](https://github.com/rvagg) - Rod Vagg * [@ryanaslett](https://github.com/ryanaslett) - Ryan Aslett * [@StefanStojanovic](https://github.com/StefanStojanovic) - Stefan Stojanovic * [@sxa](https://github.com/sxa) - Stewart X Addison * [@targos](https://github.com/targos) - Michaël Zasso * [@UlisesGascon](https://github.com/UlisesGascon) - Ulises Gascón ### Jenkins Admins Admin access to https://ci.nodejs.org/. * [@AshCripps](https://github.com/AshCripps) - Ash Cripps * [@joaocgreis](https://github.com/joaocgreis) - João Reis * [@joyeecheung](https://github.com/joyeecheung) - Joyee Cheung * [@mhdawson](https://github.com/mhdawson) - Michael Dawson * [@MoLow](https://github.com/MoLow) - Moshe Atlow * [@node-forward-build](https://github.com/node-forward-build) - node-forward build infrastructure * [@richardlau](https://github.com/richardlau) - Richard Lau * [@rvagg](https://github.com/rvagg) - Rod Vagg * [@ryanaslett](https://github.com/ryanaslett) - Ryan Aslett * [@StefanStojanovic](https://github.com/StefanStojanovic) - Stefan Stojanovic * [@sxa](https://github.com/sxa) - Stewart X Addison * [@targos](https://github.com/targos) - Michaël Zasso * [@UlisesGascon](https://github.com/UlisesGascon) - Ulises Gascón ### Release Admins Access to [release secrets][]. - [@AshCripps](https://github.com/AshCripps) - Ash Cripps - [@joaocgreis](https://github.com/joaocgreis) - João Reis - [@mhdawson](https://github.com/mhdawson) - Michael Dawson - [@MoLow](https://github.com/MoLow) - Moshe Atlow - [@richardlau](https://github.com/richardlau) - Richard Lau - [@rvagg](https://github.com/rvagg) - Rod Vagg - [@ryanaslett](https://github.com/ryanaslett) - Ryan Aslett - [@StefanStojanovic](https://github.com/StefanStojanovic) - Stefan Stojanovic - [@sxa](https://github.com/sxa) - Stewart X Addison - [@targos](https://github.com/targos) - Michaël Zasso - [@UlisesGascon](https://github.com/UlisesGascon) - Ulises Gascón Above list is manually synced with the [gpg member list](https://github.com/nodejs-private/secrets/tree/master/build/release/.gpg). ### Release Jenkins Admins Admin access to https://ci-release.nodejs.org/. * [@AshCripps](https://github.com/AshCripps) - Ash Cripps * [@joaocgreis](https://github.com/joaocgreis) - João Reis * [@mhdawson](https://github.com/mhdawson) - Michael Dawson * [@MoLow](https://github.com/MoLow) - Moshe Atlow * [@node-forward-build](https://github.com/node-forward-build) - node-forward build infrastructure * [@richardlau](https://github.com/richardlau) - Richard Lau * [@rvagg](https://github.com/rvagg) - Rod Vagg * [@ryanaslett](https://github.com/ryanaslett) - Ryan Aslett * [@StefanStojanovic](https://github.com/StefanStojanovic) - Stefan Stojanovic * [@sxa](https://github.com/sxa) - Stewart X Addison * [@targos](https://github.com/targos) - Michaël Zasso * [@UlisesGascon](https://github.com/UlisesGascon) - Ulises Gascón ### GitHub Bot Admins * [@jbergstroem](https://github.com/jbergstroem) - Johan Bergström * [@joyeecheung](https://github.com/joyeecheung) - Joyee Cheung * [@phillipj](https://github.com/phillipj) - Phillip Johnsen * [@Starefossen](https://github.com/Starefossen) - Hans Kristian Flaatten If you are interested in joining the Build WG, or for more information about accesses and team roles see [GOVERNANCE.md][]. ### Emeriti - [@addaleax](https://github.com/addaleax) - Anna Henningsen - [@anonrig](https://github.com/anonrig) - Yagiz Nizipli - [@bnoordhuis](https://github.com/bnoordhuis) - Ben Noordhuis - [@gibfahn](https://github.com/gibfahn) - Gibson Fahnestock - [@gireeshpunathil](https://github.com/gireeshpunathil) - Gireesh Punathil - [@jbergstroem](https://github.com/jbergstroem) - Johan Bergström - [@LucaLanziani](https://github.com/LucaLanziani) - Luca Lanziani - [@maclover7](https://github.com/maclover7) - Jon Moss - [@mmarchini](https://github.com/mmarchini) - mary marchini - [@MylesBorins](https://github.com/MylesBorins) - Myles Borins - [@phillipj](https://github.com/phillipj) - Phillip Johnsen - [@refack](https://github.com/refack) - Refael Ackermann (רפאל פלחי) - [@sam-github](https://github.com/sam-github) - Sam Roberts - [@Starefossen](https://github.com/Starefossen) - Hans Kristian Flaatten - [@Trott](https://github.com/Trott) - Rich Trott ## Infrastructure Providers The Node.js Project is proud to receive contributions from many companies, both in the form of monetary contributions in exchange for membership or in-kind contributions for required resources. The Build Working Group collaborates with the following companies who contribute various kinds of cloud and physical hardware to the Node.js project. ### Tier-1 Providers The Node.js Project's tier-1 infrastructure providers contribute the largest share of infrastructure to the Node.js project. Without these companies, the project would not be able to provide the quality, speed and availability of test coverage that it does today.  - **[DigitalOcean][2]**: a popular cloud hosting service, provides a significant amount of the resources required to run the Node.js project including key CI infrastructure/servers required to host [nodejs.org][node]. - **[Rackspace][3]**: a popular managed cloud company, provides significant resources used to power much of the Node.js project's CI system, including key Windows compilation servers, along with additional services such as [Mailgun][5] for some [nodejs.org and iojs.org email][6] services. ### Tier-2 Providers The Node.js Project's tier-2 infrastructure providers fill essential gaps in architecture and operating system variations and shoulder some of the burden from the tier-1 providers, contributing to availability and speed in our CI system.  - **[Microsoft][7]**: Provides Windows-related test infrastructure on [Azure][8] for the Node.js CI system. - **[Joyent][9]**: A private cloud infrastructure company, provides SmartOS and other test/build resources for the Node.js CI system, resources for backup of our critical infrastructure, redundancy for nodejs.org and or [unencrypted.nodejs.org](http://unencrypted.nodejs.org) mirror. - **[IBM][10]**: - [IBM Cloud][11] provides hardware for testing and benchmarking for the Node.js project's CI system. - Via the [Oregon State University Open Source Lab][12], provides PPC-based test and build infrastructure. - Via the [IBM LinuxOne(TM) Community Cloud][13], provides linuxOne based test and build infrastructure. - **[Scaleway][15]**: Scalable cloud platform designed for developers & growing companies, contributes key ARMv7 hardware for test and release builds for the Node.js CI system. - **[Cloudflare][16]**: CDN and internet traffic management provider, are responsible for providing fast and always-available access to [nodejs.org][node]. - **[ARM][17]**: Semiconductor intellectual property supplier, have donated ARMv8 / ARM64 hardware used by the Node.js CI system for build and testing Node.js. - **[Intel][22]**: "The world leader in silicon innovation," contributes hardware used for benchmarking in the Node.js project's CI system to advance and accelerate Node.js performance. - **[MacStadium][23]**: Managed hosting provider for Mac. Provides Mac hardware used for testing in the Node.js project's CI system. - **[Packet][24]**: Bare metal cloud for developers. Through their [Works on Arm](https://www.worksonarm.com/), Packet provides ARM64 build infrastructure and additional resources for powering our CI system. ### Community Donations From time to time, the Node.js Build Working group calls for, and receives donations of hardware in order to expand the breadth of the build and test infrastructure it maintains. The Node.js Project would like to thank the following individuals and companies that have donated miscellaneous hardware: - [NodeSource][ns] for a Raspberry Pi B, a Raspberry Pi B+, a Raspberry Pi 2 B and an ODROID-XU3 - Andrew Chilton [@chilts](https://github.com/chilts) for a Raspberry Pi B - Julian Duque [@julianduque](https://github.com/julianduque) for a Beaglebone Black - Andi Neck [@andineck](https://github.com/andineck) for 2 x Raspberry Pi B+ - Bryan English [@bengl](https://github.com/bengl) for 2 x Raspberry Pi B+ - Continuation Labs [@continuationlabs](https://github.com/continuationlabs) for a Raspberry Pi B+ - C J Silverio [@ceejbot](https://github.com/ceejbot) for a Raspberry Pi B+ and a Raspberry Pi 2 B - [miniNodes][18] for a Raspberry Pi B+ and a Raspberry Pi 2 B - Simeon Vincent [@svincent](https://github.com/svincent) for 3 x Raspberry Pi 2 B - Joey van Dijk [@joeyvandijk](https://github.com/joeyvandijk) and [Techtribe][19] for 2 x Raspberry Pi 2 B and an ODROID-U3+ - Matteo Collina [@mcollina](https://github.com/mcollina) for a Raspberry Pi 2 B - Sam Thompson [@sambthompson](https://github.com/sambthompson) for a Raspberry Pi 2 B - Louis Center [@louiscntr](https://github.com/louiscntr) for a Raspberry Pi 2 B - Dav Glass [@davglass](https://github.com/davglass/) for 2 x ODROID-XU3, Raspberry Pi 1 B+, Raspberry Pi 3, power, networking and other miscellaneous equipment - [Tessel][20] for a Tessel 2 - KahWee Teng [@kahwee](https://github.com/kahwee) for a Raspberry Pi 3 - Chinmay Pendharkar [@notthetup](https://github.com/notthetup) and Sayanee Basu [@sayanee](https://github.com/sayanee) for a Raspberry Pi 3 - Michele Capra [@piccoloaiutante](https://github.com/piccoloaiutante) for a Raspberry Pi 3 - [Pivotal Agency][pivotal] for two Raspberry Pi 3's - [SecuroGroup][securo] for two Raspberry Pi 1 B+'s and two Raspberry Pi 3's - William Kapke [@williamkapke](https://github.com/williamkapke) for three Raspberry Pi 3's and networking equipment - Jonathan Barnett [@indieisaconcept](https://github.com/indieisaconcept) for a Raspberry Pi B+ - James Snell [@jasnell](https://github.com/jasnell) for a Raspberry Pi 2 - Michael Dawson [@mhdawson](https://github.com/mhdawson) for a Raspberry Pi 1 B+ - Chris Lea [@chrislea](https://github.com/chrislea) for a Raspberry Pi 1 B+ If you would like to donate hardware to the Node.js Project, please reach out to the Build Working Group, via the [#nodejs-build channel on the OpenJS Foundation Slack instance][1] or contact [Rod Vagg](mailto:rod@vagg.org) directly. The Build Working Group reserves the right to choose what hardware is actively used and how it is used, donating hardware does not guarantee its use within the testing infrastructure as there are many other factors that must be considered. Some donated hardware, while not used actively in the CI infrastructure, is used from time to time for R&D purposes by the project. ## CI Software Build and test orchestration is performed by [Jenkins][21]. - A summary of build and test jobs can be found at: