Unify build dependencies #1952
Open
Unify build dependencies #1952
+55
−2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zfields
force-pushed
the
ch39834/workbench-installer
branch
2 times, most recently
from
94892f4 to
e184ff7
Compare
zfields
force-pushed
the
ch39834/workbench-installer
branch
from
e184ff7 to
7808102
Compare
zfields
force-pushed
the
ch39834/workbench-installer
branch
2 times, most recently
from
f20566f to
b090185
Compare
zfields
force-pushed
the
ch39834/workbench-installer
branch
from
800a2b4 to
0cd0a34
Compare
zfields
force-pushed
the
ch39834/workbench-installer
branch
from
0cd0a34 to
52af5f0
Compare
avtolstoy
approved these changes
Dec 11, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
The DeviceOS needs to describe the dependencies required to build itself in codified documentation.
Solution
Today, the Workbench has delineated the requirements of the DeviceOS in a
manifest.jsonfile. As a first step, we shall host thismanifest.jsonfile until we are able to describe a more robust enumeration of our dependencies.Steps to Test
This PR will serve as a test. The PR specifies a feature branch of the buildpack system, which will ultimately consume the new
.workbench/manifest.jsonfile. If it is valid, CI will succeed, if it is invalid, then CI will failReferences
Links to the Community, Docs, Other Issues, etc..
https://github.com/particle-iot/buildpack-hal/compare/ch39834/workbench-installer
https://github.com/particle-iot/firmware-buildpack-builder/compare/ch39834/workbench-installer
Completeness