Difference between revisions of "Build infrastructure"

Jump to navigation Jump to search
m
m (→‎Build infrastructure: Add autoygg and mm-cli)
Line 12: Line 12:
 
|-
 
|-
 
| glue || https://github.com/MassMesh/glue || Source code for the glue scripts that convert the output of the CI pipelines into the image and package repositories ||
 
| glue || https://github.com/MassMesh/glue || Source code for the glue scripts that convert the output of the CI pipelines into the image and package repositories ||
 +
|-
 +
| autoygg || https://github.com/MassMesh/autoygg || Source code for the autoygg package ||
 +
|-
 +
| mm-cli || https://github.com/MassMesh/mm-cli || Source code for the mm-cli package ||
 
|-
 
|-
 
|}
 
|}

Revision as of 10:48, 13 June 2020

Build infrastructure

MassMesh publishes openwrt packages and device images. These artifacts are generated by free software available from the links below.

Repositories
Name URL Description Artifacts
mm-toolbox https://github.com/MassMesh/mm-toolbox Source code for the Massmesh package builds https://downloads.massmesh.net/snapshots/packages/
meta-imagebuilder https://github.com/MassMesh/meta-imagebuilder Source code for the Massmesh image builds https://downloads.massmesh.net/snapshots/images/
glue https://github.com/MassMesh/glue Source code for the glue scripts that convert the output of the CI pipelines into the image and package repositories
autoygg https://github.com/MassMesh/autoygg Source code for the autoygg package
mm-cli https://github.com/MassMesh/mm-cli Source code for the mm-cli package

The artifacts are built by a CI pipeline that runs on CircleCI. The pipeline is defined in the mm-toolbox and meta-imagebuilder repositories in the .circleci/config.yml file.

If the build is successful, the CI pipeline uploads the generated artifacts to a staging directory on the downloads.massmesh.net server. The process-uploads code in the glue repository then processes those artifacts and generates the Package and Image repositories at downloads.massmesh.net. This process is described in detail in the README.

Builds from the master branch go to the snapshots repositories. Builds from other branches go to the experimental repositories. Releases will be published in the releases repositories, but as of June 2020 no releases are available yet.