-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
java.runtime.name: OpenJDK Runtime Environment
java.runtime.version: 1.8.0_242-b06
tomcat: tomcat8
CATALINA_OPTS: -Xms1024m -Xmx1024m -DJENKINS_HOME=/home/ticketuser/.jenkins/ -Xmx1G
Linux:
Distributor ID: Debian
Description: Debian GNU/Linux 8.11 (jessie)
Release: 8.11
Codename: jessie
CPU: 8
RAM: 8GBjava.runtime.name: OpenJDK Runtime Environment java.runtime.version: 1.8.0_242-b06 tomcat: tomcat8 CATALINA_OPTS: -Xms1024m -Xmx1024m -DJENKINS_HOME=/home/ticketuser/.jenkins/ -Xmx1G Linux: Distributor ID: Debian Description: Debian GNU/Linux 8.11 (jessie) Release: 8.11 Codename: jessie CPU: 8 RAM: 8GB
The first building of the day is always built with the wrong profile. There are three profiles on the Jenkins system. Development, test and productive.
The first build always builds the "prod-server" profile! This is critical because the productive database is also accessed!
The subsequent builds will be built with the correct profiles.
Dev
-T 1C clean install -P dev-server -DskipTests -Dmaven.wagon.http.ssl.insecure = true -Dmaven.wagon.http.ssl.allowall = true
test
-T 1C clean install -P test-server -DskipTests -Dmaven.wagon.http.ssl.insecure = true -Dmaven.wagon.http.ssl.allowall = true
Prod
-T 1C clean install -P prod-server -DskipTests -Dmaven.wagon.http.ssl.insecure = true -Dmaven.wagon.http.ssl.allowall = true