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

Setup CI/CD for this repo #27

Closed
Tracked by #28
sunker opened this issue Oct 21, 2021 · 1 comment · Fixed by #35
Closed
Tracked by #28

Setup CI/CD for this repo #27

sunker opened this issue Oct 21, 2021 · 1 comment · Fixed by #35

Comments

@sunker
Copy link
Collaborator

sunker commented Oct 21, 2021

Currently, the only way to publish to npm and our github registry is by running

yarn build
yarn bundle 
npm publish  --access=public --scope=@grafana

This requires you to be logged into npm and to be part of the grafana org. Not sure exactly how, but I'd like these steps to be automated. See this PR to get an idea of how this has been solved in other repos at grafana.

For the backend, we could possibly have a bot create new releases every time we merge to the main branch. This is still TBD.

This should be done after this repo is split up in two. See this issue.

@andresmgot andresmgot changed the title Setup CI for this repo Setup CD for this repo Oct 29, 2021
@andresmgot andresmgot changed the title Setup CD for this repo Setup CI/CD for this repo Oct 29, 2021
This was referenced Oct 29, 2021
@andresmgot
Copy link
Contributor

This was actually done with #30 and grafana/grafana-aws-sdk-react#1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants