Unstuck swh-icinga-plugins jenkins builds
Closed, MigratedEdits Locked
Actions

Assigned To

Authored By

	ardumont
	Oct 20 2020, 6:46 PM

Description

When pushing tags on that repository nothing happens... (instead of publishing to pypi then going on with debian packaging...).
It's stuck in january 2020 when the last tag was pushed manually.

Unstuck this.

Revisions and Commits

rCJSWH Jenkins jobs
	D4315	rCJSWHa86d1910a376 jenkins-job: Declare explicitely the python_module for each swh project

Related Objects

Mentioned In: T2685: Test update of deposit with metadata-only in integration tests
rDICP45f890025ae2: pytest.ini: Make django not load itself
Mentioned Here: D4315: jenkins-job: Declare explicitely the python_module for each swh project

Event Timeline

ardumont triaged this task as Normal priority.Oct 20 2020, 6:46 PM

ardumont created this task.

the first part was fixed, the post-hook installed was the incorrect one (it was targetting the debian deps post hook so rendering a 404 in the phab logs [1]).

This is fixed [2] so now pushing tag does the right thing.

The documentation on configuring the post hook has been updated so this mixing up post-hooks no longer happens [3]

[1]

128.93.193.30 - - [20/Oct/2020:14:56:00 +0000] "GET /buildByToken/buildWithParameters?GIT_TAG=v0.2.0&job=debian%2Fdeps%2FDICP%2Fincoming-tag&token=ph4br1cat0r&cause=Tag%20v0.2.0%20pushed%20by%20ardumont HTTP/1.1" 404 - "-" "curl/7.64.0"

[2]

128.93.193.30 - - [20/Oct/2020:15:01:00 +0000] "GET /buildByToken/buildWithParameters?GIT_TAG=v0.2.0&job=DICP%2Fincoming-tag&token=ph4br1cat0r&cause=Tag%20v0.2.0%20pushed%20by%20ardumont HTTP/1.1" 201 - "-" "curl/7.64.0"

[3] https://wiki.softwareheritage.org/wiki/Debian_packaging#Setting_up_the_repository_on_Phabricator

The second part is more tricky and is dealt with in D4315 (details there).
quoting a bit:

Current build fails because of naming discrepancy:

- the repository is named swh-icinga-plugins
- the debian package is named python3-swh.icingaplugins
- the python module is named swh.icinga-plugins
- the archive pushed for the python module is name swh.icinga_plugins

ikr?!

ardumont added a revision: D4315: jenkins-job: Declare explicitely the python_module for each swh project.Oct 20 2020, 6:50 PM

Now back to "normal", the build (stable) fails (unstable is ok) but that's the "standard" possible
discrepancy between running tox/pytest alone and running those within the
debian chroot... ¯\_(ツ)_/¯

ardumont renamed this task from Unstuck swh-icinga-plugins jenkins state to Unstuck swh-icinga-plugins jenkins builds.Oct 20 2020, 6:55 PM

ardumont updated the task description. (Show Details)

ardumont added a project: Continuous Integration.

ardumont mentioned this in rDICP45f890025ae2: pytest.ini: Make django not load itself.Oct 20 2020, 7:41 PM

I got a full build from commit with ^ then tag to pypi module builds and debian package builds ok (both stable and unstable now)

\m/

ardumont added a commit: rCJSWHa86d1910a376: jenkins-job: Declare explicitely the python_module for each swh project.Oct 21 2020, 4:08 PM

I updated the configuration documentation about ^ btw [1]

[1] https://wiki.softwareheritage.org/wiki/Debian_packaging#Setting_up_the_Jenkins_jobs

ardumont closed this task as Resolved.Oct 22 2020, 12:20 PM

ardumont claimed this task.

ardumont mentioned this in T2685: Test update of deposit with metadata-only in integration tests.