Skip to content
GitLab
Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • GitLab FOSS GitLab FOSS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 23
    • Issues 23
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLab FOSSGitLab FOSS
  • Issues
  • #4250
Closed
Open
Issue created Dec 22, 2015 by Jörn Hees@joernhees

using builds to generate pdf from latex source (nearly there)

we use gitlab in our research group (as probably many others) to write scientific papers together in latex...

with the awesome integration of gitlab ci and the runners 👍 the following .gitlab-ci.yml nearly gets you all the way so you never have to commit the PDF again or worry that you forgot to commit some graphic, etc., by simply having a runner generate it:

compile_pdf:
  image: tianon/latex
  script:
    - latexmk -pdf paper.tex
  artifacts:
    paths:
      - paper.pdf

Now the two tiny things i can't figure out are:

  • how to provide a link to the pdf instead of the artifacts.tgz
  • and how to get the latest build for a branch like master so i can put a "latest version" pdf permalink in the README

Any ideas what i'm missing? Or is this maybe not possible yet?

Assignee
Assign to
Time tracking