Skip to content

[CICD] [STARTER]: Publish Starter job fails due to missing working directory during artifact deployment #32269

@dcolina

Description

@dcolina

Parent Issue

No parent issue identified.

Problem Statement

The GitHub Actions workflow Publish Starter is failing during the deploy-artifacts job due to a missing working directory. The following error is logged:

An error occurred trying to start process ‘/usr/bin/bash’ with working directory ‘/home/runner/work/core/core/parent’. No such file or directory

This error occurs during the Update pom.xml step, which likely relies on navigating to the core/parent directory that does not exist at runtime.

Steps to Reproduce

  1. Trigger the Publish Starter workflow.
  2. Wait until the deploy-artifacts job is executed.
  3. Observe the failure at step Update pom.xml, with the logged error message pointing to a missing directory.

Acceptance Criteria

  • Ensure that the working directory core/parent exists or is created before executing this step.
  • Validate that the script or step referencing the directory gracefully handles cases where the path is invalid.
  • Confirm the full workflow completes successfully with the fix in place.

dotCMS Version

Not version-specific, applies to Publish Starter pipeline.

Proposed Objective

Quality Assurance

Proposed Priority

Priority 1 - Show Stopper

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No external links provided.

Assumptions & Initiation Needs

  • The directory core/parent may have been renamed, relocated, or never created as part of this workflow context.
  • The issue may have been introduced by changes in the directory structure or incorrect assumptions in the workflow configuration.

Quality Assurance Notes & Workarounds

  • As a temporary workaround, manually validate the directory structure before executing commands.
  • Consider using a dynamic check or fallback to ensure the step doesn’t fail silently.

Sub-Tasks & Estimates

  • Reproduce the issue in a PR run or a branch pipeline.
  • Adjust the working directory to a valid and existing path.
  • Confirm the Update pom.xml step executes without errors.
  • Validate the rest of the deployment flow.

Metadata

Metadata

Assignees

Type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions