chewkeanho / automataci Goto Github PK
View Code? Open in Web Editor NEWAn open-source, redistributable, template-guided, and semi-autonomous CI infrastructure readily available your next project.
License: Apache License 2.0
An open-source, redistributable, template-guided, and semi-autonomous CI infrastructure readily available your next project.
License: Apache License 2.0
Add an auto-generative instruction documentation (in Markdown) for static repo in the release job.
a Markdown document is always available.
a Markdown is missing.
No response
Since the Native CI is entirely in shell scripts, I have to port the existing job recipes here. Data source: https://monteur.zoralab.com/en
Template can initiate a Rust workspace immediately.
To initiate Rust workspace, manual efforts are needed.
No response
WASM will be the next generation technology for rendering web interface. It should be supported by default.
WASM is natively supported for Go Programming Language.
WASM for Go Programming Language is not available.
No response
Python can be packaged and upstream as an open-source module via PyPi channel. Hence, let's port its packaging job recipe here.
Python project is able to publish to PyPi without manual efforts.
Publishing to PyPi requires full manual efforts.
No response
WASM will be the next generation technology for rendering web interface. It should be supported by default.
WASM is natively supported for C Programming Language.
WASM for C Programming Language is not available.
Right now, Flatpak is not available for build. We should support it as it is gaining traction in Linux ecosystems.
Flatpak creation is seamlessly included.
Flatpak is not available.
No response
At the moment, the .rpm
package does not close the apt loop due to the missing supply of source.list
file and the required GPG public key. This can be done using the Google Chrome way where each package setup these ecosystem files and close the loop.
All .rpm
package now supplies source.list
and keyring in itself.
.rpm
is missing of source.list
and keyring file.
No response
They both serve the same purposes: working on MISC stuffs. Let's merge them to simplify things.
resources/
is merged completely into src/
directory.
resources/
and src/
are 2 separate directories.
No response
Generate Sha512 checksum file at the release job for temperament checksum purposes.
a sha512.txt checksum file is auto-generated for the uploadable pkg/ directory.
sha512
is practically not available.
No response
At the moment, update instruction is missing out. Please remember to add it in.
No response
There is an update instructions in the engineering specifications.
update instructions are missing.
No response
Since I have this recipe in the past, I should port it in.
Packaging and releasing docker to GitHub Packages is seamless.
Packaging and releasing docker to GitHub Packages requires manual efforts.
No response
Docker can be released on certain platforms like Docker repository or GitHub's packages repository. The process should be ported here.
Docker can be seamlessly up-streamed via Release job.
Docker has to be manually upstreamed.
No response
So that others know how to go about that automataCI
directory.
No response
There is a clear storyline flow of contributing guideline.
Contributing specs are missing.
No response
Since I already got the GitHub Pages CI recipes at hand, I should port it in for seamless execution.
Publishing to GitHub Pages is seamless.
Publishing to GitHub Pages requires manual work.
No response
Since we use Homebrew heavily for environment setup, it's time to close the loop and allow any product built from this system to be usable on Homebrew itself. Let's support it.
Spec: https://docs.brew.sh/Formula-Cookbook
Blog: https://devopstales.github.io/linux/brew-repo/
Release job now release HomeBrew to a designated tap (a GitHub Homebrew-[REPO])
HomeBrew is not supported.
No response
Since by default the label are offering communities related contents, I should add the GitHub Issue filing template in.
A dedicated "Communities" related issue content is filed.
Unavailable.
No response
Apparently, the choco emscripten package installer has a bug where it fails to report its installed dependencies (git-LFS install).
See:
No workaround is available unless the fixes come from the package itself.
choco install emscripten -y
should not yield any error.
AutomataCI re-enables its automatic installation back again while the documented manual steps serve as a redundancy.
choco install emscripten -y
is yielding error due to its internal dependency (likely false alarm mishandling).
Currently, AutomataCI disabled its automatic installation and document the manual steps.
Since there is an offering of "Artwork" tag, I should add its issue template to facilitate easier case filing.
A dedicated "Artwork" related issue template is available.
No "Artwork" related issue template available for use.
No response
As titled.
RPM now has a repo for yum install
.
RPM does not have any repo.
No response
It seems like the the OpenWRT's OPKG package manager is similar to the .deb
package format but much simple due to embedded usage.
Source: https://git.yoctoproject.org/opkg/
Release repo example: https://openwrt.pkgs.org/
Blogs: https://raymii.org/s/tutorials/Building_IPK_packages_by_hand.html
.ipk
is packaged alongside the rest.
.ipk
is not available.
No response
In case someone wants to use it outside of supported technologies.
A default baseline src/
directory is supported with empty .ci jobs for development.
src/
is support missing. How can you forget? haha. Everyone can only use it for Python tech.
No response
Debian and TinyDebian OS are staple in my tech world. Hence, let's port the CI in for a proper build. Data source: refer private ZORALab's Actualizer.
Template can easily initiate a Debian OS build workspace immediately.
To initialize a Debian OS build workspace, manual work are needed.
No response
To make sure developers can operate the repo during offline-mode without requiring an external software like Hugo.
A developer spec document template is available.
No such facility.
No response
Current PyPi Compilation yielded a deprecation notice:
copying Sample/Entity.py -> build/lib/Sample
/home/u0/Documents/holloway/AutomataCI/tools/python-engine/lib/python3.11/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated.
!!
********************************************************************************
Please avoid running ``setup.py`` directly.
Instead, use pypa/build, pypa/installer or other
standards-based tools.
See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details.
********************************************************************************
!!
self.initialize_options()
installing to build/bdist.linux-x86_64/wheel
Please comply.
PyPi is using up-to-date compilation method.
PyPi isn ot using up-to-date compilation method.
package
.No response
The changelogs (md and deb) are badly compiled when dealing with multiple data entries. It's a bug so please fix it.
changelogs are assembled correctly when multiple data entries are available.
changelogs are badly assembled.
./ci.cmd package
.tmp/deb/changelog.gz
pkg/CHANGELOG.md
and tmp/deb/changelog
.No response
Don't leave out Red Hat's ecosystem's rpm
distributions.
NativeCI can package valid GPG-signed RPM.
No possible.
No response
The latest
changelog entries should be sealed into the version number autonomously during the Release job.
latest
changelog entries are sealed autonomously in Release job.
latest
changelog entries had to be sealed manually.
No response
Since Native CI is callable externally, let' set GitHub Action to call all those default commands then.
GitHub Actions are implemented.
GitHub Actions are not supported (for now).
No response
The Stop recipe should issue the deactivate
user guide. Right now, it's still in placeholder mode.
Stop recipe for Python issues deactivate
user guide.
Stop recipe is not doing anything.
No response
Since the Native CI is entirely in shell scripts, I have to port the existing job recipes here. Data source:
https://github.com/ChewKeanHo/Template-Python
Template can initiate a Python workspace immediately.
To initiate Python workspace, manual efforts are needed.
No response
Ensures the PyPi packages are exported to targeted upstream.
PyPi packages can be seamlessly upstream to a targeted remote server.
PyPi upstream is unavailable.
No response
Since we use Chocolatey extensively to setup the Windows environment, it's time to create its release recipe and close the loop.
Doc: https://docs.chocolatey.org/en-us/create/create-packages
Chocolatey is supported natively.
Chocolatey is not supported.
No response
Reprepro is the one responsible for assembling a private .deb
repo. Let's enable it.
User can source .deb
repo using apt
.
User is unable to source .deb
repo using apt
.
No response
Since I got Debian deb
distribution ecosystem and its build specs, I should port it in so that the packaging and releasing processes are simply seamless.
packing .deb
for Debian-based system are seamless.
manual efforts are needed.
No response
At the moment, the .deb
package does not close the apt
loop due to the missing supply of source.list
file and the required GPG public key. This can be done using the Google Chrome way where each package setup these ecosystem files and close the loop.
All .deb
package now supplies source.list
and keyring in itself.
.deb
is missing of source.list
and keyring file.
No response
It's safe to say I can deploy the native CI (not relying on external CI services) to develop a product regardless whether the template will be used here or elsewhere. So, let's integrate it in.
Next new spin of repository has native CI included in. Target are:
start.cmd
- initiate the project development
prepare.cmd
- update the project to a stated version
test.cmd
- initiate project test sequences.
build.cmd
- initiate project build sequences.
package.cmd
- initiate project package sequences.
release.cmd
- initiate project release sequences.
stop.cmd
- initiate project stop sequences.
CI is not available and has to be manually included.
No response
Nim programming language is where I want to go next. Let's initialize it.
Template can initiate a Nim workspace immediately.
To initiate Nim workspace, manual efforts are needed.
No response
Apparently, if the releases directory is missing or malformed, Release job will hard reset the root repository to its first commit and official nuke the project. This is not desirable and safety check must me added here to prevent this from happening again.
Safety check is added to GIT::hard_reset_to_init
function to cross-check its root against the root repository before actually performing the reset.
No safety check is added.
./ci release
stage, observe that it shall erase the project and attempting to push to remote.No response
Generate a gpg detach signature checksum file at the release job for temperament checksum purposes.
gpg detach signature checksum files are auto-generated for the uploadable pkg/ directory.
gpg detach signature feature is practically not available.
No response
Since the Native CI is entirely in shell scripts, I have to port the existing job recipes here. Data source: https://monteur.zoralab.com/en
Template can initiate a Go workspace immediately.
To initiate Go workspace, manual efforts are needed.
No response
The conventional CI used .tar.gz
/ .tar.xz
and zip
pacakges.
Package recipes automatically package .tar.XX
and .zip
for all outputs.
Non is available.
No response
Please state your question in a brief and ended with question mark (?). You
may include sub-questions with "if cases" to communicate more effectively
instead of many 'ping-pong' passing.
Comme indiqué dans le titre.
Please provide a short description of what you are trying to ask.
Please list out all your research artifacts that you did (e.g. link, blog post,
documentations, and etc) for us to gauge your context and current efforts. We
may not reply and will close the ticket with perjuidice if this section remains
empty and unconvincing.
Please drag and drop the necessary data files (e.g. screenshot, logs, etc)
below.
Since the Native CI is entirely in shell scripts, I have to port the existing job recipes here. Data source: https://github.com/hollowaykeanho/cwr
Template can initiate a C workspace immediately.
To initiate C workspace, manual efforts are needed.
No response
Please state your question in a brief and ended with question mark (?). You
may include sub-questions with "if cases" to communicate more effectively
instead of many 'ping-pong' passing.
zzzz
Please provide a short description of what you are trying to ask.
Please list out all your research artifacts that you did (e.g. link, blog post,
documentations, and etc) for us to gauge your context and current efforts. We
may not reply and will close the ticket with perjuidice if this section remains
empty and unconvincing.
Please drag and drop the necessary data files (e.g. screenshot, logs, etc)
below.
A customizable clean job recipe.
customizable clean job is available.
clean job is not available.
No response
Basically nuke the entire repo back to initial state.
Purge is available.
Purge is not available.
No response
Appearently, DEB requires its own changelog generator. Let's port it from ZORALab's Monteur.
Changelog is automatically built and generated.
Changelog is not available.
No response
Generate Sha256 checksum file at the release job for temperament checksum purposes.
a sha256.txt checksum file is auto-generated for the uploadable pkg/ directory.
sha256
is practically not available.
No response
Since the Native CI is entirely in shell scripts, I have to port the existing job recipes here. Data source: see private repo contract 2022-12-25.
Template can initiate a NodeJS workspace immediately.
To initiate NodeJS workspace, manual efforts are needed.
It appears Flatpak allows private repo export for Release job. Let's do it.
Flatpak is exported and import struction is generated for customer to easily import the app.
Flatpak repo export is not available.
No response
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.