Linux-Media Archive on lore.kernel.org
 help / color / Atom feed
* [ANN] LinuxTV CI builder
@ 2019-08-12 18:29 Mauro Carvalho Chehab
  0 siblings, 0 replies; only message in thread
From: Mauro Carvalho Chehab @ 2019-08-12 18:29 UTC (permalink / raw)
  To: linux-media

Hi all,

Just want you to know about the latest news:

==================================
CI builder service for LinuxTV.org
==================================

Some of you may probably noticed already: thanks to OSU Open Source Lab[1], 
with is providing us a few VM instances, we now have a Jenkins server
running for the media subsystem. It can be accessed via this URL:

	https://builder.linuxtv.org/

[1] https://osuosl.org/

It is doing periodic builds on the projects related to our work, specially
for the trees hosted at linuxtv.org. I didn't add a job for a few projects
with already have another CI instance running.

Right now, we have the following projects being built:

	Userspace:
		- camorama
		- dtv-scan-tables
		- edid-decode
		- libcamera
		- tvtime
		- v4l-utils
		- xawtv3
		- xawtv4

	Kernelspace:
		- media_build 
		  (against Debian 10.0 Kernel - v4.19);
		- media_tree:
			- allmodconfig: x86_64
			- allyesconfig
				- x86_64, i386, arm and arm64
		- pull requests received by patchwork

Patchwork job
=============

The patchwork job is currently meant to help me to test the pull requests
sent by a media core maintainer, doing part of my own testing workflow.

Right now, it always apply the pull request against the master branch.

This will help me to merge patches quickly, as I'm doing a quicker review
on patches sent by a media core maintainer that the script won't point
any issues.

For patchwork pull requests, it should always do a build and provide
an answer for the build, testing against bisect breakages, and running
checkpatch/sparse/smatch, patch per patch. Currently, it is sending replies
in about 10 minutes or so, but the build time actually depends on the 
number of patches and if they're touching core header files or not.

Email policy
============

Except for the patchwork, the other jobs should send an e-mail to the ML
(and to me) when:

	- a build fails;
	- a failed build got fixed.

It shouldn't be sending e-mails if everything is fine.

Other CI instances related to media
===================================

Please notice that we have some trees with have already a CI instance
running:

	- ZBar:
	  https://travis-ci.org/mchehab/zbar

	- Kaffeine:
	  https://travis-ci.org/mchehab/kaffeine

So, no need to duplicate the efforts by adding them also to our builder.

Please let me know if you find any issues.

Future Plans
============

I'm planning to add support in the future for the CI to also handle patch
series builds from patchwork (against the master branch), but, for that to
work,  it seems that we'll need to upgrade from patchwork's stable version
to  the latest one - or wait for the next patchwork stable version. 

I'm also planning to change the media_build logic in a way that it would
not download media driver tallbals that failed on the builder machine.

Any other suggestions?

Thanks,
Mauro

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, back to index

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-08-12 18:29 [ANN] LinuxTV CI builder Mauro Carvalho Chehab

Linux-Media Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-media/0 linux-media/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-media linux-media/ https://lore.kernel.org/linux-media \
		linux-media@vger.kernel.org linux-media@archiver.kernel.org
	public-inbox-index linux-media


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-media


AGPL code for this site: git clone https://public-inbox.org/ public-inbox