Skip to content

ci: cache and export both dms-control and dms-e2e e2e names - #155

Merged
Upd4ting merged 1 commit into
mainfrom
ci/wdf26acfc-173-dms-e2e-names
Nov 19, 2026
Merged

Upd4ting merged 1 commit into
mainfrom
ci/wdf26acfc-173-dms-e2e-names

Conversation

@Upd4ting

Copy link
Copy Markdown
Member

Wdf26acfc-173. AntelopeJS/dms#1184 renamed the e2e kit's cache folders and variables with no fallback. This exports both DMS_CONTROL_RUNS and DMS_E2E_RUNS and caches both frontend directories under a new key, so CI is right before and after the dms upgrade.

Before:

ci.yml:160: DMS_CONTROL_RUNS
ci.yml:174-176: ~/.cache/dms-control/frontend, key dms-control-frontend-

After: each DMS_CONTROL_* export has its DMS_E2E_* twin; ~/.cache/dms-control/frontend and ~/.cache/dms-e2e/frontend are cached under dms-e2e-frontend-. DMS_CONTROL_MONGOD and DMS_CONTROL_NO_STANDBY are not used in this repo.

Follow-ups

  • none

@Upd4ting
Upd4ting enabled auto-merge November 19, 2026 23:14
@Upd4ting
Upd4ting added this pull request to the merge queue Nov 19, 2026
Merged via the queue into main with commit 64f3d4f Nov 19, 2026
13 checks passed
@Upd4ting
Upd4ting deleted the ci/wdf26acfc-173-dms-e2e-names branch November 19, 2026 23:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant