Skip to content

ci: add AEM 6.6 LTS (6.6.4-load5) cypress job on release/650 - #1978

Open
rismehta wants to merge 3 commits into
release/650from
rismehta/650-lts-664-load5
Open

ci: add AEM 6.6 LTS (6.6.4-load5) cypress job on release/650#1978
rismehta wants to merge 3 commits into
release/650from
rismehta/650-lts-664-load5

Conversation

@rismehta

@rismehta rismehta commented Sep 3, 2026

Copy link
Copy Markdown
Collaborator

What

Adds a new CircleCI job that runs the UI (cypress) tests against the AEM 6.5 LTS image (circleci-aem-lts:6.6.4-load5-openjdk21) on release/650.

Changes

  • .circleci/config.yml
    • New executor test_executor_ltscircleci-qp:6.4.7-openjdk21 + circleci-aem-lts:6.6.4-load5-openjdk21.
    • New job cypress-chrome-lts (AEM: classic-lts), wired into the build-and-release workflow (requires build-java-11 + build-java-8, same as the 655 jobs).
  • .circleci/ci/it-tests.js
    • New AEM=classic-lts provisioning branch that installs the LTS forms add-on.
    • The add-on version is pulled dynamically as the latest 6.1.x adobe-aemfd-linux-pkg (currently 6.1.244, the 660-compatible line — see adobe-aem-forms/aemds@615af24), mirroring how the 6.5 classic-latest job pulls the latest 6.0.x. Falls back to 6.1.244.
    • classic-lts included in the post-provision AEM restart block (on-prem add-on needs the restart).
  • .circleci/ci/ci.js
    • fetchLatestArtifactVersion takes an optional versionPrefix (defaults to 6.0.), so existing 6.5 callers are unchanged.

Prerequisite

The circleci-aem-lts:6.6.4-load5-openjdk21 image must be published by the circleci-aem pipeline (job build-cq-664-load5-image) before this job can pull it. Until then the cypress-chrome-lts job will fail to pull the image.

Validation

  • node --check passes on ci.js and it-tests.js.
  • config.yml parses; executor/job/workflow wiring verified.
  • Confirmed adobe-aemfd-linux-pkg 6.1.244 exists in maven-aemforms-release and that the 6.1. prefix filter resolves to it.

rismehta and others added 3 commits September 3, 2026 15:29
Adds a cypress-chrome-lts job that runs the UI tests against the AEM 6.5 LTS
image (circleci-aem-lts:6.6.4-load5-openjdk21):

- config.yml: new test_executor_lts (qp 6.4.7-openjdk21 + circleci-aem-lts
  6.6.4-load5-openjdk21) and cypress-chrome-lts job wired into the workflow.
- it-tests.js: new AEM=classic-lts branch that installs the LTS forms add-on
  and pulls the latest 6.1.x adobe-aemfd-linux-pkg (currently 6.1.244), the
  660-compatible line, falling back to 6.1.244.
- ci.js: fetchLatestArtifactVersion now takes an optional version prefix
  (defaults to 6.0. so existing 6.5 callers are unchanged).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Move the 6.1.x fetchLatestArtifactVersion call out of module top-level and
into the AEM=classic-lts branch, so the extra Artifactory lookup only runs
for the LTS job instead of on every cypress job (655, addon, etc.).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The 6.4.7-openjdk21 qp image has a stale Google Chrome apt signing key
(NO_PUBKEY FD533C07C264648F) that makes apt-get update in the
cypress-native-dependencies step exit 100, failing the job in ~8s. The
6.4.6-openjdk11 image (used by the 655 executors) does not have this issue.
The primary is only the test runner / qp client and does not compile, so it
does not need JDK21; AEM still runs on the JDK21 circleci-aem-lts sidecar.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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