Continuum
  1. Continuum
  2. CONTINUUM-2217

Scheduled builds stopped after upgrade

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 1.3.3 (Beta)
    • Fix Version/s: 1.3.3 (Beta)
    • Component/s: None
    • Labels:
      None
    • Environment:
      1.3.3-SNAPSHOT r768185
    • Complexity:
      Intermediate
    • Number of attachments :
      0

      Description

      We upgraded vmbuild.apache.org to Continuum 1.3.3-SNAPSHOT r768185 on Apr 24th and it looks like no scheduled builds have happened since then.

      Details on https://issues.apache.org/jira/browse/INFRA-2037

        Issue Links

          Activity

          Hide
          Maria Catherine Tan added a comment -

          looking at the logs from https://issues.apache.org/jira/browse/INFRA-2037, the warn message will only appear if continuum is trying to build more than one instance of the same project, with the same groupId, artifactId, version.

          Show
          Maria Catherine Tan added a comment - looking at the logs from https://issues.apache.org/jira/browse/INFRA-2037 , the warn message will only appear if continuum is trying to build more than one instance of the same project, with the same groupId, artifactId, version.
          Hide
          Maria Odea Ching added a comment - - edited

          I took a look at the projects causing the ".. is duplicated in the reactor" in vmbuild and it seems the Sling projects were added twice in the group? As for the jUDDi project, there are two groups of the project added in vmBuild.. both the projects in the two groups are similar and that's what's probably causing the "..is duplicated" warning message.

          Show
          Maria Odea Ching added a comment - - edited I took a look at the projects causing the ".. is duplicated in the reactor" in vmbuild and it seems the Sling projects were added twice in the group? As for the jUDDi project, there are two groups of the project added in vmBuild.. both the projects in the two groups are similar and that's what's probably causing the "..is duplicated" warning message.
          Hide
          Jevica Arianne B. Zurbano added a comment -

          The warning "...duplicated in the reactor" is displayed when a project is added twice (either in different groups or the same group). Given this scenario, the scheduled build is triggered but the project scm and the projects are not updated and queued for build.

          Show
          Jevica Arianne B. Zurbano added a comment - The warning "...duplicated in the reactor" is displayed when a project is added twice (either in different groups or the same group). Given this scenario, the scheduled build is triggered but the project scm and the projects are not updated and queued for build.
          Hide
          Wendy Smoak added a comment -

          I believe this was fixed by CONTINUUM-2219. Scheduled builds are happening again on vmbuild.

          Show
          Wendy Smoak added a comment - I believe this was fixed by CONTINUUM-2219 . Scheduled builds are happening again on vmbuild.

            People

            • Assignee:
              Wendy Smoak
              Reporter:
              Wendy Smoak
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: