Project

General

Profile

Actions
Copy link

action #120564

closed

[qem-dashboard] Assets are not cleaned up on deployment

Added by kraih about 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
kraih
Category:
-
Target version:
openQA Project (public) - Ready
Start date:
2022-11-15
Due date:
2022-11-30
% Done:

0%

Estimated time:
Tags:
reactive work

Description

Observation

The deployment pipeline does not remove old assets from the public/asset directory. That means the version that gets actually served is random and changes to the frontend might not be active after deployment.

Acceptance criteria

  • AC1: The latest assets are served after deployment

Suggestions

  • Maybe use the same asset build workflow as Cavil with npm run build:clean
Actions
Copy link
 #1

Updated by kraih about 2 years ago

  • Tags set to reactive work
  • Status changed from New to In Progress
  • Assignee set to kraih
Actions
Copy link
 #2

Updated by kraih about 2 years ago

Cleaned up the failed deployment manually, will fix the Ansible playbook next.

Actions
Copy link
 #4

Updated by openqa_review about 2 years ago

  • Due date set to 2022-11-30

Setting due date based on mean cycle time of SUSE QE Tools

Actions
Copy link
 #5

Updated by okurz about 2 years ago

  • Status changed from In Progress to Feedback
Actions
Copy link
 #6

Updated by kraih about 2 years ago

Forced a deployment and confirmed that everything works afterwards. There is now only one version of the assets.

Actions
Copy link
 #7

Updated by kraih about 2 years ago

Also looks good after the latest nightly deployment.

Actions
Copy link
 #8

Updated by kraih about 2 years ago

  • Status changed from Feedback to Resolved
Actions
Copy link

Also available in: Atom PDF