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

We should have github actions to push to do all the CI / CD. #38

Open
kunjee17 opened this issue Jan 19, 2020 · 2 comments
Open

We should have github actions to push to do all the CI / CD. #38

kunjee17 opened this issue Jan 19, 2020 · 2 comments

Comments

@kunjee17
Copy link
Contributor

As stores are growing we should be having CI/CD and publishing to nuget automated. Just to lower down a burden on maintainer.

Also, we have docs and site deployment as well. Mostly github docs. (I guess we might need more than something to readme. as mentioned in #34 :) )

@Dzoukr
Copy link
Owner

Dzoukr commented Jan 20, 2020

Great idea! I already tried something on DevOps pipelines, but the problem with CI is it's connected to Cosmos DB, Table Storage, Postgres, ... and there would have to be databases available for running tests before pushing to Nuget (required part of creating package). I think there is target to spin up Cosmos, but do you have any idea how to handle others like Table Storage, Postgres?

@kunjee17
Copy link
Contributor Author

Postgres can be handle using docker images. Means CI will spin up image for testing. LiteDB we will not require anything. Even SS testing is file based SQLite.

Table Storage. I guess there is something you can install in local machine. If it is there we can always have docker for same.

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

No branches or pull requests

2 participants