-
Notifications
You must be signed in to change notification settings - Fork 15
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 as build tool? #139
Comments
A quick google of travis latex did not provide any straight-forward answers. |
Travis will work very well in our case. I know how to set it up and can give advice. |
I have started setting up travis. Currently it only uses one branch ( |
👍 |
Instead of creating a release every time this built is run. It can be "uploaded" to the iuf's github website. The pdfs would then be available at iuf.github.io/<whatever-filename-you-choose-here>.pdf so could be sth like latest.pdf, diff2013-2015.pdf, version-2013.pdf, version-2015.pdf, ... well you get the idea. We can even create a rewrite rule on the iuf-server so https://unicycling.org/publications/iuf-rulebook-latest.pdf links to the github page's pdf. I have a deploy script ready that I use here: https://github.com/gossi/php-code-generator can just be copied and modified for usage here. What you think? |
That sounds good to me. |
How can we set this up exactly? (Skype me if you want.) |
I used this tutorial here: http://www.steveklabnik.com/automatically_update_github_pages_with_travis_example/ |
Do you have time to skype tomorrow at 13:30 CET?
|
Potentially. My class officially goes until 2:30 but we're often done On Mon, Sep 7, 2015 at 18:56 Felix Dietze [email protected] wrote:
|
I will be available today.
|
Status update: I have rebased the travis branch with all of the commits we currently have. It is now only one commit. I force pushed that commit to github so pull again before continuing work. I have reset the 2015_prelim branch to remove all of the travis work. I forced push that. Pull again if you need to change the actual rulebook at all. Travis still creates the weird first page. It's likely the result of the gitinfo2 package but I haven't tested that theory. Travis can now successfully install latexdiff and rcs-latexdiff. It then successfully make the rulebook and upload it. It is now getting stuck on make diff. The problem is that travis is only checking out one branch of the git repo but latexdiff needs the other branches in order to run. @gossi and I attempted to pull in the other remote branches, but this does not seem successful. I have yet to find a solution to this. I am stopping for tonight. |
after watching the .travis.yml again, we really should create a scripts folder and move the appropriate parts into their own scripts (install, run, after_success), because these commands look messy and unreadable in yml format. |
Update: The parts are now moved into their own script in Problem now: The Makefile has too much variables... no really too much. That prohibits to find the correct target after the diff task is ran. From travis:
@fdietze: Need help! |
In theory it's working now, but the generated diff does not compile. The diff build ends with:
My guess is that the latex code has some unclosed blocks, which somehow works in the normal build, but breaks the diff. @scotthue @gossi, please take a closer look at the tex code and build logs in the branches |
I tried to look at the log briefly this evening and didn't get anywhere. The length of the log file makes it very difficult to find the problems. Way too many latex warnings and stuff. Maybe we can run things in a more "quiet" mode? |
I'm confused. In the |
By now, latexdiff can do everything we needed rcs-latexdiff for. |
Fine, but why does rcs-latexdiff show up in the log then? On Mon, Jan 18, 2016 at 7:11 PM Felix Dietze [email protected]
|
Make is printing its contents. There is a commented line which contains rcs-latexdiff. |
I put 6503abd (commit before gossis prelim commit) into |
It's a problem with gitinfo:
|
We are using travis now. |
At the moment, felix little script runs on the IUF server to build the rulebook-pdf on-the-fly. I did a little reasearch, it should be possible to use travis-ci.org as build tool for latex. I just want to throw it in, as an alternative (search for 'travis latex' on google, gives some results). With #138 and multi-lingual versions, this might be worth looking into as it wouldn't anybody to change the build-script on the server... it can stay with the repo.
The text was updated successfully, but these errors were encountered: