Page MenuHomeSoftware Heritage

Continuous IntegrationFolder
ActivePublic

Details

Description

Continuous Integration toolchain, powering https://jenkins.softwareheritage.org/

Recent Activity

Dec 11 2020

ardumont moved T2871: Unstuck deposit tests failing the docker-dev and icinga-plugins from Backlog to Deployed on the SWORD deposit board.
Dec 11 2020, 3:22 PM · Continuous Integration, SWORD deposit

Dec 10 2020

ardumont closed T2871: Unstuck deposit tests failing the docker-dev and icinga-plugins as Resolved.

v0.7.1 packaged fixed the docker-dev build.
D4715 fixed the icinga plugins build.

Dec 10 2020, 3:30 PM · Continuous Integration, SWORD deposit
ardumont added a revision to T2871: Unstuck deposit tests failing the docker-dev and icinga-plugins: D4715: Update mocked responses of the deposit server..
Dec 10 2020, 3:06 PM · Continuous Integration, SWORD deposit
vlorentz added a revision to T2871: Unstuck deposit tests failing the docker-dev and icinga-plugins: D4713: Accept <codemeta:name> and <codemeta:author> as alternatives to <atom:name>/<atom:title> and <atom:author>..
Dec 10 2020, 12:10 PM · Continuous Integration, SWORD deposit
vlorentz claimed T2871: Unstuck deposit tests failing the docker-dev and icinga-plugins.
Dec 10 2020, 12:10 PM · Continuous Integration, SWORD deposit
ardumont updated the task description for T2871: Unstuck deposit tests failing the docker-dev and icinga-plugins.
Dec 10 2020, 11:12 AM · Continuous Integration, SWORD deposit
ardumont added a revision to T2871: Unstuck deposit tests failing the docker-dev and icinga-plugins: D4703: docker-compose.search.yml: Upgrade elasticsearch container.
Dec 10 2020, 9:23 AM · Continuous Integration, SWORD deposit
ardumont removed a revision from T2871: Unstuck deposit tests failing the docker-dev and icinga-plugins: D4703: docker-compose.search.yml: Upgrade elasticsearch container.
Dec 10 2020, 9:22 AM · Continuous Integration, SWORD deposit

Dec 9 2020

ardumont added a revision to T2871: Unstuck deposit tests failing the docker-dev and icinga-plugins: D4703: docker-compose.search.yml: Upgrade elasticsearch container.
Dec 9 2020, 6:14 PM · Continuous Integration, SWORD deposit
ardumont updated the task description for T2871: Unstuck deposit tests failing the docker-dev and icinga-plugins.
Dec 9 2020, 2:06 PM · Continuous Integration, SWORD deposit
ardumont renamed T2871: Unstuck deposit tests failing the docker-dev and icinga-plugins from Unstuck deposit tests failing the docker-dev to Unstuck deposit tests failing the docker-dev and icinga-plugins.
Dec 9 2020, 2:04 PM · Continuous Integration, SWORD deposit
ardumont updated the task description for T2871: Unstuck deposit tests failing the docker-dev and icinga-plugins.
Dec 9 2020, 11:17 AM · Continuous Integration, SWORD deposit
ardumont triaged T2871: Unstuck deposit tests failing the docker-dev and icinga-plugins as Normal priority.
Dec 9 2020, 9:46 AM · Continuous Integration, SWORD deposit

Nov 12 2020

anlambert closed T2768: unbreak swh-graph CI as Resolved by committing rDGRPH262432b1295d: server/app: Fix aiohttp >= 3.7 exception related errors.
Nov 12 2020, 3:29 PM · Continuous Integration, Graph service
anlambert added a revision to T2768: unbreak swh-graph CI: D4466: server/app: Fix aiohttp >= 3.7 exception related errors.
Nov 12 2020, 3:18 PM · Continuous Integration, Graph service

Nov 10 2020

zack triaged T2768: unbreak swh-graph CI as High priority.
Nov 10 2020, 2:23 PM · Continuous Integration, Graph service

Oct 26 2020

douardda closed T1370: Report key code metrics in prometheus as Resolved.
Oct 26 2020, 12:30 PM · Metrics/monitoring, Restricted Project, Continuous Integration, System administration
douardda closed T1370: Report key code metrics in prometheus, a subtask of T1024: Proper continuous integration setup, as Resolved.
Oct 26 2020, 12:30 PM · Restricted Project, Continuous Integration, System administration

Oct 22 2020

ardumont closed T2726: Unstuck swh-icinga-plugins jenkins builds as Resolved.
Oct 22 2020, 12:20 PM · Continuous Integration
ardumont added a comment to T2726: Unstuck swh-icinga-plugins jenkins builds.

I updated the configuration documentation about ^ btw [1]

Oct 22 2020, 12:20 PM · Continuous Integration

Oct 20 2020

ardumont added a comment to T2726: Unstuck swh-icinga-plugins jenkins builds.

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

Oct 20 2020, 7:48 PM · Continuous Integration
ardumont added a project to T2726: Unstuck swh-icinga-plugins jenkins builds: Continuous Integration.
Oct 20 2020, 6:55 PM · Continuous Integration

Oct 11 2020

zack triaged T2684: notify the swh-devel mailing list of build failures for daily CI jobs as High priority.
Oct 11 2020, 11:19 AM · Continuous Integration

Sep 24 2020

douardda closed T1296: Configure static analysis (eg. radon) reporting using jenkins warnings ng plugin, a subtask of T1024: Proper continuous integration setup, as Wontfix.
Sep 24 2020, 3:07 PM · Restricted Project, Continuous Integration, System administration
douardda closed T1296: Configure static analysis (eg. radon) reporting using jenkins warnings ng plugin as Wontfix.

This is probably mostly deprecated now we have mypy & al. Also the reporting via warnings-ng-plugin may not be such a priority now.

Sep 24 2020, 3:07 PM · Restricted Project, Continuous Integration, System administration

Nov 13 2019

seirl closed T2055: swh-graph CI hangs badly when py4j doesn't find needed files as Resolved.

Fixed in https://forge.softwareheritage.org/rDGRPHcd135e6607350710ec5b3403b19a92c1d5a28cf5 and https://forge.softwareheritage.org/rDGRPH164bf7b1464ea3b9eb38c91c2a7caee7d6b149f7

Nov 13 2019, 5:54 PM · Continuous Integration, Graph service

Nov 12 2019

zack assigned T2055: swh-graph CI hangs badly when py4j doesn't find needed files to seirl.

Another simple way to reproduce is just removing the *.jar file and running pytest on test_api_client.py.
This is not even a Java exception, but chances are fixing that case will fix at least a significant part of the general problem, if not all.

Nov 12 2019, 4:16 PM · Continuous Integration, Graph service

Nov 11 2019

zack added a comment to T2055: swh-graph CI hangs badly when py4j doesn't find needed files.

AFAICT this is a more general problem, the Java backend can hang forever in case of unexpected situations (uncaught exceptions? I really don't know…), which will make it not respond to any incoming request with no visible output.
We should make this visible and debuggable.

Nov 11 2019, 1:45 PM · Continuous Integration, Graph service

Nov 8 2019

ardumont closed D2239: base-buster/Dockerfile: Add missing subversion/mercurial dependencies.
Nov 8 2019, 1:37 PM · Continuous Integration
olasd accepted D2239: base-buster/Dockerfile: Add missing subversion/mercurial dependencies.

$kitchen_sink++

Nov 8 2019, 1:36 PM · Continuous Integration
ardumont updated the summary of D2239: base-buster/Dockerfile: Add missing subversion/mercurial dependencies.
Nov 8 2019, 1:35 PM · Continuous Integration

Nov 7 2019

olasd added a comment to T2066: when pushing several commits, only run CI on the most recent commit.

I've been wondering about this for a while too. The only use case for having red/green on every commit is that it might help people who bisect a repo, and it's certainly not worth the downsides that much.

Nov 7 2019, 1:55 PM · Continuous Integration
anlambert added a comment to T2066: when pushing several commits, only run CI on the most recent commit.

+1 on this.

Nov 7 2019, 10:29 AM · Continuous Integration
zack renamed T2066: when pushing several commits, only run CI on the most recent commit from when pushing several commits, do not run CI on all of them to when pushing several commits, only run CI on the most recent commit.
Nov 7 2019, 9:50 AM · Continuous Integration
zack triaged T2066: when pushing several commits, only run CI on the most recent commit as Normal priority.
Nov 7 2019, 9:50 AM · Continuous Integration
zack closed T1024: Proper continuous integration setup as Resolved.

closing this, as we have "proper" CI since quite a while now (it could always be improved of course, but no need to keep the meta task open at this point)

Nov 7 2019, 9:48 AM · Restricted Project, Continuous Integration, System administration

Nov 4 2019

zack renamed T2055: swh-graph CI hangs badly when py4j doesn't find needed files from swh-graph CI hangs badly on test_api_client.py to swh-graph CI hangs badly when py4j doesn't find needed files.
Nov 4 2019, 1:45 PM · Continuous Integration, Graph service
olasd added a comment to T2055: swh-graph CI hangs badly when py4j doesn't find needed files.

The .jar file is never installed within the tox environment, so the graph backend process fixture never actually succeeds in launching the server. FWIW, when running tox on my system, the tests hang just the same.

Nov 4 2019, 11:43 AM · Continuous Integration, Graph service

Nov 3 2019

zack triaged T2055: swh-graph CI hangs badly when py4j doesn't find needed files as Unbreak Now! priority.
Nov 3 2019, 4:46 PM · Continuous Integration, Graph service
zack closed T2054: CI: ImportMismatchError when running on swh-graph as Resolved by committing rDGRPH677daca371fe: tox.ini: fix pytest ImportMismatchError.
Nov 3 2019, 4:25 PM · Graph service, Continuous Integration
zack updated the task description for T2054: CI: ImportMismatchError when running on swh-graph.
Nov 3 2019, 4:12 PM · Graph service, Continuous Integration
zack updated the task description for T2054: CI: ImportMismatchError when running on swh-graph.
Nov 3 2019, 4:07 PM · Graph service, Continuous Integration
zack triaged T2054: CI: ImportMismatchError when running on swh-graph as High priority.
Nov 3 2019, 4:05 PM · Graph service, Continuous Integration

Oct 1 2019

olasd closed T2027: CI: Run swh-graph tests with Python 3.7 as Resolved.

I've rebased the jdk11 image on top of buster using the awful, awful a3776d744f. This means python 3.7 by default, and it looks like swh.graph CI works.

Oct 1 2019, 3:09 PM · Continuous Integration
seirl triaged T2027: CI: Run swh-graph tests with Python 3.7 as Normal priority.
Oct 1 2019, 1:33 PM · Continuous Integration

Sep 19 2019

ardumont added a comment to T2012: ci: Add a rule to prevent push when ci build failure.

I've definitely got a "build failed" automatic notification after a push I did a while ago. I think it was on swh-environment, before we (recently) disabled the CI on it. If this notification behavior is not uniform across repos, we should make it so.

Sep 19 2019, 11:41 PM · Continuous Integration
zack added a comment to T2012: ci: Add a rule to prevent push when ci build failure.
In T2012#37261, @zack wrote:

Count me as -1 on this.

Strict rules like these tend to get in the way of getting work done when you need it.

Sep 19 2019, 10:55 PM · Continuous Integration
zack added a comment to T2012: ci: Add a rule to prevent push when ci build failure.

From what you wrote, what I think will actually fix your problem is seeing the OK/KO CI marker in the list of pending review requests, so that you can just skip the ones with failing build without having to click them. Would that be enough?

Sep 19 2019, 10:45 PM · Continuous Integration
ardumont added a comment to T2012: ci: Add a rule to prevent push when ci build failure.

I totally agree that we need safeguards against pushing stuff that breaks CI, but we seem to have plenty already: we use code review thoroughly, and that triggers CI;

Sep 19 2019, 10:34 PM · Continuous Integration
zack added a comment to T2012: ci: Add a rule to prevent push when ci build failure.

Count me as -1 on this.

Sep 19 2019, 9:55 AM · Continuous Integration