OpenSolaris

1. Community: OS/Net (ON)
   1. Blogs
   2. Development Process
   3. Developer's Reference
      1. Introduction
      2. Prerequisites
      3. The Source Tree, part 1
      4. The Source Tree, part 2
      5. Building OpenSolaris
      6. Installing and Testing OpenSolaris
      7. Integration Procedure
      8. Best Practices and Requirements
      9. Glossary
   4. Discussions
   5. Installation (from source) Quickstart
      1. Annotated nightly(1) Mail Example
   6. Currently Known Issues
   7. CRT
      1. Advocates & Sponsors
      2. Becoming a CRT Advocate
      3. Charter
      4. RTI nits to avoid
      5. Sponsor Tasks
      6. Becoming a Sponsor
   8. Schedule
   9. ONNV Flag Days, Heads Ups, and Project Integration History
      1. All
      2. Builds 91-95
      3. Builds 86-90
      4. Builds 81-85
      5. Builds 76-80
      6. Builds 71-75
      7. Builds 66-70
      8. Builds 61-65
      9. Builds 56-60
      10. Builds 51-55
      11. Builds 46-50
      12. Builds 41-45
      13. Builds 36-40
      14. Builds 31-35
      15. Builds 26-30
      16. Builds 21-25
   10. Leaders
   11. Observers
   12. Putback Logs
   13. Developing Solaris
       1. Quality Death Spiral
   14. wx
   15. findunref and unreferenced files
   16. Bourne/Korn Shell Coding Conventions

Heads Up: per-system customization and user-configurable hooks added to nightly.sh

Date: Fri, 31 Aug 2007 17:12:34 -0400
From: Bill Sommerfeld <sommerfeld at sun dot com>
To: onnv-gate <onnv-gate at onnv dot eng dot sun dot com>
Subject: Heads Up: per-system customization and user-configurable hooks added to nightly.sh

With the integration of:

6584986 *nightly* needs a hook for shared build machines

the single post-nightly "hook" introduced by 6451117 has been
generalized into six hooks which run at various points during the
build.

In addition, nightly(1) will now read /etc/nightly.conf (if it exists)
prior to reading the developer-specified environment file, permitting
system-wide defaults and hooks to be established by build machine
maintainers; as the developer environment file is read immediately
afterwards, the developer remains free to override the defaults.

Developers and build machine maintainers interested in using these
features should review the revised nightly man page for more
information.

Other bugs may interfere with global default settings, including:

6343373 nightly.sh ignores existing DMAKE_MAX_JOBS
6439703 default nightly env files should not force empty $BUILD_PROJECT

Build machine maintainers must be careful when setting defaults to
avoid unanticipated side effects.