Allow to separately run deployment steps

Components

Labels

Description

Currently there are 2 steps, that are always executed one after another:

  • upgrade database + import language pack (both done for each module)

  • resetting various caches + discovering changes in theme files (happens once)

We need to allow to specify filter, which of them to run from command line.

Context Information

None

Additional information (do not use)

None

Activity

Alex March 10, 2016 at 12:40 PM

alex updated the test plan for D21: - Allow to separately run deployment steps.
alex added a project to D21: - Allow to separately run deployment steps: Intechnic: ATV.

Alex November 23, 2014 at 9:14 AM

alex added a comment to D21: - Allow to separately run deployment steps.

Adding comment to create corresponding "Issue Link" from JIRA Issue back to this Differential Revision.

http://qa.in-portal.org/D21

[API] Administrator November 18, 2014 at 9:10 AM

User committed a fix to 5.3.x. Commit Message:

Fixes - Allow to separately run deployment steps

Differential Revision: http://qa.in-portal.org/D21

Alex November 18, 2014 at 9:10 AM

alex closed D21: - Allow to separately run deployment steps by commit rINP16094: Fixes - Allow to separately run deployment steps.
alex updated the diff for D21: - Allow to separately run deployment steps.

http://qa.in-portal.org/D21

Alex November 18, 2014 at 9:06 AM

alex updated the diff for D21: - Allow to separately run deployment steps.
alex added a comment to D21: - Allow to separately run deployment steps.

Returning back original revision content, that was overwritten by commit.

http://qa.in-portal.org/D21

Fixed

Details

Priority

Assignee

Reporter

Developer

Reviewer

Change Log Group

Added

Change Log Message

Patch Instructions

Patches must be submitted through Phabricator.

Story Points

Fix versions

Created November 12, 2014 at 2:11 PM
Updated December 29, 2024 at 8:56 PM
Resolved November 18, 2014 at 9:10 AM