Deploy
Ship your code to the infrastructure SysJ built for it.
At a glance
What Deploy gives you.
GitOps by default
Every deployment is a commit to your repository and a sync by Argo CD in your cluster. What is running is always what the repository says.
Environments that promote
Development, staging and production in order. A release moves forward one step at a time, and production can require an approval.
Rollback in one step
Every release is kept. Rolling back is choosing an earlier one, and it goes through the same path as a new release.
Your cluster, your runtime
Workloads run in your account on your cluster. SysJ is not a hosting layer, so your apps keep running whether or not SysJ is reachable.
In detail
How it works.
Releases
A deployment is desired state, not an event you hope finished.
SysJ records what should be running in each environment and lets Argo CD converge on it. If someone changes a workload by hand, it shows up as drift beside the infrastructure drift, not as a mystery.
- Build from any branch or tag
- Image tags pinned per environment
- Drift detection covers workloads as well as infrastructure
Approvals
Production waits for a person. Development does not.
Each environment says whether a release needs approval. The approval screen shows what changes between the running release and the new one, and records who approved it.
- Per-environment approval rules
- Approve, reject or roll back from the console
- Every decision written to the activity log
Preview environments
An environment per pull request, removed when it merges.
Open a pull request and SysJ deploys it to a short-lived namespace with its own address. Merge or close it and the environment is removed, so nothing lingers on your bill.
- Created from the same templates as your real environments
- Removed automatically on merge or close
- Counted against a budget like everything else
Questions
Common questions about Deploy.
- Do I need to know Kubernetes?
- No. SysJ writes the manifests and installs Argo CD in the clusters it builds. The manifests are in your repository if you ever want to read them.
- Which source control does SysJ work with?
- Bitbucket today, with the manifests committed to a repository in your own workspace. SysJ opens changes into it rather than keeping a private copy.
- Can I deploy to a cluster SysJ did not create?
- Deployment targets clusters SysJ manages, because that is what lets it guarantee Argo CD and the platform stack are present. Bringing an existing cluster under management is the import path.
Keep reading
The rest of the platform.
See your own infrastructure as a plan.
Tell us about your team and the cloud you use. We will set up your workspace and walk through your first plan with you.