databricks-cli

Author	SHA1	Message	Date
Pieter Noordhuis	f939e57f3a	Trigger integration tests on push to main (#2035 ) ## Changes The existing workflow already had 2 trigger conditions, so instead of adding a third (and seeing more "skipped" jobs), I split them up into dedicated workflow files, each with their own trigger condition. The integration test status is reported back via commit status. ## Tests We can confirm that everything works as expected as this PR moves from here to the merge group to main.	2024-12-19 11:50:59 +00:00
hectorcast-db	2bbdd04217	[Internal] Always write message for manual integration test trigger (#1874 ) ## Changes Old script could not be run from master due to security restrictions and there is no reliable way to detect if a user as secrets. ## Tests Opened a PR in SDK Java from fork https://github.com/databricks/databricks-sdk-java/pull/375	2024-10-31 14:29:08 +00:00
hectorcast-db	20fd401550	[Internal] Add test instructions for external contributors (#1863 ) ## Changes Add test instructions for external contributors ## Tests See Go Changes https://github.com/databricks/databricks-sdk-go/pull/1073	2024-10-29 13:42:36 +00:00
hectorcast-db	5a555de503	[Internal] Automatically trigger integration tests on PR (#1857 ) ## Changes Automatically trigger integration tests when a PR is opened or updated ## Tests Workflow below. --------- Co-authored-by: Pieter Noordhuis <pieter.noordhuis@databricks.com>	2024-10-25 09:15:24 +00:00