Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci-parser: fix detection of lite CI pipelines #354

Merged
merged 1 commit into from
Jun 18, 2019

Conversation

richardlau
Copy link
Member

Fixes: #353

cc @sam-github

@codecov
Copy link

codecov bot commented Jun 13, 2019

Codecov Report

Merging #354 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #354   +/-   ##
=======================================
  Coverage   75.95%   75.95%           
=======================================
  Files          21       21           
  Lines        1364     1364           
=======================================
  Hits         1036     1036           
  Misses        328      328
Impacted Files Coverage Δ
lib/ci/ci_type_parser.js 80.95% <ø> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8d64553...433293a. Read the comment docs.

Copy link
Contributor

@sam-github sam-github left a comment

Choose a reason for hiding this comment

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

RSLGTM, though will it match with or with the trailing pipeline? Should both cases be tested? I don't know, just asking, and thanks for fixing this.

@richardlau
Copy link
Member Author

RSLGTM, though will it match with or with the trailing pipeline? Should both cases be tested? I don't know, just asking, and thanks for fixing this.

There's still a test that has the /pipeline suffix that I left alone (and still passes):

'https://ci.nodejs.org/job/node-test-pull-request-lite-pipeline/7213/pipeline/'

@sam-github
Copy link
Contributor

I'm not sure what the policy is here, if it is like node core, but I'm in support of fast-tracking and publishing this fix.

@joyeecheung
Copy link
Member

joyeecheung commented Jun 18, 2019

@sam-github The policy is basically "this can land whenever it gets an approval from someone who can write to this repo" or at least that's what we have been doing.

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.

detection of lite ci is broken again?
4 participants