ci: allow starting DPF on same container

[germa89]

Description

As the title.

Issue linked

Required by #1300

Checklist

• I have visited and read Develop PyMAPDL.
• I have tested my changes locally
• I have added necessary documentation or updated existing documentation.
• I have followed the PyMAPDL coding style guidelines.
• I have added appropriate unit tests that also ensure the minimal coverage criteria.
• I have reviewed my changes before submitting this pull request.
• I have linked the issue or issues that are solved to the PR if any.
• I have assigned this PR to myself.
• I have marked this PR as draft if it is not ready to be reviewed yet.
• I have made sure that the title of my PR follows Commit naming conventions (e.g. feat: adding new MAPDL command)

Summary by Sourcery

Enable starting the DPF server on the same container for CICD images by adding an ON_SAME_CONTAINER flag and branching CI steps accordingly.

New Features:

• Add a CI path to launch the DPF server inside the existing MAPDL container for CICD versions.

Enhancements:

• Introduce ON_SAME_CONTAINER environment variable in test-remote workflow to distinguish CICD images.
• Split the DPF server startup into separate steps for same-container and separate-container scenarios.

Build:

• Update build_matrix.sh skip logic to retain CICD versions when running on remote builds.

CI:

• Echo and output the ON_SAME_CONTAINER flag in test-remote.yml and conditionally run DPF startup steps.

[ansys-reviewer-bot]

Thanks for opening a Pull Request. If you want to perform a review write a comment saying:

@ansys-reviewer-bot review

[sourcery-ai]

Reviewer's Guide

This PR enhances the GitHub CI workflow to support starting the DPF server either on the same container (for 'cicd' versions) or on a separate container, and adjusts the build matrix script to ensure 'cicd' versions are not skipped in remote runs.

Flow Diagram: Updated Build Matrix Logic for Remote Non-Student Version Selection

graph TD
    Start["Input: A version to evaluate in build_matrix.sh"] --> IsRemoteAndNotStudent{"Context: Remote Run (ON_REMOTE=true)<br/>AND Non-Student (ON_STUDENT=false)?"};
    IsRemoteAndNotStudent -- "Yes (Logic changed by PR)" --> CheckCicd{"Version string contains 'cicd'?"};
    IsRemoteAndNotStudent -- "No (e.g. local run, or student version)" --> OtherLogic["Handled by existing/other logic (not shown)"];

    CheckCicd -- "Yes" --> IncludeVersion["Action: Include version in build<br/>(Not Skipped)"];
    CheckCicd -- "No" --> SkipVersion["Action: Skip this version for the build"];

    IncludeVersion --> EndEval["End evaluation for this version"];
    SkipVersion --> EndEval;
    OtherLogic --> EndEval;

Loading

File-Level Changes

Change	Details	Files
Introduce ON_SAME_CONTAINER flag and conditional DPF server startup in CI workflow	Initialize and export ON_SAME_CONTAINER based on inputs Extend ubuntu_check step to detect 'cicd' mapdl-version and set flag Expose ON_SAME_CONTAINER in GITHUB_OUTPUT Split DPF activation into two steps with if-conditions for same vs separate container Add echo logging for same-container startup	.github/workflows/test-remote.yml
Modify build_matrix.sh to include 'cicd' versions in remote runs	Update skip condition to bypass skipping when version contains 'cicd' Insert explicit branch to run 'cicd' versions on remote Convert original skip into an elif to preserve legacy behavior	.ci/build_matrix.sh

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @germa89 - I've reviewed your changes - here's some feedback:

• Consider refactoring the two ‘Start DPF server…’ steps into a single step with conditional logic or YAML anchors to reduce duplication and improve maintainability.
• Move the ON_SAME_CONTAINER detection and export logic up into a shared env block or step to avoid scattering environment variable assignments.
• Simplify the build_matrix.sh version check by combining the cicd version exception into the primary remote/student condition, reducing nested if/elif branches.

Prompt for AI Agents

Please address the comments from this code review:
## Overall Comments
- Consider refactoring the two ‘Start DPF server…’ steps into a single step with conditional logic or YAML anchors to reduce duplication and improve maintainability.
- Move the ON_SAME_CONTAINER detection and export logic up into a shared env block or step to avoid scattering environment variable assignments.
- Simplify the build_matrix.sh version check by combining the cicd version exception into the primary remote/student condition, reducing nested if/elif branches.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.12%. Comparing base (4494edd) to head (366e7ef).
Report is 6 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4008      +/-   ##
==========================================
- Coverage   89.17%   89.12%   -0.05%     
==========================================
  Files         187      187              
  Lines       14970    14970              
==========================================
- Hits        13349    13342       -7     
- Misses       1621     1628       +7     

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[germa89]

@pyansys-ci-bot LGTM.

[pyansys-ci-bot]

✅ Approving this PR because germa89 said so in here 😬