Problem/Motivation

Assume the following setup using l10n_update in a continuous integration environment:

  1. Checkout code on server
  2. Run l10n_update to update the database with the latest translations

Step 2 is run using drush l10n-update. When all projects are up-to-date, this command includes a console warning drush_log(dt('No languages to update.'), 'warning');. This warning in turn mark the build as 'unstable' in Jenkins.

Proposed resolution

Reduce the severity of drush l10n-update when all projects are up-to-date from 'warning' to 'status', so automatic deployments using l10n_update are no longer marked unstable due to warnings in the console.

Remaining tasks

  1. Write a patch
  2. Review
  3. Commit

User interface changes

None.

API changes

None.

Data model changes

None.

Comments

idebr created an issue. See original summary.

idebr’s picture

Status: Active » Needs review
StatusFileSize
new750 bytes

Attached patch reduce the severity of drush l10n-update when all projects are up-to-date from 'warning' to 'status', so automatic deployments using l10n_update are no longer marked unstable due to warnings in the console.

sutharsan’s picture

I think that the warning 'No languages to update' should be used when no languages are available.
This patch makes the warnings and messages more accurate.

idebr’s picture

Status: Needs review » Reviewed & tested by the community

That makes sense, thank you for taking the time to maintain this project :)

  • Sutharsan committed aa97d93 on 7.x-2.x
    Issue #2854799 by idebr, Sutharsan: Reduce drush_log severity when all...
sutharsan’s picture

Status: Reviewed & tested by the community » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.