2 min lesson
The toolchain archetype survives a vendor swap
Put yourself in this case: "A prospect runs Jenkins and is anxious that your reference customers use GitHub Actions. Calm them." Give the clearest next step.
Step 1 of 4
Enterprises run a zoo of CI/CDContinuous Integration / Continuous Delivery. The automated pipeline that builds, tests and ships code so changes reach production safely and often. Press Enter for the full definition. tools: GitHub Actions, GitLab CI, Jenkins, CircleCI, Argo, Spinnaker, Azure DevOps. Junior engineers see chaos. The field engineer sees one archetype instantiated in different syntax. Name the archetype and you can talk to any customer's stack without having memorized their YAML.
Learn more
Advanced table
Concept (archetype)
- Concept (archetype)
- Pipeline definition
- GitHub Actions
- workflow YAML
- GitLab CI
- .gitlab-ci.yml
- Jenkins
- Jenkinsfile (Groovy)
- Concept (archetype)
- Unit of work
- GitHub Actions
- job / step
- GitLab CI
- job / stage
- Jenkins
- stage / step
- Concept (archetype)
- Runner
- GitHub Actions
- runner
- GitLab CI
- runner
- Jenkins
- agent / node
- Concept (archetype)
- Reusable logic
- GitHub Actions
- composite/reusable workflow
- GitLab CI
- include / template
- Jenkins
- shared library
- Concept (archetype)
- Secrets
- GitHub Actions
- encrypted secrets / OIDCOpenID Connect. The modern single sign-on standard, built as an identity layer on top of OAuth 2.0. Where SAML is XML and enterprise-legacy, OIDC is JSON and what newer tools implement first. Press Enter for the full definition.
- GitLab CI
- CI variables / OIDCOpenID Connect. The modern single sign-on standard, built as an identity layer on top of OAuth 2.0. Where SAML is XML and enterprise-legacy, OIDC is JSON and what newer tools implement first. Press Enter for the full definition.
- Jenkins
- credentials store
| Concept (archetype) | GitHub Actions | GitLab CI | Jenkins |
|---|---|---|---|
| Pipeline definition | workflow YAML | .gitlab-ci.yml | Jenkinsfile (Groovy) |
| Unit of work | job / step | job / stage | stage / step |
| Runner | runner | runner | agent / node |
| Reusable logic | composite/reusable workflow | include / template | shared library |
| Secrets | encrypted secrets / OIDCOpenID Connect. The modern single sign-on standard, built as an identity layer on top of OAuth 2.0. Where SAML is XML and enterprise-legacy, OIDC is JSON and what newer tools implement first. Press Enter for the full definition. | CI variables / OIDCOpenID Connect. The modern single sign-on standard, built as an identity layer on top of OAuth 2.0. Where SAML is XML and enterprise-legacy, OIDC is JSON and what newer tools implement first. Press Enter for the full definition. | credentials store |
Migrate a customer from Jenkins to GitHub Actions and only the syntax moves: where the trigger is declared, how a job is spelled, how secrets are referenced. The structure holds. Same trigger→build→verify→gate→promote shape, same artifact-once-promote-everywhere rule, same red gates, same SoDSeparation of Duties. Short for separation of duties: the rule that authoring, approving and deploying a change never sit with one person. Auditors use the acronym; the control is the same. Press Enter for the full definition., same deploy strategy.
That's why Cursor's value transfers across the swap. It authors and refactors any of these pipeline definitions, reading and writing the YAML or Groovy and applying the same archetype regardless of vendor.
If asked 'do you know Spinnaker / Argo / Jenkins?' don't bluff depth. Say: 'I reason about CI/CDContinuous Integration / Continuous Delivery. The automated pipeline that builds, tests and ships code so changes reach production safely and often. Press Enter for the full definition. as one archetype - trigger, build, verify, gate, promote. Vendors differ in syntax and where the gates live, not in shape. So I can land Cursor on any of them and Cursor itself is great at authoring the vendor-specific config.'
Learn more
Optional practice
Practice: The toolchain archetype survives a vendor swap
QWhy does 'build the artifact once and promote the same artifact through environments' matter?