You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now apps:rename does a redeploy, and apps:fork does a rerelease and a redeploy. This should arguably be done by having the relevant parts of a redeploy/release handled by rename-app/fork-app hooks in the relevant release and deploy plugins (as rerelease-and-redeploy may be better accomplished by different means when renaming or forking).
The text was updated successfully, but these errors were encountered:
stuartpb
changed the title
Redeploying on apps:rename
Redeploying/releasing on apps:rename/fork
Aug 7, 2014
As an example, apps:fork does not do a rebuild, because buildstep handles forking builds differently (it creates a cheap copy of the existing build image).
Indeed, the idea that a rename doesn't require a redeploy (or even a rebuild!) is a little presumptive (who says there isn't a plugin that adds the app's name to the environment)?
Right now apps:rename does a redeploy, and apps:fork does a rerelease and a redeploy. This should arguably be done by having the relevant parts of a redeploy/release handled by
rename-app
/fork-app
hooks in the relevant release and deploy plugins (as rerelease-and-redeploy may be better accomplished by different means when renaming or forking).The text was updated successfully, but these errors were encountered: