Loading Profile...
Hello,
Can you please help me understand if our workflow is possible, or whether I need a different approach.
I am continuously working on the extension, so quite often it is in a "disassembled" state. Yet when significant tasks are completed — I create a "working" release, which I export from Crossrider IDE (using the dowload link), and send it to our QA team.
After QA confirms, that everything is fine (and that takes time, during which I continue development), I merge the changes into the "production" extension, and we upload it to Chrome Web Store etc.
So essentially we have three versions in circulation — development, QA and production.
Yet we just discovered that installing the exported installs that I provide to QA still downloads the latest development code of the extension, so there is no point in saving these releases, since they get overwritten by whatever is the latest code that is currently being developed.
Is this observation correct?
And if yes — how do we sidestep this? I hope to avoid creating another "dev" extension, and copy the files back and forth to "QA" (staging) and then "production" extensions... It would be nice for a given export to "freeze" its state and not have it update from Crossrider servers.
Best regards,
Anton
PS Having the long awaited GitHub support would help in this process too.
Help get this topic noticed by sharing it on
Twitter,
Facebook, or email.
Twitter,
Facebook, or email.
Getting previous version of extension (dev/QA/prod flow)
-
-
-
EMPLOYEE
1Hello Anton,
If I understand your scenario correctly, then given your dev cycle(dev - QA - production), I think the minimum most effective solution would be to have 2 extensions(1) the Production(production mode) / QA(staging mode) extension and(2) the Dev extension.
I see it working as follows:- All dev work is carried out in the Dev extension so that it can have no bearing on the Production extension
- Once the code it ready
for QA, Dev exports the extension package from the Dev extension and QA imports it to the staging mode of the Production extension and performs tests.
In the event that QA does not give the OK, the following steps can be used:
(a) QA can export the extension package from the Production extension 's staging mode and send it back to Dev for fixing
(b) Upon receiving the QA package, the Dev team, in the Dev extension,
can sync the staging mode code to production and import the QA package and make the requested fixes
(c) Once the QA fixes are implemented, the dev team can repeat the process, but this time after exporting the extension package from the Dev extension 's staging mode, they can sync the production code back to staging mode and continue developing where they left off - Once QA has approved the extension, the extension is simply sync'd with production to distribute it to existing and new installations
- By segmenting the dev efforts into a separate extension, you avoid the possibility of dev code slipping into production extensions.
Anyway, that's my thoughts on how you may achieve a useful cycle: )
If anyone else has any better ideas, please feel free to share.- view 3 more comments
-
-
-
-
Can you email the ZIP file? I'll test it at my end. Please send it to support@crossrider,com
-
-
Hi Shlomo, sent, thanks for looking into it. I guess the main question for me, since I can use "Clone" to create DEV versions, is to have a reliable way to import a .zip into an existing extension (PROD/QA).
-
-
-
