logo_kerberos.gif

Continuous integration

From K5Wiki
(Difference between revisions)
Jump to: navigation, search
(AppVeyor URL works now)
 
Line 25: Line 25:
 
http://web.mit.edu/krbdev/testing/README.txt
 
http://web.mit.edu/krbdev/testing/README.txt
   
We run a nightly cron job on two machines (one Linux, one Solaris) which builds a snapshot and reports success or failure. This is currently our only regular build for Solaris; if we set up a Solaris buildbot slave, then we can decommission the nightly build infrastructure.
+
We run a nightly cron job on two machines (one Linux, one Solaris) which builds a snapshot and reports success or failure. We now have a Solaris buildbot worker, so we can probably decommission the nightly build infrastructure.

Latest revision as of 18:44, 23 February 2017


Our continuous integration infrastructure includes Buildbot, Travis CI, AppVeyor, and a nightly cron job.

Contents

[edit] Buildbot

http://krbdev.mit.edu/buildbot/

Automatically builds and tests master and active release branches on every push (with a 5-minute stability timer). Doesn't currently build pull requests. Periodically does a Coverity Scan build.

[edit] Travis CI

https://travis-ci.org/krb5/krb5

Builds and tests all active branches and pull requests. Use [ci skip] in a commit message to request that Travis skip that commit.

[edit] AppVeyor

https://ci.appveyor.com/project/krb5/krb5

Build and tests all active branches and pull requests under Windows.

[edit] Nightly builds

http://web.mit.edu/krbdev/testing/README.txt

We run a nightly cron job on two machines (one Linux, one Solaris) which builds a snapshot and reports success or failure. We now have a Solaris buildbot worker, so we can probably decommission the nightly build infrastructure.

Personal tools