Project

Profile

Help

Issue #5769

closed

Story #5762: [Epic] CI Improvements

ansible-pulp molecule CI seems slower than it should be

Added by mdepaulo@redhat.com about 5 years ago. Updated almost 3 years ago.

Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
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:
Quarter:

Description

Ticket moved to GitHub: "pulp/pulpcore/1857":https://github.com/pulp/pulpcore/issues/1857


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.


Sub-issues 2 (0 open2 closed)

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
Actions #1

Updated by mdepaulo@redhat.com about 5 years ago

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

Updated by mdepaulo@redhat.com about 5 years ago

  • Description updated (diff)
Actions #3

Updated by fao89 about 5 years ago

  • Triaged changed from No to Yes
Actions #4

Updated by mdepaulo@redhat.com about 5 years ago

  • Description updated (diff)
Actions #5

Updated by fao89 almost 5 years ago

  • Tags CI/CD added
Actions #6

Updated by pulpbot almost 3 years ago

  • Description updated (diff)
  • Status changed from NEW to CLOSED - DUPLICATE

Also available in: Atom PDF