Skip to main content

Azure DevOps–Reindexing

The search experience in Azure DevOps(Server) is powered by ElasticSearch. If for any reason your search didn’t seem to work, a lot of Powershell scripts are available to help you with maintaining, updating and monitoring the health of your ElasticSearch instance.

Remark: Be sure to take the correct scripts for your version of Azure DevOps.

One of the scripts I use the most is the TriggerCollectionIndexing.ps1 script. This script allows you to reindex everything(wiki, workitem, code) at the collection level.

Remark: You have to run this script on a server that has the SQL Server Client Tools installed.

Let’s try it out:

PS N:\Azure_DevOps_Server_2019> .\TriggerCollectionIndexing.ps1

cmdlet TriggerCollectionIndexing.ps1 at command pipeline position 1

Supply values for the following parameters:

(Type !? for Help.)

SQLServerInstance: mytfssqlinstance

CollectionDatabaseName: tfs_defaultcollection

ConfigurationDatabaseName: tfs_configuration

CollectionName: DefaultCollection

EntityType: WorkItem

Cannot load module SQLSERVER. Trying to load SQLPS module.

Loaded SQLPS module...

Cleaned up the WorkItem Collection Indexing state.

Successfully queued the WorkItem Indexing job for the collection!!

Column1

-------

      1

In the example above, we triggered a reindex of the WorkItems in a specific collection You can do the same thing for Code or Wiki by changing the EntityType in the command above.

Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...
Read more