4
 Followers
15
 Likes

Autopublish applications after upgrade

Install Processes
On our radar

Hi everybody.


I don't know wheter this is an idea or a question, or maybe we don't know a tool exist for this situation.


We, at my company, are quite new working with Outsystems Platform. Some few days ago I did a minor upgrade from 9.0.0.2 to 9.0.0.19 version. Following the Upgrade Guide is a straightforward process but there is a point where things can become complicated: we have to republish every application and module manually, being specially carefull with dependencies.


I think it would be really nice that this process could be automated as a taks performed inside the platform.


What do you think?

Created on 31 Dec 2014
Comments (12)
It would be nice if it was part of the upgrade process. After doing it once or twice it isn't too bad to just make the solution and re-publish it, but I agree that making it automatic (or an option to do it as part of the upgrade) would be great.

J.Ja

Hi Johannes,


Currently, the platform does require the republish of the applications after an upgrade. Since O10, the whole installation process can automated using the Unattended Installation API. You can check it here.  

The OSPTool has a command that allow you to republish the entire factory without the need of create an solution first:

  • outsystems_common_path\OSPTool.com /PublishFactory hostname username password

This doesn't solve possible problems with broken dependencies between the versions but allow you to automate the upgrade process.


Does this address your concerns?

Changed the status to
Implemented
on 19 Apr 2018


I will mark this as implemented with the deliver of an Unattended Installation API that allow you to automate all the process including the republish of the factory. Drop us a line or submit a new idea if there is something in your mind that you like us to improve.

Best regards

I don't think that telling people to write a bunch of code and somehow test it to get an unattended installation is what people asked for. That's a nice thing to have in a large very enterprise/DevOps environment, but that does NOT describe most current customers. Especially since so many on-prem customers only upgrade a few times a year. The "cost" to automate this process is far higher than the cost of doing it manually.

If there is an idea for "we want an API for an unattended installation/upgrade" that should get marked as "implemented",  but what people are asking for here was not a method to automate upgrades, but a way to make manual upgrades easier.

J.Ja

Changed the status to
On our radar


Thanks for your feedback JJ. That was exactly the kind of answer or feedback that I wanted when I first reply to the thread.

We will keep this marked as in our radar to keep discussing this topic.

Cheers

Merged this idea with 'Automate the platform upgrade process' (created on 06 Feb 2019 20:44:48 by John Williams)

Currently after an environment upgrade we are asked to republish all espaces as per the instruction on this page

https://success.outsystems.com/Support/Enterprise_Customers/Upgrading/Upgrade_your_applications_to_a_new_OutSystems_Platform_version

In our environment we have over 1000 espaces and every time we follow those instructions and try to add all espaces to a solution  there is a significant delay followed by and "Internal Error" most likely due to timeouts (Yes we have raised a support ticket). We then have to add every espace in groups of around 10 which takes hours due to the delay between each add.

It would be far simpler if there was an automated upgrade process that simply republished any espace that had not been published since the last upgrade.

This isn't a new issue by the way, so far I've done around 4 platform upgrades and not one of them has gone without some sort of error, including this particular error.



This comment was:
- originally posted on idea 'Automate the platform upgrade process' (created on 06 Feb 2019 by John Williams)
- merged to idea 'Autopublish applications after upgrade' on 07 Feb 2019 20:21:35 by Justin James

Changed the category to Install Processes




This comment was:
- originally posted on idea 'Automate the platform upgrade process' (created on 06 Feb 2019 by John Williams)
- merged to idea 'Autopublish applications after upgrade' on 07 Feb 2019 20:21:35 by Justin James

Hi John,

Thank you for your contribution. We merged your idea with a previous one that already existed with the same purpose.

Regarding your comment in concrete, I would like to ask you a couple of questions:

  1. You mentioned that during the republishing of your factory, a publication that evolves all content (around 1000 eSpaces), you end up on getting Internal Errors. Can you elaborate what kind of error or message does it show?
  2. Currently, there is a way to trigger that operation (republish the whole factory) via OSPTool. You can find the documentation of that API here.  Let me speculate a bit: imagine that after an update when the installation of the Service Center ended, you were prompted if you want to republish all factory for that environment? (something that you need to do since it's a mandatory step from the installation checklist). Do you think that having it more visible and actionable would help?

Cheers!

Hi Tiago, 

For point 1, That was the exact error message, just "Internal Error" nothing else. Support helped me with the actual issue in the end, there was a timeout during the addition of all espaces, most likely due to the number of espaces and the size of the espace version entities.

For Point 2, yes that would help, however what would be far more useful is for the dev environments to just automatically proceed with the republish as part of the platform upgrade. During this upgrade process it took me over 15 hours (no I'm not exaggerating, included having to restart half way due to the IIS app pool being recycled by support troubleshooting the first issue)

Because the republish is mandatory it would save lot of time and outage if support could just trigger the process for us after they finish the base environment upgrade.   Not for Production though, I agree that we need a lot more control and transparency for that environment.

Thanks for your insights John.

Just to clarify, in this particular case, you are talking about an environment hosted in our OutSystems Cloud right?

Yes this is a cloud hosted system.

views
380
Followers
4