Blog posts by owaiskhan2026-06-16T13:43:41.0000000Zhttps://world.optimizely.com/blogs/owaiskhan/Optimizely WorldCI/CD deployment failure in Optimizely DXP Passportal. .NET 10 and GitHub Runner Compatibility<h3>.NET 10 and GitHub Runner Compatibility</h3>
<p class="isSelectedEnd">With the release of .NET 10, the <code>windows-latest</code> and <code>ubuntu-latest</code> GitHub Actions runners may use the latest installed .NET SDK by default.</p>
<p class="isSelectedEnd">As a result, if your application is built using a different SDK version and no SDK version is explicitly specified, the build and deployment process may use the latest SDK available on the runner. This can lead to build failures, deployment issues, or the website failing to start after deployment.</p>
<p class="isSelectedEnd">To avoid this issue, define the required SDK version in a <code>global.json</code> file at the root of your repository. This ensures that the build pipeline consistently uses the intended .NET SDK version regardless of updates to the GitHub-hosted runners.</p>
<p class="isSelectedEnd">Example:</p>
<pre><code>{
"sdk": {
"version": "8.0.100"
}
}</code></pre>
<p>By pinning the SDK version in <code>global.json</code>, you can ensure predictable builds and deployments across different environments and runner updates.</p>2026-06-16T13:43:41.0000000ZBlog postIntegrating Optimizely CMP Assets into an Existing Document Listing Page<p class="isSelectedEnd">Integrating Optimizely CMP Assets into an Existing Document Listing Page</p>
<p class="isSelectedEnd">In some projects, there may be a requirement to retrieve assets from Optimizely CMP and display them alongside existing content on the website.</p>
<h3>Scenario</h3>
<p class="isSelectedEnd">Consider an existing <strong>Document Listing</strong> page where all documents are managed in <strong>Optimizely CMS</strong> and indexed through <strong>Episerver Search & Navigation (Find)</strong>. A new requirement is introduced to display assets stored in <strong>Optimizely CMP</strong> within the same listing page, together with CMS documents.</p>
<h3>Available Options for Retrieving CMP Assets</h3>
<h4>1. Optimizely CMP Graph API</h4>
<p class="isSelectedEnd"><a href="https://cg.optimizely.com/app/graphiql?auth={singlekey">https://cg.optimizely.com/app/graphiql?auth={singlekey</a>}</p>
<h4>2. Optimizely CMP Open REST API</h4>
<p class="isSelectedEnd"><a href="https://www.postman.com/optimizely/optimizely-s-postman-collection-s/collection/9vnewz3/optimizely-cmp-open-rest-api?sideView=agentMode">https://www.postman.com/optimizely/optimizely-s-postman-collection-s/collection/9vnewz3/optimizely-cmp-open-rest-api?sideView=agentMode</a></p>
<p class="isSelectedEnd"><a href="https://developers.welcomesoftware.com/openapi.html">https://developers.welcomesoftware.com/openapi.html</a></p>
<h3>Proposed Solution</h3>
<p class="isSelectedEnd">Implement a dedicated <strong>CMP API Service</strong> responsible for retrieving assets from Optimizely CMP. The service should:</p>
<ul>
<li>Fetch asset data using either the CMP Graph API or Open REST API.</li>
<li>Map CMP asset data to a common document model already used by the existing Document Listing page.</li>
<li>Merge CMP assets and Optimizely CMS documents into a unified collection.</li>
<li>Apply existing filtering, sorting, and pagination logic consistently across both content sources.</li>
<li>Render the combined results on the same listing page without requiring significant changes to the front-end implementation.</li>
</ul>
<p>This approach allows the existing listing page to support content from multiple sources while maintaining a consistent user experience and minimizing changes to the current architecture.</p>2026-06-16T12:56:07.0000000ZBlog post