SOLVED
Test Environment
We have added extra environment that is Test Environment and share JS with developer. But in publishing flow i can move between dev, staging and production. How i can make sure Test script also work. When i moved to staging than acceptance link is working but test environment link is not working.
1 Accepted Solution
@Jennifer_Dungan , i have this library in published (i think prduction), how i can ensure same works at test environment also
I just did a quick test to check this.
I created a new Launch property with 2 Development environments:
I checked that Publishing Workflow is empty.
So I created 2 libraries: Library 1 (using Dev1) and Library 2 (using Dev2). Both libraries don't have any Rules, Data Elements nor Extensions yet.
After saving and building these 2 empty Libraries, Publishing Workflow shows both of them with the green status.
Going back into Library 1, I add the Core extension, then save and build the library.
Library 2 is still empty and doesn't show any Extensions in its "Resources Upstream" section.
Now, with Library 1, I Approve & Publish to Production. So, Publishing Workflow shows Library 1 in Production. But notice now that Library 2 has an orange indicator. This means that Launch changed Library 2 when I published Library 1.
Opening Library 2, I now see the Core extension is in the "Resources Upstream" section.
So we have the answer to your query:
@chirag_madan wrote:
Hi @Jennifer_Dungan Thanks for detailed explication. I have one scenario, let’s say we have 2 dev websites with different dev codes.
Dev website1: Dev env1
Dev website2 : Dev env2
ruleA published on dev1>staging>priduction.
I didn’t used dev 2 as if now and it is not having any changes. Now when i go to dev website2 will it have the rule published in production in effect as per upstream concept or i have to explicitly create a nee library in and push it to dev 2 to check productioN changes.
The answer is Yes, Dev 2 will get Dev 1's published changes, even though Dev 2 has not been published yet.
This makes sense as the expected behaviour in Launch: all development libraries automatically get all published changes. Otherwise, having many "branches" will cause a lot of synchronisation and maintenance challenges.
Ok, you're not dealing with libraries in your question. In that case, no Development environments where their libraries have not been built will not have the upstream published changes.
To verify this, I re-created my test property, with the same setup as before. But I also created a third Development environment, Dev3:
I still have 2 Libraries for Dev1 and Dev2 (remember, I recreated my property, so the 2 libraries are still under Development):
Library 1 has the Core extension, and I can see this in Dev1's script:
But Dev2's script doesn't have this extension:
And neither does Dev3's script:
Now, I Approve & Publish Library 1 to production. As expected, Library 2 has changed.
But Dev1's script still has the old content from before. Notice that the "buidDate" has not changed.
Similarly, Dev2's script has not changed (remember that Dev2 has Library 2 attached to it):
And Dev3's script also has not been changed (remember that there is no library attached to Dev3):
When I build Library 2, then Dev2's script gets changed:
Now, I create a new Library 1-1 and attach it Dev1:
After saving and building Library 1-1, Dev1's script gets changed (see the updated buildDate):
But Dev3's script is still unchanged:
So you must build a library with a Development environment in order for that Development environment's script to get updated with the upstream resources. That means in your example, when you load your dev environment 2 that has Dev2 script, then you should not expect to see any of Dev1's published changes because you have not re-built the library for Dev2.
BTW if Dev2 is a brand new environment and has never had any library attached to it, then you should expect another outcome: your browser will simply report a 404 not found error for Dev2's script when you open your website. So there are 2 things to note:
- Development environment that has never had a library built for it --> browser reports 404 error not found with the Development environment's script.
- Development environment has had at least 1 library built for it --> the Development environment's script is correct as of the last build.
So you can have multiple "development" environments, one staging environment and one prod environment.
When you go to publishing flow, in your development flow column, you can create multiple Libraries (in the environment drop down, all the available development libraries should be listed)
If any of your Dev environments already have a Library attached to it, they will appear greyed out in the dropdown.
You will need to create libraries for each "Development" environment.
This is most often used when you have multiple QA/Dev servers (you can create a build for QA1, a build for QA2, etc - and for multiple releases working in parallel where "change 1" may go before or after "change 2"... you can test the tracking in isolation and deploy in whatever order you need)... I suspect in your case, your developers have a separate development environment that they want more isolated from your QA changes?
If that's the case, you shouldn't need to promote your "Test" builds up any further than development.. but when your changes go to prod you will need to sync up your developer's version of the code to what is in production....
@Jennifer_Dungan , i have this library in published (i think prduction), how i can ensure same works at test environment also
