Skip to content
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

Update .npmrc location in release helper scripts #2303

Merged
merged 5 commits into from May 6, 2024

Conversation

jekloudaMSFT
Copy link
Contributor

I had to rename the pipeline reference name we were using in our release pipeline to be compliant with the OneBranch template. This PR updates that name in our release helper scripts as well.

@jekloudaMSFT jekloudaMSFT requested a review from a team as a code owner May 3, 2024 00:53
Copy link
Contributor

@AE-MS AE-MS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code change looks okay to me but you'll need a changefile, it says.

Given the directory in which this change is being made, I wonder if it should be excluded from the changefile requirement? Something to consider for the future.

AE-MS
AE-MS previously approved these changes May 3, 2024
Ella-ly
Ella-ly previously approved these changes May 3, 2024
Set-Content -Path $Env:SYSTEM_DEFAULTWORKINGDIRECTORY/microsoft-teams-library-js-pipeline/NPMFeed/.npmrc -Value "//registry.npmjs.org/:_authToken=$Env:NPM_TOKEN"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

End of line is required

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you sure? We've already been using this script without issue, I'm just updating the path

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I understand but as per github guidelines it's mandate to have EOL. You can see the red circle with dash in this PR.
https://gist.github.com/camh-/1bebfcff1b0f814e9b191edc60d5206b

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not related to execution; it is related to code-readability.

@@ -1,4 +1,4 @@
$version = Get-ChildItem -Path $Env:SYSTEM_DEFAULTWORKINGDIRECTORY/_OfficeDev.microsoft-teams-library-js/CDNFeed -Directory -Name
$version = Get-ChildItem -Path $Env:SYSTEM_DEFAULTWORKINGDIRECTORY/microsoft-teams-library-js-pipeline/CDNFeed -Directory -Name
Write-Host "Releasing version $version"
Write-Host "CDN: https://res-sdf.cdn.office.net/teams-js/$version/js/MicrosoftTeams.min.js "
Write-Host "NPM: https://www.npmjs.com/package/@microsoft/teams-js/v/$version"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here

@jadahiya-MSFT
Copy link
Contributor

jadahiya-MSFT commented May 3, 2024

Small question here, but would this change impact the current releases. If this pipeline isn't working as expected and we need to fallback to the previous system we have in place, will this still work? Since these scripts are published as artifacts with each build.

We can test this by disabling every step except for the powershell scripts in our current SDF release.

Copy link
Contributor

@jadahiya-MSFT jadahiya-MSFT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just waiting on the above confirmation

@jekloudaMSFT
Copy link
Contributor Author

Small question here, but would this change impact the current releases. If this pipeline isn't working as expected and we need to fallback to the previous system we have in place, will this still work? Since these scripts are published as artifacts with each build.

We can test this by disabling every step except for the powershell scripts in our current SDF release.

Good call, I'll make a new script for the yaml pipeline so we don't break current release

@jekloudaMSFT jekloudaMSFT dismissed stale reviews from Ella-ly and AE-MS via a7c645f May 3, 2024 21:17
Copy link
Contributor

@AE-MS AE-MS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@jekloudaMSFT jekloudaMSFT merged commit 68b5e07 into main May 6, 2024
21 checks passed
@jekloudaMSFT jekloudaMSFT deleted the jeklouda/npmrcUpdate branch May 6, 2024 15:59
alexneyman-MSFT pushed a commit that referenced this pull request May 6, 2024
* Update .npmrc location

* Changefile

* Update @microsoft-teams-js-b63da2d9-3e02-4b83-9664-78aa8f49c713.json

* use new scripts for onebranch pipelines

---------

Co-authored-by: AE ( ͡ಠ ʖ̯ ͡ಠ) <36546967+AE-MS@users.noreply.github.com>
alexneyman-MSFT pushed a commit that referenced this pull request May 9, 2024
* Update .npmrc location

* Changefile

* Update @microsoft-teams-js-b63da2d9-3e02-4b83-9664-78aa8f49c713.json

* use new scripts for onebranch pipelines

---------

Co-authored-by: AE ( ͡ಠ ʖ̯ ͡ಠ) <36546967+AE-MS@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants