nyuuzyou/wikis huggingface dataset:
Full Pass Test Report for Yocto 1.4 M5 RC3 201304032 Build

=Testing data=
 
 Test type: Full Pass Post-release
 Branch: master
 Milestone: 1.4 M5
 Build name: 1.4 M5 RC3
 poky commit: fe336b149552b1f4f24d979c40302653298b98cc
 poky commit date: Wed Apr 3 05:11:50 2013 +0000
 meta-intel commit: 3de2325133eb581c5c8d66133821ea5a801cf8ae
 Eclipse Plugin commit: 5e20d3c32072ddd91dceb8b2b793ef13f25b915e
 Autobuilder images repository: http://autobuilder.yoctoproject.org/pub/nightly/20130403-2
 Environments used for testing: Ubuntu 12.04 x86-64, Ubuntu 12.10 x86-64, Fedora 17, Fedora 18, OpenSUSE 12.2 x86-64
 Distribution Testing was performed on: Ubuntu 12.04, Ubuntu 12.10, Fedora 17, Fedora 18, OpenSUse 12.1, OpenSuse 12.2, CentOS 6.3 
=Summary Report=
==Core Build System==
Status:
Bugs:
==HOB==
Status:
Bugs:
==BSP & QEMU==
Status:
Bugs:
==Performance testing==
Status:
Bugs:
Performance Metrics
Build performance metrics
==Build-appliance==
Status:
Bugs:
==ADT & Eclipse Plugin==
Status:
Bugs:
=Detailed Report=
==Core Build System==
===Bitbake===
Status
Bugs
Agenda
===Meta-Yocyo===
Status
Bugs
Agenda
===OE-Core===
Status
Bugs
Agenda
==Hob==
Status
Bugs
Agenda
==BSP==
===Atom-pc: core-image-sato-sdk===
Status
Bugs
Agenda
===NUC: core-image-sato-sdk===
Status
Bugs
Agenda
===Emenlow: core-image-sato-sdk===
Status
Bugs
Agenda
===Sugarbay: core-image-sato-sdk===
Status
Bugs
Agenda
===Jasperforest: core-image-sato-sdk===
Status
Bugs
Agenda
===Crownbay: core-image-sato-sdk-noemgd===
Status
Bugs
Agenda
===FRI2: core-image-sato-sdk===
Status
Bugs
Agenda
===Beagleboard: core-image-sato-sdk===
Status
Bugs
Agenda
===Routerstationpro: core-image-sato-sdk===
Status
Bugs
Agenda
===MPC8315e-rdb: core-image-sato-sdk===
Status
Bugs
Agenda
===P1022ds-rdb: core-image-sato-sdk===
Status
Bugs
Agenda
==Qemu==
===qemux86: core-image-sato-sdk===
Status
Bugs
Agenda
===qemux86-64: core-image-sato-sdk===
Status
Bugs
Agenda
===qemuarm: core-image-sato-sdk===
Status
Bugs
Agenda
===qemumips: core-image-sato-sdk===
Status
Bugs
Agenda
===qemuppc: core-image-sato-sdk===
Status
Bugs
Agenda
==Performance Testing==
Status
Bugs
Agenda
Performance Metrics 
bitbake core-image-sato: 1:16.00
bitbake core-image-sato -c rootfs: 5:30.17
Detailed result at: Build performance metrics
==Build-appliance==
Status
Bugs
Agenda
==ADT==
===ADT on: Fedora 17 i686===
Status
Bugs
Agenda
===ADT on: Fedora 18 x86-64===
Status
Bugs
Agenda
===ADT on: Ubuntu 12.04 x86-64===
Status
Bugs
Agenda
===ADT on: OpenSUSE 12.2 x86-64===
Status
Bugs
Agenda
==Eclipse Plugin==
Status
Bugs
Agenda
Full Pass Test Report for Yocto 1.4 M6 RC1 201304113 Build

=Testing data=
 
 Test type: Full Pass post-release
 Branch: dylan
 Milestone: 1.4 M6
 Build name: 1.4 M6 RC1
 poky commit: dab237bc6a7679dfeaa981c14736aedc7b04ecb9
 poky commit date: Wed Apr 10 15:15:57 2013 -0700
 poky commit(used with meta-intel): cb1941c1801276f8a098ca84aa063cc3e043e801
 meta-intel commit: dylan:94c0feea5ec4f2bc47b05f3265d5e969654b499e
 Eclipse Plugin commit: dylan:46be27bd3400419e8325d753b85a76bfb1898944
 Autobuilder images repository: http://autobuilder.yoctoproject.org/pub/nightly/20130411-3
 Environments used for testing: Ubuntu 12.04 x86-64, Ubuntu 12.10 x86-64, Fedora 17, Fedora 18
 Distribution Testing was performed on: Ubuntu 12.04, Ubuntu 12.10, Fedora 17, Fedora 18, OpenSUse 12.1, OpenSuse 12.2, CentOS 6.3 
=Summary Report=
==Core Build System==
Status:
Bugs:
==HOB==
Status:
Bugs:
==BSP & QEMU==
Status:
Bugs:
==Performance testing==
Status:
Bugs:
Performance Metrics
Build performance metrics
==Build-appliance==
Status:
Bugs:
==ADT & Eclipse Plugin==
Status:
Bugs:
=Detailed Report=
==Core Build System==
===Bitbake===
Status
Bugs
Agenda
===Meta-Yocyo===
Status
Bugs
Agenda
===OE-Core===
Status
Bugs
Agenda
==Hob==
Status
Bugs
Agenda
==BSP==
===Atom-pc: core-image-sato-sdk===
Status
Bugs
Agenda
===NUC: core-image-sato-sdk===
Status
Bugs
Agenda
===Emenlow: core-image-sato-sdk===
Status
Bugs
Agenda
===Sugarbay: core-image-sato-sdk===
Status
Bugs
Agenda
===Jasperforest: core-image-sato-sdk===
Status
Bugs
Agenda
===Crownbay: core-image-sato-sdk-noemgd===
Status
Bugs
Agenda
===FRI2: core-image-sato-sdk===
Status
Bugs
Agenda
===Beagleboard: core-image-sato-sdk===
Status
Bugs
Agenda
===Routerstationpro: core-image-sato-sdk===
Status
Bugs
Agenda
===MPC8315e-rdb: core-image-sato-sdk===
Status
Bugs
Agenda
===P1022ds-rdb: core-image-sato-sdk===
Status
Bugs
Agenda
==Qemu==
===qemux86: core-image-sato-sdk===
Status
Bugs
Agenda
===qemux86-64: core-image-sato-sdk===
Status
Bugs
Agenda
===qemuarm: core-image-sato-sdk===
Status
Bugs
Agenda
===qemumips: core-image-sato-sdk===
Status
Bugs
Agenda
===qemuppc: core-image-sato-sdk===
Status
Bugs
Agenda
==Performance Testing==
Status
Bugs
Agenda
Performance Metrics 
Detailed result at: Build performance metrics
==Build-appliance==
Status
Bugs
Agenda
==ADT==
===ADT on: Fedora 18 i686===
Status
Bugs
Agenda
===ADT on: Ubuntu 12.10 x86-64===
Status
Bugs
Agenda
==Eclipse Plugin==
Status
Bugs
Agenda
Full Pass Test Report for Yocto 1.4 M6 RC2 201304181 Build

=Testing data=
 
 Test type: Full Pass post-release
 Branch: dylan
 Milestone: 1.4 M6 rc2
 Build name: Full Pass
 poky commit: 789b2b7e0cca404ff8ba8ed5ba823d215e6ba5b4
 poky commit date: Thu Apr 18 22:02:26 2013 +0100
 meta-intel commit: 76f70c337e5daa9593153dfdf5107aec08610a44
 Eclipse Plugin commit: dc9a609c68fe4a6bbbf34d418fd6611489c1d6f7
 Autobuilder images repository: http://autobuilder.yoctoproject.org/pub/nightly/20130418-1/
 Environments used for testing: Ubuntu 12.04 x86-64, Ubuntu 12.10 x86-64, Fedora 17, Fedora 18, OpenSUSE 12.2 x86-64
 Distribution Testing was performed on: Ubuntu 12.04, Ubuntu 12.10, Fedora 17, Fedora 18, OpenSUse 12.1, OpenSuse 12.2, CentOS 6.3 
=Summary Report=
==Core Build System==
Status:
Bugs:
==HOB==
Status:
Bugs:
==BSP & QEMU==
Status:
Bugs:
==Performance testing==
Status:
Bugs:
Performance Metrics
Build performance metrics
==Build-appliance==
Status:
Bugs:
==ADT & Eclipse Plugin==
Status:
Bugs:
=Detailed Report=
==Core Build System==
===Bitbake===
Status
Bugs
Agenda
===Meta-Yocyo===
Status
Bugs
Agenda
===OE-Core===
Status
Bugs
Agenda
==Hob==
Status
Bugs
Agenda
==BSP==
===Atom-pc: core-image-sato-sdk===
Status
Bugs
Agenda
===NUC: core-image-sato-sdk===
Status
Bugs
Agenda
===Emenlow: core-image-sato-sdk===
Status
Bugs
Agenda
===Sugarbay: core-image-sato-sdk===
Status
Bugs
Agenda
===Jasperforest: core-image-sato-sdk===
Status
Bugs
Agenda
===Crownbay: core-image-sato-sdk-noemgd===
Status
Bugs
Agenda
===FRI2: core-image-sato-sdk===
Status
Bugs
Agenda
===Beagleboard: core-image-sato-sdk===
Status
Bugs
Agenda
===Routerstationpro: core-image-sato-sdk===
Status
Bugs
Agenda
===MPC8315e-rdb: core-image-sato-sdk===
Status
Bugs
Agenda
===P1022ds-rdb: core-image-sato-sdk===
Status
Bugs
Agenda
==Qemu==
===qemux86: core-image-sato-sdk===
Status
Bugs
Agenda
===qemux86-64: core-image-sato-sdk===
Status
Bugs
Agenda
===qemuarm: core-image-sato-sdk===
Status
Bugs
Agenda
===qemumips: core-image-sato-sdk===
Status
Bugs
Agenda
===qemuppc: core-image-sato-sdk===
Status
Bugs
Agenda
==Performance Testing==
Status
Bugs
Agenda
Performance Metrics 
Detailed result at: Build performance metrics
==Build-appliance==
Status
Bugs
Agenda
==ADT==
===ADT on: Fedora 18 i686===
Status
Bugs
Agenda
===ADT on: Ubuntu 12.10 x86-64===
Status
Bugs
Agenda
==Eclipse Plugin==
Status
Bugs
Agenda
Fullpass Test Report for Yocto 1.5 M1.RC1 2013-06-04-5 Build

=Testing data=
 
 Test type: Fullpass Test
 Branch: master
 Milestone: 1.5 M1
 Build name: Fullpass
 poky commit: a62aed41f2d8f874f7ae24d0e5be5dbc66ea2199
 poky commit date: Date: Fri May 31 16:02:00 2013 +0000
 eclipse-poky: 0b2dc574b1b08eab2102b37f3b64ab7bd70d9595
 Eclipse Plugin commit: Date: Tue Jun 4 14:42:15 2013 -0700
 Autobuilder images repository: http://autobuilder.yoctoproject.org/pub/nightly/20130604-5/
 Distributions tested: Ubuntu 12.04 x86_64, Ubuntu 13.04 x86_64, OpenSUSE 12.3, Fedora 18 i686, CentOS 6.4 x86_64 
=Summary Report=
	
=Detailed Report=
Fullpass Test Report for Yocto 1.5 M1 2013-05-28-2 Build

=Testing data=
 
 Test type: Fullpass Test
 Branch: master
 Milestone: 1.5 M1
 Build name: Fullpass
 poky commit: 676fd3f394a0c0576b63c77ed2184bf5f42c29b6
 poky commit date: Date: Thu May 23 16:09:20 2013 +0000
 Eclipse Plugin commit: Date: Thu May 23 16:09:20 2013 +0000
 Autobuilder images repository: http://autobuilder.yoctoproject.org/pub/nightly/20130528-2/
 Distributions tested: Ubuntu 12.04 x86_64, Ubuntu 13.04 x86_64, OpenSUSE 12.3, Fedora 18 i686, CentOS 6.4 x86_64 
=Summary Report=
	
=Detailed Report=
GDC Team Bug Maintenance

== Yocto Project Planning ==
* YP Planning
== Total estimate times by member (Dev)==
=== Release 2.4 ===
==== Milestone 4 ====
=== Release 2.5 ===
==== Milestone 1 ====
==== Milestone 2 ====
==== Milestone 3 ====
==== Milestone 4 ====
== Total estimate times by member (QA)==
=== 2.3 ===
==== M3 ====
==== M4 ====
=== 2.4 ===
==== M1 ====
==== M2 ====
==== M3 ====
==== M4 ====
== Bugs and enhacements by Owner ==
=== DEV ===
==== Jose ====
==== Leonardo ====
==== Daniela ====
==== Alex ====
=== QA ===
==== Jose ====
==== Paco ====
==== Liby ====
==== Humberto ====
==== Jair ====
==== Sonia ====
==== David ====
==== Juan Ramos ====
== Bugs and Enhancements by Priority ==
=== High ===
=== Medium+ ===
=== Medium ===
=== Low ===
== Old Milestone ==
GPG sign notes & git tags

== Current Process ==
Release notes are reviewed by the Yocto Project TSC and the release manager and signed by the infrastructure lead before signing.
Git tags are saved as part of the build process. They are reviewed by the release manager and signed by the infrastructure lead.
Artefacts themselves are not signed. They are not intended to run outside of testing and exist primarily to show what was tested.
== Obtaining the keys and management ==
Tags and release notes for the Yocto Project are signed with a dedicated build and release GPG key. This key is available from Yocto Project and kernel.org. Primary key fingerprint: 2AFB 13F2 8FBB B0D1 B9DA F630 87EB 3D32 FB63 1AD9. This key is signed by the previous release key and the infrastructure lead.
The key itself was generated on an air-gapped machine using a LiveCD downloaded from the Fedora Linux project and properly verified. The signing subkeys were transferred to a pair of Yubikey hardware tokens. One for the release engineer and one for the infrastructure lead. Since then the Yocto Project has only used these openpgp smartcards for signing git tags and release notes.
== To verify release notes ==
 
curl -O https://downloads.yoctoproject.org/releases/yocto/keys/yocto-release-key.asc
gpg --import yocto-release-key.asc
curl -O https://downloads.yoctoproject.org/releases/yocto/yocto-5.0/RELEASENOTES
gpg --verify RELEASENOTES
To verify git tags in the poky repo
curl -O https://downloads.yoctoproject.org/releases/yocto/keys/yocto-release-key.asc
gpg --import yocto-release-key.asc
git clone https://git.yoctoproject.org/poky
cd poky
git tag --verify yocto-5.0
GSoC

= Yocto Project Summer of Code =
This is the Yocto Project specific page for Google Summer of Code. The Yocto Project is applying to be a mentoring organization for 2020 and is recruiting mentors and students.
Prospective mentors are requested to assist with the ideas page, add themselves to the list, join the dedicated mailing list and contact Nicolas Dechesne to be invited to be a mentor on Google's tool.
Students are requested to engage possible mentors and may begin submitting applications for Yocto Project related projects starting now. This is the first time the project is engaging with Google Summer Of Code, and we are hoping it will be successful attempt. We recommend all students to engage with us now to help make your application strong!
Here are some links to help students with their applications:
* GSoC home
* [TBD Yocto Project GSoC page]
* Guide from drupal.org
== Projects ==
* Current ideas page: Project Ideas for 2020
* Yocto Project GSoC Mailing list
== Key Dates for 2020 ==
January 14 19:00 UTC 	Mentoring organizations can begin submitting applications to Google
February 5 19:00 UTC 	Mentoring organization application deadline
February 5 - February 19	Google program administrators review organization applications
February 20 18:00 UTC 	List of accepted mentoring organizations published
February 20 - March 16 	Potential student participants discuss application ideas with mentoring organizations
March 16 18:00 UTC 	Student application period begins
March 31 18:00 UTC 	Student application deadline
April 14 18:00 UTC 	Student slot requests due from Org Admins
April 23 18:00 UTC 	Student Project selections due from Org Admins
April 27 18:00 UTC 	Accepted student projects announced
Community Bonding Period	Students get to know mentors, read documentation, get up to speed to begin working on their projects
May 18 	Coding officially begins!
June 15 18:00 UTC 	Mentors and students can begin submitting Phase 1 evaluations
June 19 18:00 UTC 	Phase 1 Evaluation deadline
Work Period 	Students work on their project with guidance from Mentors
July 13 18:00 UTC 	Mentors and students can begin submitting Phase 2 evaluations
July 17 18:00 UTC 	Phase 2 Evaluation deadline
Work Period 	Students continue working on their project with guidance from Mentors
August 10 - 17 18:00 UTC	Final week: Students submit their final work product and their final mentor evaluation
August 17 - 24 18:00 UTC	Mentors submit final student evaluations
August 25 	Final results of Google Summer of Code 2020 announced
October 	Mentor Summit
== Links ==
* Yocto Project GSoC Mailing list
* Summer of Code Ideas
* Our project proposal guidelines
* Our application to become a mentoring organization. Application
* FOSDEM video from 2009 about the Summer of Code
GSoC/Application

= GSoC Project proposal guidelines =
== Requirements ==
* Applicants meet Google's requirements for participation in Summer of Code.
* Applicants are in regular and close contact with their mentors and the community (IRC).
* Applicants know their target programming language.
* Applicants have successfully upstream'd a simple patch to demonstrate they know the process.
* Applicants are willing to blog (or use social media) weekly and interact with the community (failure to do so will result in a fail at the next review)
== Proposal Outline ==
* Name and Contact Information
* Title
* A short summary.
* Benefits to the Community.
* Deliverables. Give a brief, clear work breakdown structure with milestones and deadlines. 
* Biographical Information: 
** Summarize your education, work, and open source experience.
** List your skills and give evidence of your qualifications.
** Please list any non-Summer-of-Code plans you have for the Summer, especially employment and class-taking. Be specific about schedules and time commitments.
== General Notes ==
Your proposal should be around 1500-4000 words in plain text and should clearly state what you intend to do and the necessary steps to get there. There is no limit on the number of submitted proposals, if you have several ideas, please submit several proposals. Do include URLs pointing to information that would help convince us of your chances of success: preliminary project plans or progress, other projects you've been involved with that were successful, code samples, etc.
It is better if your project is under-scoped and sure to complete; as opposed to a largish project which may not get done.
See GSoC for project ideas.
Git hosting application

Yocto Project Git hosting Application Form
Name of repo must not conflict with official namespaces
Name of repo: [ text ]
Is this addition being made as a membership benefit?: [ yes / no ]
If so, which member and which membership level: [ member ] [ level ]
Explain why this repo should be added to the git.yoctoproject.org: [ text ]
Who will be the maintainer(s): [ text ]
Where are changes to the repo reviewed (e.g. GitHub): [ text ]
Send form to Yocto TSC <tsc@lists.yoctoproject.org>
Glossary of Terms and Acronyms

Back to Yocto Project Main Page.
== Terminology ==
Here is a list of basic terms users new to the Yocto Project might find helpful. For a more complete list of terms, see the 
"Yocto Project Terms" section in the Yocto Project Development Manual.
:Yocto Project: A Linux Foundation project that acts as an umbrella for various efforts to improve Embedded Linux.
: OpenEmbedded: The build system architecture promoted by the Yocto Project.
: BitBake: A tool that reads metadata and runs tasks.
: OpenEmbedded-Core: The common base set of metadata that BitBake uses. This metadata is shared between OpenEmbedded and the Yocto Project.
: Poky: A reference distribution used for test and release purposes by the Yocto Project.
: Recipe: Meta data defining how bitbake is to configure, build and package a software project.
: Layer: A collection of recipes and/or configuration used by bitbake. Typically each layer is organised around a specific theme, e.g. adding recipes for building web browser software.
== Acronyms ==
:BSP	Board Support Package
: CCB	Change Control Board
: PMP	Program Management Plan
: POR	Plan of Record
: PRD	Product Requirements Document
Googlechart prototype

Shopping List 	Shopping List	Shopping List	Shopping List	Shopping List	Shopping List
Bread & Butter	Pie 	Buns 	Danish 	Croissant 	Croissant
Bread & Butter	Cheese 	Ice cream 	Ice cream 	Butter 	Yogurt
==============================================================================================================
Test Report (Count of passed, failed, skipped group by test_component, test_configuration)
==============================================================================================================
--------------------------------------------------------------------------------------------------------------
test_component | test_configuration | passed | failed | skipped
--------------------------------------------------------------------------------------------------------------
manual/testresults.json | manual_sdk_20181213140200 | 1 | 0 | 0
None | manual_sdk_20181213140200 | 1 | 0 | 0
--------------------------------------------------------------------------------------------------------------
==============================================================================================================
Test Report (Percent of passed, failed, skipped group by test_component, test_configuration)
==============================================================================================================
--------------------------------------------------------------------------------------------------------------
test_component | test_configuration | passed_% | failed_% | skipped_%
--------------------------------------------------------------------------------------------------------------
manual/testresults.json | manual_sdk_20181213140200 | 100.00 | 0.00 | 0.00
None | manual_sdk_20181213140200 | 100.00 | 0.00 | 0.00
--------------------------------------------------------------------------------------------------------------
Governance/AdvisoryBoardMinutes

This page links to minutes from all Yocto Project Advisory Board meetings.
= 2012 =
* 04 January 2012
* 16 February 2012
* 05 April 2012
Next meeting: 16 May, 2012
= 2011 =
* 29 March, 2011 (call)
* 07 April, 2011 (F2F - San Francisco, CA)
* 3 May, 2011 (call)
* 8 June, 2011 (call)
* 13 July, 2011 (call)
* 24 August, 2011 (F2F - Vancouver, BC)
* 21 September, 2011 (call)
* 26 October, 2011 (F2F - Prague, CZ)
* 09 December 2011
* 14 December 2011
Guidelines for contributing to meta-intel layer

Note: This page is "Work in Progress", it is not finalized yet.
= meta-intel Layer Information =
git repository location:
* git://git.yoctoproject.org/meta-intel
Mailing List:
* List email address: meta-intel@yoctoproject.org
* How to subscribe : https://lists.yoctoproject.org/listinfo/meta-intel
= Guidelines for sending commits to meta-intel =
Please follow general guidelines for contributing to Yocto Project. Here are some of the links.
* Community Guidelines
* Contribution Guidelines
* Recipe & Patch Style Guide
* The Yocto Project Development Manual
= Guidelines for submitting BSPs to meta-intel =
1st follow these general BSP developer's guides:
* Board Support Packages (BSP) - Developer's Guide
* Yocto Project Linux Kernel Development Manual
* To save everybodies time, please make sure you can meet these expectations before submitting a BSP for meta-intel layer
= Expectations for up-streaming a BSP in meta-intel layer =
To keep the meta-intel layer in good shape, all the owners of the BSPs in the layer need to fulfill these expectations.
===1. Make sure the BSP is functioning well at all the times ===
Sometimes dependent layers such as oecore introduce changes which can break layers and BSPs depending on it. The maintainer of the BSP need to regularly validate the BSP with the latest dependent layers, to make sure it is still functioning properly. 
Check this link showing status of the various meta-intel BSPs kept up to date: Last Known Good Commits for meta-intel
===2. Prepare the BSP for release with every meta-intel release ===
This involves these things:
* tag the commit of the release in the meta-intel repository
* Get the "Yocto Project Compatibile" certification for the BSP from here: https://www.yoctoproject.org/webform/yocto-project-compatible-registration
* Build the binary images of the BSP with the meta_tlk layer, and make sure commercial licenses are turned off while building.
* Provide the built release tarball of the BSP to the release engineer for releasing to Yocto Project BSP release area
= Review process for sending commits and BSPs to meta-intel layer =
* All the commits for meta-intel layer must go through the meta-intel mailing list.
* The changes should be sent as individual commits. There are scripts available to prepare and send patches for review. Check http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#how-to-submit-a-change 
* Do not send tarballs of code for review.
= Guidelines for releasing BSPs =
* Third Party BSP Release Guidelines
Hash Equivalence Server

There are two hashserv instances running on on the Yocto Project autobuilder. The private read-write at hashserv.yocto.io:8686 and the read-only public copy at hashserv.yocto.io:8687.
On a VM with 7.5GB of memory and 2 vcpus we created a 150GB fast volume and mounted it at /home/hashserv. Our hashserv.db hovers at about 35GB and has gone as high as 90GB. We setup up automated snapshots for backup.
Run some commands to set up a user and grab the code:
 adduser --system hashserv
 su - hashserv
 git clone https://git.openembedded.org/bitbake
 exit
Copy the following to /etc/systemd/system/hashserv.service
 # /etc/systemd/system/hashserv.service
[Unit]
Description=Bitbake Hash Server
After=network.target
[Service]
User=hashserv
WorkingDirectory=/home/hashserv
Type=simple
ExecStart=/usr/bin/python3 /home/hashserv/bitbake/bin/bitbake-hashserv --bind :8686
[Install]
WantedBy=multi-user.target
Copy the following to /etc/systemd/system/hashserv-readonly.service
 # /etc/systemd/system/hashserv-readonly.service
[Unit]
Description=Bitbake Read-Only Hash Server
After=network.target
[Service]
User=hashserv
WorkingDirectory=/home/hashserv
Type=simple
ExecStart=/usr/bin/python3 /home/hashserv/bitbake/bin/bitbake-hashserv --bind :8687 --read-only
[Install]
WantedBy=multi-user.target
Some commands to enable and start the services:
 systemctl daemon-reload
 systemctl enable hashserv.service hashserv-readonly.service
 systemctl start hashserv.service hashserv-readonly.service 
Then we opened up the firewall for 8686/tcp to our autobuilder private network and opened 8687/tcp to the world. There is no authentication so it's important to use the correct firewall settings.