Skip to Content (Press Enter)
Back to Ideas
53
Like
Follow Idea
Save multiple deployment plans
1344Views
22Comments
Implemented
Lifetime

When working on a large project it is common to do fairly much the same deployment each sprint into our QA environments. It would be great if we could setup the deployment in lifetime, give it a name and save for future deployments. We can sort of do this at the moment but you can only have one saved plus it saves the current versions of everything so if espaces are updated in the source environment you don't get those updates when you finally go back in and deploy the saved plan. It will still need to run all the normal validation checks each time and allow us to add additional applications before hitting the deploy but would at least save time adding all the same common ones each time.

Yes we could do this by creating a solution and deploying via servicecenter but then it is a multi step process and we don't get all the additional reference checks and auto including from the validation step.

17 Dec 2018
Copy link to comment
Changed the category to
Lifetime
17 Dec 2018
Copy link to comment
Changed the status to
On our RadarOn our radar

Hi John,


Thank you for your idea!


We love your idea so we've moved it to "on our radar". We are planning to give the capability to reuse deployment plans, so you can create a deployment plan based on another one. Let me know if this capability fits better or not your purpose. 


Thank you,

Joao Bento

27 Dec 2018
Copy link to comment

Hello João,

Another purpose is having multiple applications in your environment with different lifecycles (imagine a CoE).

Application A goes to QA every Monday.


Application B goes to QA every Wednesday.

I can't have 2 deployment plans, one for each, one of the applications can't use deployment plans and has to do everything by hand every time.

24 Jan 2019
Copy link to comment

We had some disussion about this in last meet-up here, where, in bigger environments it would be nice if multiple plans can be created when also making the use with automatic deployments. Now it has to wait till a deployment plan is finished before executing the scheduled deployment plan.

So yeah would indeed be helpfull +1

02 Apr 2019
Copy link to comment

Just reinforcing the idea, in factories with multiple applications with different life cycles it would be extremely helpful to be able to create more than one deployment plan and save them for deployment at a later time, as for example outside office hours.

We definitely would benefit from this idea! I was going to create this idea but with a quick search was able to find that others also have this requirement.

--Tiago Bernardo

15 Dec 2020
Copy link to comment
Merged this idea with 'Add a queue to Lifetime deploy plans' (created on 11 Feb 2021 13:51:10 by Leandro Oliveira)
12 Feb 2021
Copy link to comment

Currently when a deployment is taking place it is not possible to create another plan.

Adding a queue system to the lifetime promotion process could help developers and managers to better organize deploys without having to wait for the current deploy to complete. It would also be interesting to be able to change the execution order of those plans that are in the queue, for example, some manager decided to prioritize a plan.



This comment was:
- originally posted on idea 'Add a queue to Lifetime deploy plans' (created on 11 Feb 2021 by Leandro Oliveira)
- merged to idea 'Save multiple deployment plans' on 12 Feb 2021 06:46:15 by Daniël Kuhlmann
11 Feb 2021
Copy link to comment

I was about to create a new idea for "parking" saved deployment plans, but then I found this idea.

I would really want to be able to "park" a saved deployment plan (in the below example it is one created by another team) as it block deployments/releases for other teams. Now I have to discard this saved deployment plan if my team is planning on deploying first and the other team would have to recreate their deployment plan.

The ability to add saved deployment plans to a queue or to create multiple deployment plans from environment A to environment B would be a very welcoming feature.

Regards,

Nordin

11 May 2021
Copy link to comment
Merged this idea with 'LifeTime Queue' (created on 16 Nov 2021 15:54:12 by Sergio Duarte)
31 Dec 2021
Copy link to comment

Hi there,

In a factory when you have several teams developing is quite a pain to deploy to the same environment when you have someone deploying at the same time.

I think will be great to have a queue of plans in order to deploy without having to wait for a plan to finish.


Thank you

16 Nov 2021
Copy link to comment

This would be AWESOME and very handy!

16 Nov 2021
Copy link to comment

Well the good news is in the future with Project Neo, we can all simultaneously deploy and not have to wait on each other.

17 Nov 2021
Copy link to comment

nice idea

22 Nov 2021
Copy link to comment

Good idea.

16 Dec 2021
Copy link to comment

Just writing "good idea" is not really a contribution to the discussion. If you like the idea, yes press the like button.

16 Dec 2021
Copy link to comment

Sure @Daniel Kuhlmann I hit the Like button, Thank you

16 Dec 2021
Copy link to comment

Hi Sergio,

I knew this idea already existed because I wanted to create it once and then found out someone already beat me to it.

@Daniel merge idea with this one:

https://www.outsystems.com/ideas/6069/save-multiple-deployment-plans/

30 Dec 2021
Copy link to comment
Merged this idea with 'Saving/Copying/Editing a Deployment Plan for a specific Application for later use' (created on 04 Sep 2022 08:32:41 by James Palin)
05 Sep 2022
Copy link to comment

I have several Application teams who are working continuously on new deployments. I sometimes find that a team has started to prepare a deployment plan, but not deployed, yet,  and that another team then wants to execute its plan immediately. 

My organization would find it a lot easier to manage if you could create a Deployment plan per app, and potentially per environment that could be saved, edited and reloaded when necessary ~ without impacting any other plans.

To improve upon this, it should be possible to copy a lower environment plan into a higher environment plan. Eg For App A deployment from Dev to Test; I would like to copy this plan to App A deployment from Test to PP; edit it, Save it, then execute.

04 Sep 2022
Copy link to comment
Merged this idea with 'Deployment Plan "Do it Later"' (created on 14 Nov 2022 09:54:35 by Ricardo Pereira)
15 Nov 2022
Copy link to comment

Hi,

For me make total since that we can create a deployment plan and we can put it saved but aside, opening the way to others deployment plans to run. Something like, "do it later".

With this we can have the ability to prepare our deployment plans and don't need to discard them if someone need to deploy other applications to the same target environment.


Best regards,

Ricardo Pereira

14 Nov 2022
Copy link to comment
Changed the status to
Implemented
on 03 Jul 2024

Hi Team,

Closing this idea as implemented, since it is now possible to do this and more from LifeTime 11.24.0 where we introduced the support for creating, editing and executing deployment plans in parallel.

A big thank you to everyone who sponsored the idea!

03 Sep 2024
Copy link to comment