Uploaded image for project: 'Build'
  1. Build
  2. BUILD-1143

External experimental DB is used after recent upgrade of pipeline-maven-plugin

    XMLWordPrintable

Details

    • Task
    • Resolution: Unresolved
    • Neutral
    • None
    • None
    • None
    • None

    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

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              Unassigned Unassigned
              mmichel Maxime Michel
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Work Started:

                Checklists

                  Task DoR