Skip to content
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

[travis] Don't fail "deploy latest docs" if there's nothing new to deploy #136

Closed
DirectXMan12 opened this issue Dec 1, 2017 · 6 comments
Assignees
Milestone

Comments

@DirectXMan12
Copy link
Member

Currently, since both the actual commit job and the tag job run "deploy latest docs", there can be nothing to deploy (since the tag would be the same, even the "which tag did this build off of" file is the same). We should either not fail when this happens, or not run "deploy latest docs" on tag deploys

@DirectXMan12
Copy link
Member Author

Also seen on the cron job that runs periodically (we could just disable it there).

@frozencemetery
Copy link
Member

(I had disabled it after it failed.)

@DirectXMan12
Copy link
Member Author

you disabled the cron job? That'll cause issues, since the cron job is what rebuilds the Docker images that we use to build. I was suggesting just disabling the docs build if we're in a cron build.

@frozencemetery
Copy link
Member

I didn't think we were using custom docker images for this yet?

@DirectXMan12
Copy link
Member Author

oh, right, I never merged that. Brain fart :-/

@DirectXMan12
Copy link
Member Author

nevermind ;-)

@frozencemetery frozencemetery modified the milestones: 1.3.1, 1.4.1 Feb 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants