Setup Echidna for continuous deployment from TR branch #93
Conversation
To publish a new Working Draft, run the following steps: - Ensure the local fork of the Git repository is up-to-date - Switch to the TR branch and merge the gh-pages into it - Push the TR branch to the repository on GitHub - Travis CI should detect the push and send the right publication request to Echidna - Check the result of the publication on the public-tr-notifications@w3.org In short, to publish a new version: git checkout TR git merge gh-pages git push w3c TR
LGTM, although this removes the bits of the travis set up used to do actual continuous integration (although these bits aren't using the latest approach for that either, so probably not a big loss at this point). Also, for obvious reason, I can't verify that the publication token is correct :) |
@dontcallmedom Thanks for the review. I think the best way to test whether this works as expected is to give it a spin and try to publish a new WD using the new setup. We can refine the CI steps in subsequent updates, add webidl-check and friends. The .travis.yml used is based on https://github.com/w3c/echidna/wiki/Using-Travis-with-Echidna. Is there a more authoritative guide for using Travis with Echidna? |
Setup Echidna for continuous deployment from TR branch
https://github.com/w3c/echidna/wiki/Using-Travis-with-Echidna is the authoritative source (at least, that's the one I use myself :) |
All seems good, except I forgot to add w3cids to the spec source for all the editors (@dontcallmedom let's continue debug this off the GH). Here's the Echidna error log https://lists.w3.org/Archives/Public/public-tr-notifications/2016Jan/0025.html for the curious. |
|
||
env: | ||
global: | ||
- URL="https://rawgit.com/w3c/mediacapture-depth/TR/ECHIDNA" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if that explains the bug we've encountered, but can you try with http://htmlpreview.github.io/?https://github.com/w3c/mediacapture-depth/TR/ECHIDNA instead? (the publication token will need to be updated in this case I think)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The rawgit.com URL works (well, at least last time we published) for the Presentation API with Echidna, so I believe this cannot be the reason for the failure?
https://github.com/w3c/presentation-api/blob/gh-pages/.travis.yml#L11
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you're right, forgot what I said, I got confused :)
Current status: we hit a bug in Echidna likely related to an upgrade of the backend, see w3c/echidna#251 |
The bug was fixed, and the publication went through this time: https://lists.w3.org/Archives/Public/public-tr-notifications/2016Jan/0030.html; yeah :) |
Excellent, thanks for debugging this with me! |
This is to close an action to pilot the use of automated publication with Echidna with mediacapture-depth. The setup is as such that whenever there's a push to the TR branch, a new WD is published.
@dontcallmedom Please review.