-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Updating to travis dpl v2 #6595
Conversation
Testing to see if compatible with the update and if warnings disappear
Codecov Report
@@ Coverage Diff @@
## master #6595 +/- ##
=======================================
Coverage 93.91% 93.92%
=======================================
Files 169 169
Lines 11970 11991 +21
=======================================
+ Hits 11242 11262 +20
- Misses 728 729 +1
Continue to review full report at Codecov.
|
I couldn't find much documentation on this, but using `api` itself says it's unknown.
re-running failed postgres test |
I think I got the configuration correct this time, |
If this doesn't work, revert to `git`
why would we want to swtich to edge? why not just wait till its released? I.e. is this curiosity, or do you think we should actually make this switch? I'm inclined to wait as it works currently. |
We can wait until V2 is ready |
Yup, I initially looked into this to get rid of the warnings in Travis and then I realized those warnings were for preparation for dpl v2. When it’s released it looks like Parse will be ready and the warnings in Travis will be gone. |
Switched to GitHub Actions for deployments |
Testing to see if compatible with the update and if warnings disappear
Note that
skip_cleanup
has been renamed tocleanup
and defaults tocleanup: false
which is different from pervious version. In addition,deploy
now asks for astrategy
which defaults tostrategy: git
for GitHub pages. The other option isstrategy: api
which looks like it's for all others that are not GitHub pages.This is just a prep PR and can wait until dpl v2 is out of beta to commit