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
{{ message }}
This repository was archived by the owner on Sep 6, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: jekyll/_cci2/admin-faq.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ published: true
12
12
13
13
#### Can I monitor available build containers?
14
14
15
-
Yes, refer to the Introduction to Nomad Cluster Operation document for details. Refer to the [Administrative Variables, Monitoring, and Logging]({{site.baseurl}}/2.0/monitoring/) document for how to enable additional container monitoring for AWS.
15
+
Yes, refer to the [Introduction to Nomad Cluster Operation]({{site.baseurl}}/2.0/nomad) document for details. Refer to the [Administrative Variables, Monitoring, and Logging]({{site.baseurl}}/2.0/monitoring/) document for how to enable additional container monitoring for AWS.
16
16
17
17
#### How do I provision admin users?
18
18
@@ -45,7 +45,7 @@ New Nomad Clients joining the fleet will use the new passphrase. Existing Nomad
45
45
46
46
#### How can I gracefully shutdown a Nomad Clients?
47
47
48
-
Refer to the Introduction to Nomad Cluster Operation document for details.
48
+
Refer to the [Introduction to Nomad Cluster Operation]({{site.baseurl}}/2.0/nomad) document for details.
49
49
50
50
#### Is it possible to run iOS/macOS builds on CircleCI?
51
51
@@ -66,7 +66,7 @@ We set the services box to have termination protection in AWS. We also write to
66
66
67
67
#### Do the builders store any state?
68
68
69
-
They can be torn down without worry as they don't persist any data.
69
+
They can be torn down without worry as they don't persist any data.
70
70
71
71
72
72
#### How do I verify TLS settings are failing?
@@ -137,7 +137,7 @@ Replicated starts many Docker containers to run CCIE, so it may be useful to che
137
137
You should see something similar to this output:
138
138
139
139
```
140
-
sudo docker ps
140
+
$ sudo docker ps
141
141
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
142
142
03fb873adf26 <service-box-ip>:9874/circleci-frontend:0.1.149242-d650d3c "/docker-entrypoint.s" 3 days ago Up 3 days 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp, 0.0.0.0:4434->4434/tcp e53e4f74259a6ec0a268d8c984ac6277
143
143
113b9ea03b46 <service-box-ip>:9874/circleci-slanger:0.4 "/docker-entrypoint.s" 3 days ago Up 3 days 0.0.0.0:4567->4567/tcp, 0.0.0.0:8081->8080/tcp d262cc492bd5d692d467f74d8cc39748
Copy file name to clipboardExpand all lines: jekyll/_cci2/api-job-trigger.md
+10-9Lines changed: 10 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -45,15 +45,16 @@ and refers to the name of your branch.
45
45
For a complete reference of the API,
46
46
see the [CircleCI API Documentation]({{ site.baseurl }}/api/v1-reference/).
47
47
48
-
**Note:**
49
-
It is possible to trigger [workflows]({{ site.baseurl }}/2.0/workflows/) with the CircleCI API, using a new endpoint, see the Trigger a Build by Project section of the [CircleCI API Projects Documentation]({{ site.baseurl }}/api/v1-reference/#new-project-build).
50
-
51
-
Jobs triggered with the API may contain a `workflows` section.
52
-
These workflows do **not** have to reference the job
53
-
you trigger with the API.
54
-
Jobs triggered with the API do **not** have access to environment variables
55
-
created for [a CircleCI Context]({{ site.baseurl }}/2.0/contexts/).
56
-
Instead, define these variables at the [Project level]({{ site.baseurl }}/2.0/env-vars/#setting-an-environment-variable-in-a-project).
48
+
**Important Considerations When Triggering A Job Via The API**
49
+
50
+
- Jobs triggered with the API may contain a `workflows` section
51
+
- Your workflow does **not** have to reference the job you triggered with the API
52
+
- Jobs that are triggered via the API do **not** have access to environment
53
+
variables created for [a CircleCI Context]({{ site.baseurl }}/2.0/contexts/)
54
+
- If you wish to use environment variables they have to be defined at the [Project level]({{ site.baseurl }}/2.0/env-vars/#setting-an-environment-variable-in-a-project)
55
+
- It is currently not possible to trigger a single job if you are using CircleCI 2.1 and Workflows
56
+
- It is possible to trigger [workflows]({{ site.baseurl }}/2.0/workflows/) with the CircleCI API, using the [Trigger a Build by Project]({{ site.baseurl}}/api/v1-reference/#new-project-build) endpoint
Copy file name to clipboardExpand all lines: jekyll/_cci2/building-docker-images.md
+3-1Lines changed: 3 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,9 @@ jobs:
27
27
28
28
When `setup_remote_docker` executes, a remote environment will be created, and your current [primary container][primary-container] will be configured to use it. Then, any docker-related commands you use will be safely executed in this new environment.
29
29
30
-
**Note:** `setup_remote_docker` is not currently compatible with the `machine` or the `macos` executors.
30
+
**Note:** The use of the `setup_remote_docker` key is reserved for configs in
31
+
which your primary executor _is_ a docker container. If your executor is
32
+
`machine`or `macos` (and you want to use docker commands in your config) you do not need to use the `setup_remote_docker` key.
0 commit comments