← Back to branch summary

~alejdg/mojo/mojo-specs

« back to all changes in this revision

Viewing changes to mojo-how-to/manifests/test-autodeploy

  • Committer: mergebot at canonical
  • Author(s): "Tom Haddon"
  • Date: 2020-01-15 11:01:39 UTC
  • mfrom: (146.1.2 no-more-build-phase)
  • Revision ID: mergebot@juju-139df4-prod-is-toolbox-0.canonical.com-20200115110139-ikaks76a0eiq3id9
mojo-how-to: Switch from build to script steps for the example project, so it can be used from a containerless project

Reviewed-on: https://code.launchpad.net/~mthaddon/mojo/no-more-build-phase/+merge/377622
Reviewed-by: Benjamin Allot <benjamin.allot@canonical.com>

Show diffs side-by-side

added added

removed removed

Lines of Context:
mojo-how-to/manifests/test-autodeploy
11
11
# Having confirmed there's a deployment to test, we first need to bring the
12
12
# environment up in it's current state on production
13
13
 
14
 
# We need the markdown package to be able to generate the docs for Mojo
15
 
builddeps packages=make,markdown,bzr
16
14
# Run the collect step
17
15
collect
18
16
# Run the build step
19
 
build config=build-production-revno
 
17
script config=build-production-revno
20
18
# Deploy services only
21
19
deploy config=services local=services-secret delay=0
22
20
# Copy our built resources to the instances