镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

Run the weekly SIPNET integration test against SIPNET v2.2.0 too - #4191

Draft
madhavzanwar wants to merge 1 commit into
PecanProject:developfrom
madhavzanwar:GH-3870-sipnet-v2-ci
Draft

madhavzanwar wants to merge 1 commit into
PecanProject:developfrom
madhavzanwar:GH-3870-sipnet-v2-ci

Conversation

@madhavzanwar

Copy link
Copy Markdown
Contributor

Related to #3870. Following @dlebauer's suggestion to add SIPNET 2.2.0 to CI,
and @infotroph's earlier suggestion to keep the v1.3.0 run.

What

  • sipnet.yml: new optional sipnet-version input, default v1.3.0, so
    PR CI behaves as before. The download step picks the right asset: v1.x
    releases ship a bare binary, v2.x releases ship
    sipnet-linux-x86_64-<version>.tar.gz containing sipnet.
  • ci-weekly.yml: new sipnet-v2 job running the integration test against
    v2.2.0 (R 4.5 only). It runs weekly only, not on PRs.
  • CHANGELOG entry.

Testing

  • Both workflow files parse as YAML.
  • I ran the download logic locally for v1.3.0 and v2.2.0: both give a working
    binary (v2.2.0 reports SIPNET version 2.2.0).
  • I could NOT run the integration test itself (it needs the BETY database and
    the CI container), so I don't know yet whether it passes with v2.2.0. This
    is a draft until the weekly workflow has run once on my fork
    (workflow_dispatch). A failure there would be information about v2, not
    necessarily a bug in this PR.

sipnet.yml takes an optional sipnet-version input (default v1.3.0) and
downloads either the v1 binary or the v2 tarball. ci-weekly.yml adds a
job that uses v2.2.0.

Refs PecanProject#3870
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant