Richard Martens has been involved in information technology for more than 25 years.
He started as a web developer using the Oracle database as no more than data storage. Richard has been responsible for major European multilingual websites and has been working with the Oracle database since 2000. During those years, he developed himself using a multitude of technologies and specialized in PL/SQL and Oracle APEX.
With APEX, he combines the things he loves most: the Oracle database and web technologies.
Richard has been granted an Ace award in 2015.
During Contech2022, Richard Martens will present APEX Application lifecycle with feature based deployment
|APEX Application lifecycle with feature based deployment – Abstract:|
APEX application deployment is mostly done by exporting and importing the application. But what if your team continuously develops, where do you stop developing to start preparing your release? This session shows you how to deploy based on features, without developers having to halt development.
APEX application deployment is mostly done by exporting the application and importing it into the target environment. But what if your team continuously develops (as they should), where do you stop developing to start preparing your release-deployment? You should be able to deploy based on features; without your developers having to halt their development.
The solution presented defines the core components of an APEX application as: – database objects (tables, views, pacakages etc) – the apex-application – static files on the web-server
Using the deployment-method explained in this presentation you will be able to deploy based on features or tickets in your ticketing system. The method includes things like Code versioning (GIT), Feature-tickets (Jira), Code Review (Quality), Automated Deployment using Jenkins and Flyway. When implemented you will be able to successfully and predictively deploy your APEX applications (including underlying database objects) to the different deployment-environments. With a few modifications you can even upgrade the methodology to be a “continuous delivery” methodology.
The result is a situation where you can deploy a specific version of your APEX application with the push of a button, wether it be at the test server, the acceptation-server or in production.