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

Update pathogen-repo-ci to "generic"/"smart" workflow #44

Closed
genehack opened this issue May 30, 2024 · 1 comment
Closed

Update pathogen-repo-ci to "generic"/"smart" workflow #44

genehack opened this issue May 30, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@genehack
Copy link
Contributor

Context

Per recent discussion, as well as various legacy conversations here, here, and here, we want to update the pathogen-repo-ci GitHub Action to a "strict" version that can be used across all of our "modern" pathogen repos with zero configuration on the consuming repo side.

Description

Update the pathogen-repo-ci workflow so that:

  1. For each build-name (i.e., each of ingest, phylogenetic, and nextclade):
    a. If the repo contains a <build-name>/Snakefile file and a <build-name>/build-configs/ci/config.yaml file
    b. Run nextstrain build <build-name> --configfile build-configs/ci/config.yaml

The consuming repo will be responsible for providing an appropriate config file that either sets up appropriate example data or results in a subset of a full workflow being run, so as to validate that the repo workflows have not been broken by a change.

Examples

This workflow, plus the appropriate build-config files, should be sufficient to enable CI for a pathogen repo:

name: CI
on:
  - push
jobs:
  ci:
    name: CI
    uses: nextstrain/.github/workflows/pathogen-repo-ci.yaml
@genehack
Copy link
Contributor Author

This was opened in the wrong repo, and is being closed in favor of nextstrain/.github#89, which has the supreme advantage of being in the correct repo.

Those responsible for the error have been sacked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant