Add a separate playbook for subdomains, reduce deployment time #1361
Conversation
This file contains 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Current runtime in jenkins is 1h18min, this is not very handy for quick fixes or deployments.$159 \cdot 38 = 6042$ Tasks
This is related to the symlink strategy we are using in the
galaxyproject.galaxyrole. It saves ~ 16G disk space for EU by symlinking static files instead of duplicating them for each subdomain's static directory. Because ansible tasks are quite slow and there is a task for each file in each subdomain this scales quite badly with