reachableceo/MarkdownResume-Pipeline-ClientExample
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Squashed 'vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline/' changes from 0c3b9b4..a956f3a

Browse Source 
a956f3a now with variables for all

git-subtree-dir: vendor/git.knownelement.com/reachableceo/MarkdownResume-Pipeline
git-subtree-split: a956f3ad42499c8c0580b56d110e0d346eacbc10
This commit is contained in:
Charles N Wyble 2024-12-15 08:12:43 -06:00
parent d5bc7841f7
commit dc741450df
1 changed files with 16 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
build/build-pipeline-server-markdown.sh
View File

@ -1,5 +1,7 @@
#!/usr/bin/env bash
set -euo pipefail
#####################################################################################################
#Markdown to PDF/MSWord Resumek and candidate info sheet
#####################################################################################################
@ -8,7 +10,11 @@
# Create the candidate information PDF
#############################################
$MO_PATH $PipelineClientWorkingDir/build/BuildTemplate-CandidateInfoSheet.yml > $BUILDYAML_CANDIDATEINFOSHEET
# Expand variables into rendered YAML files. These will be used by pandoc to create the output artifacts
$MO_PATH $YamlInputTemplateFileJobBoard > $BUILDYAML_JOBBOARD
$MO_PATH $YamlInputTemplateFileClientSubmission > $BUILDYAML_CLIENTSUBMISSION
$MO_PATH $YamlInputTemplateFileClientSubmission > $BUILDYAML_CANDIDATEINFOSHEET
echo "Creating candidate info sheet..."
@ -16,16 +22,13 @@ $MO_PATH $PipelineClientWorkingDir/Templates/MarkdownResume/CandidateInfoSheet/C
pandoc \
"$CandidateInfoSheetMarkdownOutputFile" \
--template eisvogel \
--metadata-file="$PipelineClientWorkingDir/build-temp/MarkdownResume/CandidateInfoSheet.yml" \
--template $PANODOC_TEMPLATE \
--metadata-file="$BUILDYAML_CANDIDATEINFOSHEET" \
--from markdown \
--to=pdf \
--output $CandidateInfoSheetPDFOutputFile
# Expand variables into rendered YAML files. These will be used by pandoc to create the output artifacts
$MO_PATH $PipelineClientWorkingDir/build/BuildTemplate-JobBoard.yml > $BUILDYAML_JOBBOARD
$MO_PATH $PipelineClientWorkingDir/build/BuildTemplate-ClientSubmission.yml > $BUILDYAML_CLIENTSUBMISSION
echo "Combining markdown files into single input file for pandoc..."
@ -125,16 +128,18 @@ echo "Generating PDF output for job board version..."
pandoc \
"$JobBoardMarkdownOutputFile" \
--template eisvogel \
--metadata-file="$PipelineClientWorkingDir/build-temp/MarkdownResume/JobBoard.yml" \
--metadata-file="$BUILDYAML_JOBBOARD"\
--from markdown \
--to=pdf \
--output "$JobBoardPDFOutputFile"
echo "Generating MSWord output for job board version..."
pandoc \
"$JobBoardMarkdownOutputFile" \
--metadata-file="$PipelineClientWorkingDir/build-temp/MarkdownResume/JobBoard.yml" \
--metadata-file=" $BUILDYAML_JOBBOARD" \
--from markdown \
--to=docx \
--reference-doc="$PipelineClientWorkingDir/build/resume-docx-reference.docx" \
@ -144,8 +149,8 @@ echo "Generating PDF output for client submission version..."
pandoc \
"$ClientSubmissionMarkdownOutputFile" \
--template eisvogel \
--metadata-file="$PipelineClientWorkingDir/build-temp/MarkdownResume/ClientSubmission.yml" \
--template "$PANDOC_TEMPLATE" \
--metadata-file="$BUILDYAML_CLIENTSUBMISSION" \
--from markdown \
--to=pdf \
--output "$ClientSubmissionPDFOutputFile"
@ -154,7 +159,7 @@ echo "Generating MSWord output for client submission version..."
pandoc \
"$ClientSubmissionMarkdownOutputFile" \
--metadata-file="$PipelineClientWorkingDir/build-temp/MarkdownResume/ClientSubmission.yml" \
--metadata-file="$BUILDYAML_CLIENTSUBMISSION"\
--from markdown \
--to=docx \
--reference-doc="$PipelineClientWorkingDir/build/resume-docx-reference.docx" \