The Jenkins continuous integration environment at builds pull requests using the GitHub Integration Plugin.


The main pull request builder is:

  • pull-requests-bionic (Ubuntu 18.04) runs PostgreSQL 10, MySQL 5.7 and MariaDB 10.2.39. GIS: spatialite 4.3.0a-5, GDAL 2.2.3, GEOS 3.6.2, PostGIS 2.4

Other pull request builders which can be triggered manually with the corresponding comment phrases:

  • pull-requests-oracle runs on Oracle The Oracle tests take about 40 minutes, so we avoid them unless we suspect a change may have broken something on Oracle.
    • buildbot, test on oracle.
  • pull-requests-selenium runs the selenium tests.
    • buildbot, test on selenium.
  • Retired:
    • Ubuntu 12.04 runs PostgreSQL 9.1 and MySQL 5.5. GIS: spatialite 3.0.0~beta, GDAL 1.7.3, GEOS 3.2.2, PostGIS 1.5.3
    • Ubuntu 14.04 runs PostgreSQL 9.3 and MySQL 5.6. GIS: spatialite 4.1.1, GDAL 1.10.1, GEOS 3.4.2, PostGIS 2.1
    • Ubuntu 16.04 runs PostgreSQL 9.5 and MySQL 5.7. GIS: spatialite 4.3.0a-5, GDAL 1.11.3, GEOS 3.5.0, PostGIS 2.2

Other checks

Some other builders run on all pull requests:


Q: The build result disappeared. How do I get it back?

A: Build results are kept for a few days. Repush to your branch if you need to run the build again.

Q: The build failed with "ModuleNotFoundError: No module named 'memcache'"

A: The Python dependencies probably failed to install from PyPI. There's an issue where PyPI sometimes fails to return a correct response.

Q: Why is the disk nearly full on the Jenkins master node?

A: /var/log/jenkins/jenkins.log may be many gigabytes in size. Remove that file and restart Jenkins with service jenkins restart.

Notes for other builds


Python SQLite
3.6.8 3.21.0
3.7.9 3.31.1
3.8.9 3.34.0
3.9.4 3.34.0
3.10.0rc2 3.35.5

(installed with Windows x86-64 executable installer)

Last modified 12 days ago Last modified on 09/08/2021 05:14:46 AM
Back to Top