dotCMS / dotCMS/core

Release blocked: 'Install xmllint' apt-get update hangs for hours in CLI Deploy

Open Beginner friendly
#37,118 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Team : Enablement
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

Problem

Every release attempt on 2026-08-19 stalled in Deployment / deploymentCLI DeployInstall xmllint. The step runs:

sudo apt-get update && sudo apt-get install -y libxml2-utils

azure.archive.ubuntu.com was unreachable from the runner (every index line Ign:), apt fell back to archive.ubuntu.com, fetched the four InRelease files, then stalled forever on the Packages indices. Composite-action steps cannot carry timeout-minutes, so nothing bounded it — the job simply hung until a human cancelled.

Observed:

Run Deployment duration Last log line before cancel
32264406479 (26.08.19-01) 4h24m Get:5 …/ubuntu noble-security InRelease @ 15:41:43, cancelled 19:15:52
32298005348 (26.08.19-03) 3h26m Get:5 …/ubuntu noble-security InRelease @ 21:15:56, cancelled 00:02:34

This is unrelated to the dev-image pgvector fix in #36807 — run -01 hung here at 15:41Z, over four hours before that PR merged (20:05Z). Run -02 failed earlier, in the dev-image build, which #36807 fixed; -03 then got past the dev image and surfaced this pre-existing hang.

Fix

xmllint is called exactly once in deploy-jfrog/action.yml, to read distributionManagement/<repository|snapshotRepository>/url out of pom.xml. Three sibling steps in the same action already read POM values with mvn help:evaluate. Use that here too and delete the apt step — the release path stops depending on Ubuntu package mirrors entirely.

Verified against pom.xml — identical output:

  • repositoryhttps://repo.dotcms.com/artifactory/libs-release-local
  • snapshotRepositoryhttps://repo.dotcms.com/artifactory/libs-snapshot-local

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in deploy-jfrog/action.yml and compare the xmllint step with the three sibling steps that use mvn help:evaluate. Verify the deployment action no longer depends on apt package mirrors and that it produces the repository and snapshotRepository URLs shown in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, java
Domain
ci-cd, release
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
84/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.