Do a shallow clone for Docker tests. #42966
Conversation
This comment has been minimized.
This comment has been minimized.
typescript-bot
added
the
For Uncommitted Bug
|
I just realized we always pull right after - but I don't know why we do that either. Do we need that step @weswigham? |
|
Probably just force of habit on my part; I always pull after a clone to fetch remote refs, and that may have made its way into the scripts. |
|
Okay, cool! Newest change doesn't pull either. @typescript-bot test this |
|
Heya @DanielRosenwasser, I've started to run the extended test suite on this PR at 6bc1140. You can monitor the build here. |
|
@typescript-bot user test this |
|
Heya @weswigham, I've started to run the parallelized community code test suite on this PR at 6bc1140. You can monitor the build here. |
|
The user suite test run you requested has finished and failed. I've opened a PR with the baseline diff from master. |
|
Looks like it successfully sent a PR - all good? |
| FROM node:current | ||
| RUN npm install -g @microsoft/rush | ||
| RUN git clone https://github.com/Azure/azure-sdk-for-js.git /azure-sdk | ||
| RUN git clone --depth 1 https://github.com/Azure/azure-sdk-for-js.git /azure-sdk |
There was a problem hiding this comment.
We may combine these run into one line? Especially after big IO.
Just saves a bit of time and work since we don't need the full history.