Bug 13742 - HashEquiv server should have a read-only port or endpoint
Summary: HashEquiv server should have a read-only port or endpoint
Status: RESOLVED FIXED
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium+ enhancement
Target Milestone: 3.4 M3
Assignee: Jan-Simon Moeller
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2020-01-21 16:34 UTC by Jan-Simon Moeller
Modified: 2021-09-16 15:09 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan-Simon Moeller 2020-01-21 16:34:15 UTC
Use-case:
Have a build farm fill the server but have a read-only port available to the outside world.
Comment 1 Randy MacLeod 2021-03-18 15:05:22 UTC
3.3 development is closed, move to 3.4
Comment 2 Richard Purdie 2021-09-16 15:09:45 UTC
We now have read-only support in hashequiv.