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

Concurrent build is broken because modules do not depend on feature-packs they provision that are built in other modules

XMLWordPrintable

    • Hide
      mvn clean install -Dquickly -T 3C -DskipTests
      Show
      mvn clean install -Dquickly -T 3C -DskipTests
    • Workaround Exists
    • Hide

      Explicitly skip the test suite modules from reactor.

      Show
      Explicitly skip the test suite modules from reactor.
    • ---
    • ---

      Building concurrently demonstrates the issue easily on e.g. a on a fresh system since the artifacts are not cached in the local repository form the previous build.

      The problem is that maven has NO information about the dependencies since the galleon layers being provisioned are only defined in the build execution but are not added as module dependences. That results in concurrent build getting faster to the module that is provisioning before the module has been build since it doesn't know it's a dependency. 

      Typical developer will not notice this because the old version is already pre-cached from the previous build so the server being provisioned for testing is a stale one.

       

      $ mvn clean install -Dquickly -T 3C -DskipTests
      ...
      [INFO] WildFly Test Suite: Integration - Smoke ............ FAILURE [ 14.722 s]
      [INFO] WildFly Test Suite: Base Server Aggregator ......... SUCCESS [  0.044 s]
      [INFO] WildFly: Dependency Management (Expansion Test Dependencies) SUCCESS [  0.054 s]
      [INFO] WildFly Test Suite: Expansion Server Build Demander  SKIPPED
      [INFO] WildFly Test Suite: Expansion Aggregator ........... SUCCESS [  0.029 s]
      [INFO] WildFly: Legacy Dependency Management (Expansion Dependencies) SUCCESS [  0.056 s]
      [INFO] WildFly: Galleon Pack Layer Tests .................. SKIPPED
      [INFO] WildFly: Release ................................... SKIPPED
      [INFO] WildFly Preview: BOM of Test Dependencies .......... SUCCESS [  0.032 s]
      [INFO] WildFly Preview: Dependency Management (Expansion Test Dependencies) SUCCESS [  0.032 s]
      [INFO] ------------------------------------------------------------------------
      [INFO] BUILD FAILURE
      [INFO] ------------------------------------------------------------------------
      [INFO] Total time:  44.640 s (Wall Clock)
      [INFO] Finished at: 2025-04-14T13:05:56+02:00
      [INFO] ------------------------------------------------------------------------
      [ERROR] Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:5.1.0.Final:provision (server-provisioning) on project wildfly-ts-integ-smoke: Provisioning failed: Failed to resolve org.wildfly:wildfly-galleon-pack:zip:37.0.0.Beta1-SNAPSHOT: The following artifacts could not be resolved: org.wildfly:wildfly-galleon-pack:zip:37.0.0.Beta1-SNAPSHOT (absent): Could not find artifact org.wildfly:wildfly-galleon-pack:zip:37.0.0.Beta1-SNAPSHOT -> [Help 1]
      [ERROR]
      [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
      [ERROR] Re-run Maven using the -X switch to enable full debug logging.
      [ERROR]
      [ERROR] For more information about the errors and possible solutions, please read the following articles:
      [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
      [ERROR]
      [ERROR] After correcting the problems, you can resume the build with the command
      [ERROR]   mvn <args> -rf :wildfly-ts-integ-smoke

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

                Created:
                Updated:
                Resolved: