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

chore(NA): moving @elastic/datemath into bazel #94665

Merged
merged 35 commits into from
Apr 1, 2021

Conversation

mistic
Copy link
Member

@mistic mistic commented Mar 16, 2021

One step forward on #69706

That PR moves the @elastic/datemath into Bazel by pushing a BUILD file for that package.
After merging this the package will be consumed from within bazel/bin folder.

@mistic mistic added chore v8.0.0 release_note:skip Skip the PR/issue when compiling release notes v7.13.0 labels Mar 16, 2021
@mistic mistic requested a review from tylersmalley March 16, 2021 02:40
@mistic mistic mentioned this pull request Mar 16, 2021
23 tasks
@mistic mistic added the Team:Operations Team label for Operations Team label Mar 16, 2021
@tylersmalley tylersmalley self-requested a review March 16, 2021 20:55
@mistic

This comment has been minimized.

@mistic mistic marked this pull request as ready for review March 16, 2021 21:11
@mistic mistic requested review from a team as code owners March 16, 2021 21:11
@kibanamachine

This comment has been minimized.

@mistic

This comment has been minimized.

@mistic mistic force-pushed the moving-elastic-datemath-into-bazel branch from b325a6f to d5ee22d Compare March 31, 2021 15:44
@mistic

This comment has been minimized.

@mistic mistic force-pushed the moving-elastic-datemath-into-bazel branch from f69487a to 8e40699 Compare April 1, 2021 16:07
@mistic mistic added the auto-backport Deprecated - use backport:version if exact versions are needed label Apr 1, 2021
@mistic

This comment has been minimized.

Copy link
Member

@jbudz jbudz left a comment

Choose a reason for hiding this comment

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

Tested on Windows. LGTM.

@@ -98,7 +98,7 @@
"@elastic/apm-rum": "^5.6.1",
"@elastic/apm-rum-react": "^1.2.5",
"@elastic/charts": "26.1.0",
"@elastic/datemath": "link:packages/elastic-datemath",
"@elastic/datemath": "link:bazel-bin/packages/elastic-datemath/npm_module",
Copy link
Contributor

Choose a reason for hiding this comment

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

👍 I like this better than the build target name.

@kibanamachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

✅ unchanged

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@mistic mistic merged commit f424b9c into elastic:master Apr 1, 2021
@kibanamachine
Copy link
Contributor

💔 Backport failed

❌ 7.x: Commit could not be cherrypicked due to conflicts

To backport manually run:
node scripts/backport --pr 94665

mistic added a commit to mistic/kibana that referenced this pull request Apr 1, 2021
* chore(NA): majority of the changes needed to build elastic-datemath with bazel

* chore(NA): add missing bits on elastic-datemath package

* chore(NA): add missing build and watch scripts

* chore(NA): remove build scripts for elastic datemah

* chore(NA): remove typo from build baze production projects logs

* chore(NA): force install on CI

* chore(NA): introduce custom preserve symlinks resolver for jest

* chore(NA): update jest integration snapshot

* chore(NA): fix build for bazel packages

* chore(NA): correctly copy bazel built packages into final distributable build

* chore(NA): update kbn pm dist

* chore(NA): experimental new logic to handle bazel yarn rule rerun using yarn-integrity file

* chore(NA): update snapshots

* refact(NA): ensure yarn integrity exists into two methods

* chore(NA): fix ts error

* chore(NA): update snapshots

* chore(NA): update elastic-datemath build file to include ts_project rule

* chore(NA): update basic optimization test snapshots

* chore(NA): merge and solve conflicts cherry-pick from elastic#96066

* chore(NA): update package.json and yarn.lock file

* chore(NA): update bazel/bin into bazel-bin on kbn-pm build bazel packages

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
# Conflicts:
#	package.json
mistic added a commit that referenced this pull request Apr 2, 2021
* chore(NA): majority of the changes needed to build elastic-datemath with bazel

* chore(NA): add missing bits on elastic-datemath package

* chore(NA): add missing build and watch scripts

* chore(NA): remove build scripts for elastic datemah

* chore(NA): remove typo from build baze production projects logs

* chore(NA): force install on CI

* chore(NA): introduce custom preserve symlinks resolver for jest

* chore(NA): update jest integration snapshot

* chore(NA): fix build for bazel packages

* chore(NA): correctly copy bazel built packages into final distributable build

* chore(NA): update kbn pm dist

* chore(NA): experimental new logic to handle bazel yarn rule rerun using yarn-integrity file

* chore(NA): update snapshots

* refact(NA): ensure yarn integrity exists into two methods

* chore(NA): fix ts error

* chore(NA): update snapshots

* chore(NA): update elastic-datemath build file to include ts_project rule

* chore(NA): update basic optimization test snapshots

* chore(NA): merge and solve conflicts cherry-pick from #96066

* chore(NA): update package.json and yarn.lock file

* chore(NA): update bazel/bin into bazel-bin on kbn-pm build bazel packages

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
# Conflicts:
#	package.json
@mistic
Copy link
Member Author

mistic commented Apr 2, 2021

7.x/7.13: b47ab19

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-backport Deprecated - use backport:version if exact versions are needed chore release_note:skip Skip the PR/issue when compiling release notes Team:Operations Team label for Operations Team v7.13.0 v8.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants