Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Launch Publishing Workflow: Developing within a release cycle ?

Avatar

Level 3

While Launch allows for the publication of libraries continuously, some of us must adhere to strict release windows

In our scheme, only one person has the ability to publish to production and that can only be done during particular hours on a particular day (every two weeks)

My question is, how can I not be blocked from development while QA and UAT are in progress?

For example. When I complete my dev work within the sprint and submit to Staging (where QA/UAT happens), I want to create a new library in Development to start on my next round of work

However, if the library is rejected and sent back to Development, only ONE library can exist within that environment

1 Accepted Solution

Avatar

Correct answer by
Level 2

Alandy_Iceboats​  Multiple libraries can exist in Dev status but they cannot share the same embed codes, so in this case you'd need to create a new environment. You can do this by going to the Environments tab and selecting "Add Environment".The new environment will have its own unique embed code, allowing you to test only your newest changes and keep them separate from the rejected library.

1847368_pastedImage_1.png

1847668_pastedImage_17.png

It sounds like your team's workflow would not permit merging your newest changes into the rejected library, but technically speaking that would be one option as well.

View solution in original post

1 Reply

Avatar

Correct answer by
Level 2

Alandy_Iceboats​  Multiple libraries can exist in Dev status but they cannot share the same embed codes, so in this case you'd need to create a new environment. You can do this by going to the Environments tab and selecting "Add Environment".The new environment will have its own unique embed code, allowing you to test only your newest changes and keep them separate from the rejected library.

1847368_pastedImage_1.png

1847668_pastedImage_17.png

It sounds like your team's workflow would not permit merging your newest changes into the rejected library, but technically speaking that would be one option as well.