Skip to content

Improve getDependency workflow #6461

@llxia

Description

@llxia

Currently, the pipeline downloads 3rd party jars twice.

Having large libraries (i.e., dacapo), the first download is very likely to fail.

00:03:56.638  downloading https://openj9-jenkins.osuosl.org/job/test.getDependency/lastSuccessfulBuild/artifact//dacapo.zip
00:04:57.358  ERROR: downloading https://openj9-jenkins.osuosl.org/job/test.getDependency/lastSuccessfulBuild/artifact//dacapo.zip failed, return code: 4608
00:04:57.358    % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
00:04:57.358                                   Dload  Upload   Total   Spent    Left  Speed
00:04:57.358  
00:04:57.358    0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
00:04:57.358    1 1368M    1 21.8M    0     0  27.2M      0  0:00:50 --:--:--  0:00:50 27.2M
...
00:04:57.358   75 1368M   75 1035M    0     0  19.4M      0  0:01:10  0:00:53  0:00:17 24.1M
00:04:57.358  curl: (18) transfer closed with 348610934 bytes remaining to read

As a result, not all jars are downloaded and we rely on the second download. However, the second download may not be stable due to 3rd party URL. See #6460

The getDependency workflow should be improved to download the required jars only. In summary, we do not download all jars at the Jenkins level. We only download on demand in build.xml. In the first try, download from the test.getDependency job. If the first one fails, use 3rd party URL in the second try.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions