-
Notifications
You must be signed in to change notification settings - Fork 385
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
Remove unused Travis deploy stage #3340
Conversation
The file Also, this cache folder referenced in Line 25 in 0c627dc
|
Good catch. Fixed in 1cc08e0. |
Seems good to go! |
Failed due to unrelated E2E test failure, so merging anyway. |
* Remove unused Travis deploy stage * Remove obsolete bin/deploy-travis-pantheon.sh and deployment-targets cache
* tag '1.3.0': (318 commits) Bump 1.3.0 Add inline styles for custom fonts (#3345) Limit deeply-nesting test to 200 to fix Xdebug error (#3341) Bump 1.3-RC2 (#3335) Sanitize invalid children of amp-story and amp-story-page elements to prevent white story of death (#3336) Remove unused Travis deploy stage (#3340) Implement automated accessibility testing using Axe (#3294) Only add all Google Font style rules in editor context Prevent adding AMP query var to Story URLs in Compatibility Tool Prevent attempting to redirect Stories with rejected validation errors Ensure all AMP scripts (including v0.js) get moved to the head Make sure that media picker is background types are filter correctly. Normalize style[type] attribute quote style after r46164 in WP core Fix phpunit covers tags Bump version to 1.3-RC1 Strip 100% width/height from layout=fill elements Fix issue with cut (#3246) Remove unused Google Fonts SVGs (#3289) Fix resize for non-fit text box (#3259) Use template_dir consistently as signal for transitional mode ...
We're currently not using the
ampconfdemo
environment for testing, which is what the currentdeploy
stage is targeting. In any case, the limit of multidev environments on that site has been overrun doing deploys when pushing to the 1.3 branch currently causes a failure:So we should just eliminate the
deploy
stage and re-focus on getting automatic deployments to a testing environment set up. See #1840, #2084.