[MGNLDEMO-89] Missing update tasks cause migration diffs. Re-bootstrap all contents/configuration. Created: 13/Aug/15  Updated: 17/Sep/15  Resolved: 17/Sep/15

Status: Closed
Project: Magnolia Demo Projects
Component/s: None
Affects Version/s: 0.5.1
Fix Version/s: 0.8

Type: Bug Priority: Neutral
Reporter: Roman Kovařík Assignee: Philip Mundt
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 2d 4.75h
Original Estimate: Not Specified

Issue Links:
causality
caused by MGNLDEMO-84 Add SVG assets for the destination icons Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Sprint: Basel 9, Basel 10
Story Points: 3

 Description   

So the original decision was to ignore update tasks till version 1.0.
There is the branch MGNLDEMO-84 with the missing update tasks for MGNLDEMO-84 if we'll decide to fix it but there is more missing update tasks related to other tickets.

We should update all demo project by re-bootstrapping all contents.

We only do website and module config for this issue.



 Comments   
Comment by Philip Mundt [ 17/Sep/15 ]

Under certain circumstances the updates will remove the wrong "old" site definition from the multisite module. This causes a migration diff.

Comment by Philip Mundt [ 17/Sep/15 ]

Added re-fix on branch MGNLDEMO-89

Comment by Philip Mundt [ 17/Sep/15 ]

QA Should involve making sure that migration diffs from the following jobs are gone/stay gone:

Generated at Mon Feb 12 05:16:11 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.