[#1741] Added pcntl PHP extension to CLI container to allow PHPCS parallel runs.

[AlexSkrypnyk]

closes #1741

Summary by CodeRabbit

• Chores
  • Updated the CLI Docker container to include the PHP pcntl extension.
  • Improved environment variable handling and command invocation in the update-fixtures-no-install command.
  • Adjusted the parallel process setting in the PHPCS configuration for better compatibility with available CPU cores and added an explanatory comment.

[coderabbitai]

Walkthrough

The changes update the Docker CLI container to install the PHP pcntl extension, adjust PHPCS parallelism in its configuration, and revise environment variable handling and command structure in a YAML configuration file for test fixture updates. No changes were made to public or exported entities.

Changes

File(s)	Change Summary
.docker/cli.dockerfile	Added installation of PHP pcntl extension in the CLI Dockerfile.
phpcs.xml	Changed PHPCS "parallel" argument from 75 to 10 and added a comment about CPU core adjustment.
.vortex/.ahoy.yml	Improved environment variable handling and command invocation for the update-fixtures-no-install command.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant Dockerfile
    participant PHP
    Developer->>Dockerfile: Build CLI container
    Dockerfile->>PHP: Install pcov extension
    Dockerfile->>PHP: Enable pcov extension
    Dockerfile->>PHP: Install pcntl extension
    Dockerfile->>PHP: Remove build dependencies

Loading

Assessment against linked issues

Objective	Addressed	Explanation
Add docker-php-ext-install pcntl to CLI Dockerfile (#1741)	✅
Set PHPCS parallel option to 10 in config (#1741)	✅

Assessment against linked issues: Out-of-scope changes

Code Change	Explanation
Improved environment variable handling and command structure in .vortex/.ahoy.yml	This change is not mentioned in the objectives of the linked issue and appears unrelated to PHPCS parallelism or Dockerfile extension installation.

Poem

In the garden of code, a rabbit hops with glee,
PHPCS runs tenfold, as quick as can be!
With pcntl now baked in the CLI stew,
The fixtures update smartly, environment variables anew.
🐇✨
Code grows ever greener, thanks to this clever crew!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 34a8dba and 35b94c7.

⛔ Files ignored due to path filters (5)

• .vortex/installer/tests/Fixtures/install/_baseline/.docker/cli.dockerfile is excluded by !.vortex/installer/tests/Fixtures/**
• .vortex/installer/tests/Fixtures/install/_baseline/phpcs.xml is excluded by !.vortex/installer/tests/Fixtures/**
• .vortex/installer/tests/Fixtures/install/hosting_acquia/phpcs.xml is excluded by !.vortex/installer/tests/Fixtures/**
• .vortex/installer/tests/Fixtures/install/theme_absent/.docker/cli.dockerfile is excluded by !.vortex/installer/tests/Fixtures/**
• .vortex/installer/tests/Fixtures/install/theme_absent/phpcs.xml is excluded by !.vortex/installer/tests/Fixtures/**

📒 Files selected for processing (3)

• .docker/cli.dockerfile (1 hunks)
• .vortex/.ahoy.yml (1 hunks)
• phpcs.xml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (12)

• GitHub Check: build (1)
• GitHub Check: build (0)
• GitHub Check: vortex-test-deployment (1)
• GitHub Check: vortex-test-deployment (0)
• GitHub Check: vortex-test-workflow (3)
• GitHub Check: vortex-test-workflow (1)
• GitHub Check: vortex-test-workflow (0)
• GitHub Check: vortex-test-workflow (2)
• GitHub Check: vortex-test-common
• GitHub Check: vortex-test-installer (8.2)
• GitHub Check: vortex-test-installer (8.3)
• GitHub Check: vortex-test-installer (8.4)

🔇 Additional comments (3)

phpcs.xml (1)

19-21: Reduce PHPCS parallel processes and add guidance

The number of parallel processes has been decreased to 10, with a clarifying comment to tune this value per available CPU cores. This prevents overloading the build environment while guiding future adjustments.

.vortex/.ahoy.yml (1)

90-94: Refine environment variable handling for fixture updates

Exporting UPDATE_FIXTURES, XDEBUG_MODE, and COMPOSER_PROCESS_TIMEOUT at the top of the command block ensures these settings apply consistently across the retry logic and improves readability.

.docker/cli.dockerfile (1)

55-55: Installation of the pcntl extension
The added docker-php-ext-install pcntl step correctly compiles and installs the PHP pcntl extension, enabling PHPCS parallel runs as intended.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.89%. Comparing base (34a8dba) to head (35b94c7).
Report is 1 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #1744   +/-   ##
========================================
  Coverage    71.89%   71.89%           
========================================
  Files           77       77           
  Lines         4415     4415           
========================================
  Hits          3174     3174           
  Misses        1241     1241           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.