Unregistered user charging changes #9636
Open
+40
−23
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rosieyohannan
commented
Sep 29, 2025
| :experimental: | ||
|
|
||
| It is possible for _unregistered_ users to trigger pipelines, and therefore, spend credits. Use the **Prevent unregistered user spend** option to only allow registered users the ability to trigger work that consumes credits. For a full breakdown of the various ways pipelines can be triggered, see the xref:orchestrate:triggers-overview.adoc[Triggers overview]. | ||
| Unregistered users trigger pipelines, spend credits and count towards your plan usage. You can choose to use the **Prevent unregistered user spend** option to only allow registered (users with a CircleCI account) users the ability to trigger work that consumes credits. For a full breakdown of the various ways pipelines can be triggered, see the xref:orchestrate:triggers-overview.adoc[Triggers overview]. |
There was a problem hiding this comment.
@nathanfishcircleci main change here
yaningo
reviewed
Sep 30, 2025
| Docker layer caching (DLC) reduces build times on pipelines where Docker images are built by only rebuilding Docker layers that have changed (read more on the xref:guides:optimize:docker-layer-caching.adoc[Docker Layer Caching] page). DLC costs 200 credits per job run. | ||
|
|
||
| To estimate your DLC cost, look at the jobs in your config file with Docker layer caching enabled, and the number of Docker images you are building in those jobs. There are cases where a job can be written once in a config file but the job runs multiple times in a pipeline, for example, with parallelism enabled. | ||
| To estimate your DLC cost, look at the jobs in your config file with Docker layer caching enabled, and the number of Docker images you are building in those jobs. It is possible for a job to appear once in a config file but the job runs multiple times in a pipeline, for example, with parallelism enabled. |
There was a problem hiding this comment.
The sentence:
It is possible for a job to appear once in a config file but the job runs multiple times in a pipeline, for example, with parallelism enabled.
sounds "weird" (for lack of a better word).
Could we reword it? Something like:
In some cases, a job that appears only once in a config file can run multiple times in a pipeline. For example, with parallelism enabled.
There was a problem hiding this comment.
ooo yes thanks for fixing that weirdness!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Update to sections that mention active or unregistered users to be correct with pricing model
Reasons
Why did you make these changes?
Content Checklist
Please follow our style when contributing to CircleCI docs. Our style guide is here: https://circleci.com/docs/style/style-guide-overview.
Please take a moment to check through the following items when submitting your PR (this is just a guide so will not be relevant for all PRs):