Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #26765 Reduce number of stages executed in parallel in the CI pipelines
    Actions
    Infos
    #26765
    Thomas Gerbet (tgerbet)
    2022-05-06 08:12
    2022-05-05 16:29
    28291
    Details
    Reduce number of stages executed in parallel in the CI pipelines

    It looks like we are a bit short in term of memory with the current codebase and tooling. The pipelines shows weird behaviors that looks like OOM kills.

    Reducing the number of stages of stages executed in parallel in the pipelines is a quick & easy solution that should be good enough for now. It should not impact the pipelines execution times too much (or at all): some stages are quite long so they run during the whole time and I'm guessing we are currently wasting a lot of time on the context switches.

    Dev tools
    Empty
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Thomas Gerbet (tgerbet)
    Closed
    2022-05-06
    Attachments
    Artifact links

    Releases

    Fixed in

    Artifact ID Project Tracker Summary Status Last Update Date Submitted By Assigned to
    rel #25713 Tuleap Releases 13.9 Delivered 2022-25-05 14:19 Manuel Vacelet (vaceletm)
    Empty
    References
    Referencing request #26765

    Git commit

    tuleap/tuleap/stable

    Merge commit 'refs/changes/58/25858/1' of ssh://gerrit.tuleap.net:29418/tuleap into HEAD dcdde4cd0d
    User avatar Nicolas Terray (nterray) , 2022-05-06 08:04
    request #26765: Reduce number of stages executed in parallel in the CI pipelines 8fb6ab9896
    User avatar Thomas Gerbet (tgerbet) , 2022-05-05 16:29
    Referenced by request #26765

    Artifact Tracker v5

    rel #25713 13.9

    Other

    gerrit #25858
    Display settings

    Follow-ups

    User avatar
    Thomas Gerbet (tgerbet)2022-05-06 08:12

    For information, additional troubleshooting has shown that it was likely the memory was not the issue. It looks more like a combination of disk and CPU contentions.