Lifetime Fast Forward Deployment [LFFD]

By Robin Kouwen on 30 Jun

I do understand that the deployment process has been made very simple, trust me, i'm very thankful for that, But I'm just one of those lazy ones that eventually don't want to do anything. 

Would it be nice to be able to fast forward your deployment in lifetime without going through the painstaking  process of manually deploying on each environment over and over just because you made a typo in your description? Imagine having 4 environments D/T/A/P. 

When can this be useful?

  • Only acceptance testing is required, you can do a [LFFD to A]
  • Initial deployments, you can do a [LFFD to P]
  • When documenting or fixing some documentation typos, you can do a [LFFD to P]
  • When you introduce a minor change that don't need to be tested(Never happens ?), you can do a [LFFD to P]
  • Etc etc

You can already do this.

J.Ja

It's just not very obvious.

J.Ja

Hi Robin,

For the sake of whoever reads this thread, I am sharing two of the techniques that can be used to deploy to an arbitrary environment:

1) Create a user with access limited to the source and target environments for the deployment. Login with that user in Lifetime and you can deploy to the target environment (actually, that is the only environment you can deploy to with that user).

2) Use the Deployment API: https://success.outsystems.com/Documentation/10/Reference/OutSystems_APIs/LifeTime_Deployment_API

Joao


Hi


you can also start a deployment, for example D -> T and the first thing you do is clicking on the T environment (there's a dropdown button there), and change to the destination environment you want to.


here is a quick gif to illustrate what I've described earlier

Yes, what Joao B. showed is what I meant. It's not obvious (and OutSystems needs to make this more obvious, I did not know about it for a long time either!), but it's been there for a while.

J.Ja

Hi JB and JJ, 

I know about this technique as I have been using it for quite some time on some hybrid environments. This method skips completely the middle server during deployment, Which is great if you are having multiple production environment like in the Hybrid scenario, And if you don’t need the applications on both servers. I was more thinking of a way to populate all your servers with just one click.