mirror of
https://github.com/dbeaver/cloudbeaver.git
synced 2026-04-25 13:46:02 +03:00
[GH-ISSUE #2303] Seeking Advice for Efficient Development and Testing #732
Labels
No labels
AS
can't reproduce
can't reproduce
deployment
development
documentation
duplicate
duplicate
ee
enhancement
external
new driver
performance
pull-request
third party issue
wait for response
wait for review
wontfix
x:Oracle
x:cassandra
x:clickhouse
x:db2
x:duckdb
x:greenplum
x:h2
x:h2gis
x:hana
x:hive
x:intersystems
x:kyuubi
x:maria
x:mongo
x:mysql
x:postgresql
x:presto
x:sql server
x:sqlite
x:teradata
x:trino
xf:accessibility
xf:administration
xf:ai
xf:authentication
xf:aws
xf:commit-mode
xf:connection
xf:dark theme
xf:data editor
xf:datatransfer
xf:dba
xf:driver management
xf:erd
xf:filters
xf:i18n
xf:i18n
xf:installer
xf:json
xf:kerberos
xf:ldap
xf:local config
xf:log viewer
xf:metadata
xf:metadata editor
xf:navigator
xf:okta
xf:query manager
xf:resource manager
xf:scripts
xf:sql editor
xf:tasks
xf:ui/uix
xo: Firefox
xo:eclipse
xo:internet explorer
xo:macos
xp:major
xrn:internal
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/cloudbeaver#732
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @tryantdb on GitHub (Jan 16, 2024).
Original GitHub issue: https://github.com/dbeaver/cloudbeaver/issues/2303
Hello CloudBeaver Team and Community,
recently I'm learning code of Dbeaver and Cloudbeaver. And I did some changes to the cloudbeaver code.
Here is how I test my code works:
1. Implement code changes.
2. run deploy/build.bat.
3. execute deploy/cloudbeaver/run-server.bat in debug mode.
4. Use idea remote JVM debug to test the code.
My questions are:
It always takes serveral mininutes to run the build.bat after a code change which is disturbing and time-consuming.
In light of this, I'm reaching out to seek your insights and recommendations. I'm curious to learn about the approaches and strategies you employ for developing and testing CloudBeaver. Are there more efficient methods or best practices that you follow within your team? Any tips or tools that could expedite the build and test process would be immensely helpful.
Thank you for your time and for the incredible work you do with DBeaver. I look forward to any suggestions or advice you might have.