When installing dev package, target a specific index

[scbedd]

@praveenkuttappan @tjprescott I am pretty certain this will be fine for our runs.

Does this same concern affect how we currently install the api-stub-generator during APIView deploy?

[check-enforcer-staging]

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

[tjprescott]

@scbedd I think targeting a specific index makes sense, but shouldn't it be here, not the SDK? Didn't you move the pylint-guidelines-checker to this repo?

[scbedd]

I see. I'm just an idiot where I blindly updated this install.

[scbedd]

@tjprescott No I think this is right.

This api-stub-generator is what gets used to create APIReviews right? And it uses the pylint-guidelines-checker to generate part of it's failures.

In the pipeline checking this api stub generator, do we want to use the version being developed or the same one as what APIView uses?

If it's just "use what's developed" then I totally agree and will add a relative install, otherwise, we need to install from a specific feed, not using extra-index.

[tjprescott]

@scbedd we should what APIView uses so this looks like the right approach. Thank you!

[scbedd]

This PR will fail until this other PR is invoked for the dependent packages.

[scbedd]

/azp run tools - api-stub-generator - ci

[scbedd]

/azp run tools - api-stub-generator - ci

[azure-pipelines]

No pipelines are associated with this pull request.

[scbedd]

/azp run tools - api-stub-generator - ci

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).