Revision as of 15:05, 6 November 2009 by Admin (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)

CND incremental builds


  • The primary goal is early errors discovery. For this purpose:
  • Run a CND cluster rebuild and extended set of CND unit tests and metrics on a regular basis, frequently (after each commit or set of commits into CND)
  • Make results easily accessible and understandable for the team
  • Allow mail notification for failures, regressions, etc

Tests to run

  • Full CND JUnit test suite (including several remote development tests)
  • Close-source codemodel tests (/set/ide/mars/intg/codemodeltests)
  • I18n test script
  • Compiler warnings check
  • FindBugs


  • Solaris x86

Technical details


Server address

Builds are run on elif server, upon each push that affects CND. Address is



There is a mail alias,

Notifications are sent to this alias in the following cases:

  • Build failed
  • Build became unstable
  • Build is back to normal
  • I18N check is failed (a separate notification with failure lines is sent)

How to install static code checkers on your machine

There is no released version of Netbeans integration yet. However a snapshot is available:

It contains 52 plugins that have complex mutual dependencies. I installed them all except the ones that contain "Maven" word in their names.

FindBugs seems to work more or less ok.

Please be aware that it consumes a lot of memory.



Glass fish resides in /opt/SUNWappserver

Hudson resides in /export1/hudson/

CND incremental bilds are in /export1/hudson/jobs/cnd-incremental-build/

App Server log is /opt/SUNWappserver/domains/domain1/logs/server.log

So to see the processes run by application server, use
ps -Af | grep /opt/SUNWapp
and then use ptree

Restarting application server.

  • Login to elif as administrator
  • Make sure .bashrc is run
  • Run /opt/SUNWappserver/bin/asadmin stop-domain domain1
  • Run /opt/SUNWappserver/bin/asadmin start-domain domain1

Sometimes VNC server gets stuck, then use pgrep and kill unnecessary instances (but make sure you won't kill the one that runs on :1 or one launched by somebody other - use pargs and ptree to investigate)

Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo