Project

Profile

Help

Issue #5769

Story #5762: [Epic] CI Improvements

ansible-pulp molecule CI seems slower than it should be

Added by mdepaulo@redhat.com 9 months ago. Updated 4 months ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
Start date:
Due date:
Estimated time:
(Total: 0:00 h)
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
CI/CD
Sprint:

Description

ansible-pulp CI is currently taking like 30 minutes.

Some theories on why this is happening:
1. ansible pipelining is not working. So there is a large overhead per every ansible task.
2. The Travis VM is low on RAM as it tests 3 containers at once (C7, Fedora & Debian).
3. Although purely an improvement, we could implement libeatmydata/nosync, or at other layers (like docker) make all disk writes unsafely cached.


Subtasks

Issue #5817: ansible-pulp CI is slower than it should be due to a lack of ansible pipeliningCLOSED - CURRENTRELEASEmdepaulo@redhat.comActions
Issue #6046: ansible-pulp molecule CI does duplicate molecule stagesCLOSED - CURRENTRELEASEfao89Actions

History

#1 Updated by mdepaulo@redhat.com 9 months ago

  • Subject changed from ansible molecule CI seems slower than it should be to ansible-pulp molecule CI seems slower than it should be

#2 Updated by mdepaulo@redhat.com 9 months ago

  • Description updated (diff)

#3 Updated by fao89 9 months ago

  • Triaged changed from No to Yes

#4 Updated by mdepaulo@redhat.com 9 months ago

  • Description updated (diff)

#5 Updated by fao89 8 months ago

  • Tags CI/CD added

Please register to edit this issue

Also available in: Atom PDF