I think it would be useful to work with revisions, thinking about ways :
- on the destination force a revision for each deploy (the log message would have to be automatic)
- upload the node with its revision(s) from the source server (question is whether to take only the last rev, or which ones to take ...)

It is probably more of an issue for services ? I havent seen anything revision related in their open issues.
thanks

Comments

gdd’s picture

gdd
he/him
Primary language English
Location Portland, OR
commented
Status: Active » Postponed

It would be a problem for both me AND Services to support revisions. Unfortunately I don't think this is going to happen in the current version. However it is a good feature, so I am marking it Postponed.

nonsie’s picture

nonsie
she/her
Primary language Estonian
commented

Subscribing - I'd love to have support for revisions.

okeedoak’s picture

okeedoak commented

This feature makes sense to have implemented. So right now there's no roll back functionality on the destination server after a deploy (?), but there could be on the source server though, right, at least for simple node updates?

jpwarren00’s picture

jpwarren00 commented

So the major problem with implementing 'revisions support' is the services module? Do you want me to see if I can figure out a work-around? It should be possible since you have to have deploy installed on both staging and production machines.

gdd’s picture

gdd
he/him
Primary language English
Location Portland, OR
commented

I'm having a hard time seeing how revisions fit into deploy. Do people want to be able to push a specific revision? To push all revisions when a node is deployed? I'd like some thoughts on how this would work.

jpwarren00’s picture

jpwarren00 commented

While I personally don't see a need for it in most sites, the project I just signed on with has to meet some strict government documentation standards. Enabling revision support in deployment would simplify the process, keep it all in Drupal without any outside scripts, and make it more reliable.

By the way, as part of the project I'm on, I'd like to help you maintain the project and close out some TODOs. Could I help out as a maintainer?

-John W

gdd’s picture

gdd
he/him
Primary language English
Location Portland, OR
commented

I still don't understand what you want deploy revision control to do. If you have four revisions on the local server, do you want them all to move to the live server when you push? If you have revisions turned on on the remote server, a revision will currently be created when the node is pushed. I guess I still don't understand what this feature should look like.

keltic’s picture

keltic commented

We have a business requirement to only deploy the latest non-draft revision of referenced nodes. Currently, we are seeing draft revisions get pushed into production when another node references it.

I dug into this and determined that the actual business requirement was that nodes only get deployed if they are added to a plan, not if they are referenced by another node added to a plan. However, this is not possible without breaking referential integrity.

The current revisions, not the draft revisions, are getting deployed properly.