Solution publish should fail early
976
Views
8
Comments
New
Service Center

When there is an error, like missing reference, at the beginning of solution publish - it still continues to go for half an hour or more, and only after "Gathering dependencies..." stage it fails with a message like "The deployment was aborted due to errors. No applications or modules were deployed".

This is really really really frustrating, especially when you are in a hurry, especially when you have noticed the error and fixed it, but you still have to wait for half an hour because there is no way to stop solution publish.

Why would it not stop immediately after the fatal error has occurred? Or at least show  that "continue/abort" confirmation, immediately.

Isn't this rule #2 from The Book?

Changed the category to
Service Center

Exactly what I was also looking for in OutSystems too.
But currently not available.

After waiting much more then expected(for our scenario, its more than 4-5 hours), it simply says, "Deployment Aborted. No modules or applications were deployed"

This is not expected from OutSystems(such a great tool).

it will be great if such issues are resolved and available as soon as possible.

Thanks & Regards,
Palak Patel

Merged this idea with 'Should be option to stop Current Publish for a module in Outsystems11' (created on 01 Jul 2021 12:36:26 by Amit Jain)
2025-08-07 06-30-56
Amit J
Champion

While I was working in Outsystems 9 and 10, there was an option to stop the Current publish using the service centre to a module. But when I start work on 11, That option not available now. It should be as previous. Because if we tart publish by mistake then have the option to abort immediately it. Otherwise, it may affect consumer modules.

Merged this idea with 'Abort/Cancel 1-Click Publish' (created on 28 Sep 2022 02:19:04 by Venkatesh Sundarajan)

Hi, 

It would be great if we can have Abort/Cancel 1-CP to current publishing version inside service studio, by mistakenly someone publishes we can rollback to the current version instead of over writing from "Other Module Version".

This button can be made visible/enabled only during 1-CP runs.

Thanks.


Merged this idea with 'All componenets solution publish| Abort the publuish after 1st error' (created on 26 Jan 2023 15:54:36 by Naren)

When we do the upgrades or change the configuration settings ,we need to re-publish all the components by creating a solution.

Problem:
As we have different steps in while publishing the solution i.e. Upgrading ,Uploading,verifying,upgrading modules....etc 
example : If there is an error in upgrading step it will proceed next step ,next step until it reaches to the gathering dependencies phase and it aborts the publish
Solution:
Do not proceed to next step if the current step of publish is failing   so we can figure out which modules it is failing on at the beginning and  remove them from solution or publsih them manually  rather than waiting it to reach till some certain point and faill and we need to re-do all the steps again ,in return it compiles multiple times every time we run the publish and it will eat up the space on Database