sai | pronouced like 'sigh
kandi X-RAY | sai Summary
kandi X-RAY | sai Summary
sai is a C library. sai has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.
Sai (pronouced like 'sigh', "Trial" in Japanese) is a very lightweight lws-based network-aware distributed CI builder and coordinating server. You can run the sai-builder daemon on any number of devices ad-hoc without central registration or inbound internet access, to offer builds for those platforms... builders can run:. A sai-server daemon runs on a server to receive wss connections from the builders, git update hooks POST signed JSON job matrices from configured git servers, and sai-server coordinates dispatching concurrent jobs to dynamically availabe remote builders of the correct platforms, collecting logs and results. A sai-web server daemon is also available usually on :443 or via a proxy to provide a live web / websockets interface with synamic updates and realtime build logs in the browser, with JWT-authentication for manual job control.
Sai (pronouced like 'sigh', "Trial" in Japanese) is a very lightweight lws-based network-aware distributed CI builder and coordinating server. You can run the sai-builder daemon on any number of devices ad-hoc without central registration or inbound internet access, to offer builds for those platforms... builders can run:. A sai-server daemon runs on a server to receive wss connections from the builders, git update hooks POST signed JSON job matrices from configured git servers, and sai-server coordinates dispatching concurrent jobs to dynamically availabe remote builders of the correct platforms, collecting logs and results. A sai-web server daemon is also available usually on :443 or via a proxy to provide a live web / websockets interface with synamic updates and realtime build logs in the browser, with JWT-authentication for manual job control.
Support
Quality
Security
License
Reuse
Support
sai has a low active ecosystem.
It has 1 star(s) with 0 fork(s). There are 2 watchers for this library.
It had no major release in the last 6 months.
sai has no issues reported. There are no pull requests.
It has a neutral sentiment in the developer community.
The latest version of sai is current.
Quality
sai has no bugs reported.
Security
sai has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
License
sai does not have a standard license declared.
Check the repository for any license declaration and review the terms closely.
Without a license, all rights are reserved, and you cannot use the library in your applications.
Reuse
sai releases are not available. You will need to build from source code and install.
Installation instructions, examples and code snippets are available.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of sai
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of sai
sai Key Features
No Key Features are available at this moment for sai.
sai Examples and Code Snippets
No Code Snippets are available at this moment for sai.
Community Discussions
No Community Discussions are available at this moment for sai.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install sai
Testing is based around CTest, it can either run on the build host inside the container, or run on a separate embedded device. In the separate case, the flow can include steps to flash the image that was built and to observe and drive testing via usually USB tty devices. IO on these additional ttys is logged separately than IO from build host subprocess stdout and stderr.
/home/sai/
git-mirror/
remote git url_project name -- individual git mirrors
jobs/
server hostname-platform name-instance index/ - project_name/ - checkouts and builds occur in here
Building sai produces two different sets of apps and daemons by default, for running on a the server that coordinates the builds and for running on machines that offer the actual builds for particular platforms to one or more servers. You can use cmake options -DSAI_MASTER=0 and -DSAI_BUILDER=0 to disable one or the other. First you must build lws with appropriate options. For redhat type distros, you probably need to add /usr/local/lib to the /etc/ld.so.conf before ldconfig can rgister the new libwebsockets.so. The actual cmake options needed depends on if you are building sai-server and / or sai-builder. Similarly the two daemons bring in different dependencies. Freebsd presents a few differences from Linux.
pkg install bash and other prerequisites like git, cmake etc
Create the sai user via adduser and set the uid to 883.
Create the builder logproxy socket dir one time as root
For script portability, ln -sf /usr/local/bin/bash /bin/bash
As root copy scripts/etc-rc.d-sai_builder-FreeBSD to /etc/rc.d.
As root, edit /etc/rc.conf and add a line sai_builder_enable="YES", then, sudo /etc/rc.d/sai_builder start
Create and prepare /etc/sai/builder/conf as for Linux
/home/sai/
git-mirror/
remote git url_project name -- individual git mirrors
jobs/
server hostname-platform name-instance index/ - project_name/ - checkouts and builds occur in here
Building sai produces two different sets of apps and daemons by default, for running on a the server that coordinates the builds and for running on machines that offer the actual builds for particular platforms to one or more servers. You can use cmake options -DSAI_MASTER=0 and -DSAI_BUILDER=0 to disable one or the other. First you must build lws with appropriate options. For redhat type distros, you probably need to add /usr/local/lib to the /etc/ld.so.conf before ldconfig can rgister the new libwebsockets.so. The actual cmake options needed depends on if you are building sai-server and / or sai-builder. Similarly the two daemons bring in different dependencies. Freebsd presents a few differences from Linux.
pkg install bash and other prerequisites like git, cmake etc
Create the sai user via adduser and set the uid to 883.
Create the builder logproxy socket dir one time as root
For script portability, ln -sf /usr/local/bin/bash /bin/bash
As root copy scripts/etc-rc.d-sai_builder-FreeBSD to /etc/rc.d.
As root, edit /etc/rc.conf and add a line sai_builder_enable="YES", then, sudo /etc/rc.d/sai_builder start
Create and prepare /etc/sai/builder/conf as for Linux
Support
Testing is based around CTest, it can either run on the build host inside the container, or run on a separate embedded device. In the separate case, the flow can include steps to flash the image that was built and to observe and drive testing via usually USB tty devices. IO on these additional ttys is logged separately than IO from build host subprocess stdout and stderr.
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page
