Date: Sat, 29 Mar 2014 21:17:33 -0400 From: Thomas Hoffmann <trh411@gmail.com> To: freebsd-testing@freebsd.org Subject: Jenkins Dashboard Message-ID: <CAB7-odksLQRnma-Bs5zMdZLK-Lu0c8PxBJsyWAQGh3d4qegzrQ@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Just wanted to say what a great resource the Jenkins Dashboard is for me. I do near-nightly builds of -CURRENT and having a resource that I can use to virtually eliminate build false starts is priceless. Today's experience provides a good example. Just as I was planning for my nightly build, I noticed that FreeBSD_HEAD #370 failed. Looked in the log to see the error and offending item. Waited for the item to be fixed (committed to svn). Waited for build #371 to complete successfully. Proceeded with my nightly build. So, I was able to avoid a failed build (false start), avoid needless posts to the developer on the mailing lists, and avoid opening a needless PR, all because I knew exactly what was going on. Had I decided to build anyway. I could have easily checked out up to the revision causing the problem because I knew which commit caused the build fail. One question: are all the FreeBSD_HEAD builds for amd64? Thanks for this great resource. -Tom
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAB7-odksLQRnma-Bs5zMdZLK-Lu0c8PxBJsyWAQGh3d4qegzrQ>