Skip to content

Moving common dependencies of the tools to a internal package and convert it to a module#14650

Merged
ArcturusZhang merged 24 commits intoAzure:masterfrom
ArcturusZhang:moving-common-dependencies-to-common-package
May 19, 2021
Merged

Moving common dependencies of the tools to a internal package and convert it to a module#14650
ArcturusZhang merged 24 commits intoAzure:masterfrom
ArcturusZhang:moving-common-dependencies-to-common-package

Conversation

@ArcturusZhang
Copy link
Copy Markdown
Member

@ArcturusZhang ArcturusZhang commented May 11, 2021

This PR creates tools/internal module consisting of the packages that are widely used by some tools we are having, including

  • tools/apidiff/delta
  • tools/apidiff/exports
  • tools/apidiff/report
  • tools/apidiff/markdown
  • tools/apidiff/repo
  • tools/internal/dirs
  • tools/internal/modinfo
  • tools/internal/ioext

The following tools are removed:

  • picker is removed in this PR, because it is no longer used and it is referencing apidiff as a dependency.
  • versioner is removed in this PR, we will remain the track 1 SDK un-moduled and do not introduce major version sub-directory in track 2, therefore we no longer need its functionality any more

This PR also creates module for every tool in the tools directory.

@ArcturusZhang
Copy link
Copy Markdown
Member Author

Please do not merge this PR because we still do not resolve the ambiguous import issue now.

@ArcturusZhang ArcturusZhang force-pushed the moving-common-dependencies-to-common-package branch from 508b0ae to f2619b7 Compare May 12, 2021 03:06
@ArcturusZhang ArcturusZhang changed the title Moving common dependencies of the tools to a common package and convert it to a module Moving common dependencies of the tools to a internal package and convert it to a module May 12, 2021
@ArcturusZhang
Copy link
Copy Markdown
Member Author

Do you think we need to create CI for every tool after we change tools into modules? @jhendrixMSFT

@jhendrixMSFT
Copy link
Copy Markdown
Member

It would be ideal to create a pipeline just for tools so that you don't have to run track 1 CI which takes forever.

@ArcturusZhang ArcturusZhang force-pushed the moving-common-dependencies-to-common-package branch 3 times, most recently from 5390c82 to 8106ae4 Compare May 13, 2021 02:49
@ArcturusZhang
Copy link
Copy Markdown
Member Author

It would be ideal to create a pipeline just for tools so that you don't have to run track 1 CI which takes forever.

Since it might not be easy after a bit rounds of trying, I decide we could introduce that later after some offline discussion.

@ArcturusZhang ArcturusZhang force-pushed the moving-common-dependencies-to-common-package branch from 8106ae4 to 7fc97a2 Compare May 13, 2021 02:57
@ArcturusZhang ArcturusZhang force-pushed the moving-common-dependencies-to-common-package branch from 7fc97a2 to c61cf9a Compare May 17, 2021 02:27
@ArcturusZhang
Copy link
Copy Markdown
Member Author

Hi @jhendrixMSFT could you please take a look again?
I just switched to this version on my fork, and everything is working now.

After this PR gets merged, the steps should be

  1. release a new version for track 1 SDK v54.2.1
  2. I will open another PR to switch the azure-sdk-for-go dependency in internal to official, and release the first module version of tools/internal (maybe tools/internal/v0.1.0)
  3. I will open some more PRs, each for one tool, switch the internal and azure-sdk-for-go version to v0.1.0 and the official v54.2.1

@ArcturusZhang ArcturusZhang merged commit 00e7775 into Azure:master May 19, 2021
@ArcturusZhang ArcturusZhang deleted the moving-common-dependencies-to-common-package branch May 19, 2021 06:26
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