Difference between revisions of "Build infrastructure"

Jump to navigation Jump to search
m
m (Update README path in glue repo)
 
Line 21: Line 21:
 
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.
 
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 [https://downloads.massmesh.net/snapshots/packages/ Package] and [https://downloads.massmesh.net/snapshots/images/ Image] repositories at [https://downloads.massmessh.net downloads.massmesh.net]. This process is described in detail in the [https://github.com/MassMesh/glue/blob/master/process-uploads/README README].
+
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 [https://downloads.massmesh.net/snapshots/packages/ Package] and [https://downloads.massmesh.net/snapshots/images/ Image] repositories at [https://downloads.massmessh.net downloads.massmesh.net]. This process is described in detail in the [https://github.com/MassMesh/glue/blob/master/process-uploads/README.md README].
  
 
Builds from the master branch go to the '''[https://downloads.massmesh.net/snapshots/ snapshots repositories]'''. Builds from other branches go to the '''[https://downloads.massmesh.net/experimental/ experimental repositories]'''. Releases will be published in the '''[https://downloads.massmesh.net/releases/ releases repositories]''', but as of June 2020 no releases are available yet.
 
Builds from the master branch go to the '''[https://downloads.massmesh.net/snapshots/ snapshots repositories]'''. Builds from other branches go to the '''[https://downloads.massmesh.net/experimental/ experimental repositories]'''. Releases will be published in the '''[https://downloads.massmesh.net/releases/ releases repositories]''', but as of June 2020 no releases are available yet.

Latest revision as of 16:07, 14 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 of autoygg
mm-cli https://github.com/MassMesh/mm-cli Source code of mm-cli

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.