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
Using Travis CI to build stdlib's documentation #45
Comments
I support you in getting push permission. On 12/30/2014 07:53 PM, gallais wrote:
Best regards, |
Gallais, thanks for the travis instance for the standard library! I invited you to the Agda community. Frankly, there is a small moment of hesitation as you do not use your Cheers, On 30.12.2014 21:40, Nicolas Pouillard wrote:
Andreas Abel <>< Du bist der geliebte Mensch. Department of Computer Science and Engineering |
I've slightly edited my profile to make it clearer that "gallais" really is just a convenient way of writing "G. Allais" as in "Guillaume Allais". Hope it clears any doubt. Thanks for the credentials! |
Which is the difference between the documentation generated via Travis and the documentation generated in the gh-pages branch (see https://github.com/agda/agda-stdlib/blob/gh-pages/README.md) ? |
It's done automatically after each commit rather than manually by Ulf. |
Are you sure? Is Ulf manually generating the documentation after each commit? |
Via a script AFAICT https://github.com/agda/agda-stdlib/blob/master/publish-listings.sh |
I see. Isn't it possible to write a post-commit hook in the server side to perform this task? (I don't see any problems to write the hook in the client side, but it is not a good solution). |
If I'm not mistaken, this is precisely what travis is doing: every time a (group of) commit(s) is pushed, it spawns a VM which follows the script described by the .travis.yml file. |
I don't run the script manually obviously. I have a cron job that runs it every night. I'd be happy to turn that off and let Travis to the heavy lifting though. |
@gallais You are right. |
Ok, I have pushed the version using a static executable built from agda/agda here: 532c76f Someone with admin rights on the repository needs to turn travis builds on for agda/agda-stdlib here: https://travis-ci.org/profile/agda Why a static executable? First of all because it guarantees that the build won't fail because agda/agda's master is in a state where agda cannot be built. Second of all, it cuts down the runtime by ~75% as witnessed by these two branches: https://travis-ci.org/gallais/agda-stdlib/branches |
I just flipped the switch. Thanks, G.! |
I've spent the last few days playing with travis to build various projects of mine and applied the newly acquired knowledge to Agda's standard library.
Here is the result
Here are the builds
Here is my repo with the appropriate scripts, travis file and cleaned up gh-pages branch.
Now, travis needs a token from a user allowed to push to the repository in order to deploy the pages so I can't really prepare a pull request that would work. I can either explain to someone how to replicate the work based on the state my repo is in or do it myself if you give me push rights.
Happy holidays,
The text was updated successfully, but these errors were encountered: