jenkinsci / jenkinsci/debian-package-builder-plugin

Problems when building for several architectures + uploading to mini-dinstall

Open
#52 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
28
Forks
28
PR merge metrics
No merged PRs in 30d

Description

I'm using this plugin to build packages and publish to mini-dinstall managed repository.
I have several slaves with different architectures, so the packages are built as multi-configuration projects, simultaneously for armel, armhf, i386 and amd64.

Resulting artifacts have the same filenames for .tar.xz and .dsc for all configurations

Therefore, if a debrelease from a concurrent build is called before mini-dinstall processes the incoming - .tar.xz and .dsc are overwritten. As a result only one package is added.

Is there any recommended way to fix this apart from forcing a sequential build for each configuration and call remote mini-dinstall -b to index newly uploaded package everytime?

Contributor guide

Open the contributing guide

Research direction

Start by reproducing concurrent multi-configuration builds for armel, armhf, i386, and amd64, then trace how the resulting .tar.xz and .dsc artifacts are passed to debrelease and mini-dinstall. Done should prevent artifacts from different architectures being overwritten and allow all packages to be indexed without requiring sequential builds.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.