700
Views
6
Comments
Solved
Should you publish with full compilations after cloud environment upgrade

Hi All, 

Our OutSystems Cloud platform has just been upgraded to the latest version so that we can get cracking with Reactive Web Apps (so excited!) 

Just a quick devops question, should the option to Publish with full compilations be selected when republishing your apps (using a solution) after the upgrade? 

Thanks, 

Nicholas

2024-06-13 07-53-34
Paulo Moreira
Ā 
MVP
Solution

Hi Nicholas,

After an upgrade, it's always a good practice to fully republish everything you have on your factory.

For aditional reference, please check https://www.outsystems.com/forums/discussion/52215/documentation-on-solution-publishing/  

Rephrasing @Tiago Pinho on the above post:


Replicating a full compilations refresh:

For every module on your solution:

1. Open

2. Refresh references

3. Publish

4. A new version (of module) is created if differences were found (after refresh references). You can even have a "broken" module as new version.


Replicating a normal refresh:

For every module on your solution:

1. Open

2. Publish (without refreshing references)

3. No new version (of module) is created


There are probably other differences that only OutSystems can confirm.


Thank you.

Best regards,

Paulo Moreira
2019-01-16 07-23-24
Nicholas van Wyngaard

Paulo Moreira wrote:

Hi Nicholas,

After an upgrade, it's always a good practice to fully republish everything you have on your factory.

For aditional reference, please check https://www.outsystems.com/forums/discussion/52215/documentation-on-solution-publishing/  

Rephrasing @Tiago Pinho on the above post:


Replicating a full compilations refresh:

For every module on your solution:

1. Open

2. Refresh references

3. Publish

4. A new version (of module) is created if differences were found (after refresh references). You can even have a "broken" module as new version.


Replicating a normal refresh:

For every module on your solution:

1. Open

2. Publish (without refreshing references)

3. No new version (of module) is created


There are probably other differences that only OutSystems can confirm.


Thank you.

Best regards,

Paulo Moreira

Thanks Paulo.


2020-02-03 03-15-14
Farooq Hamza

selecting "Publish with full compilations" DID NOT create any new versions, and DID NOT refresh any references (as when I do manage dependency on any module, I still see some pending references of systems components changes due to platform upgrade).
.
For more context on my specific scenario:
My solution has every modules and extensions associated
Platform upgrade was to 11.18.1 (Build 37828)
Dealing with around 150 applications
.
Hoping this feature will be soon improvised and documented better. 

2024-07-05 14-16-55
Daniël Kuhlmann
Ā 
MVP

Hi Farooq,

Why are you replying to a discussion of over 2 years old? with already a reply marked as solution.

Better to start a new discussion, and put the URL of this discussion in your text for reference.

Since 2020, features on the platform have improved around Platform Upgrade, please always use the latest documentation as reference to learn on how to execute a platform upgrade.

https://success.outsystems.com/Documentation/11/Setup_and_maintain_your_OutSystems_infrastructure/Upgrade_OutSystems_platform/Modules_deployment_step_during_Platform_Server_upgrade

Regards,

Daniel


2020-02-03 03-15-14
Farooq Hamza

Hi Daniel,
My comment was for anyone who reached these articles just like me, I did refer every latest articles at that time. Deploy feature in upgrading section was introduced on platform version 11.18.0(dec 2022) which immediately recalled, and 11.18.1 version did not had that feature. Regardless, for anyone seeking or hoping to use "Publish with full compilations" thru solution, my above notes stays valid (as of jan 2023).

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.