Add eng\scripts\ci.yml to run pester unit tests

[haolingdong-msft]

Description

Fix #47398

Hi @weshaggard and @raych1, I have added the eng\scripts\ci.yml to run pester unit tests referring to this comment: #47373 (comment).
May I know how could I verify the CI successfully triggers the pester unit test of updating changelogs? Thanks in advance for your guidance!

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[Copilot]

Pull request overview

This PR adds a new CI configuration file to automatically run Pester unit tests for PowerShell scripts in the eng/scripts/ directory, addressing issue #47398. The configuration leverages the existing Azure SDK PowerShell testing infrastructure.

Key Changes:

• Adds eng/scripts/ci.yml to trigger Pester unit tests on changes to eng/scripts/* (excluding typespec)
• Configures automatic triggers for main, feature, release, and hotfix branches
• Sets up PR validation for the same branch patterns

[weshaggard]

One question but looks good otherwise. Please do create the pipeline and ensure it is passing before merging

[haolingdong-msft]

One question but looks good otherwise. Please do create the pipeline and ensure it is passing before merging

Hi @weshaggard, thanks for the suggestion! I completely agree to create pipeline and have a validation first. But as I wrote in the PR's description, I'm afraid I'm not famliar with pipelines and CI. Could you please provide some guidance on how to create pipeline and whether to create public pipeline or internal pipeline? Do I just click 'New Pipeline' here? https://dev.azure.com/azure-sdk/internal/_build

I also tried to check dotnet ci.yml. But did not know how to find the corresponding pipeline created. 😢

Thanks in advance for your guidance!

[weshaggard]

Sorry I missed your earlier question. You have to manually create the pipeline which you might not have permissions for. I've created a pipeline https://dev.azure.com/azure-sdk/public/_build/results?buildId=5628830&view=results. It should trigger each time you push a new commit now so let's be sure to get it passing before we merge this PR.

[weshaggard]

/azp run java - eng-scripts - ci

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[haolingdong-msft]

/azp run java - eng-scripts - ci

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[haolingdong-msft]

Sorry I missed your earlier question. You have to manually create the pipeline which you might not have permissions for. I've created a pipeline https://dev.azure.com/azure-sdk/public/_build/results?buildId=5628830&view=results. It should trigger each time you push a new commit now so let's be sure to get it passing before we merge this PR.

Thanks @weshaggard for creating the pipeline! But I'm afraid below pipelines seem hanging forever, however, when I click 'view more details', it shows the pipelins successfully complete. https://dev.azure.com/azure-sdk/public/_build/results?buildId=5628830&view=results

I also tried to rerun using the same command as you input, but seems the two hanging pipelines are not re-triggered. And it is strange to me that there are duplicate pipelines to test powershell UT(see below screenshots). Could you provide some suggestions on beging able to run below pipelines successfully? Thank you in advance!

[haolingdong-msft]

/azp run Azure.azure-sdk-for-java

[azure-pipelines]

No pipelines are associated with this pull request.

[weshaggard]

I renamed it from Azure.azure-sdk-for-java to java - eng-scripts - ci and that messed up the status checks. We should be able to update it from main to fix that.

[haolingdong-msft]

I renamed it from Azure.azure-sdk-for-java to java - eng-scripts - ci and that messed up the status checks. We should be able to update it from main to fix that.

Thanks @weshaggard for help. The CI passed now. I just merged the PR.