Make sure a site can be succesfully moved to another platform (ie: release), To ensure that the site can successfully run on it's destination platform. Also pick up if a db update is required.

We don't have to do this immediately, as we can roll back on issues, but without this functionality we are operating with much less of a safety net.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

anarcat’s picture

Project: Hostmaster (Aegir) » Hosting
Version: 5.x-0.1-alpha3 » 5.x-0.1-beta1

This belongs to hosting.

anarcat’s picture

Priority: Normal » Critical

We should probably do this for 0.2.

anarcat’s picture

Status: Active » Reviewed & tested by the community

I think this works now. We can't downgrade drupals. Not sure all is done, maybe adrian can comment on that.

adrian’s picture

Status: Reviewed & tested by the community » Needs work

Not there yet.

http://drupal.org/node/368294 is a pre-requisite for this, and i'm almost done with it.

adrian’s picture

The requirements are now basically done.

What needs to happen now is we need to test the packages associated between the platforms.

ie: Select the packages between the two target platforms and compare them.

adrian’s picture

FileSize
57.62 KB

Yay. getting there

adrian’s picture

FileSize
91.32 KB
91.24 KB

Committing what i have so far.

I realized the only way to do this was to provide the user with the relevant details so they could make up their own mind.
I still need to do the form plumbing.

You need to run update.php, and this will create new verify tasks for _EVERYTHING_.

This can take a long while.

We have some cleaning up to do of this from a UX standpoint too.

On the provision side, the backend should do some checking from the package manifests during validate as well.

adrian’s picture

FileSize
94.72 KB

Added form elements and made the form validate.

sadly, migrate seems broken on the provision side now =\

This screen also needs a bit of css love.

adrian’s picture

FileSize
83.66 KB

And this is what it looks like.

I'm stopping here.

We can create new tickets for any issues we find, and i'm sure there will be several.

adrian’s picture

Version: 5.x-0.1-beta1 » 5.x-0.2.x-dev
Status: Needs work » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.