Set up continuous deployment process for development branch #2284
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
epiclabsDASH
changed the title
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.
Configures a continuous deployment process for development branch. Whenever changes are pushed to development branch, and only if build and test tasks were successful, resulting files are automatically deployed and can be tested using the url http://reference.dashif.org/dash.js/development/samples/dash-if-reference-player/index.html.
Deployment is done in development folder (instead of nightly one) to not interfere in current auto deployment process. Once this change is pushed and tested successfully for a few weeks, we will replace nightly build with this new process.