• Icon: Task Task
    • Resolution: Done
    • Icon: Minor Minor
    • evergreen
    • None
    • Evergreen - Milestone 1

      Acceptance criteria

      For the git-plugin define the list of P1 cases

          [JENKINS-50536] git-plugin P1 cases definition

          The plugin can be updated and configuration for a job serialized
          • An user can install a newer version of the plugin and the existing configuration is preserved and job is still working (Not covered by any test AFAICT)
          Provide a full SCM API implementation for Git 
          • A Job can perform a checkout from a Git repo into workspace (Covered in ATH) 
          • A job can generate changelogs from a Git repo and display them (Covered in ATH)
          • A job can perform a checkout of a concrete tag/btanch/commit of a git repo into the workspace (Covered in ATH)
          • A job can perform polling to a Git repository to react to code changes (Covered in ATH)
          • A job can perform a checkout from a protected Git repo into workspace using username/password credentials using the proper URL (Partially covered in unit tests) 
            • Both with proper username/password and a PAT 
          • A job can perform a checkout from a protected Git repo using SSH credentials (Covered in ATH)
          • A job should be able to interact with different Git providers (Not covered by any test AFAICT)
          Support for git hooks
          • A job can be triggered automatically on PR request (Not covered by any test AFAICT)
          • A job can be triggered automatically on merges to master (Not covered by any test AFAICT)
          • A job should be able to filter events based on the source of them (different branches, etc) (Not covered by any test AFAICT)
          Support for custom behaviours
          • A job should be able to select from a list of additional behaviours to fine tune the workflow (Covered by ATH)

          Raul Arabaolaza added a comment - The plugin can be updated and configuration for a job serialized An user can install a newer version of the plugin and the existing configuration is preserved and job is still working (Not covered by any test AFAICT) Provide a full SCM API implementation for Git  A Job can perform a checkout from a Git repo into workspace (Covered in ATH)  A job can generate changelogs from a Git repo and display them (Covered in ATH) A job can perform a checkout of a concrete tag/btanch/commit of a git repo into the workspace (Covered in ATH) A job can perform polling to a Git repository to react to code changes (Covered in ATH) A job can perform a checkout from a protected Git repo into workspace using username/password credentials using the proper URL (Partially covered in unit tests)  Both with proper username/password and a PAT  A job can perform a checkout from a protected Git repo using SSH credentials (Covered in ATH) A job should be able to interact with different Git providers (Not covered by any test AFAICT) Support for git hooks A job can be triggered automatically on PR request (Not covered by any test AFAICT) A job can be triggered automatically on merges to master (Not covered by any test AFAICT) A job should be able to filter events based on the source of them (different branches, etc) (Not covered by any test AFAICT) Support for custom behaviours A job should be able to select from a list of additional behaviours to fine tune the workflow (Covered by ATH)

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

              Created:
              Updated:
              Resolved: