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

Complete the PCT flow started in JENKINS-50540 for git plugin

    XMLWordPrintable

Details

    • Task
    • Status: In Progress (View Workflow)
    • Minor
    • Resolution: Unresolved
    • evergreen
    • None
    • Evergreen - Milestone 1

    Description

      As discussed in JENKINS-50540 The tooling for the complete flow of the PCT testing for essentials plugins is not yet complete, this ticket is to modify the testing flow of git plugin once all the tooling is in place.

      The complete flow to implement is:

      • Use the work on Custom war packager and JEP-305 to generate a war file that contains the SUT and the essentials plugins in the proper versions that means the ones defined in essentials BOM which as jglick stated before should be deployed to Artifactory on every production change.
      • That war file is then fed into ATH and PCT

      And apart from the plugins in the essentials umbrella we need to run the PCT for the plugins specified in JENKINS-50539

      Attachments

        Issue Links

          Activity

            oleg_nenashev Oleg Nenashev added a comment -

            rarabaolaza vilacides I have created a PR for JENKINS-51093 with basic Incrementals support. Please let me know whether it's enough for you. Or do you need JENKINS-51094 (automatic picking of latest releases)?

            oleg_nenashev Oleg Nenashev added a comment - rarabaolaza vilacides I have created a PR for JENKINS-51093 with basic Incrementals support. Please let me know whether it's enough for you. Or do you need JENKINS-51094 (automatic picking of latest releases)?
            rarabaolaza Raul Arabaolaza added a comment - - edited

            oleg_nenashev With this and JENKINS-50953 is enough IMO

            rarabaolaza Raul Arabaolaza added a comment - - edited oleg_nenashev With this and JENKINS-50953 is enough IMO

            So, it seems there are some unstability on git-plugin current builds, so first step here will be to help with that if necessary as I do not want to change the current flow until is stable

            rarabaolaza Raul Arabaolaza added a comment - So, it seems there are some unstability on git-plugin current builds, so first step here will be to help with that if necessary as I do not want to change the current flow until is stable

            Unstability has been solved apparently, also there are new facilities in pipeline-library provided by the always amazing oleg_nenashev that mostly implement all the desired flow, so starting with this again.

            rarabaolaza Raul Arabaolaza added a comment - Unstability has been solved apparently, also there are new facilities in pipeline-library provided by the always amazing oleg_nenashev that mostly implement all the desired flow, so starting with this again.

            It seems the PCT docker image is not able to deal with multimodule plugins like BO, need to fix that, also there are a bunch of plugins not passing the PCT due to various reasons, I will create tickets to fix them (or I will remove from the list)

            rarabaolaza Raul Arabaolaza added a comment - It seems the PCT docker image is not able to deal with multimodule plugins like BO, need to fix that, also there are a bunch of plugins not passing the PCT due to various reasons, I will create tickets to fix them (or I will remove from the list)

            Currently blocked by JENKINS-51298

            rarabaolaza Raul Arabaolaza added a comment - Currently blocked by JENKINS-51298

            Not blocked, it was my mistake, using wrong groupIds...

            rarabaolaza Raul Arabaolaza added a comment - Not blocked, it was my mistake, using wrong groupIds...

            People

              rarabaolaza Raul Arabaolaza
              rarabaolaza Raul Arabaolaza
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: