Pillars of Creation documentation
Pillars of Creation is SmoothGlue's shared GitLab CI/CD pipeline. It provides framework builds, source and artifact analysis, evidence collection, and release jobs. Your project's files and settings determine which jobs run.
Use these guides and references from your application project. You do not need access to the Pillars implementation repository to read or use this documentation. To run the pipeline, your platform team must supply a template that GitLab can access, an approved revision, and suitable runners.
Start here
- Read how Pillars works for its stages, responsibilities, and outputs.
- Follow Use the Pillars pipeline to connect your project, configure its jobs, and verify the first pipeline.
- Review your framework's prerequisites below before running its build. Some build jobs also publish packages to a staging registry.
Already have a failed run? Start with Troubleshoot Pillars.
Find your framework
| Application | Prerequisites, jobs, and settings |
|---|---|
| JavaScript or TypeScript using npm | npm |
| Java using Gradle | Gradle |
| Python using pip | pip |
| Python using Poetry | Poetry |
| Go | Go |
| C or C++ using CMake | CMake |
| .NET | .NET |
Framework detection selects shared jobs; it does not generate missing application files or credentials. For a container build, also check the Dockerfile and image settings.
Configure your pipeline
| I need to… | Read |
|---|---|
| Set variables, select jobs, or understand failure rules | Pipeline configuration |
| Configure builds, tests, or package registries | Framework jobs |
| Configure scanners, SonarQube, or web tests | Analysis jobs |
| Build Helm charts or Zarf packages, update manifests, or publish releases | Delivery and releases |
| Look up a variable's declared default and scope | Variable defaults |
| Find SBOMs and understand evidence outputs | SBOM generation and evidence |
Use the functional reference for prerequisites and behavior, then the defaults catalog for exact values. Installation overrides can change those values; keep the approved template revision with your pipeline record.
Resolve a problem
- Pipeline not created
- A job is missing or skipped
- A build or test failed
- A scanner or application test failed
- Evidence or release output is missing
Keep the pipeline URL, template revision, affected job, and relevant non-secret error when asking your platform team for help.