Skip to article frontmatterSkip to article content
Site not loading correctly?

This may be due to an incorrect BASE_URL configuration. See the MyST Documentation for reference.

33_trigger_parse_manuscript.sh - Start the manuscript conversion

Description

Starts the m-parse-manuscript pipeline for the current Jira ticket with bitbucket_trigger_pipeline.py. The ingest pipelines call it right after their “started” comment, so the conversion runs while the ingest runs.

The pipeline is only started when it is needed. The script downloads the PDF attachments into a scratch directory and compares the manuscript(s) with the checksums in generated/manuscript.sha256, which 31_parse_manuscript.sh records after each successful conversion:

Checksum fileManuscriptResult
Missing or emptyPresentStarted
Differs (changed, renamed, added or removed)PresentStarted
SamePresentNot started
AnyNone attachedNot started

Other PDFs, such as forms, do not count. If the check itself fails, or there is no Jira ticket to check, the pipeline is started anyway.

It never fails. The ingest does not depend on the conversion, so a pipeline that could not be started is only reported as a warning. (The atlassian/trigger-pipeline pipe that hands over to the big ingest cannot be made optional this way: a failing pipe stops the step.)

Usage

. ./tools/resolve_jiraticket.sh
./automations/33_trigger_parse_manuscript.sh

Environment Variables