Skip to content

Commit

Permalink
Copy phylogenetic-ncbi to phylogenetic-fauna
Browse files Browse the repository at this point in the history
Will make edits in subsequent commit to reflect the default fauna build
  • Loading branch information
joverlee521 committed Jun 21, 2024
1 parent f652842 commit 4a12b55
Showing 1 changed file with 57 additions and 0 deletions.
57 changes: 57 additions & 0 deletions .github/workflows/phylogenetic-fauna.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,57 @@
name: Phylogenetic NCBI

defaults:
run:
# This is the same as GitHub Action's `bash` keyword as of 20 June 2023:
# https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsshell
#
# Completely spelling it out here so that GitHub can't change it out from under us
# and we don't have to refer to the docs to know the expected behavior.
shell: bash --noprofile --norc -eo pipefail {0}

on:
workflow_dispatch:
inputs:
image:
description: 'Specific container image to use for ingest workflow (will override the default of "nextstrain build")'
required: false
type: string
trial-name:
description: |
Trial name for deploying builds.
If not set, builds will overwrite existing builds at s3://nextstrain-data/avian-flu*
If set, builds will be deployed to s3://nextstrain-staging/avian-flu_trials_<trial_name>_*
required: false
type: string

jobs:
phylogenetic:
permissions:
id-token: write
uses: nextstrain/.github/.github/workflows/pathogen-repo-build.yaml@master
secrets: inherit
with:
runtime: docker
run: |
declare -a config;
config+=(
s3_src="s3://nextstrain-data/files/workflows/avian-flu/h5n1"
);
if [[ "$TRIAL_NAME" ]]; then
config+=(
deploy_url="s3://nextstrain-staging/avian-flu_trials_${TRIAL_NAME}_"
)
fi;
nextstrain build \
. \
deploy_all \
--snakefile Snakefile.genome \
--config "${config[@]}"
env: |
NEXTSTRAIN_DOCKER_IMAGE: ${{ inputs.image }}
TRIAL_NAME: ${{ inputs.trial-name }}
artifact-name: phylogenetic-full-genome-build-output

0 comments on commit 4a12b55

Please sign in to comment.