Use a volatile resource lock for host port 5080
ClosedPublic
Actions

Authored by lunar on Nov 14 2022, 4:02 PM.

Details

Reviewers

olasd

Group Reviewers

System administrators

Commits

rCJSWH693ebea630a4: Use a volatile resource lock for host port 5080
rCJSWH7a97d4a503de: Convert swh-docker-dev job from freestyle to Pipeline

Summary

swh-docker-dev and swh-mirror/run-tests both uses Docker containers
bound to port 5080. One to test if the generated images work fine, the
other as part of the mirror stack being tested. To prevent issues,
we explicitly use a volatile resource lock in their pipeline
definitions.

See: https://www.jenkins.io/doc/pipeline/steps/lockable-resources/

We first transform swh-docker-dev from a freestyle job to a Pipeline job in
order to implement fine-grained locked.

Diff Detail

Repository

rCJSWH Jenkins jobs

Branch

master

Lint

No Linters Available

Unit

No Unit Test Coverage

Build Status

Buildable 32794
Build 51381: arc lint + arc unit

Event Timeline

lunar created this revision.Nov 14 2022, 4:02 PM

Herald added a reviewer: System administrators. · View Herald TranscriptNov 14 2022, 4:02 PM

lunar requested review of this revision.Nov 14 2022, 4:02 PM

Harbormaster completed remote builds in B32788: Diff 31852.Nov 14 2022, 4:02 PM

lunar edited the summary of this revision. (Show Details)Nov 14 2022, 4:03 PM

Fix the issue by adding a level of indirection in the yaml (replacing the job
by an identical job-template, and instantiating it through a project).
It seems jinja2 templates aren't actually supported in direct job definitions,
only in job templates. Thanks to olasd for finding this out and suggesting a fix.

Harbormaster completed remote builds in B32794: Diff 31859.Nov 14 2022, 6:06 PM

lunar edited the summary of this revision. (Show Details)Nov 14 2022, 6:08 PM