Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-20539

Define upgrade strategy for software.amazon.awssdk artifacts

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 37.0.0.Final, 38.0.0.Final
    • Clustering
    • None
    • ---
    • ---

      The software.amazon.awssdk:* are the dependencies of JGroups AWS project and it's the sole user of this dependency.

      The problem at hand is that the releases are extremely frequent, virtually almost daily to the extreme that there are days with TWO releases in a day, see
      https://mvnrepository.com/artifact/software.amazon.awssdk/bom

      This poses a problem that is at least twofold:

      1. we currently do not run automated tests in public that would use real credentials due to various reasons (security, cost, etc)
      2. and even if we did and could verify the functionality, it still poses a lot of merging effort and unnecessary git log history pollution for no real advantage

      The proposed solution is to:

      • do the upgrade once at the time of release of WildFly
      • do an upgrade at the time of upgrading jgroups-aws
      • disable dependabot upgrades for WF to save CI/queue resources

      Opened as a follow up on discussion at:
      https://github.com/wildfly/wildfly/pull/18818#issuecomment-2725523452

              rhn-engineering-rhusar Radoslav Husar
              rhn-engineering-rhusar Radoslav Husar
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: