Skip to content

Conversation

@SashaLsnko
Copy link
Contributor

Description

DO NOT MERGE until https://circleci.atlassian.net/browse/PIPE-5329 and https://circleci.atlassian.net/browse/PIPE-5119 are done

Reasons

We are extending flexible requires with a new status not_run, that defines a job as finished without starting (non-runnable blocked job)

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):

  • Break up walls of text by adding paragraph breaks.
  • Consider if the content could benefit from more structure, such as lists or tables, to make it easier to consume.
  • Keep the title between 20 and 70 characters.
  • Consider whether the content would benefit from more subsections (h2-h6 headings) to make it easier to consume.
  • Check all headings h1-h6 are in sentence case (only first letter is capitalized).
  • Include relevant backlinks to other CircleCI docs/pages.

@SashaLsnko
Copy link
Contributor Author

I didn't update "CircleCI server job status transitions" graph because this will only be available in the next server release. I can make a ticket to update this around the time of the next release so that we don't forget

@SashaLsnko SashaLsnko requested a review from a team November 24, 2025 16:46
@SashaLsnko SashaLsnko force-pushed the add_not_run_job_status branch 2 times, most recently from 035e24b to 0e7ff8f Compare November 27, 2025 16:59
- skipped status is returned as not_run in UI and API
- we don't create pipelines for skip-ci anymore
 (since circleci/workflows-conductor#4527)
- abusive/sanctioned reasons now cause the workflow to fail
@briceicle briceicle force-pushed the add_not_run_job_status branch from 0e7ff8f to 223abc1 Compare December 2, 2025 16:45
@briceicle briceicle marked this pull request as ready for review December 2, 2025 16:51
@briceicle briceicle requested review from a team as code owners December 2, 2025 16:51
pending --> running
pending --> skipped : Only build PRs setting enabled<br/>ci-skip<br/>No project found<br/>Abusive<br/>Sanctioned
pending --> not_run : Only build PRs setting enabled
Copy link
Contributor

@stig stig Dec 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this transition still exist? I think we now either create the pipeline or not based on this setting, but if we create a job that will be allowed to complete.

Copy link
Contributor

@stig stig Dec 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, I see, server. Ho hum. I guess it depends on the version of server... 4.9 should have the same behaviour as Cloud, but legacy versions may not. I stand corrected.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yea it still exists in Server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants