• Icon: Task Task
    • Resolution: Fixed
    • Icon: Major Major
    • blueocean-plugin
    • None
    • pannonian, iapetus, 1.0, Blue Ocean 1.0-rc3

      Scope

      • New REST endpoint to validate that the given Git credentials work

      Notes
      If this is easy to do it will remove a lot of friction (e.g. no one will have to run the pipeline to validate)

      Theres some way that Jenkins talks to git repos remotely for change detection that could be used to validate?

          [JENKINS-41397] API to validate Git credentials

          Cliff Meyers added a comment -

          This doesn't necessarily need to be a standalone REST API endpoint; we could just add this validation to the Git creation endpoint.

          Cliff Meyers added a comment - This doesn't necessarily need to be a standalone REST API endpoint; we could just add this validation to the Git creation endpoint.

          Vivek Pandey added a comment -

          Ok, I will work on adding this validation in creation endpoint.

          Vivek Pandey added a comment - Ok, I will work on adding this validation in creation endpoint.

          James Dumay added a comment -

          michaelneale downgrading this as the UI work for it is marked as Major

          James Dumay added a comment - michaelneale downgrading this as the UI work for it is marked as Major

          Vivek Pandey added a comment -

          Vivek Pandey added a comment - PR https://github.com/jenkinsci/blueocean-plugin/pull/759  is merged in to https://github.com/jenkinsci/blueocean-plugin/pull/895  and being tracked over in  https://issues.jenkins-ci.org/browse/JENKINS-42120 .

            vivek Vivek Pandey
            jamesdumay James Dumay
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: