1
0
Fork 0
mirror of synced 2024-07-13 02:05:54 +12:00
budibase/.github/workflows
melohagan 9ecf82e0f6
Add endpoint to GET tenant info from tenant global DB. (#13923)
* Add GET tenant info endpoint

* Add GET global tenant to endpoint list.

* Use correct not found code

* Fix unit test

* Code review comments

* Ignore account portal check types

* remove account-portal-ui from type check ignore

* Remove ignore account-portal-ui from type check
2024-06-17 09:22:44 +00:00
..
budibase_ci.yml Add endpoint to GET tenant info from tenant global DB. (#13923) 2024-06-17 09:22:44 +00:00
check-oss-contributor.yml Change webhook url 2023-11-20 10:05:25 +01:00
cla.yml Only check CLA on PRs to master. 2023-10-19 18:00:40 +01:00
close-featurebranch.yml Update github checkout action to v4 2024-01-25 09:15:37 +01:00
deploy-featurebranch.yml Update github checkout action to v4 2024-01-25 09:15:37 +01:00
deploy-qa.yml No not deploy account portal automatically for QA 2023-12-04 09:36:07 +01:00
force-release.yml qa-arc-runner-set -> ubuntu-latest 2024-06-03 17:15:51 +03:00
pr-labeler.yml Fix labelling for PClmnt 2024-06-07 08:34:53 +02:00
README.md Document rollback 2023-12-11 16:40:11 +01:00
stale_bot.yml Fix stale bot (#12692) 2024-01-03 11:32:08 +00:00
tag-release.yml Update github checkout action to v4 2024-01-25 09:15:37 +01:00

Budibase CI Pipelines

Welcome to the Budibase CI pipelines directory. This document details what each of the CI pipelines are for, and come common combinations.

All CI Pipelines

Standard CI Build Job (budibase_ci.yml)

Triggers:

  • PR or push to master

The standard CI Build job is what runs when you raise a PR to master.

  • Installs all dependencies,
  • builds the project
  • run the unit tests
  • Generate test coverage metrics with codecov
  • Run the integration tests
  • Check that the pro and account portal submodules are pointing to the lastest master head

Release Job (tag-release.yml)

Triggers:

  • Manually triggered

This job is responsible for building and pushing all the production services, packages and images. This is done via budibase-deploys.

An input is required, indicating if the new version will be a patch, minor or major bump.

More documentation can be found in here: https://budibase.atlassian.net/wiki/spaces/DEVOPS/pages/347930625/Production+release

Common Workflows

Deploy Changes to Production (Release)

  • Merge your changes into master
  • Run tag-release.yml
  • Check the progress in budibase-deploys

Rollback A Bad Cloud Deployment

Rollback documentation can be found in here. https://budibase.atlassian.net/wiki/spaces/DEVOPS/pages/347930625/Production+release#Rollback