- Shell 100%
|
|
||
|---|---|---|
| .forgejo | ||
| .gitea | ||
| .github | ||
| .gitlab | ||
| .husky | ||
| .provisioning | ||
| .vscode | ||
| .woodpecker | ||
| modules | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .prettierignore | ||
| .prettierrc | ||
| autogen.sh | ||
| CODE_OF_CONDUCT.md | ||
| devWorkflow.uxf | ||
| Dockerfile.probe | ||
| Dockerfile.sdk | ||
| LICENSE.txt | ||
| package.json | ||
| probe.sh | ||
| README.md | ||
| requirements.txt | ||
| source.sh | ||
| trivy.yaml | ||
| yarn.lock | ||
Description
RealmProbe was meant to check if CI/CD provides minimal as well as maximum set of capabilities, allowing rapid builds.
Is only for testing if CI/CD can be anyhow usable and at what level.
Contains as well:
- Code coverage
- System toolkits
Builds
Lurk for the latest "Green tick" next to repo commits, would point the status of probe.
Important
In the
.provisioningdirectory there are Woodpecker CI/CD configuration files for building OCI images, both being shipped on local git instance and Docker Hub. What's being executed on probed instances is in.woodpecker,.forgejo/workflows,.gitea/workflows,.github/workflows,.gitlab-ci.yml.
Development
Warning
Please read the Code of Conduct and Apache 2.0 License before contributing.
Make sure to run source source.sh and use vscode / any IDE which supports Prettier & Husky for git integrity.
This repository can utilize Git LFS for handling binary files.