Currently the user does not know about what tools are natively supported by the Pipeline as a Service until it reaches the step 3 (criteria), but we are requesting the definition of tooling services in step 2. This means that the user has to go to step 3 and if the tool is not listed there, get back to step 2 to define a container that will provide it.
Currently the user does not know about what tools are natively supported by the Pipeline as a Service until it reaches the step 3 (criteria), but we are requesting the definition of tooling services in step 2. This means that the user has to go to step 3 and if the tool is not listed there, get back to step 2 to define a container that will provide it.
I see two approaches to circumvent this: