Adds Test upstream button to maven upstream form
What does this MR do and why?
Adds Test upstream button to maven upstream form
When the form is in Create mode we call the group API with group path & paramters from the input field.
When the form in in Edit mode, we call the upstream API with the upstream id.
EE: true
References
- Created a shared component
TestMavenUpstreamButtonso that it can be used in #559014[LinkExistingUpstream_MVC.png] - While editing, the
Test upstreambutton tests the API with values stored for the upstream & does not take into account any edited changes made on the page. This is because the API does not allow passing any additional parameters for an existing upstream.
Screenshots or screen recordings
| Create upstream | Edit upstream |
|---|---|
![]() |
![]() |
How to set up and validate locally
- Ensure you have enabled the following feature flags
$ gdk rails console
Feature.enable(:maven_virtual_registry)
Feature.enable(:ui_for_virtual_registries)
- Go to a group
- Go to
Deploy -> Virtual Registry - Create a new maven registry
- Click on the
Add upstreambutton - The required fields are
name,url. For the URL, you can usehttps://repo.maven.apache.org/maven2 - Click on the
Test upstreambutton and confirm the functionality works as expected. - Click on
Create upstreamand observe the list update - Click on the edit icon and confirm that
Test upstreambutton is available on theTest upstreampage
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Related to #560922 (closed)
Edited by Rahul Chanila

