Skip to content
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

Add CI job to the old workflow #66

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .github/workflows/build_paper.yml
Original file line number Diff line number Diff line change
@@ -1,5 +1,3 @@
# This is a basic workflow to help you get started with Actions

name: Compile paper

# Provide permissions to read and write the repo, create releases.
Expand Down Expand Up @@ -30,11 +28,13 @@ jobs:
}
}' > ${HOME}/.latexminted_config

# Uses the latest TeXLive distribution (currently with minted v3+)
- name: Compile paper
uses: xu-cheng/latex-action@master
with:
root_file: paper.tex

# Uses the latest TeXLive distribution (currently with minted v3+)
- name: Compile submission
uses: xu-cheng/latex-action@master
with:
Expand Down
32 changes: 27 additions & 5 deletions .github/workflows/build_paper_old.yml
Original file line number Diff line number Diff line change
@@ -1,5 +1,3 @@
# This is a basic workflow to help you get started with Actions

name: Compile paper

# Provide permissions to read and write the repo, create releases.
Expand All @@ -12,21 +10,45 @@ on: [push, pull_request]

# A workflow run is made up of one or more jobs that can run sequentially or in parallel
jobs:
# This workflow contains a single job called "build"
build:
# This workflow contains two jobs called "build1" and "build2"
build1:
# The type of runner that the job will run on
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be worth putting the minted or latex version in the name of the workflow, so that we don't just have 3 similar looking "build" workflows

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, good point, we can do both i.e., add the docker image release date tag (20240901) and the minted version.

runs-on: ubuntu-latest
container:
# Most recent version of texlive image has broken minted/pygments
# Uses an older TeXLive distribution (with minted v2.6)
image: ghcr.io/xu-cheng/texlive-full:20221101

# Steps represent a sequence of tasks that will be executed as part of the job
steps:
# Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
- uses: actions/checkout@v3

- name: Compile paper
run: |
latexmk -shell-escape -pdf paper

- name: Compile submission
run: |
latexmk -shell-escape -pdf submission
build2:
# The type of runner that the job will run on
runs-on: ubuntu-latest

# Steps represent a sequence of tasks that will be executed as part of the job
steps:
# Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
- uses: actions/checkout@v3

# Uses an older TeXLive distribution (with minted v2.9)
- name: Compile paper
uses: xu-cheng/latex-action@master
with:
root_file: paper.tex
docker_image: ghcr.io/xu-cheng/texlive-full:20240901

# Uses an older TeXLive distribution (with minted v2.9)
- name: Compile submission
uses: xu-cheng/latex-action@master
with:
root_file: submission.tex
docker_image: ghcr.io/xu-cheng/texlive-full:20240901
Loading