You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently our .travis.yml file does not contain instructions to build and deploy our DESC Note - we need to copy and edit the relevant lines from the .travis.yml file that start_paper provided into the main travis file. Also, I notice that two of thedeployment conditions have been commented out: we should uncomment those, we only want the html and pdf files to be updated when the master branch is updated. Want to have a go at this, @aimalz ? If I were you, I'd carry out this "hot fix" by editing files on the master branch directly (even using the web editor), using your admin privileges; then we can check that things get deployed correctly when we next merge some other issue's PR.
The text was updated successfully, but these errors were encountered:
I've been fiddling with the .travis.yml and am stuck on a bug in the compilation of the LaTeX that doesn't happen locally. I've spent a lot of time on this without figuring it out so think it's time to ask for help. Sorry to bother you with this!
On Mon, Mar 27, 2017 at 10:48 AM, Alex Malz ***@***.***> wrote:
I've been fiddling with the .travis.yml and am stuck on a bug in the
compilation of the LaTeX that doesn't happen locally. I've spent a lot of
time on this without figuring it out so think it's time to ask for help.
Sorry to bother you with this!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#62 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AArY97hzNKCfbjpMY1eUFPaJxQmkzYlMks5rp_ZugaJpZM4MoYo8>
.
Currently our .travis.yml file does not contain instructions to build and deploy our DESC Note - we need to copy and edit the relevant lines from the
.travis.yml
file thatstart_paper
provided into the main travis file. Also, I notice that two of thedeployment conditions have been commented out: we should uncomment those, we only want the html and pdf files to be updated when the master branch is updated. Want to have a go at this, @aimalz ? If I were you, I'd carry out this "hot fix" by editing files on the master branch directly (even using the web editor), using your admin privileges; then we can check that things get deployed correctly when we next merge some other issue's PR.The text was updated successfully, but these errors were encountered: