Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-33277

ivy plugin triggers build although module does not longer exist (with this name)

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • ivy-plugin
    • Jenkins (1.642.1), mask-passwords (2.8), ivy (1.26)

      One ivy-build job can build multiple ivy modules that are located in one git repository:

      repository/
      ├── Module A/
      │   ├── src/...
      │   ├── build.xml
      │   └── ivy.xml
      ├── Module B/
      │   ├── src/...
      │   ├── build.xml
      │   └── ivy.xml
      ├── Module C/
      │   ├── src/...
      │   ├── build.xml
      │   └── ivy.xml
      └── ...
      

      If one of the modules is removed from resp. renamed in the repository, the ivy plugin continues to trigger builds. These builds fail with "FATAL: Unable to find build script at...", as the module does not exist any more (at this location).

      Current workaround: delete the module directory under $JENKINS_HOME$/jobs/<jobname>/modules/<module directory> and restarting jenkins resp. "Reload Configuration from Disk"

          [JENKINS-33277] ivy plugin triggers build although module does not longer exist (with this name)

          Christian Bitschnau created issue -
          Christian Bitschnau made changes -
          Description Original: One ivy-build job can build multiple ivy modules that are located in one git repository:

          repository/
          ├── Module A/
          │ ├── src/...
          │ ├── build.xml
          │ └── ivy.xml
          ├── Module B/
          │ ├── src/...
          │ ├── build.xml
          │ └── ivy.xml
          ├── Module C/
          │ ├── src/...
          │ ├── build.xml
          │ └── ivy.xml
          └── ...

          If one of the modules is removed from resp. renamed in the repository, the ivy plugin continues to trigger builds. These builds fail with "FATAL: Unable to find build script at...", as the module does not exist any more (at this location).

          Current workaround: delete the module directory under $JENKINS_HOME$/jobs/<jobname>/modules/<module directory> and restarting jenkins resp. "Reload Configuration from Disk"
          New: One ivy-build job can build multiple ivy modules that are located in one git repository:


          {{repository/
          ├── Module A/
          │ ├── src/...
          │ ├── build.xml
          │ └── ivy.xml
          ├── Module B/
          │ ├── src/...
          │ ├── build.xml
          │ └── ivy.xml
          ├── Module C/
          │ ├── src/...
          │ ├── build.xml
          │ └── ivy.xml
          └── ...
          }}

          If one of the modules is removed from resp. renamed in the repository, the ivy plugin continues to trigger builds. These builds fail with "FATAL: Unable to find build script at...", as the module does not exist any more (at this location).

          Current workaround: delete the module directory under $JENKINS_HOME$/jobs/<jobname>/modules/<module directory> and restarting jenkins resp. "Reload Configuration from Disk"
          Christian Bitschnau made changes -
          Description Original: One ivy-build job can build multiple ivy modules that are located in one git repository:


          {{repository/
          ├── Module A/
          │ ├── src/...
          │ ├── build.xml
          │ └── ivy.xml
          ├── Module B/
          │ ├── src/...
          │ ├── build.xml
          │ └── ivy.xml
          ├── Module C/
          │ ├── src/...
          │ ├── build.xml
          │ └── ivy.xml
          └── ...
          }}

          If one of the modules is removed from resp. renamed in the repository, the ivy plugin continues to trigger builds. These builds fail with "FATAL: Unable to find build script at...", as the module does not exist any more (at this location).

          Current workaround: delete the module directory under $JENKINS_HOME$/jobs/<jobname>/modules/<module directory> and restarting jenkins resp. "Reload Configuration from Disk"
          New: One ivy-build job can build multiple ivy modules that are located in one git repository:


          {noformat}
          repository/
          ├── Module A/
          │ ├── src/...
          │ ├── build.xml
          │ └── ivy.xml
          ├── Module B/
          │ ├── src/...
          │ ├── build.xml
          │ └── ivy.xml
          ├── Module C/
          │ ├── src/...
          │ ├── build.xml
          │ └── ivy.xml
          └── ...
          {noformat}

          If one of the modules is removed from resp. renamed in the repository, the ivy plugin continues to trigger builds. These builds fail with "FATAL: Unable to find build script at...", as the module does not exist any more (at this location).

          Current workaround: delete the module directory under $JENKINS_HOME$/jobs/<jobname>/modules/<module directory> and restarting jenkins resp. "Reload Configuration from Disk"
          Christian Bitschnau made changes -
          Summary Original: ivy plugin triggers build although module does not longer exist (whith this name) New: ivy plugin triggers build although module does not longer exist (with this name)
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 169172 ] New: JNJira + In-Review [ 183387 ]

            tbingaman Timothy Bingaman
            titan_cb Christian Bitschnau
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: