5.3.2.5.1. Pre-Release Checklist¶
The bulk of the work to release each component is to verify that the component is ready for release. Below is the list of verifications that must be executed before proceeding with the release. If any of these steps fail, the problem identified must be fixed before you can proceed with the tag and release steps.
- Verify a release is warranted
- Verify the changelog
- Verify RPMs can be created
- Verify unit tests pass
- Verify acceptance tests pass
- Verify the component RPM upgrade succeeds
- Verify the component yields valid SIMP ISOs
5.3.2.5.1.1. Verify a release is warranted¶
The check verifies a new release is warranted and the version has been properly updated.
Clone the component repository and checkout the development branch to be tagged
git clone https://github.com/simp/simp-adapter.git cd simp-adapter git checkout master # this step isn't needed for master branch
Manually compare manually the development branch with the last release tag. (The existing rake task
compare_latest_tag
won’t necessarily work here.)git fetch -t origin # manually figure out which is last tag git diff tags/<last release tag> --name-only # manually verify mission-impacting changes have been # made (i.e., changes that warrant a release) and the # version has been updated in the CHANGELOG, version.rb # and/or build/<component>.spec file.
5.3.2.5.1.2. Verify the changelog¶
This check verifies the changelog information is available and can be extracted:
- Manually inspect the appropriate file (CHANGELOG or %changelog
section of <component>.spec file). (The existing rake task
changelog_annotation
won’t necessarily work here.) - FIXME
simp-doc
has its ownCHANGELOG
, but requires theChangelog.rst
fromsimp-core
to be current as well. It may make more sense to move thesimp-doc
release into the instructions for releasing a SIMP ISO.
5.3.2.5.1.3. Verify RPMs can be created¶
This check verifies that an RPM can be generated for this module from
simp-core
:
Clone
simp-core
git clone https://github.com/simp/simp-core.git``
Update the URL for the component under test
Puppetfile.tracking
, if neededcd simp-core vi Puppetfile.tracking
Build RPM
bundle update bundle exec rake deps:checkout bundle exec rake pkg:single[adapter]
Note
This command will build the RPM for the OS of the server on which it was executed.
5.3.2.5.1.4. Verify unit tests pass¶
This check verifies that the component’s unit tests have succeeded in TravisCI:
- Navigate to the project’s TravisCI results page and verify the tests for the development branch to be tagged and released have passed. For our project, this page is https://travis-ci.org/simp/simp-adapter/branches
Important
If the tests in TravisCI fail, you must fix them before proceeding. The automated release procedures will only succeed, if the unit tests succeed in TravisCI.
5.3.2.5.1.5. Verify acceptance tests pass¶
This check verifies that the component’s acceptance tests have succeeded:
Run the appropriate acceptance test rake task, if it exists. For this project,
rake beaker:suites
is the appropriate taskbundle exec rake beaker:suites
Note
If the GitLab instance for the project is configured and current (it is sync’d every 3 hours), you can look at the latest acceptance test results run by GitLab. For our project, the results would be at https://gitlab.com/simp/simp-adapter/pipelines.
5.3.2.5.1.6. Verify the component RPM upgrade succeeds¶
This check verifies that the RPM for this component can be used to upgrade the last full SIMP release. For both CentOS 6 and CentOS 7, do the following:
Bring up a CentOS server that was booted from the appropriate SIMP ISO and for which
simp config
andsimp bootstrap
has been run.Note
If the VirtualBox for the last SIMP ISO was created by the simp-packer project, you can simply setup the appropriate VirtualBox network for that box and then bring up that bootstrapped image with
vagrant up
.Copy the component RPM generated from the above RPM verification step to the server and install with yum. For example,
sudo yum install simp-adapter-0.0.3-0.el7.noarch.rpm
Note
If the component requires updated dependencies, those RPMs will have to be built and installed at the same time.
Verify the
puppet agent
runs succeed on the Puppet master- login as root
- execute
puppet agent -t
Execute any other verifications unique to the component
5.3.2.5.1.7. Verify the component yields valid SIMP ISOs¶
This check verifies that with this component, valid SIMP ISOs for
for CentoOS 6 and CentOS 7 can be built. An ISO is considered
to be valid when a SIMP server can be booted from it, configured via
simp config
, and then bootstrapped via simp bootstrap
. For
CentOS 6 and CentOS 7:
Login to a machine that has Docker installed and the
docker
service running.Important
In our development environment, the version of Docker that is available with CentOS works best.
Checkout the
simp-core
project for the last SIMP release. For this discussion, we will assume it is6.0.0-1
.git clone https://github.com/simp/simp-core.git`` cd simp-core git fetch -t origin git checkout tags/6.0.0-1
Create a
Puppetfile.tracking
file that contains the contents ofPuppetfile.stable
in which the URLs for the component and any of its updated dependencies have been updated to reference the versions under test.Populate
simp-core/ISO
directory with CentOS6/7 distribution ISOsmkdir ISO cp /net/ISO/Distribution_ISOs/CentOS-6.9-x86_64-bin-DVD*.iso ISO/ cp /net/ISO/Distribution_ISOs/CentOS-7-x86_64-1708.iso ISO/
Build each ISO for CentOS 6 and CentOS 7. For example,
bundle update SIMP_BUILD_docs=no \ SIMP_BUILD_verbose=yes \ SIMP_PKG_verbose=yes \ bundle exec rake beaker:suites[rpm_docker]
Important
- By default, the
default.yml
for therpm_docker
suite builds an ISO for CentOS 7. You must manually edit thedefault.yml
file to disable theel7-build-server
instead of theel6-build-server
, in order to create a CentOS 6 ISO. - The most reliable way to build each ISO is from a clean checkout
of
simp-core
.
- By default, the
Use simp-packer to verify the SIMP ISO can be bootstrapped, when booted with the default options.