add cron job to nightly tests (#7128)#7158
Merged
IanMatthewHuff merged 1 commit intomicrosoft:releasefrom Aug 30, 2019
Merged
Conversation
IanMatthewHuff
requested review from
DonJayamanne,
brettcannon,
ericsnowcurrently and
kimadeline
Codecov Report
@@ Coverage Diff @@
## release #7158 +/- ##
===========================================
- Coverage 58.48% 58.43% -0.06%
===========================================
Files 485 485
Lines 21437 21437
Branches 3462 3462
===========================================
- Hits 12537 12526 -11
- Misses 8122 8135 +13
+ Partials 778 776 -2
Continue to review full report at Codecov.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Port of this PR to release:
#7128
The AzDO pipeline schedules added via the UI have been deprecated. I made a change in master to add in a cron job to do the nightly build. However since this yaml change is only in master branch it only applies to master branch so right now only master branch is getting built on schedule. Pulling in this change will get release on the schedule as well. I've just been building release manually for the last day or two to work around this.
package-lock.jsonhas been regenerated by runningnpm install(if dependencies have changed)