[BUILD-1143] External experimental DB is used after recent upgrade of pipeline-maven-plugin Created: 18/Sep/23  Updated: 19/Sep/23

Status: Selected
Project: Build
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Maxime Michel Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Work Started:

 Description   

Up until now, we have used that plugin in a mode that uses a local H2 and isn't recommended:

By default, the Jenkins Pipeline Maven Plugin uses an H2 embedded database, but it is recommend to use an external MySQL database.
https://plugins.jenkins.io/pipeline-maven/#plugin-content-db-setup-mysql

Also:

{}Using H2 might degrade your environment stability{} (The H2 database is running in your instance JVM and could request too many resources).

At some point a version of the plugin refactored the DAO connection, from this point we went for a dedicated DB as the built-in H2 appeared to no longer work. In theory it should have, but it was anyway not recommended.

I have therefore spinned up an Aurora DB from our experimental account, and connected it successfully to the Jenkins instance. However, this should ideally be managed by Terraform in repository foundation-internal-base. The goal of this ticket is to perform that migration.

FTR this page was helpful in making the DB publicly available: https://repost.aws/knowledge-center/aurora-mysql-connect-outside-vpc


Generated at Sun Feb 11 23:48:33 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.