• Jenkins
• TODO

jenkins-admin@ TODO list

ci.FreeBSD.org

Jenkins on FreeBSD

TBD Items

• Pipeline execution time: building world & kernel is faster than running full regression tests. We might do:

  • Build world & kernel as often as we can, then trigger full regression tests if there is no one running.

  • Wait until a full regression test complete, then start next round building world & kernel

• Create job naming convention
• How to do real hardware test?
• How to work with re@?
  • Provide snapshot build
  • Perform ABI compatibility check

Details

Integration with reviews.FreeBSD.org

• Master branch of https://github.com/uber/phabricator-jenkins-plugin supports svn repository, but has no official release currently

  • https://issues.jenkins-ci.org/browse/JENKINS-31335

  • Pull request: https://github.com/uber/phabricator-jenkins-plugin/pull/214

• Current jobs:

  • https://ci.freebsd.org/view/phabric/

• Phabricator build rules:

  • https://reviews.freebsd.org/H75

  • https://reviews.freebsd.org/H76

• Phabricator build plans:

  • https://reviews.freebsd.org/harbormaster/plan/6/

  • https://reviews.freebsd.org/harbormaster/plan/5/

  • https://reviews.freebsd.org/harbormaster/plan/4/

• Currently new build only triggered by a patch author is in certain list (committers), for some security consideration.
  • Is it possible for it to be triggered by a tag set by a committer attached to a patch?
• Known issue:

  • error on fetching patch, ex: https://ci.freebsd.org/job/phabric-FreeBSD-head-amd64-build/249/console

    • need to know it's setting error on phabricator site or error of jenkins's phabricator plugin
  • applying a malformated patch cause infinite loop: FreeBSD-head-amd64-build-phabric build #251 generated 20G log
  • if head is broken, all patch builds will fail. so need to check out the latest known buildable revision.

Design more fine-grained pipeline

• https://lists.freebsd.org/pipermail/freebsd-testing/2015-June/001014.html

• ex: quick amd64/i386 build to detect compiling failure first -> make universe / build for other architectures -> test in VM

Design a way to purpose new job easier

• A possible way: make a "template job", some preliminary work:

  • https://github.com/freebsd/freebsd-ci/tree/master/scripts/jail

  • https://github.com/freebsd/freebsd-ci/tree/master/jobs

• Create "FreeBSD jail wrapper" plugin, let user can run almost arbitrary commands inside jail.

• Submit ${JENKINS_HOME}/jobs/<jobname>/config.xml with some additional documents

• Use jenkins-job-builder

  • https://github.com/freebsd/freebsd-ci/tree/master/jjb

• Let user can easily test locally

Revive clang-scan-build job

• Use Clang Scan-Build Plugin

• Use make analyze:

  make CLANG_ANALYZE_OUTPUT_DIR=${WORKSPACE}/clangScanBuildReports CLANG_ANALYZE_OUTPUT=html analyze

• Perhaps make "make analyze" recursively check all sub-directories when type in /usr/src ?

• Current amd64 job: https://ci.freebsd.org/job/FreeBSD-head-scan_build/

  • Latest result: https://ci.freebsd.org/job/FreeBSD-head-scan_build/lastCompletedBuild/clangScanBuildBugs/

Check reproducible build

• Related tools:

  • sysutils/py-diffoscope

  • HTML Publisher Plugin

• Issues:
  • Cannot use settimeofday(2) in jail, the second build should use VM

Non-default-on tests: DTrace test suite

• src.conf: WITH_DTRACE_TESTS

• amd64: https://ci.freebsd.org/job/FreeBSD-head-amd64-dtrace_test/

• TODO: distfile dedup

Provide more images on artifact server

• need makefs(8) support to replace mount_msdosfs(8) usage in jail
  • need to import new makefs(8) from NetBSD.

  • In progress, see https://github.com/emaste/freebsd/blob/makefs-wip/TODO-makefs.md

CategoryTodo