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

PCT - PCT is not able to recognize plugins from pipeline-stage-view as it's a multi-module

      pipeline-stage-view plugin is a multi-module and because of this, PCT is not able to validate it out of the box.

      PCT needs a new hook to detect the pipeline-stage-view context and checkout the correct repository.

          [JENKINS-55508] PCT - PCT is not able to recognize plugins from pipeline-stage-view as it's a multi-module

          Adrien Lecharpentier created issue -
          Adrien Lecharpentier made changes -
          Comment [ At first, I thought that implementing a hook (like [BlueOceanHook.java|https://github.com/jenkinsci/plugin-compat-tester/blob/master/plugins-compat-tester/src/main/java/org/jenkins/tools/test/hook/BlueOceanHook.java] would be enough. But, the {{pipeline-stage-view}} plugin has some customization which requires more work on PCT:

          # the modules inside the repository aren't named after the plugins' name
          ** {{pipeline-rest-api}} -> {{rest-api}} module and not {{pipeline-rest-api}} module ]
          Adrien Lecharpentier made changes -
          Remote Link New: Cette demande est liée à "PR-110 (Lien Web)" [ 22180 ]
          Adrien Lecharpentier made changes -
          Component/s New: pipeline-stage-view-plugin [ 21139 ]

          I still have a problem as the parent pom replacement done by PCT breaks the hierarchy on the plugin. The groupId of the plugin is different than what other plugins are using.

          Adrien Lecharpentier added a comment - I still have a problem as the parent pom replacement done by PCT breaks the hierarchy on the plugin. The groupId of the plugin is different than what other plugins are using.

            Unassigned Unassigned
            alecharp Adrien Lecharpentier
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: