Fixes DEVELOPER-748 #336
Fixes DEVELOPER-748 #336
Conversation
|
Triggering build using a merge of 6eb7335 on branch master: |
|
Build 221 is now running using a merge of 6eb7335 on branch master: |
|
Build 221 outcome was failure using a merge of 6eb7335 on branch master: |
|
retest this please |
|
Triggering build using a merge of 6eb7335 on branch master: |
|
Build 227 is now running using a merge of 6eb7335 on branch master: |
|
Build 227 outcome was failure using a merge of 6eb7335 on branch master: |
|
retest this please |
|
Triggering build using a merge of 666d045 on branch master: |
|
Build 228 is now running using a merge of 666d045 on branch master: |
|
Build 228 outcome was success using a merge of 666d045 on branch master: |
|
Triggering build using a merge of 0f04094 on branch master: |
|
Build 229 is now running using a merge of 0f04094 on branch master: |
|
Build 229 outcome was success using a merge of 0f04094 on branch master: |
|
@pmuir @lukas-vlcek could we get the changes to the mapping added to the dcp instances please? |
|
If the mapping has been put in place, we should rebuild and try this again. |
|
retest this please |
|
Triggering build using a merge of 0f04094 on branch master: |
|
Build 405 is now running using a merge of 0f04094 on branch master: |
|
Build 405 outcome was failure using a merge of 0f04094 on branch master: |
I think, anyway. Local testing is inconclusive. Adding DCP changes and using it in the javascript I completely forgot about this (the dcp part). We need this added to the environments to make use of this. Adding the sandbox quickstarts to be experimental too. Removing include_in_all
|
Triggering build using a merge of fe42e7b on branch master: |
|
Build 408 is now running using a merge of fe42e7b on branch master: |
|
Build 408 outcome was success using a merge of fe42e7b on branch master: |
|
@LightGuard Thanks for fixing. I need to work with Lukas to have the dups removed and to coordinate getting this fix into production. |
|
Broken links: http://www-stg.jboss.org/pr/336/blinkr/408 |
|
retest this please |
|
Triggering build using a merge of fe42e7b on branch master: |
|
Build 429 is now running using a merge of fe42e7b on branch master: |
|
Build 429 outcome was failure using a merge of fe42e7b on branch master: |
|
retest this please |
|
Triggering build using a merge of fe42e7b on branch master: |
|
Build 432 is now running using a merge of fe42e7b on branch master: |
|
Build 432 outcome was success using a merge of fe42e7b on branch master: |
|
Broken links: http://www-stg.jboss.org/pr/336/blinkr/432 |
|
retest this please |
|
Triggering build using a merge of fe42e7b on branch master: |
|
Build 459 is now running using a merge of fe42e7b on branch master: |
|
@LightGuard this looks to be working now. Searching for the "sandbox" format on this PR and in production returns the same amount of results. Can you verify that you also think it is working, then I'll work with Lukas to get this pushed to production. |
|
Build 459 outcome was success using a merge of fe42e7b on branch master: |
|
Broken links: http://www-stg.jboss.org/pr/336/blinkr/459 |
|
retest this please |
|
Triggering build using a merge of fe42e7b on branch master: |
|
Build 770 is now running using a merge of fe42e7b on branch master: |
|
Build 770 outcome was success using a merge of fe42e7b on branch master: |
I think, anyway. Local testing is inconclusive.