2. Updating a version NEW

2.1. Launching on the daemon development server

The update is automatically launched on the development server under the administration account (aster) via a crontab:

aster @frontal1: ~$ crontab -l

# m h dom mon dow command

# launch of the update

# —————————

#

#

# development releases

# =====

#

# development version

40 0.2 ** 3.4 /home/aster/majnew/prepa_majnew_dvp.csh > /dev/null

…

For the update, the administrator must draw up the list of developers who declared to have performed a restore and file it under /aster/eda/ version /ldvp. This file is built from the list of accounts that submitted a refund during EDA (/aster/pre_eda/ version). The update procedure will verify that all renderings have been completed correctly (iret=0 or iret=2) and then submit the prepa_majnew update script.

The /home/aster/majnew/prepa_majnew_dvp.csh script prepares a file that can be submitted in batch to the reference server.

2.2. The construction of parallel versions

During the update, if the sequential version is built successfully, parallel version MPI is built from the /aster/agla/tool/make_mpi.sh script:

/aster/agla/tool/make_mpi.sh version

version: Code_Aster version concerned (NEW10 to NEW1x).

2.3. The construction of the peripheral versions

During the update, if the sequential version is built successfully, the various peripheral versions are built from the /aster/agla/tool/maj_versions_locales.sh script:

/aster/agla/tool/maj_versions_locales.sh version

version: Code_Aster version concerned (NEW10à NEW1x).