Publish and stage solutions between service centers

By Hans Bruins on 12 Jul 2010
If you have a couple of OS servers with development and production environments then you have for each of them a service center (I have now 5 or 6 of them).

When you want to place a solution from the development to the production environment then you need first to save it from the development serve to a local disk, login to the production server and execute there an upload and publish action.

I think it would be nice if the 2 (or more) service centra just can "see" eachother and move solutions from one to another. Discarding the need for local savings.


Fernando Sousa13 Jul 2010
Could the concept of "Infrastructure" from the "Intellectual Property" feature be used to manage the environments?

Could there be a button like "deploy to <environment>"?
Joop Stringer19 Jul 2010
In larger companies, you as developer (or team), will not be able to publish to another server. This because of security issues and also the fact the organisation wants to control de delivery process.
It would be very nice if a solution / E-space form e.g. a QA Platform Server could directly be published from QA to Production.

The Solution screen could look like this:


Merged from 'Publishing from one Platform server to the other' (idea created on 2010-12-24 08:29:28 by Eric Oud Ammerveld), on 2011-03-26 15:42:19 by Rodrigo Castelo
This could be a nice feature. Off course the button need to be on a different permission so not all users can press this button ;).

To a addition I would like to also have the upload to production button so I can first upload it to production and publish the solution later.

Merged from 'Publishing from one Platform server to the other' (idea created on 2010-12-24 08:29:28 by Eric Oud Ammerveld), on 2011-03-26 15:42:19 by Rodrigo Castelo
Requires
-Publish to production permission page.
-Publish to production settings page.


Merged from 'Publishing from one Platform server to the other' (idea created on 2010-12-24 08:29:28 by Eric Oud Ammerveld), on 2011-03-26 15:42:19 by Rodrigo Castelo
Hi guys,

Thanks for brainstorming with me.

I think that if the Outsystems platform is more 'aware' of it's own development set-up (e.g. DEV / TEST / QA / PROD) it's easier to :
- Publish from one platform to another
- Delegate the role of publishing and testing to another developer or an application manager

Currently I've created some E-space functions that have this 'awareness' making sure that things like verbose debugging info per default is disabled on Production servers and making sure that slightly different Active Directory credentials are checked in the test environment.

Merged from 'Publishing from one Platform server to the other' (idea created on 2010-12-24 08:29:28 by Eric Oud Ammerveld), on 2011-03-26 15:42:19 by Rodrigo Castelo
Gonçalo Martins27 Jan 2011
It would be very usefull if the platform somehow support the possibility to publish eSpaces, extensions or even solutions from a Service Center on a server to another server, directly and only selecting the destination server. This would be great if we use when we work for example with the common three environments - development, quality and production.



Merged from 'Publish to different servers from Service Center' (idea created on 2011-01-27 22:14:24 by Gonçalo Martins), on 2011-03-18 12:40:20 by Rodrigo Castelo

Merged from 'Publishing from one Platform server to the other' (idea created on 2010-12-24 08:29:28 by Eric Oud Ammerveld), on 2011-03-26 15:42:19 by Rodrigo Castelo
João Carvalho29 Jul 2010
Quite often ia have to develop and publish simultaneously in more than one environment. Specilly when developing espaces to be consumed by several other teams and/or in different environments.

Let's say that currently each time i publish, i have to do it in 3 environments (dev, quality, pre-production)...

Beeing able at studio to connect to several environments instead of only one would do it but maybe simpler options would be preferrable.

Tkx!

Merged from 'Publish simultaneously to several environments in one publish only' (idea created on 2010-07-29 10:58:01 by Joao Carlos Carvalho), on 2011-03-26 15:42:30 by Rodrigo Castelo
J.3 Aug 2010

What would be the advantage in that?

If it fails on the first then the other two are going to fail as well.?
not to mention, there is a develop/test/accept path to think of.

Or do you mean, an easy switch of the servers (which can be done by selecting the server already)





Merged from 'Publish simultaneously to several environments in one publish only' (idea created on 2010-07-29 10:58:01 by Joao Carlos Carvalho), on 2011-03-26 15:42:30 by Rodrigo Castelo
Diogo Cordeiro19 Aug 2010
yeah, definitely.

Quality and pre-production do have a purpose...

Sometimes they seem to be there just to give someone more work....but you should not forget that if they do need to exist, is because Mr. Murphy is somewhere around the corner

Merged from 'Publish simultaneously to several environments in one publish only' (idea created on 2010-07-29 10:58:01 by Joao Carlos Carvalho), on 2011-03-26 15:42:30 by Rodrigo Castelo
Goncalo Borrega11 Jun 2012
From version 7.0 you're able to deploy applications between environments with full control over the dependencies of each application.
Enjoy LifeTime!