Improve the deployment process #265
rmontagnin
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Based on how the BDJuno repository is currently organized, when a new projects needs to have official BigDipper support we have to perform the following operations:
v2/cosmos/stargateorv2/cosmos/v0.44.xto create a custom BDJuno branch for the new projectAlso, each time something is fixed inside either one of the two main branches (
v2/cosmos/stargateorv2/cosmos/v0.44.x) we have to:This has become an incredibly complicated work to be done, since it requires the knowledge of many different things such as where are the BDJuno instance deployed?, should I also updated Hasura?, etc. For this reason, onboarding new projects inside BDJuno has become increasingly harder to do and it will become the main blocking problem in the future.
Fortunately, as it might be easy to understand, all these tasks can be automated using a Continuous Deployment (CD) setup. Particularly, I think that we should now focus on creating an environment that performs the following tasks for us based on a configuration that we provide it (and we should design):
I believe that by doing so we can have a better working environment that allows us to onboard new projects faster and more safely making sure that no regression bugs are introduced.
Please help me figure out if this makes sense and how this idea can be improved anyhow!
Beta Was this translation helpful? Give feedback.
All reactions