Skip to content

skip pipeline if all changed files are under docs/#178

Closed
hl475 wants to merge 1 commit intovllm-project:mainfrom
hl475:skip_pipeline_for_doc_only_changes
Closed

skip pipeline if all changed files are under docs/#178
hl475 wants to merge 1 commit intovllm-project:mainfrom
hl475:skip_pipeline_for_doc_only_changes

Conversation

@hl475
Copy link
Collaborator

@hl475 hl475 commented Sep 29, 2025

we could skip the entire pipleine from bootstrap stage if the changes only touching docs

@hl475 hl475 force-pushed the skip_pipeline_for_doc_only_changes branch from f3c72d1 to cdbfc46 Compare September 29, 2025 19:53
@hl475
Copy link
Collaborator Author

hl475 commented Sep 29, 2025

Copy link
Collaborator

@khluu khluu left a comment

Choose a reason for hiding this comment

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

Thanks! Can you test using a PR with only docs changes to see if it works?

# ----------------------------------------------------------------------

# skip pipeline if all changed files are under docs/
if [[ "${DOCS_ONLY_DISABLE}" != "1" && "${RUN_ALL}" != "1" && "${NIGHTLY}" != "1" ]]; then
Copy link
Collaborator

Choose a reason for hiding this comment

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

can we just do DOCS_ONLY here?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

absolutely! just updated the PR, thanks!

Signed-off-by: Huamin Li <3ericli@gmail.com>
@hl475 hl475 force-pushed the skip_pipeline_for_doc_only_changes branch from cdbfc46 to 56a909d Compare September 29, 2025 20:02
@hmellor
Copy link
Member

hmellor commented Sep 29, 2025

Is this different to #177? Should the older PR be reverted if this PR is preferred?

@hl475
Copy link
Collaborator Author

hl475 commented Sep 29, 2025

@khluu per instructions from https://github.com/vllm-project/ci-infra?tab=readme-ov-file#how-to-test-changes-in-this-repo, could you please help me add into the repo, so I can create a feature branch? Thanks!

@hl475
Copy link
Collaborator Author

hl475 commented Sep 29, 2025

@hmellor

Is this different to #177? Should the older PR be reverted if this PR is preferred?

Yeah, I "think" this PR skips the entire pipeline from bootstrap stage and #177 was done in one step afterwards the stage. I will coordinate with @rzabarazesh to make a decision.

@hmellor
Copy link
Member

hmellor commented Sep 29, 2025

I think prefer this solution as it also skips the image build

@hl475
Copy link
Collaborator Author

hl475 commented Sep 29, 2025

I discussed with @rzabarazesh offline for the preference. We will go with this PR and revert the old one once testing is done.

@hl475
Copy link
Collaborator Author

hl475 commented Sep 30, 2025

will close this PR and use #180 instead

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.

3 participants