Merge pull request #37 from mcanoy/db-sync

Get all engagements request. Allow for updating files

Author: mcanoy

Jenkinsfile

@@ -151,7 +151,6 @@ Deployment template will read from the above secret and inject following env var
 * `CACHE_USER`
 * `CACHE_PASS` (should be secret and match the Infinispan operator secret)
 * `CACHE_USE_AUTH` set to true
-* *
 
 ### OpenShift Applier
 
@@ -163,82 +162,4 @@ ansible-galaxy install -r requirements.yml --roles-path=roles --force
 ansible-playbook apply.yml -i inventory/
 ```
 
-## Pipeline (deprecated)
-
-The deployment pipeline is running through a `Jenkinsfile` located in the root folder of the project. This `Jenksinfile` is written in groovy.
-The pipeline expects the nexus is available nexus:8080. Make sure that nexus is available and accessible to Jenkins.
-
-#### Prepare environment for [ENVIRONMENT] deploy
-
-The first stage is going to set environment vars based on the branch selected to build:
-
-```groovy
-master - env.PROJECT_NAMESPACE = "${NAMESPACE_PREFIX}-test"
-         env.NODE_ENV = "test"
-         env.QUARKUS_PROFILE = "openshift-test"
-         env.RELEASE = true
-
-develop.* or feature.* - env.PROJECT_NAMESPACE = "${NAMESPACE_PREFIX}-dev"
-                         env.NODE_ENV = "dev"
-                         env.QUARKUS_PROFILE = "openshift-dev"
-```
-
-#### Ansible
-
-Jenkins will spin up an Ansible agent that will run a playbook called OpenShift Applier (https://github.com/redhat-cop/openshift-applier). The openshift-applier is used to apply OpenShift objects to an OpenShift Cluster. 
-
-This stage is going to download the playbook dependencies using Ansible Galaxy and apply the playbook using **build** as a *filter_tag*. This is going to create the necessary resources for our application build in an OpenShift cluster. 
-
-#### Test/Maven Build/Nexus/OpenShift Build
-
-Jenkins will spin up a Maven agent to test, Maven build, upload to Nexus and start the OpenShift build.
-
-##### Test
-
-```
-mvn clean test
-```
-
-##### Maven Build
-
-```
-mvn clean install
-```
-
-##### Static Code Analysis
-
-```
-mvn checkstyle:checkstyle
-mvn org.jacoco:jacoco-maven-plugin:prepare-agent install -Dmaven.test.failure.ignore=true
-```
-
-##### Nexus
-
-```
-mvn deploy
-```
-
-##### OpenShift Build
-
-The OpenShift build is going to start after the Nexus deployment is complet and successful.
-
-###### OpenShift Atomic Registry
-
-If you're pushing from the master branch the build will create a container image and push it to the Openshift internal registry.
-
-```
-oc project ${PIPELINES_NAMESPACE}
-oc patch bc ${APP_NAME} -p "{\\"spec\\":{\\"output\\":{\\"to\\":{\\"kind\\":\\"ImageStreamTag\\",\\"name\\":\\"${APP_NAME}:${JENKINS_TAG}\\"}}}}"
-oc start-build ${APP_NAME} --from-file=target/${ARTIFACTID}-${VERSION}-runner.jar --follow
-```
-
-###### Quay
-
-If you're pushing from a release tag the build will create a container image and push it to Quay.
-
-```
-oc project ${PIPELINES_NAMESPACE} # probs not needed
-oc patch bc ${APP_NAME} -p "{\\"spec\\":{\\"output\\":{\\"to\\":{\\"kind\\":\\"DockerImage\\",\\"name\\":\\"quay.io/rht-labs/${APP_NAME}:${JENKINS_TAG}\\"}}}}"
-oc start-build ${APP_NAME} --from-file=target/${ARTIFACTID}-${VERSION}-runner.jar --follow
-```
 

README.md

@@ -0,0 +1 @@
+lombok.addLombokGeneratedAnnotation = true

lombok.config

@@ -78,8 +78,8 @@
 		</dependency>
 		<!-- Metrics -->
 		<dependency>
-			<groupId>org.eclipse.microprofile.metrics</groupId>
-			<artifactId>microprofile-metrics-api</artifactId>
+			<groupId>io.quarkus</groupId>
+			<artifactId>quarkus-smallrye-metrics</artifactId>
 		</dependency>
 		<!-- Other -->
 		<dependency>