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

Move extension files to subfolder #189

Merged
merged 2 commits into from
Mar 12, 2022
Merged

Conversation

JatinSanghvi
Copy link
Contributor

@JatinSanghvi JatinSanghvi commented Mar 12, 2022

  • Keeping the root directory clean. Motivation for changes:

    • Java and .NET coding require separate environments for coding. For instance, if one has opened the root folder in VS code, they will in any case be unable to build and debug Java library code.
    • Commands like dotnet test will see a .NET project structure, The CLI won't find Java files in first place to be able to ignore them.
  • Fixed regex string used for parsing version tag. It was not allowing a version tag like v2.0.0

@JatinSanghvi JatinSanghvi force-pushed the reorder-files branch 2 times, most recently from 4391f6b to 23dbf37 Compare March 12, 2022 12:10
@@ -22,7 +22,7 @@
│ ├───Microsoft.Azure.WebJobs.Extensions.RabbitMQ.2.0.0-preview.symbols.nupkg
│ └───_manifest
│ └───<files>
└───drop-java-bindings
└───drop-java-library
└───2.0.0-preview
├───_manifest
│ └───<files>
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Modified three files: RELEASE_PROCESS.md, azure-pipeline.yml, and .gitignore. Rest of all files are only shifted to different folders.

@@ -29,7 +29,7 @@ jobs:
displayName: WebJobs extension
steps:
- powershell: | # Allow tags matching v1.2.3 and v1.2.3-xyz1
$found = '$(Build.SourceBranchName)' | Select-String -Pattern '^v((\d+\.\d+\.\d+)(?:-\w+))*$'
$found = '$(Build.SourceBranchName)' | Select-String -Pattern '^v((?:0|[1-9]\d*)\.(?:0|[1-9]\d*)\.(?:0|[1-9]\d*)(?:-\w+)?)$'
if (-not $found) {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

The earlier pattern was incorrect (don't remember why I even committed it like this 🤦). It did not allow a tag like v2.0.0 which is intended tag for next major release.

Copy link
Member

Choose a reason for hiding this comment

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

I should have also look at it it carefully the previous time, my bad.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I don't think you reviewed the PR with this particular change :)

Copy link
Contributor Author

@JatinSanghvi JatinSanghvi Mar 12, 2022

Choose a reason for hiding this comment

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

I had added above PR comment soon after the making the first commit. I meant I should have checked the regex when I had worked on build pipeline 1-2 months back.

@JatinSanghvi
Copy link
Contributor Author

Thanks for approving the PR, @v-shenoy. I found two issues with the build pipeline that impacted release builds. Please check the latest commit at your free time and approve the PR if things look good.

@v-shenoy
Copy link
Member

Thanks for approving the PR, @v-shenoy. I found two issues with the build pipeline that impacted release builds. Please check the latest commit at your free time and approve the PR if things look good.

Approved, @JatinSanghvi

@JatinSanghvi JatinSanghvi merged commit e2e17de into Azure:dev Mar 12, 2022
@JatinSanghvi JatinSanghvi deleted the reorder-files branch March 12, 2022 15:52
@JatinSanghvi JatinSanghvi restored the reorder-files branch March 12, 2022 15:52
@JatinSanghvi JatinSanghvi deleted the reorder-files branch March 12, 2022 15:53
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.

2 participants