Project

General

Profile

action #88837

Separate out style checks into a dedicated environment

Added by cdywan 5 months ago. Updated 5 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Feature requests
Target version:
Start date:
2021-02-19
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

Especially in the context of CI, perltidy and other style checks can get mixed up with cache failures or other test failures.

Suggestion

  • Run perltidy separate from other tests
  • Run style checks in a smaller environment where the general cached isn't used
  • Consider style checks in general here, although tidy might be seen as the most prominent one to look out for

Related issues

Related to openQA Project - action #73309: every time a direct dependency is updated in Factory our CI jobs fail until the package is updatedWorkable2020-10-13

History

#1 Updated by cdywan 5 months ago

  • Related to action #73309: every time a direct dependency is updated in Factory our CI jobs fail until the package is updated added

#2 Updated by okurz 5 months ago

  • Target version set to future

Also available in: Atom PDF