Neon/Builder: Difference between revisions

From KDE Community Wiki
No edit summary
No edit summary
Line 15: Line 15:
The Jenkins jobs are created by running the pangea-tooling script <code>jenkins_jobs_update_nci.rb</code>.  This creates some manual Jobs specified in the script such as the ISO jobs but mostly uses factories to create batches of jobs based on archives.
The Jenkins jobs are created by running the pangea-tooling script <code>jenkins_jobs_update_nci.rb</code>.  This creates some manual Jobs specified in the script such as the ISO jobs but mostly uses factories to create batches of jobs based on archives.


The YAML files in [[https://github.com/blue-systems/pangea-conf-projects pangea-conf-projects]] define what jobs get created.
The YAML files in [https://github.com/blue-systems/pangea-conf-projects pangea-conf-projects] define what jobs get created.


For each package there is a parent MultiJob which runs some sub jobs.
For each package there is a parent MultiJob which runs some sub jobs.


<code>parent job</code> this is set to checkout the relevant archive from [[https://quickgit.kde.org KDE Git]] as source/ (for Developer Editions), then check out the relevant archive from [[https://packaging.neon.kde.org KDE neon Git]] as packaging/.
<code>parent job</code> this is set to checkout the relevant archive from [https://quickgit.kde.org KDE Git] as source/ (for Developer Editions), then check out the relevant archive from [https://packaging.neon.kde.org KDE neon Git] as packaging/. It then runs a number of child jobs...
 
<code>src</code> will create the source package.  For User Edition this means running uscan to use the debian/watch file to download the relevant tar, for Dev Editions it uses the source the parent job checked out.  It then builds the source package.
 
<code>bin</code> job will extract the source, install the build dependencies and compile the package.  It finishes by checking the output from lintian and fails on any errors, you can override errors with lintian-overrides files in the normal .deb packaging method (see dh_lintian).  It also checks for any list-missing files and fails if there are any, override by adding a debian/not-installed files.  It also fails if cmake reports build-dependencies it needs, override with debian/meta cmake-ignore.
 
 
= The Packaging =
 
how to package
ci variable
overlapping files

Revision as of 14:23, 27 September 2016

Neon uses a Jenkins continuous integration system to build its packages

The Setup

drax.kde.org is the master server, owned by Blue Systems and administrated by KDE Sysadmins. It runs a Jenkins instance which is a Continuous Integration website at build.neon.kde.org that has many jobs to build the packages and run other functions, either on demand or at pre-scheduled intervals.

The code behind build.neon is from pangea-tooling which also runs the code for DCI Debian CI, KCI Kubuntu CI, ACI Appstream CI, and MCI Mobile neon Plasma CI.

The Jenkins jobs farm off the hard build work to 4 DigitalOcean build servers.

To use the scripts to access Jenkins you will need to set ~/.config/pangea-jenkins.json using access key available inside Jenkins to administrators.

The Jobs

The Jenkins jobs are created by running the pangea-tooling script jenkins_jobs_update_nci.rb. This creates some manual Jobs specified in the script such as the ISO jobs but mostly uses factories to create batches of jobs based on archives.

The YAML files in pangea-conf-projects define what jobs get created.

For each package there is a parent MultiJob which runs some sub jobs.

parent job this is set to checkout the relevant archive from KDE Git as source/ (for Developer Editions), then check out the relevant archive from KDE neon Git as packaging/. It then runs a number of child jobs...

src will create the source package. For User Edition this means running uscan to use the debian/watch file to download the relevant tar, for Dev Editions it uses the source the parent job checked out. It then builds the source package.

bin job will extract the source, install the build dependencies and compile the package. It finishes by checking the output from lintian and fails on any errors, you can override errors with lintian-overrides files in the normal .deb packaging method (see dh_lintian). It also checks for any list-missing files and fails if there are any, override by adding a debian/not-installed files. It also fails if cmake reports build-dependencies it needs, override with debian/meta cmake-ignore.


The Packaging

how to package ci variable overlapping files