Skip to content

Chore/update he tme and test app #701

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.

Sign up for GitHub

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

Open
ari-nz wants to merge 2 commits into
base: main
Choose a base branch
from
+28 −7
Open

Chore/update he tme and test app #701

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c3ded7a
chore: test-app and he-tme are now available to run version 1.3.0
ari-nz Jul 30, 2026
90eb620
docs: Update the contribution guide to mention triggering github acti…
ari-nz Jul 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -122,6 +122,27 @@ Notes:
- **PR labels**: Add labels with the same names (e.g., `skip:ci`, `skip:test:long-running`) to your pull request
- Both methods work independently - you can use either or both


### Run Github Actions

One can trigger GitHub Actions workflows locally using commands like so:

```shell
BRANCH=$(git rev-parse --abbrev-ref HEAD)

# Hourly (quick smoke) and Daily (thorough) — staging
gh workflow run scheduled-testing-staging-hourly.yml --ref "$BRANCH" -f branch="$BRANCH"
gh workflow run scheduled-testing-staging-daily.yml --ref "$BRANCH" -f branch="$BRANCH"

# Same against production
gh workflow run scheduled-testing-production-hourly.yml --ref "$BRANCH" -f branch="$BRANCH"
gh workflow run scheduled-testing-production-daily.yml --ref "$BRANCH" -f branch="$BRANCH"
```

This is especially useful for testing that new he-tme versions will pass the scheduled testing workflows before merging into main.



### Publish Release

Releases follow a four-phase workflow that allows Ketryx compliance approvals to be collected before publishing:
Expand Down
14 changes: 7 additions & 7 deletions tests/constants_test.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -106,13 +106,13 @@
match os.getenv("AIGNOSTICS_PLATFORM_ENVIRONMENT", "production"):
case "production":
TEST_APPLICATION_ID = "test-app"
TEST_APPLICATION_VERSION = "1.0.0"
TEST_APPLICATION_VERSION = "1.3.0"

HETA_APPLICATION_ID = "he-tme"
HETA_APPLICATION_VERSION = "1.2.0"
TEST_APPLICATION_VERSION_USE_LATEST_FALLBACK_SKIP = False
HETA_APPLICATION_VERSION = "1.3.0"
TEST_APPLICATION_VERSION_USE_LATEST_FALLBACK_SKIP = True

PIPELINE_GPU_TYPE = "L4"
PIPELINE_GPU_TYPE = "A100"
PIPELINE_GPU_PROVISIONING_MODE = "SPOT"
PIPELINE_GPU_FLEX_START_MAX_RUN_DURATION_MINUTES = None
PIPELINE_MAX_GPUS_PER_SLIDE = 1
Expand All @@ -121,13 +121,13 @@

case "staging":
TEST_APPLICATION_ID = "test-app"
TEST_APPLICATION_VERSION = "1.0.0"
TEST_APPLICATION_VERSION = "1.3.0"

HETA_APPLICATION_ID = "he-tme"
HETA_APPLICATION_VERSION = "1.3.0-rc.1"
HETA_APPLICATION_VERSION = "1.3.0"
TEST_APPLICATION_VERSION_USE_LATEST_FALLBACK_SKIP = True

PIPELINE_GPU_TYPE = "L4"
PIPELINE_GPU_TYPE = "A100"
PIPELINE_GPU_PROVISIONING_MODE = "SPOT"
PIPELINE_GPU_FLEX_START_MAX_RUN_DURATION_MINUTES = None
PIPELINE_MAX_GPUS_PER_SLIDE = 1
Expand Down
Loading