zshaheen/github_release.png

## github_release.png

      
    Raw
  

              github_release.png
            
          
## how_to_release_e3sm_diags.md

      
    Raw
  

              how_to_release_e3sm_diags.md
            
          
    How to Prepare a Release for the E3SM Diagnostics Package

In this guide, we'll cover:

preparing the code for a release
releasing the code on Github
releasing the software on Anaconda
building and releasing the Docker image

Preparing The Code For Release

These steps entail modifying files before a release is made.


Pull the lastest code from whatever branch you want to release from. It's usually master.
git checkout master
git pull origin master


Edit the version argument in setup.py to the new version. Don't prefix this with a "v".
setup(
    name="e3sm_diags",
    version="1.1.0",  # Change this line.
    author="Chengzhu (Jill) Zhang, Zeshawn Shaheen",
    author_email="zhang40@llnl.gov, shaheen2@llnl.gov",
    description="E3SM Diagnostics",
    scripts=["acme_diags/acme_diags_driver.py"],
    packages=find_packages(exclude=["*.test", "*.test.*", "test.*", "test"]),
    data_files=data_files,
    entry_points={
        'console_scripts': [
            'e3sm_diags=acme_diags.acme_diags_driver:main',
            'acme_diags=acme_diags.acme_diags_driver:main'
    ]}
)


Edit the version label in the Dockerfile as well.
label version="1.1.0"  # Change this line.


Edit __version__ in acme_diags/__init__.py. We use __version__ when generating the viewer webpages.
__version__ = 'v1.1.0'


Change the version and git_rev tag in conda/meta.yaml. version is what the version of the software will be on Anaconda and git_rev is the tag that we'll setup on GitHub in the next section.
When running conda build, conda will download the code tagged by git_rev. Even though meta-release.yaml is in your local clone of the repo, running conda build from here does not build the package based on your local code.
package:
    name: e3sm_diags
    version: 1.1.0

source:
    git_url: git://github.com/E3SM-Project/e3sm_diags
    git_rev: v1.1.0


Now in conda/e3sm_diags_env.yml, change the version of e3sm_diags under the dependencies tag to whatever version is in the previous step.
We don't need to edit anything in conda/e3sm_diags_env_dev.yml because there is no version of e3sm_diags installed in the environment for that yml file.
dependencies:
- e3sm_diags=1.1.0


Commit and push your changes
git commit -am 'Changes before release.'
git push origin master


Creating A Release On GitHub


Go to the Releases on the GitHub repo of the project here and draft a new release.
The tag should be what git_rev was in step 4 of the previous section. You can change the branch which you want to release from, this is specified after the tag (@ Target: master).
The title of a release is often the same as the tag, but you can set it to whatever you want.
Remember to write a description.


Example of a completed page to release the code
 
Releasing The Software On Anaconda


Since we're building with noarch, you can run the below steps on either a Linux or macOS machine. You do not need to run this steps on both.


Make sure you have the latest versions of anaconda, conda and conda-build. You cannot be in an existing Anaconda environment when you run conda update, so run conda deactivate first. If the conda deactivate command doesn't work, use source deactivate. This means you have an older version of Anaconda, which should be remedied after the following commands.
conda deactivate
conda update anaconda conda conda-build


Go on your machine and pull the latest version of the code. This will have the meta.yaml we edited in the first section.
git checkout master
git pull origin master


Run the command below. The conda/ folder is where meta.yaml is located and the channels are where the dependencies defined in meta.yaml can be found.
conda build conda/ -c conda-forge -c cdat


When conda build is completed, you should see something like the example below. We only have one package of type noarch, so it's compatible with both Python 2 and 3. But since we only officially support Python 3, it might not work with Python 2.
# Automatic uploading is disabled
# If you want to upload package(s) to anaconda.org later, type:

anaconda upload /Users/shaheen2/anaconda3/conda-bld/noarch/e3sm_diags-1.1.0-py_0.tar.bz2

# To have conda build upload to anaconda.org automatically, use
# $ conda config --set anaconda_upload yes

Copy the anaconda upload command and append -u e3sm to upload the package to the e3sm Anaconda channel. Below is an example.
anaconda upload /Users/shaheen2/anaconda2/conda-bld/osx-64/e3sm_diags-1.1.0-0-py_0.tar.bz2 -u e3sm

If the command isn't found, it's in the bin folder of where Anaconda is installed.
So instead of anaconda upload, try one of the following:
~/anaconda2/bin/anaconda upload ...
~/anaconda3/bin/anaconda upload ...

If you're having permission issues uploading a package to either of these channels, contact either Jill Zhang (zhang40@llnl.gov) or Charles Doutriaux (doutriaux1@llnl.gov) for permission. If they don't respond, I guess you can contact Zeshawn Shaheen (shaheen2@llnl.gov).


Check the https://anaconda.org/e3sm page to view the newly updated package.


Notify the maintainers of the unified E3SM environment about the new release on the E3SM Confluence site.


How To Build and Release The Docker Image

A Docker image of e3sm_diags needs to be created and released as well.
This Docker image can be ran as a container via Docker, Shifter, or Singularity.
We'll build the image, test it, and then release it.
Prerequisites


Please make a Docker ID if you haven't done so already.
This is needed to release and upload the image.


Also make sure that you have access to the e3sm Dockerhub, and specifically the e3sm_diags repo there.
If you don't, you'll see an error when you run docker push later on in this guide.
Email Jill Zhang (zhang40@llnl.gov) or Rob Jacob (jacob@anl.gov)


Building


Set an environmental variable, E3SM_DIAGS_VERSION, to the version that you're releasing.
export E3SM_DIAGS_VERSION=v1.5.0


A Temporary Diversion


When installing the software, a user needs to do pip install --user . instead of the traditional python setup.py install. It's the way Anaconda recommends creating packages. This is currently causing issues when building the Docker image. Due to this, open setup.py and change the INSTALL_PATH to be os.path.join(sys.prefix, 'share/e3sm_diags/').
# INSTALL_PATH = 'share/e3sm_diags/'
INSTALL_PATH = os.path.join(sys.prefix, 'share/e3sm_diags/')


Open the Dockerfile and change any instance of pip install --user . to python setup.py install.
RUN conda env update -n base --file conda/e3sm_diags_env_dev.yml && \
        conda clean --all -y && \
        source activate base && \
        # pip install --user . && \
        python setup.py install && \
        rm -r build/


Back to Building the Image


Go to the root of the project, where the Dockerfile is located and run the command below.
This builds the image and adds two tags, one titled latest and one based on the version you're releasing. By prefixing the tag with e3sm/, it'll upload it to the e3sm Dockerhub, which we'll do in forthcoming steps.
When Docker builds an image, it sends all of the data in the current working directory as the build context. So if the current directory has a lot of data (like sample runs, large nc files, etc), remove them before continuing. Check the size of the current directory with du -sh ..
docker build . -t e3sm/e3sm_diags:latest -t e3sm/e3sm_diags:$E3SM_DIAGS_VERSION


View the Docker images you have. You should see the images you've made, based on the tags.
docker images

You should see something like this:
REPOSITORY               TAG                 IMAGE ID            CREATED             SIZE
e3sm/e3sm_diags          latest              bc7f93375025        6 minutes ago       3.57GB
e3sm/e3sm_diags          v1.5.0              bc7f93375025        6 minutes ago       3.57GB
continuumio/miniconda    4.5.4               16e4fbac86ce        7 weeks ago         544MB
hello-world              latest              e38bc07ac18e        5 months ago        1.85kB


Testing


Go to the folder with the system tests.
cd tests/system/


wget or curl the script to run the image. When you actually run an image, it's called a container.
wget https://raw.githubusercontent.com/E3SM-Project/e3sm_diags/master/acme_diags/container/e3sm_diags_container.py

# Or use this:
curl -O https://raw.githubusercontent.com/E3SM-Project/e3sm_diags/master/acme_diags/container/e3sm_diags_container.py


Run the tests twice with both graphical backends.
Check the terminal and results after each run to ensure that everything was created without errors.
python e3sm_diags_container.py --docker -p all_sets.py -d all_sets.cfg
python e3sm_diags_container.py --docker -p all_sets.py -d all_sets.cfg --backend vcs


If you do find an error, it could be with the script e3sm_diags_container.py or with e3sm_diags itself.
Please fix this. You might need to delete the release, or release a bug-fix version.


Releasing


Push both of the images, one with the latest tag and the other with the version you're releasing.
docker push e3sm/e3sm_diags:latest
docker push e3sm/e3sm_diags:$E3SM_DIAGS_VERSION


Congratulations, you're done! You can go home/nap for the day, I won't tell.


Optional: Cleanup


These images can take up a fair amount of space on your machine, since each is around 4GB. Here are some ways to manage them.

View all of the images you have with docker images.
You can remove an image by the image id.
The --force option is also supported.
docker rmi <image_id>


Run the command below once in a while to remove unused data. This includes any intermediate or broken images/container.
docker system prune