with new tests coming (mirror notification), the 40mn timeout is now a
bit short(!).

Antoine Lambert authored 3 months ago and Antoine Lambert committed 2 months ago

Align with Python version from latest debian stable.

Antoine Lambert authored 3 months ago and Antoine Lambert committed 2 months ago

Those packages should support Python 3.10 so ensure to build and test
them with that version.

swh-graph exceeded the timeout once: https://jenkins.softwareheritage.org/blue/organizations/jenkins/DGRPH%2Fgitlab-builds/detail/gitlab-builds/2430/pipeline/60

Rust tests take 20 minutes to build, like swh-graph's

In order to run tests on swh/devel/swh-provenance!184
which is probably going to be merged soon.

Cypress tests on Jenkins suddenly start to fail with connection refused
errors when performing HTTP requests with the axios library.

This is likely due to a nodejs upgrade.

As a workaround, use IP address of localhost in cypress variable baseUrl.

It enables to speedup jobs execution time by not recompiling crates
whose versions are already stored in remote cache.

Use local cargo cache for crates code, remote sccache for the compiled
crates and do not compile in release mode.

vlorentz authored 6 months ago and vlorentz committed 6 months ago

By default, 'cargo doc' builds documentation of all crates recursively used by the project
in order to provide a self-contained documentation tree.

Here we only use it to check there are no syntax issues or broken references, so this
is unnecessary

Prefer to rely on pre-commit to run all code quality checks in order
to also benefit from black, codespell and isort checks.

This will enforce newly introduced code to pass those checks and force
external contributors to install the pre-commit hooks.

Custom !include-raw YAML tag has been deprecated in jenkins-job-builder 6.1.

Use new !include-raw-verbatim tag instead.

The Jenkins instance located at jenkins.softwareheritage.org now
uses java 17 so align the base docker image used to test jenkins
jobs changes accordingly.

Some swh packages like provenance use main as default branch name
instead of master.

It was needed to make orcxx-rs build, but we don't use that dependency anymore

swh/devel/swh-graph!601 removes the Java code

It should not be needed any more since the docker test suite now use only
docker chosen ports to expose the edge router (nginx).

Run job in the Jenkins docker agent.

Add support for testing merge requests.

Update kafka broker URL.

Latest release of jenkins-job-builder is now attempting to delete old
Jenkins views when updating but this new code triggers an exception when
deploying jobs on our Jenkins instance, so add option --jobs-only to
jenkins-job update command as a workaround to restore previous behavior.

When rebuilding a merge request for the swh-jenkins-dockerfiles repository
by manually triggering the job from the jenkins UI, the built images were
pushed on the swh container registry but it should only happen when pushing
a commit to the master branch.

Errors can happen otherwise when executed on a different node.

This was missed when the job was turned to a pipeline one.

It notably enables to use the same docker image for running tests as
in jobs testing swh packages independently.

More integration tests require more time...

The swh-docker-dev was only a daily build of the same build script than
the docker-tests one.

Now the job is only concerned by the docker git repository, we no longer
need to filter the execution of the docker build image step and the
docker test step.

Also document a bit the handling of the '--no-cache' argument when
building the swh/stack docker image.

It seems one cannot override the 'gitlab_project_name' in a job-template
if it has already been defined in the job-group section...