Rev 104 |
Rev 106 |
Go to most recent revision |
Last modification |
Compare with Previous |
View Log
| RSS feed
Last modification
- Rev 105 2007-07-25 10:03:57
- Author: rsolanki
- Log message:
- DevTools/ManagerSuite/Release_Manager: Checkin by Svn Import
Moving forward with the autobuild and having daemon builds, a number of GUI changes have been put in place for different levels of access for users:
Developers:
The Build Environment section under the Package Information section would have the Build Machines:
Solaris, Win32, Linux, Generic. Cannot set Generic with other options, but can set Solaris and Win32 and Linux.
NB:
Solaris could map to any number of Solaris machines, depending on the project eg Solaris 8 sparc, Solaris 10 sparc, Solaris 10 x64, Solaris 11 (coming soon)
Win32 could map to any number of Win32 machines, depending on the project eg XP Server 2003, XP Pro x64 Edition, Vista (coming soon)
ditto Linux
Generic maps to all machines, depending on the project
In addition to that, there would be a section for defining ERG's Build Standards: JATS, ANT or none (only a Leader can check none on a new package, default is JATS on a new package)
Depending on the selection of the Build Standard, the Addendums available would be:
JATS Addendum: Debug, Production, Debug and Production
ANT Addendum: Java 1.4, Java 1.5
Project Administrators
Administrators would be able to configure the build daemons and machtypes per release.
For example, we can associate release ABC with the GBE_MACHTYPES: solaris10_x86, solaris10_sparc, win32 etc.
Each of these GBE_MACHTYPE would be associated with a hostname to identify the build machine delivering that GBE_MACHTYPE.
These daemons would then be associated with a host either in MASTER or SLAVE mode. Only onde daemon can be the master.
<b>Release Date:</b> 07-December-2006