caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Helmut Brandl <helmut.brandl@gmx.net>
To: caml users <caml-list@inria.fr>
Subject: [Caml-list] Auto deploy to gh-pages with travis-ci
Date: Mon, 29 Apr 2019 18:33:06 -0500	[thread overview]
Message-ID: <BD8DAB77-7613-49DC-8AF4-0770D3E1280D@gmx.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]

Hello list,

I have used the ocaml/ocaml-ci-scripts to start continuous integration with travis-ci. I have copied the ‘.travis.yaml’ file into my repository and started pushing to my GitHub repo. With that everything works fine. Travis builds the project, runs the tests and creates the documentation (I use ‘dune build’, ‘dune build @runtest’ and ‘dune build @doc').

Now I wanted to start an automatic deploy to GitHub pages and added the following to my ‘.travis.yaml’ file:

deploy:
  provider: pages
  skip_cleanup: true
  github_token: $GITHUB_TOKEN
  keep_history: false
  on:
    branch: master
  local_dir: _build/default/_doc/_html/


First I have forgotten to add the last line and travis-ci added the hole root directory to GitHub pages. After adding the last list, the script cannot find the specific documentation directory. I have checked in the log file, that the build script generates the documentation. However it possibly removes it at the end.

Does anybody have an idea how I can find the built documentation? I have difficulties in understanding the ‘.travis.opam.sh’ and ‘.travis.ocaml.sh’ scripts which are obviously loaded by the ‘.travis.yaml’ file.

Thanks for hints.
Helmut

[-- Attachment #2: Type: text/html, Size: 3486 bytes --]

                 reply	other threads:[~2019-04-29 23:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BD8DAB77-7613-49DC-8AF4-0770D3E1280D@gmx.net \
    --to=helmut.brandl@gmx.net \
    --cc=caml-list@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).