Posts

Octopus Environment and Octous Tentacle

Image
Setting up Octopus to go with TeamCity. Mainly what Octopus does is that it takes over the deployment phase. TeamCity builds and creates a package of the application (according to the artifacts specified - will get to that in the next blog), and at this point, Octopus acquires the package created by TeamCity, and deploy it to target environments. This will be installed on the same server that the TeamCity installed in. Prerequisites: Octopus  Tentacle https://octopus.com/downloads/tentacle Steps: Installing SQL server 2017 Octopus Tentacle: according to Octopus documentation "If you want to deploy a package on your Octopus Server, you should install a Tentacle on your Octopus Server and treat it just like any other deployment target." I downloaded the x64.msi file and run it. Click Next. Select the communication style to be Listening Tentacle Click Next. Select the folders that the Tentacle will use to store the logs and applications   Clic...

Setting up TeamCity Build Configuration

Image
In this blog, I will go through setting up TeamCity project and adding the minimum needed build steps to rebuild and create the package that will be used through the Octopus server to deploy. So, here we go: Start by creating the project and set the VCS root Let us start by navigating to the Administration on the upper right corner. Click on + Create Project. Insert the General Setting. Project name and ID, you can leave other information as it is Setup the VCS root (I already have a created root. If you want to create one click on Create VCS root) Start by inserting type of VCS, root name, fetch URL and the branch you want to use for the deployment Specify the Authentication method and insert the needed credentials Now test the information inserted and credential by clicking on Test Connection. Then save Next we will create the build steps. Remember that there is a large number of Runner Types that can be added to configure the sequence of buil...

Installing Octopus for the first time

Image
Setting up Octopus to go with TeamCity. Mainly what Octopus does is that it takes over the deployment phase. TeamCity builds and creates a package of the application (according to the artifacts specified - will get to that in the next blog), and at this point, Octopus acquires the package created by TeamCity, and deploy it to target environments. This will be installed on the same server that the TeamCity installed in. Prerequisites: Octopus https://octopus.com/downloads SQL server Steps: Installing SQL server 2017 I installed a separate server than the one used for TeamCity, just to make sure that the collation specified for each server won't have some side effects or cause problems later. So for this step, setup SQL server - as usual - but this time don't worry about the collation and do not change the default one Before we finish the SQL server setup the last step would be to create a new database name it 'OctopusDeploy' database must use a case-insens...

Installing TeamCity for the first time

Image
First, I will be describing the steps for installing Teamcity considering that this will be the first time installing and configuring Teamcity, I will install it on Windows Server 2016. Prerequisites: S QL server 2017   SQL management tools TeamCity download the TeamCity installation package depending on your target environment, for me, I installed Executable Windows installer TeamCity-2019.2.2.exe Steps: Installing SQL server 2017 the things to make sure you do when installing the SQL server (start the installation as usual) Server Configuration: set the collation Latin1_General_CS_AS (Teamcity requires a Case-Sensitive and Accent-Sensitive collation) Select customize and adjust the collation if you want to use a separate user account for Teamcity add it as an administrator account After the installation is done, configure the installed SQL server to be used with TeamCity, by enabling TCP/IP protocol for that SQL server for SQL Server Configu...

Sitecore 9.0.2 SXA 1.7.1 search load more

Sitecore 9.0.2 SXA 1.7.1 search load more. Same conditions as in this blog . Issue: We are using SXA the default search control , and in one of the cases we had even more than two searches in one page, and noticed that the search Load More keeps disappearing and appearing many times while loading and sometimes it does not show even that the Page Size is less than the returned search items count, which caused a wrong behavior. We made sure that the signatures for each search is different but the issue was still there. We had to make some changes to js file component-search-load-More. js to solve this issue and check Signature before hiding or showing the Load More component. Original component-search-load-more.js - SearchLoadMoreView: SearchLoadMoreView = Backbone.View.extend({ initialize : function () { var dataProperties = this.$el.data(), that = this; if (dataProperties.properties.searchResultsSignatu...

Sitecore 9.0.2 SXA 1.7.1 search results count.

Sitecore 9.0.2 SXA 1.7.1 search result issue. So if you are using Sitecore and SXA, one of the SXA great features that SXA offers is the flexible out-of-the-box search functionality that enables the website visitors to quickly find what they are looking for. And from the toolbox, you can find many renderings for the search. All you have to do is to drag and drop. One of the SXA projects I worked on were we used Sitecore 9.0.2 along with SXA 1.7.1, I faced some issues with the Search functionality/Results specifically in the search result count. Issue: L ets say we are using Sitecore 9.0.2 and SXA 1.7.1 we have search page and we are using SXA Search Results + Results Count ( SXA default search control s ) , but we also have partial design lets say it's for the Header and it contains Search Results in its presentation details, and we only display the item's title (no Search result count). So now we have a page that contains two search functionalities, e ac...