You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/guides/modules/orchestrate/pages/jobs-steps.adoc
+86-1Lines changed: 86 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,7 +69,92 @@ There are four types of jobs:
69
69
70
70
You can set the type of a job by adding the `type` key to the job configuration.
71
71
72
-
See the xref:reference:ROOT:configuration-reference.adoc#job-type[Confirguration reference] page for more information on how to use the different job types.
72
+
See the xref:reference:ROOT:configuration-reference.adoc#job-type[Configuration reference] page for more information on how to use the different job types.
73
+
74
+
=== Job status transitions
75
+
76
+
The following diagram and table shows the possible job statuses and transitions.
77
+
78
+
.CircleCI cloud job status transitions
79
+
[mermaid]
80
+
----
81
+
stateDiagram-v2
82
+
direction TB
83
+
[*] --> blocked
84
+
85
+
state "blocked or not running" as pending
86
+
blocked --> pending : Job instructed to start but not yet started
87
+
blocked --> unauthorized : Trying to use a context without permission
88
+
89
+
pending --> running
90
+
91
+
pending --> blocked : Rerun
92
+
93
+
running --> canceled
94
+
pending --> canceled
95
+
blocked --> canceled
96
+
97
+
pending --> failed : Abusive / Sanctioned
98
+
running --> failed
99
+
running --> success
100
+
101
+
failed --> [*]
102
+
success --> [*]
103
+
canceled --> [*]
104
+
unauthorized --> [*]
105
+
----
106
+
107
+
.CircleCI server job status transitions
108
+
[mermaid]
109
+
----
110
+
stateDiagram-v2
111
+
direction TB
112
+
[*] --> blocked
113
+
114
+
state "blocked or not running" as pending
115
+
blocked --> pending : Job instructed to start but not yet started
116
+
blocked --> unauthorized : Trying to use a context without permission
|Blocked/Not Running | All jobs start off in a blocked state. Jobs called `build` move on to a Not Running state before starting.
142
+
143
+
|Running | Job is running.
144
+
145
+
| On Hold | The job is running but requires manual approval.
146
+
147
+
| Not Run | The job is skipped.
148
+
149
+
| Success | The job succeeded.
150
+
151
+
| Failed | The job failed or terminated for unknown reasons.
152
+
153
+
| Canceled | The job was canceled. An actor might cancel a job, or cancel a workflow. A job may be cancelled due to auto-cancellation. Support engineers can force cancellation of a job.
154
+
155
+
| Unauthorized | The job uses a restricted context and the actor that triggered the work does NOT have access to that context.
Copy file name to clipboardExpand all lines: docs/guides/modules/orchestrate/pages/pipelines.adoc
+24Lines changed: 24 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -114,6 +114,30 @@ Once you have set up a pipeline you need to set up a trigger to connect it to. S
114
114
--
115
115
====
116
116
117
+
== Pipeline states
118
+
119
+
The following diagram outlines the various states a pipeline can be in.
120
+
121
+
.Pipeline states
122
+
[mermaid]
123
+
----
124
+
stateDiagram-v2
125
+
direction TB
126
+
state "Is this dynamic config?" as isdynamic
127
+
[*] --> isdynamic
128
+
state "setup-pending" as setuppending
129
+
isdynamic --> setuppending : Yes
130
+
isdynamic --> pending : No
131
+
132
+
setuppending --> setup
133
+
setup --> pending
134
+
pending --> created
135
+
pending --> errored
136
+
created --> [*]
137
+
errored --> [*]
138
+
139
+
----
140
+
117
141
== Pipeline parameters
118
142
119
143
Pipeline parameters are declared using the `parameters` key at the top level of a `.circleci/config.yml` file. Pipeline parameters can be referenced by value and used as a configuration variable under the scope `pipeline.parameters`.
NOTE: If you rerun a workflow containing a job that was previously re-run with SSH, the new workflow runs with SSH enabled for that job, even after SSH capability is disabled at the project level.
847
847
848
848
[#states]
849
-
=== Workflow states
849
+
== Workflow states
850
+
851
+
The following state diagram shows the possible states and transitions of a workflow:
852
+
853
+
.CircleCI cloud workflow states
854
+
[mermaid]
855
+
----
856
+
stateDiagram-v2
857
+
[*] --> running
858
+
859
+
running --> success
860
+
861
+
running --> failing
862
+
863
+
running --> on_hold
864
+
on_hold --> canceled
865
+
on_hold --> running : approval job
866
+
on_hold --> success
867
+
868
+
running --> canceled
869
+
failing --> failed
870
+
failing --> canceled
871
+
872
+
running --> failed
873
+
running --> error
874
+
running --> unauthorized
875
+
876
+
running --> queued
877
+
queued --> running: queued as part of a serial group
878
+
879
+
success --> [*]
880
+
canceled --> [*]
881
+
failed --> [*]
882
+
error --> [*]
883
+
unauthorized --> [*]
884
+
885
+
----
886
+
887
+
.CircleCI server workflow states
888
+
[mermaid]
889
+
----
890
+
stateDiagram-v2
891
+
[*] --> running
892
+
893
+
running --> success
894
+
895
+
running --> failing
896
+
897
+
running --> on_hold
898
+
on_hold --> canceled
899
+
on_hold --> running : approval job
900
+
on_hold --> success
901
+
902
+
running --> canceled
903
+
failing --> failed
904
+
failing --> canceled
905
+
906
+
running --> failed
907
+
running --> error
908
+
running --> not_run
909
+
running --> unauthorized
910
+
911
+
running --> queued
912
+
queued --> running: queued as part of a serial group
913
+
914
+
success --> [*]
915
+
canceled --> [*]
916
+
failed --> [*]
917
+
error --> [*]
918
+
unauthorized --> [*]
919
+
not_run --> [*]
920
+
921
+
----
850
922
851
923
Workflows may have one of the following states:
852
924
@@ -858,10 +930,6 @@ Workflows may have one of the following states:
858
930
| Workflow is in progress
859
931
| No
860
932
861
-
| NOT RUN
862
-
| Workflow never started
863
-
| Yes
864
-
865
933
| CANCELED
866
934
| Workflow canceled before it finished
867
935
| Yes
@@ -889,10 +957,16 @@ Workflows may have one of the following states:
889
957
| UNAUTHORIZED
890
958
| One or more of the jobs terminated with a `unauthorized` job status. The user who triggered the pipeline or approved an approval job does not have access to a required restricted context.
891
959
| Yes
960
+
961
+
| QUEUED
962
+
| The workflow is queued due to being part of a serial group. For more information, see the xref:controlling-serial-execution-across-your-organization.adoc[Controlling serial execution across your organization] page.
963
+
| No
964
+
892
965
|===
893
966
894
967
NOTE: After 90 days non-terminal workflows are automatically cancelled by CircleCI.
0 commit comments