-
Enhancement
-
Resolution: Not an Issue
-
P2
-
7
-
None
-
other
-
other
Soalris 11 requires IPS packages. Dsitribution engineering does not build the bundles for solaris sparc and solaris x86. Two bundles are reuired for every build the SVR4 bundles and the IPS bundles. Disitribution engineering has created a script and tested it in the engineering environment. The script nees to be integrated and tested in the RE environment.
Engineering has a temporary workaround to produce bundles on demand using Hudson.
The IPS package creation process needs to be integrated into the nightly process. It is really bad practice to have different procedures for building in different teams. Saying it another way we want to produce packages the same way RE will do it so there is no discussion as to how the packages are created. The nightly builds for Java Distribution engineering are to produce IPS packages and run an automated test that verifies that the packages install on sparc and x86 and pass the 32 and 64 bit flag test on each of those systems as well as other tests.
There are two ways to build the packages.
1) Hudson build Service that takes parameters and creates the packages as well as run the tests
2) Script that runs directly in the build system and builds the packages this option requires 3 instances
a) Solaris 11 build machine
b) Solaris 11 X86 test machine
c) Solaris 11 Sparc test machine
You can login into to the build server using ssh and run the build and copy and move files
Use of NFS may add 2-3 hours -- use of direct mounts adds about 15 minutes to the build for build and test
Please note that Solaris 11 does not work the same as 10 so things that just use to work are not quite the same. I can provide assistance with those issues.
If you provide me with directions or an environment to test in I will do the testing and integration or directions on how to create one. The fact that we do not have a staging system for build testing is a *risk*. If we can't do that and need to test this with production environments I do not want tests treated as errors in production building. I am not ready to say that this system will build IPS packages until it is integrated into the build systems and passing the tests on a regular basis.
What I can provide -- 1 set of three instances for development building. I could provide servers for RE but that would be wrong since those machines need to be part of the production build chain that should operate 7x24 with daily analysis of failures and that is not currently occurring. Given the IP address changes it is a really bad time to have the Production daily build with JDS code not working. We may be missing new failures. Is the daily build of JDS working and are we running the tests on it?
Engineering has a temporary workaround to produce bundles on demand using Hudson.
The IPS package creation process needs to be integrated into the nightly process. It is really bad practice to have different procedures for building in different teams. Saying it another way we want to produce packages the same way RE will do it so there is no discussion as to how the packages are created. The nightly builds for Java Distribution engineering are to produce IPS packages and run an automated test that verifies that the packages install on sparc and x86 and pass the 32 and 64 bit flag test on each of those systems as well as other tests.
There are two ways to build the packages.
1) Hudson build Service that takes parameters and creates the packages as well as run the tests
2) Script that runs directly in the build system and builds the packages this option requires 3 instances
a) Solaris 11 build machine
b) Solaris 11 X86 test machine
c) Solaris 11 Sparc test machine
You can login into to the build server using ssh and run the build and copy and move files
Use of NFS may add 2-3 hours -- use of direct mounts adds about 15 minutes to the build for build and test
Please note that Solaris 11 does not work the same as 10 so things that just use to work are not quite the same. I can provide assistance with those issues.
If you provide me with directions or an environment to test in I will do the testing and integration or directions on how to create one. The fact that we do not have a staging system for build testing is a *risk*. If we can't do that and need to test this with production environments I do not want tests treated as errors in production building. I am not ready to say that this system will build IPS packages until it is integrated into the build systems and passing the tests on a regular basis.
What I can provide -- 1 set of three instances for development building. I could provide servers for RE but that would be wrong since those machines need to be part of the production build chain that should operate 7x24 with daily analysis of failures and that is not currently occurring. Given the IP address changes it is a really bad time to have the Production daily build with JDS code not working. We may be missing new failures. Is the daily build of JDS working and are we running the tests on it?
- relates to
-
JDK-6979976 Solaris IPS packages needed for Solaris 11 RR
-
- Closed
-
-
JDK-7023786 Review RE Solaris 11 IPS Engineering has updated the Requirements Document
-
- Closed
-