"core/scripts/drupal install" should provide a --no-progress option

Created on 27 June 2024, 6 months ago
Updated 14 July 2024, 5 months ago

Problem/Motivation

For automated installations via CI or similar the progress output of core/scripts/drupal install is unnecessary and looks a bit strange, for example:

 0/17 [░░░░░░░░░░░░░░░░░░░░░░░░░░░░]
Installing Drupal
 6/17 [▓▓▓▓▓▓▓▓▓░░░░░░░░░░░░░░░░░░░]
Set up database
 7/17 [▓▓▓▓▓▓▓▓▓▓▓░░░░░░░░░░░░░░░░░]
Set up database
 9/17 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓░░░░░░░░░░░░░░]
Install site
11/17 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓░░░░░░░░░░]
Configure site
12/17 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓░░░░░░░░░]
Configure site
13/17 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓░░░░░░░]
Congratulations, you installed Drupal!
17/17 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓]
Congratulations, you installed Drupal!

Steps to reproduce

Proposed resolution

There should be a --no-progress option, similar to other command-line tools such as Composer, PHPUnit, etc.

The option should then be used when running the install script in tests, as progress output does is not displayed there anyway.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

📌 Task
Status

Needs work

Version

11.0 🔥

Component
Install 

Last updated 6 days ago

No maintainer
Created by

🇩🇪Germany tstoeckler Essen, Germany

Live updates comments and jobs are added and updated live.
  • Needs manual testing

    The change/bugfix cannot be fully demonstrated by automated testing, and thus requires manual testing in a variety of environments.

Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024