Files

T

blam e44cb85b22 Merge branch 'master' of github.com:spotify/backstage into migrate-to-msw

* 'master' of github.com:spotify/backstage: (66 commits)
  chore: fix lerna linting
  v0.1.1-alpha.25
  Add Code Insights plugin to sample app and marketplace (#2833)
  Improve main CI build status badge in README (#2866)
  Update roadmap: Design System 🚢 (#2858)
  github/codecov: switch to informational mode
  github/workflows: use the tip of master as the base for comparing PR code coverage
  make saml provider path from globalConfig (#2855)
  fix(catalog-backend): limit search value lengths
  Update project Copyright (#2852)
  fix(catalog-backend): actually use modified entity output (default namespace was broken)
  remove unnecessary center keyword
  Move card header bg to up contrast, fix #2558
  Update name of env authentication env vars
  Fix feedback from dtuite
  Remove chart testing workflow for now
  Only lint charts on Pull Requests
  Move the k8s deployment docs to its own helm deployment page
  Remove line in initdb script that creates backend db
  Use app-config.development.yaml to provide configuration instead of local
  ...

2020-10-13 03:56:13 +02:00

dev

Created a plugin for cloud build as CI/CD

2020-09-17 17:59:05 +02:00

src

Merge branch 'master' of github.com:spotify/backstage into migrate-to-msw

2020-10-13 03:56:13 +02:00

.eslintrc.js

Created a plugin for cloud build as CI/CD

2020-09-17 17:59:05 +02:00

package.json

Merge branch 'master' of github.com:spotify/backstage into migrate-to-msw

2020-10-13 03:56:13 +02:00

README.md

Updated plugin name on the README.md

2020-09-23 16:33:05 +02:00

README.md

Google Cloud Build

Welcome to the Google Cloud Build plugin!

This plugin was created through the Backstage CLI

Getting started

Your plugin has been added to the example app in this repository, meaning you'll be able to access it by running yarn start in the root directory, and then navigating to /cloudbuild.

You can also serve the plugin in isolation by running yarn start in the plugin directory. This method of serving the plugin provides quicker iteration speed and a faster startup and hot reloads. It is only meant for local development, and the setup for it can be found inside the /dev directory.