COU-652 - Verify regression issue in Courier before release

Created by Claus Jensen 07 Mar 2018, 10:04:38 Updated by Jacob Midtgaard-Olesen 16 Mar 2018, 07:58:35

Relates to: COU-654

Relates to: COU-655

Is required for: UAASSCRUM-1068

Subtask of: UAASSCRUM-1068

I believe we've merged in some changes that aren't "all good" recently in Courier (after the 3.1.6 release).

Haven't spent much time looking into it, but can say for sure that I was seeing some things not doing as they were supposed to regarding generation of .courier files and I suspect it could have something to do with the recent changes to the messaging service. Rebuilding from the 3.1.6 commit, everything seemed to work as expected. This was on a cloned site running local with latest commits of Courier - didn't test anything in Cloud.

This is an issue for when we need to upgrade, as part of that upgrade requires all (older) sites to have the latest Courier - due to the changes made with messaging module... so if there's something not really working as expected here, it needs to be resolved before we intend to do this update.

  • We need to verify that .courier files are generated correctly on Cloud.
  • We need to verify that .courier files are generated correctly on Local.
  • We need to verify that these files are correctly added to git both on Cloud and Local when created.
  • If not - we need to locate the issue causing this (look into the recent changes)

This of course has to be done with a build of the latest commits done after 3.1.6 tag as that one seemed to be fine.

Comments

Claus Jensen 09 Mar 2018, 10:53:14

I've tested everything in the latest commits vs. older commits vs. current release and it seems to only be related to a specific site and not Courier in general. All tests were done both on local and Cloud.

  • Confirmed that rebuild tasks run on local and Cloud (although a bit quirky due to file/dir locks not really being handled well).
  • Confirmed that .courier files are generated as expected on local and Cloud.
  • Confirmed that .courier files are committed to git in Cloud on anything but the latest commits.
  • Note that no git commits are done in Live Cloud with the latest commits of Courier. Verifying with Morten whether this is expected or if we have an issue to fix.

So - only tasks coming out of this is a few non-important fixup tasks that has been added to the tracker.


Priority: Normal

Type: Task

State: Fixed

Assignee:

Difficulty:

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions:

Due in version:

Sprint: Sprint 80

Story Points: 3

Cycle: 8