Jenkins - Revision history

Ardumont: Install redirect to docs page

2021-10-27T10:03:38Z

Install redirect to docs page

← Older revision		Revision as of 10:03, 27 October 2021
Line 1:		Line 1:
	~~= Jenkins =~~		#REDIRECT [[swhdocs:sysadm/deployment/jenkins.html]]

	~~The CI is run by [https://jenkins.io/ Jenkins] on jenkins.softwareheritage.org~~

	~~== Authentication ==~~

	~~Software Heritage staffers can login via the Jenkins Web user interface using the same personal *nix credentials they use to login into other machines.~~

	~~== Jobs ==~~

	~~There are 2 categories of job:~~

	* jobs related to jenkins itself, like running Jenkins Job Builder, updating and managing docker images. These are found in the [https://jenkins.softwareheritage.org/job/jenkins-tools/ jenkins-tools] directory.
	* jobs dedicated to testing/building swh packages.

	~~=== Jobs definition ===~~

	~~Most of the jobs are created using [https://docs.openstack.org/infra/jenkins-job-builder/ Jenkins Job Builder] (aka JJB).~~

	~~The source repository is https://forge.softwareheritage.org/source/swh-jenkins-jobs/~~

	Each time a new revision is pushed on this repo, the [https://jenkins.softwareheritage.org/job/jenkins-tools/job/swh-jenkins-job-builder/ JJB job] is executed. This job updates already existing jobs or create new ones (if any). Beware not to break the JJB job!

	~~=== Job execution environments ===~~

	~~Jenkins job execution may occur either on the Jenkins master node directly (typically for [https://jenkins.softwareheritage.org/job/jenkins-tools/ jenkins-tools] jobs), or in a docker jenkins slave.~~

	~~Docker images used by Jenkins are created and updated using the Dockerfiles in~~
	~~https://forge.softwareheritage.org/source/swh-jenkins-dockerfiles/~~

	~~For now, there are 2 different images:~~

	* swh-jenkins/tox: a Debian stretch with python3 and tox installed; used to run unit tests; it's available in Jenkins under the label [https://jenkins.softwareheritage.org/label/swh-tox/ swh-tox]
	* swh-jenkins/sphinx: based on the former tox image, it adds everything needed to compile the documentation with sphinx; it's available in Jenkins under the label [~~https://jenkins.softwareheritage.org/label/swh-sphinx/ swh-sphinx].~~

	~~=== swh packages ===~~

	~~Each swh package has a Jenkins~~ [~~https://plugins.jenkins.io/cloudbees-folder Folder] in which are all the jobs dedicated to this package.~~

	~~There are two jenkins jobs for each swh package:~~

	* [https://jenkins.softwareheritage.org/job/DCORE/job/tox/ Phab. Diff] (here for [https://forge.softwareheritage.org/source/swh-core/ swh-core]): these jobs are executed each time a Phabricator Diff is created or updated,
	* [https://jenkins.softwareheritage.org/job/DCORE/job/pipeline/ master branch] (here for [https://forge.softwareheritage.org/source/swh-core/ swh-core]): these jobs are executed when git revisions are pushed on the master branch.

	When these jobs are started by Phabricator, the job's end status is pushed back on the Phabricator object that triggered the build (ie. the Diff object or the Revision object). As a result, the build status for a given Diff or git revision will be displayed in the forge.

	~~The Diff in Phabricator will typically look like:~~

	~~[[File:JenkinsDiffReport.png]]~~

	~~The Diffusion view of a git repository will look like:~~

	~~[[File:JenkinsRevisionReport.png]]~~

	~~where the green "checks" in each revision means the CI passed OK on this revision.~~

	~~=== Dashboards and metrics ===~~

	The [https://jenkins.softwareheritage.org/view/swh%20dashboard/ swh dashboard] gives a global view on the CI status of swh packages. It shows all the "master branch" job status for all swh packages, as well as a few metrics for these builds (%success, code coverage, execution time, etc.)

	~~=== Starting a job manually ===~~

	~~[[File:JenkinsBuildButton.png\|frameless\|left]]~~
	You should be able to execute any job by hand. When logged in, on the job's description page (eg. [https://jenkins.softwareheritage.org/view/swh%20dashboard/job/DCORE/job/tests/ swh-core master]) you should be able to push the "Build with Parameters" button which opens a form where you can specify the job's input parameters.

	~~[[File:JenkinsRestartFromStage.png\|frameless\|left]]~~
	~~[[File:JenkinsReplay.png\|frameless\|left]]~~
	Note that you can also restart a (generally failed) job. From the job execution summary (eg. [https://jenkins.softwareheritage.org/view/swh%20dashboard/job/DCORE/job/tests/50/ this execution]) you may find a "Restart from Stage" button (on "master branch" jobs only) or a "Replay" button that will allow you to recreate a job with the same parameters as the original job execution.

	~~== Phabricator ==~~

	~~[https://wiki.softwareheritage.org/wiki/Debian_packaging#Setting_up_the_repository_on_Phabricator Setting up the repository to trigger debian package]~~

	~~== New swh module jenkins job ==~~

	~~[https://wiki.softwareheritage.org/wiki/Debian_packaging#Setting_up_the_Jenkins_jobs Setting up a new swh module jenkins job]~~

	~~[[Category:Software development~~]]

Ardumont: Add links to the actual page declaring the steps to setup phabricator or new jenkins jobs

2020-09-23T13:11:48Z

Add links to the actual page declaring the steps to setup phabricator or new jenkins jobs

← Older revision		Revision as of 13:11, 23 September 2020
Line 70:		Line 70:
	== Phabricator ==		== Phabricator ==

	~~TODO~~		[https://wiki.softwareheritage.org/wiki/Debian_packaging#Setting_up_the_repository_on_Phabricator Setting up the repository to trigger debian package]

			== New swh module jenkins job ==

			[https://wiki.softwareheritage.org/wiki/Debian_packaging#Setting_up_the_Jenkins_jobs Setting up a new swh module jenkins job]

	[[Category:Software development]]		[[Category:Software development]]

StefanoZacchiroli: /* Jobs */

2018-11-27T13:29:49Z

Jobs

← Older revision		Revision as of 13:29, 27 November 2018
Line 11:		Line 11:
	There are 2 categories of job:		There are 2 categories of job:

	- jobs related to jenkins itself, like running Jenkins Job Builder, updating and managing docker images. These are found in the [https://jenkins.softwareheritage.org/job/jenkins-tools/ jenkins-tools] directory.		* jobs related to jenkins itself, like running Jenkins Job Builder, updating and managing docker images. These are found in the [https://jenkins.softwareheritage.org/job/jenkins-tools/ jenkins-tools] directory.
			* jobs dedicated to testing/building swh packages.
	- jobs dedicated to testing/building swh packages.

	=== Jobs definition ===		=== Jobs definition ===
Line 46:		Line 45:
	When these jobs are started by Phabricator, the job's end status is pushed back on the Phabricator object that triggered the build (ie. the Diff object or the Revision object). As a result, the build status for a given Diff or git revision will be displayed in the forge.		When these jobs are started by Phabricator, the job's end status is pushed back on the Phabricator object that triggered the build (ie. the Diff object or the Revision object). As a result, the build status for a given Diff or git revision will be displayed in the forge.

	The Diff in Phabricator will typically look like:		The Diff in Phabricator will typically look like:

	[[File:JenkinsDiffReport.png]]		[[File:JenkinsDiffReport.png]]

Douardda at 08:43, 27 November 2018

2018-11-27T08:43:47Z

@@ Line 1: / Line 1: @@
-For Continuous Integration (CI) we use a (work in progress) Jenkins instance running at https://jenkins.softwareheritage.org/
+= Jenkins =
 == Authentication ==
 Software Heritage staffers can login via the Jenkins Web user interface using the same personal *nix credentials they use to login into other machines.
 [[Category:Software development]]

StefanoZacchiroli at 14:24, 30 October 2018

2018-10-30T14:24:59Z

← Older revision		Revision as of 14:24, 30 October 2018
Line 1:		Line 1:
			For Continuous Integration (CI) we use a (work in progress) Jenkins instance running at https://jenkins.softwareheritage.org/
	~~We have~~ a (work in progress) Jenkins instance running at https://jenkins.softwareheritage.org/

	== Authentication ==		== Authentication ==

StefanoZacchiroli: page stub, just documenting how to login

2018-10-30T14:22:31Z

page stub, just documenting how to login

New page

We have a (work in progress) Jenkins instance running at https://jenkins.softwareheritage.org/

== Authentication ==

Software Heritage staffers can login via the Jenkins Web user interface using the same personal *nix credentials they use to login into other machines.

[[Category:Software development]]