Forum Academy Marketplace Showcase Pricing Features

Development, Staging (QA)?, Production

We have a missing peace in our development/test model. No staging system for QA to test.

We had a successful Go-Live last week, and now our production system is off limits to our QA team. Our developers would rather not have QA testing on the development system.

Any ideas on a good approach to this operational problem using Bubble?

Thanks
Bryan

4 Likes

You could clone the app to a new app and let them go wild on there!:slight_smile:

Staging would be good however…

1 Like

@DaveA, Good idea about cloning. But there is still a hole in the release model, especially when we need to perform parallel development and hot fixes.

I have gotten the model down to the following, but there is one piece missing in the model:

  1. The Version 1 app is running on App1. App2 is a copy of App1. App2 is used for feature development of the Version 3.
  2. App1 “Development” is used for QA testing of Version 2. If hot fixes are necessary, then they can be applied to App1 “Development”, and QA can resume testing. Hot fixes can be manually applied to App2.
  3. Release candidate of Version 2 can be pushed to App1 “Production”

I believe the problem with this approach is that when App2 (Version 3) is ready to go live, do we point the domain abc123.com to App2? If so, then how do we migrate the production data from App1 to App2?

Would love to hear everyone’s ideas here.

Thanks,
Bryan

It would be great to know if others have found answers to this. The issue of having to rip into Dev and blow your production back up away is nauseating and something that professionals never do. Definitely cloning gives some relief but is not a part of a migration strategy. Has anyone progressed this?

Does anyone here know how to start a new thread? (This is a rhetorical question, please don’t answer.) These zombie thread resurrections are becoming a real annoyance.

@sanastasi: if the last post is two years ago, FTLOF, just start a new thread with a specific question. The current behavior here is bizarre. Are Bubble users clueless about everything? (Again, don’t answer that. It’s a rhetorical question.)

@keith, I take it you have nothing to add of importance then? Don’t answer that, it’s rhetorical. In fact, the forum software itself explains the advantage of replying to an old thread in order to push it back to the top.

The age of this question does not diminish its importance. If we’d like to resurrect the conversation in a new thread, then be my guest. I’ll follow it no matter how old it its. Either way, I’ll awaiting an informed opinion. Enjoy.

4 Likes

“2 Years Later” c’mon bruh

@sanastasi

Haven’t read the full thread but here is my latest experience with versioning if it helps.

Not having a QA is still an issue. If I clone to create QA then that app needs to be on a paid-plan too. If u r using some of the paid features which most people will.

And then if your app is live then your data goes stale on both QA and Dev. So you need to bring QA back on to Dev before deploying. Or sync prod data to QA and make that live instead.

But there is hope. A new feature called selective deployment is just pushed down by Bubble team. So you can push quick fixes to prod. I didn’t get time to test it but could be very useful.

1 Like

Thanks Prashant, yes the selective deployment is good although determining the activities within the change stream is very cumbersome. I’ve managed to do it to 2-3 times I’ve needed it but I always felt it was a bit of a guess and limited only to activities that are small enough to identify in full across the entire stream. Once you’ve done a decent amount of work in an environment that approach loses it’s value.

What’s needed in simplest terms is a test or staging option so that we can at least have Dev - Test - Production which is the minimum for solutions being built for real customers. Many of us cannot afford to have our dev environment (which serves as our only easy migration to production) get so out of sync with changes that it no longer represents something we can immediately repair production issues from. I’m currently in that position with a re-write of features that is leaving me very nervous.

Thanks for your insights.

3 Likes

It looks like the last response was in 2018 (3 years ago). Has there been any movement on this? I’m running into the same issue. I’m building an application and I NEED a staging version deployed to a real URL for QA purposes. How are people getting around this? I’ve got a team of 5 working on this so the preview option is constantly asking for a refresh.

Surely bubble has some option to fix this?