>��A problem I anticipate is that since we only keep the latest build,

how did you manage that? :-o

When I was using bintray we had trouble that we could only store every commit; so I guess I am interested to see what your process is. :-)

Peter

On Fri, Aug 25, 2017 at 9:06 PM, Damien Pollet <damien.pollet@gmail.com> wrote:
A problem I anticipate is that since we only keep the latest build, the PDF will only match master or any pull request until the next commit/build (I don't like storing stuff for each and every commit). But maybe that could be fixed by naming the PDF according to their originating branch���

On 25 August 2017 at 20:11, Dimitris Chloupis <kilon.alios@gmail.com> wrote:
+100 :)


On Fri, Aug 25, 2017 at 5:45 PM Stephane Ducasse <stepharo.self@gmail.com> wrote:
��Hi

with Damien Pollet, we went over all the booklets and some of the
Pharo books currently written in Pillar and made sure that each time
you commit

- a travis job is run
- latex is produced as well as pdf
- the pdf is stored on bintray
- the release versions are stored on the github repo (I should verify)

So now you can just do a PR and you get a super nice PDF.

Have a look at Glorp or Voyage for example

- https://github.com/SquareBracketAssociates/Booklet-Glorp
- https://github.com/SquareBracketAssociates/Booklet-Voyage

You can access the bintray files from the squarebracketassociates
lovely binTray account :)

https://bintray.com/squarebracketassociates/wip/download_file?file_path=voyage-wip.pdf


I'm writing a doc of the process so that other people can do it for
their private projects.


Stef




--
Damien Pollet
type less, do more [ | ] http://people.untyped.org/damien.pollet