CI/CD Pipeline Deployment Petri Net

Scenario

A CI/CD pipeline where a new source code commit triggers a sequence of build, test, deploy to staging, manual approval, and deploy to production, with limited environment resources.

Key decisions

• Model environments as reusable resource places (BuildEnv, TestEnv, etc.) to enforce resource constraints.
• Use a transition for approval gate that does not require a separate resource token.
• Return tokens to environment places after each stage to allow reusability.

When to reuse this

When you need to analyze the flow and concurrency of changes in a pipeline with shared, limited resources, or communicate the process to stakeholders.