-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[build] add avahi daemon and library #3263
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM:+1:
@gjc13 - you need to update the |
Updated. |
eb0ea62
to
09ff656
Compare
integrations/docker/run.sh
Outdated
@@ -35,7 +35,7 @@ ORG=${DOCKER_RUN_ORG:-connectedhomeip} | |||
IMAGE=${DOCKER_RUN_IMAGE:-$(basename "$here")} | |||
|
|||
# version | |||
VERSION=${DOCKER_RUN_VERSION:-$(cat "$here/version")} || | |||
VERSION=${DOCKER_RUN_VERSION:-latest} || |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we haven't been keeping latest up to date...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Using $(cat "$here/version")
with cause the cirque build to fail. Is it okay to ignore it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should probably just use a specific version like 0.4.11
, like GitHub actions does. That avoids the circular dependency when updating the dockerfile.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- can't ignore cirque builds
- can't use a specific version (because version is shared, via symlinks)
For this PR to land, all of the images need to be pushed first.
This should probably be looked at again. When I wrote all this, it was expedient to bump all versions all the time because chip-build was the image that changed most often and all the children needed the latest chip-build.
Today, we can version chip-build independently and let children update as necessary.
Changes needed:
- images/*/version files to be un-symlinked
- Dockerfile FROM directives to use specific versions
- integrations/docker/images/build-all.sh to be reworked with the above in mind
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've unlinked the version file in build-cirque and fix it to v0.4.11 as a temporary fix.
ef37c57
to
9e56d28
Compare
Reminder to use the "re-request review" button. |
- Modify flow to allow for RequirePINforRemoteOperation to be TRUE or FALSE - Reorder steps 7-9 to ensure subsequent test of WrongCodeEntryLimit doesn't already have existing failed entry attempts - Fix incorrect PICS (use .Write PICS) for writing WrongCodeEntryLimit and UserCodeTemporaryDisableTime Fixes project-chip#3263 Fixes project-chip#3265 Fixes project-chip#3266
…ration to be TRUE or FALSE - Modify flow to allow for RequirePINforRemoteOperation to be TRUE or FALSE - Reorder steps 7-9 to ensure subsequent test of WrongCodeEntryLimit doesn't already have existing failed entry attempts - Fix incorrect PICS (use .Write PICS) for writing WrongCodeEntryLimit and UserCodeTemporaryDisableTime Fixes project-chip#3263 Fixes project-chip#3265 Fixes project-chip#3266
…ration to be TRUE or FALSE (#28523) * TC-DRLK-2.2/2.3/2.12: Modify flow to allow for RequirePINforRemoteOperation to be TRUE or FALSE - Modify flow to allow for RequirePINforRemoteOperation to be TRUE or FALSE - Reorder steps 7-9 to ensure subsequent test of WrongCodeEntryLimit doesn't already have existing failed entry attempts - Fix incorrect PICS (use .Write PICS) for writing WrongCodeEntryLimit and UserCodeTemporaryDisableTime Fixes #3263 Fixes #3265 Fixes #3266 * Restyled by autopep8 * Exclude .yaml tests from CI due to use of EqualityTests pseudo-cluster * Add zap-regen'd files * Exclude .yaml tests from CI linux due to use of EqualityTests pseudo-cluster --------- Co-authored-by: Restyled.io <[email protected]>
…ration to be TRUE or FALSE (project-chip#28523) * TC-DRLK-2.2/2.3/2.12: Modify flow to allow for RequirePINforRemoteOperation to be TRUE or FALSE - Modify flow to allow for RequirePINforRemoteOperation to be TRUE or FALSE - Reorder steps 7-9 to ensure subsequent test of WrongCodeEntryLimit doesn't already have existing failed entry attempts - Fix incorrect PICS (use .Write PICS) for writing WrongCodeEntryLimit and UserCodeTemporaryDisableTime Fixes project-chip#3263 Fixes project-chip#3265 Fixes project-chip#3266 * Restyled by autopep8 * Exclude .yaml tests from CI due to use of EqualityTests pseudo-cluster * Add zap-regen'd files * Exclude .yaml tests from CI linux due to use of EqualityTests pseudo-cluster --------- Co-authored-by: Restyled.io <[email protected]>
…ration to be TRUE or FALSE (project-chip#28523) * TC-DRLK-2.2/2.3/2.12: Modify flow to allow for RequirePINforRemoteOperation to be TRUE or FALSE - Modify flow to allow for RequirePINforRemoteOperation to be TRUE or FALSE - Reorder steps 7-9 to ensure subsequent test of WrongCodeEntryLimit doesn't already have existing failed entry attempts - Fix incorrect PICS (use .Write PICS) for writing WrongCodeEntryLimit and UserCodeTemporaryDisableTime Fixes project-chip#3263 Fixes project-chip#3265 Fixes project-chip#3266 * Restyled by autopep8 * Exclude .yaml tests from CI due to use of EqualityTests pseudo-cluster * Add zap-regen'd files * Exclude .yaml tests from CI linux due to use of EqualityTests pseudo-cluster --------- Co-authored-by: Restyled.io <[email protected]>
Problem
#3241 requires avahi as build dependency.
Summary of Changes
Adds avahi daemon and lib to the build docker.