Skip to content

Improve CI speed by changing repo targeted by Forks tests #258

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 29, 2020

Conversation

HowardWolosky
Copy link
Contributor

Description

Pull #251 changed the repo targeted by the forks tests from microsoft/PowerShellForGitHub to octocat/Hello-World in order to prevent the accidental deletion of real forks when running the UT's locally against your own account.

In practice, this almost doubled the execution time of the UT's, because the execution time of the Forks API's took so much longer against a repo with 1400+ forks.

Changing the test over to use a repo that currently only has 39 forks (several orders of magnitude fewer).

Issues Fixed

n/a

References

n/a

Checklist

  • You actually ran the code that you just wrote, especially if you did just "one last quick change".
  • Comment-based help added/updated, including examples.
  • Static analysis is reporting back clean.
  • New/changed code adheres to our coding guidelines.
  • New/changed code continues to support the pipeline.
  • Changes to the manifest file follow the manifest guidance.
  • Unit tests were added/updated and are all passing. See testing guidelines. This includes making sure that all pipeline input variations have been covered.
  • Relevant usage examples have been added/updated in USAGE.md.
  • If desired, ensure your name is added to our Contributors list

Pull microsoft#251 changed the repo targeted by the forks tests from
`microsoft/PowerShellForGitHub` to `octocat/Hello-World` in order
to prevent the accidental deletion of real forks when running the UT's
locally against your own account.

In practice, this almost doubled the execution time of the UT's,
because the execution time of the Forks API's took so much longer
against a repo with 1400+ forks.

Changing the test over to use a repo that currently only has 39 forks
(several orders of magnitude fewer).
@HowardWolosky HowardWolosky added the tests A change related to the Pester tests for the module. label Jun 29, 2020
@HowardWolosky
Copy link
Contributor Author

/azp run PowerShellForGitHub-CI

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@HowardWolosky HowardWolosky merged commit 4287ac9 into microsoft:master Jun 29, 2020
@HowardWolosky HowardWolosky deleted the fasterForks branch June 29, 2020 23:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tests A change related to the Pester tests for the module.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant