[
https://issues.apache.org/jira/browse/GEODE-8406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17171774#comment-17171774
]
ASF GitHub Bot commented on GEODE-8406:
---------------------------------------
rhoughton-pivot commented on pull request #5427:
URL: https://github.com/apache/geode/pull/5427#issuecomment-669521913
> does this affect PRs only or regular pipelines as well? Do I understand
correctly that this will cause the jobs to run super-fast? That will mess with
timing statistics for each job...but I guess that's my problem. The whole
reason for doing it this way instead of as git resource exclusions is because
of required PR checks, yes?
This makes all the jobs run quick, without starting a heavy-lifter, in the
event that the PR is non-testable. We could experiment with twiddling the PR
resource to two versions, one for "code" and one for "no-code". Code would run
as-is, no-code would only set "status:passed". We'd have to be careful about
our GitHub API quotas if we did that; the resource uses a lot more API calls if
we start filtering by file/directory.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> enable early-return for CI only changes in Geode Concourse
> ----------------------------------------------------------
>
> Key: GEODE-8406
> URL: https://issues.apache.org/jira/browse/GEODE-8406
> Project: Geode
> Issue Type: Improvement
> Components: ci
> Reporter: Robert Houghton
> Priority: Major
> Labels: pull-request-available
>
> The Geode Concourse PR pipeline pulls the _ci_ scripts from upstream, not the
> code under test. Ergo, CI changes are untestable by the main CI itself, and
> running the PR jobs is useless, and costly.
> GitHub does not allow granular control of what directories require a _status_
> to allow merging, so our solution is to short circuit the work for CI-only
> PRs, allowing the status to be set.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
