PaaS+, the cloud platform for software developers, enables you to create an environment with all different sorts of programming languages. The creations are automatically configurated at the very beginning to facilitate web applications from the specific programming languages. In this way you can set-up applications via Repository, the Maven Build Node and the Marketplace, where user-ready packages such as GitLab Server, GitBlit and Jenkins are available. This results in having complete set tools available to realise your own DevOps Pipeline. In this blog I will review the different tools.

1. Unroll via Repository

One of the most important functions of the DevOps Pipeline is the possibility to unroll applications directly onto the PaaS-environment via a repository. PaaS+ supports GIT and SVN-repositories. At the initiation of the unfoldment a connection is made between the application server or server cluster and a branch within the remote repository. After that, files from the specific branch are taken from the repository and unfolded on the application server. Furthermore, PaaS+ gives you the opportunity to automatically control and change the remote repository and to automate the unfoldment. You can set the interval of how many times the repository needs to be checked on changes.

2. Maven Build Node

The Maven Build node can be added when unrolling a Java environment and it offers support when unrolling a Java web application from a remote repository. Maven collects the Java web application from the repository and complicates the files. After this process, the Maven Build node transports the complicated web application to the application server. After that the web application is unrolled over the application server

3. Marketplace

The Marketplace is a nifty function within the dashboard of PaaS+. From here the users can unroll packages which are ready and can support the DevOps pipeline. Examples of this are: GitLab Server, GitBlit, Nexus Repository and Jenkins. When you select a package from the Marketplace, automatically an environment is rolled out in which the selected application is hosted in a Docker container or application server. In this way, within a couple of minutes entire GitLab servers can be set up without installing a VPS (Virtual Private Server) in a lot of complicated and time-demanding steps. The only thing left for the user to do is to arrange the application to its wishes and demands.

In the next article I will go deeper into the different tools such as GitLab, GitHub and more.

This is the second part of our blog series, curious to our first part?

1.      The introduction of PaaS+, what is it?

© 1998 - 2020 Previder Conditions Privacy | Contact Supportdesk Previder is part of the Odin Groep