Skip to content

Commit

Permalink
Passes env var during apt-test upgrade testing
Browse files Browse the repository at this point in the history
Pointed out by @msheiny during review, so lifting the patch from PR
discussion and implementing to resolve. The goal is to ensure that the
"use apt-test repo" env var is declared during the "create" phase of the
scenario, which is now handled.
  • Loading branch information
Conor Schaefer committed Jan 4, 2019
1 parent 6c837ff commit 9303a4d
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 1 deletion.
4 changes: 4 additions & 0 deletions Makefile
Original file line number Diff line number Diff line change
Expand Up @@ -167,6 +167,10 @@ clean: ## DANGER! Purges all site-specific info and developer files from project
upgrade-start: ## Boot up an upgrade test base environment using libvirt
@SD_UPGRADE_BASE=$(STABLE_VER) molecule converge -s upgrade

.PHONY: upgrade-start-qa
upgrade-start-qa: ## Boot up an upgrade test base env using libvirt in remote apt mode
@SD_UPGRADE_BASE=$(STABLE_VER) QA_APTTEST=yes molecule converge -s upgrade

.PHONY: upgrade-destroy
upgrade-destroy: ## Destroy up an upgrade test base environment
@SD_UPGRADE_BASE=$(STABLE_VER) molecule destroy -s upgrade
Expand Down
2 changes: 1 addition & 1 deletion docs/development/upgrade_testing.rst
Original file line number Diff line number Diff line change
Expand Up @@ -79,7 +79,7 @@ create the environment:

.. code:: sh
make upgrade-start
make upgrade-start-qa
Then, log into the *Application Server*:

Expand Down

0 comments on commit 9303a4d

Please sign in to comment.