Adding CG support, moving analyze_deps to analyze job#4345
Adding CG support, moving analyze_deps to analyze job#4345scbedd merged 18 commits intoAzure:masterfrom
Conversation
|
Can one of the admins verify this patch? |
1 similar comment
|
Can one of the admins verify this patch? |
Codecov Report
@@ Coverage Diff @@
## master #4345 +/- ##
==========================================
+ Coverage 53.45% 53.53% +0.07%
==========================================
Files 10449 10452 +3
Lines 218338 218687 +349
==========================================
+ Hits 116717 117066 +349
Misses 101621 101621
Continue to review full report at Codecov.
|
scbedd
left a comment
There was a problem hiding this comment.
Glad to see the CG stuff works with python. Make these adjustments!
a0db1f9 to
4ee7074
Compare
.azure-pipelines/client.yml
Outdated
| os.name: 'Linux' | ||
| os.vmImage: 'ubuntu-16.04' | ||
| python.version: '2.7' | ||
| OSName: 'Linux' |
There was a problem hiding this comment.
@scbedd it doesn't even look like we use the OSName anywhere so we should probably just delete it. @mikeharder I see you do use OsName as part of a task description in the JS pipeline. Given that the strategy name is used in the job name I personally don't feel it is worth plumbing this extra information through. What do others think?
There was a problem hiding this comment.
Yeah. everywhere in the template we use os.name.
There was a problem hiding this comment.
I must be missing the usages then as I don't see "os.name" or "OSName" being used anywhere in this pipeline.
There was a problem hiding this comment.
You are correct. It's been updated.
@Azure/azure-sdk-eng