Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Test upgrade from v0.0.6 and below to v0.1.0 #47

Open
lazypower opened this issue Jun 2, 2015 · 0 comments
Open

Test upgrade from v0.0.6 and below to v0.1.0 #47

lazypower opened this issue Jun 2, 2015 · 0 comments
Assignees
@lazypower
Labels
help wanted question
Milestone
v0.1.2

Comments

@lazypower
Copy link
Owner

With the release of v0.1.0 there are some changes to the core structure of the charm that need to be tested in isolation when upgrading, to ensure were fetching the ansiblecharm support, and other required libs that are now direct dependencies for the charm.
@lazypower lazypower added this to the v0.1.0 milestone Jun 2, 2015
@lazypower lazypower self-assigned this Jun 2, 2015
@lazypower lazypower modified the milestones: v0.1.1, v0.1.0, v0.1.2 Jun 2, 2015
lazypower pushed a commit that referenced this issue Sep 12, 2015
Updates to new docker repo
021882b 
Adds the new docker repository + key to latest_docker.yaml
updates config.yaml with new format for version, dependent on the apt
string. If no version specified, defaults to the metapackage (useful for
always getting latest)

Refactored tests which were blocking acceptance
removed the unit_test directive from the testplan yaml as it was causing
weird side-effect behavior in canonical ci

closes #22, #47
@lazypower lazypower mentioned this issue Sep 12, 2015
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lazypower lazypower

Labels
help wanted question
Projects
None yet
Milestone
v0.1.2
Development

No branches or pull requests
1 participant
@lazypower