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

add the runPCT step to the git-plugin on a PR basis

    XMLWordPrintable

Details

    • Evergreen - Milestone 1

    Description

      We need to modify the git-plugin flow so it runs the PCT on PR basis for git-plugin and all the critical upstream dependencies

       Acceptance criteria

      • For every PR to the git-plugin there is a run of the PCT exercising all git-plugin upstream dependencies
      • The run has to be against a TBD version of Jenkins core
        • Latest one
        • The one included in essentials
        • Latest LTS
      • What are the versions of the git-plugin dependencies to use? TBD cc jglick rarabaolaza oleg_nenashev
        • For example the ones included in essentials, the latest ones? Or more generally, what environment are we going to use for this PCT run? The UC, a custom UC generated from essentials.yml a war file generated from the new custom war packager tool using essentials.yml as source...

      Attachments

        Issue Links

          depends on

          Task - A task that needs to be done. JENKINS-50539 Determine critical plugins that depend on git-plugin

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          is duplicated by

          Task - A task that needs to be done. JENKINS-50516 Add the run PCT step to run on a PR basis to essentials

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          relates to

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-47498 Select compatible plugin versions using a BOM

          • Major - Major loss of function.
          • Resolved

          Task - A task that needs to be done. JENKINS-51008 Complete the PCT flow started in JENKINS-50540 for git plugin

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • In Progress

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-50598 Add support of running JTH with custom WAR

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          links to

          Web Link Git#585

          Web Link https://github.com/jenkinsci/jenkins-test-harness/pull/99

          Web Link Pipeline-library#48

          Activity

            Ascending order - Click to sort in descending order
            vilacides Isa Vilacides created issue -
            vilacides Isa Vilacides made changes -
            Field Original Value New Value
            Epic Link JENKINS-50534 [ 189601 ]
            vilacides Isa Vilacides made changes -
            Link This issue depends on JENKINS-50539 [ JENKINS-50539 ]
            rarabaolaza Raul Arabaolaza made changes -
            Description We need to modify the git-plugin flow so it runs the PCT on PR basis for git-plugin and all the critical upstream dependencies

             *Acceptance criteria*
             * For every PR to the git-plugin there is a run of the PCT exercising all git-plugin upstream dependencies
             * The run has to be against a TBD version of Jenkins core
             ** Latest one
             ** The one included in essentials
             ** Latest LTS
             * What are the versions of the git-plugin dependencies to use? TBD cc [~jglick] [~rarabaolaza] [~oleg_nenashev]             		We need to modify the git-plugin flow so it runs the PCT on PR basis for git-plugin and all the critical upstream dependencies

             *Acceptance criteria*
             * For every PR to the git-plugin there is a run of the PCT exercising all git-plugin upstream dependencies
             * The run has to be against a TBD version of Jenkins core
             ** Latest one
             ** The one included in essentials
             ** Latest LTS
             * What are the versions of the git-plugin dependencies to use? TBD cc [~jglick] [~rarabaolaza] [~oleg_nenashev]
             ** For example the ones included in essentials, the latest ones?
            rarabaolaza Raul Arabaolaza made changes -
            Description We need to modify the git-plugin flow so it runs the PCT on PR basis for git-plugin and all the critical upstream dependencies

             *Acceptance criteria*
             * For every PR to the git-plugin there is a run of the PCT exercising all git-plugin upstream dependencies
             * The run has to be against a TBD version of Jenkins core
             ** Latest one
             ** The one included in essentials
             ** Latest LTS
             * What are the versions of the git-plugin dependencies to use? TBD cc [~jglick] [~rarabaolaza] [~oleg_nenashev]
             ** For example the ones included in essentials, the latest ones?             		We need to modify the git-plugin flow so it runs the PCT on PR basis for git-plugin and all the critical upstream dependencies

             *Acceptance criteria*
             * For every PR to the git-plugin there is a run of the PCT exercising all git-plugin upstream dependencies
             * The run has to be against a TBD version of Jenkins core
             ** Latest one
             ** The one included in essentials
             ** Latest LTS
             * What are the versions of the git-plugin dependencies to use? TBD cc [~jglick] [~rarabaolaza] [~oleg_nenashev]
             ** For example the ones included in essentials, the latest ones? Or more generally, what environment are we going to use for this PCT run? The UC, a custom UC generated from {{essentials.yml}} a war file generated from the new custom war packager tool using {{essentials.yml}} as source
            rarabaolaza Raul Arabaolaza made changes -
            Description We need to modify the git-plugin flow so it runs the PCT on PR basis for git-plugin and all the critical upstream dependencies

             *Acceptance criteria*
             * For every PR to the git-plugin there is a run of the PCT exercising all git-plugin upstream dependencies
             * The run has to be against a TBD version of Jenkins core
             ** Latest one
             ** The one included in essentials
             ** Latest LTS
             * What are the versions of the git-plugin dependencies to use? TBD cc [~jglick] [~rarabaolaza] [~oleg_nenashev]
             ** For example the ones included in essentials, the latest ones? Or more generally, what environment are we going to use for this PCT run? The UC, a custom UC generated from {{essentials.yml}} a war file generated from the new custom war packager tool using {{essentials.yml}} as source             		We need to modify the git-plugin flow so it runs the PCT on PR basis for git-plugin and all the critical upstream dependencies

             *Acceptance criteria*
             * For every PR to the git-plugin there is a run of the PCT exercising all git-plugin upstream dependencies
             * The run has to be against a TBD version of Jenkins core
             ** Latest one
             ** The one included in essentials
             ** Latest LTS
             * What are the versions of the git-plugin dependencies to use? TBD cc [~jglick] [~rarabaolaza] [~oleg_nenashev]
             ** For example the ones included in essentials, the latest ones? Or more generally, what environment are we going to use for this PCT run? The UC, a custom UC generated from {{essentials.yml}} a war file generated from the new custom war packager tool using {{essentials.yml}} as source...
            rtyler R. Tyler Croy made changes -
            Assignee R. Tyler Croy [ rtyler ]
            jglick Jesse Glick made changes -
            Link This issue relates to JENKINS-47498 [ JENKINS-47498 ]
            oleg_nenashev Oleg Nenashev made changes -
            Link This issue relates to JENKINS-50598 [ JENKINS-50598 ]
            oleg_nenashev Oleg Nenashev made changes -
            Remote Link This issue links to "https://github.com/jenkinsci/jenkins-test-harness/pull/99 (Web Link)" [ 20378 ]
            rarabaolaza Raul Arabaolaza made changes -
            Sprint Essentials - Milestone 1 [ 511 ]
            rarabaolaza Raul Arabaolaza made changes -
            Link This issue relates to JENKINS-51008 [ JENKINS-51008 ]
            rarabaolaza Raul Arabaolaza made changes -
            Link This issue is blocked by INFRA-1571 [ INFRA-1571 ]
            rarabaolaza Raul Arabaolaza made changes -
            Link This issue is blocked by INFRA-1571 [ INFRA-1571 ]
            rarabaolaza Raul Arabaolaza made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            oleg_nenashev Oleg Nenashev made changes -
            Labels plugin-compat-tester
            rarabaolaza Raul Arabaolaza made changes -
            Assignee Raul Arabaolaza [ rarabaolaza ]
            rarabaolaza Raul Arabaolaza made changes -
            Remote Link This issue links to "Git#585 (Web Link)" [ 20511 ]
            rarabaolaza Raul Arabaolaza made changes -
            Remote Link This issue links to "Pipeline-library#48 (Web Link)" [ 20512 ]
            rarabaolaza Raul Arabaolaza made changes -
            Status In Progress [ 3 ] In Review [ 10005 ]
            rarabaolaza Raul Arabaolaza made changes -
            Resolution Done [ 10000 ]
            Status In Review [ 10005 ] Resolved [ 5 ]
            rarabaolaza Raul Arabaolaza made changes -
            Link This issue is duplicated by JENKINS-50516 [ JENKINS-50516 ]
            markewaite Mark Waite made changes -
            Status Resolved [ 5 ] Closed [ 6 ]

            People

              rarabaolaza Raul Arabaolaza
              vilacides Isa Vilacides
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: