...
Task | Who | Status | Notes |
---|---|---|---|
Update README.txt | JJKP | RC1: RC2: N/A RC2-2: N/A | |
Build Windows installer | JJKP (backup: TGG) | RC1: RC2: RC2-2: RC3: RC4: | Version string: R2014a-rc# |
Bundle Windows zip | JJKP (backup: TGG) | RC1: RC2: RC2-2: RC3: RC4: | Version string: R2014a-rc# |
Run TestComplete smoke tests | TR | RC1: | These are tests on the packaged versions of GMAT: the installer and the zip bundle. |
Run TestComplete system test missions | TR | RC1: | These are tests on the packaged versions of GMAT: the installer and the zip bundle. |
Run script test system | JJKP (backup: TGG) | RC1: RC2: RC2-2: RC3: RC4: | Run the internal installer tests on T4 and the public installer tests on Joel's machine. Run .zip bundle tests afterwards on same build to compare. |
Test all sample scripts | SPH | RC2: | At a minimum these need to be run individually by hand. I ran them by adding the folder, and they run so fast I missed some pretty big problems. Ideally, these should all be in script regression tests. Many but not all already are regression tested. |
Run TestComplete full regression tests | TR | (For final RC only) |
...
- Create the build
- Log into
gs580w-gmat-t4
as "gs580w-gmat-t4\builduser
". The credentials are on the network drive, in theInfrastructure
folder. - Start Task Scheduler.
- [RC1 only] Disable the "GMAT Daily Build" task, so it doesn't run automatically during the RC cycle (this can make things overly confusing).
- Manually run the "GMAT Daily Build" task.
- Log into
- Create the bundles
- On your local system, navigate to
GmatDevelopment\build\install\windows-nsis
. There's aREADME.txt
file there that explains things. - Open a MinGW Shell in this directory.
- Run "
make VERSION="R2014a-rc#"
", where "#
" is the number of the RC you're creating. This will create four packages in the current directory: A.zip
and a.exe
file for both the internal and public versions. - Copy the four package files to the network:
\\mesa-file\595\GMAT\Builds\windows\VS2010_build\R2014a
- To clean everything up afterwards, run "
make clean
".
- On your local system, navigate to
- Run the script test system on the internal installer package. See Running the script test system, below.
...