Multibranch pipeline: Jenkinsfile not found

I have been working with Windows-environments for more than 11 years so far and never really thought much  about case-sensitivity (PowerShell, cmd and other tools are case-agnostic, for example, Get-Verb or get-VerB both will work fine). However, today I faced with a little issue while configuring multibranch pipeline in Jenkins:

jenkins multibranch pipeline issue

I use the same paths for my jenkinsfile as for other pipelines (that are not multibranched) and that path is consisted of lowercase letters. In fact, if we open an explorer and check the path, my folder is named as “HelloWorld” plus other directories also have uppercase letters. And once I changed the script path to “HelloWorld/Scripts/Jenkinsfile“, the pipeline successfully checked all branches. The possible reason – multibranch pipelines are provided by completely different and apparently case-sensitive plugin. Looks like we should always use case-sensitive values for everything in order to avoid any strange issues. Ok. New rules, new habits 🙂

jenkins multibranch pipeline issue solution

Jenkins: there is no “Launch agent via Java Web Start” method

Jenkins uses a TCP port to communicate with agents launched via the JNLP protocol, such as Windows-based agents. As of Jenkins 2.0, by default this port is disabled. You need to verify that JNLP is enabled and TCP port is defined in the Global Security section.

Go to Manage Jenkins -> Configure Global Security, and then scroll down to Agents, define a static TCP port for JNLP agents (random ports making it difficult to manage firewall rules on agents hosts ’cause port is chosen during the boot of Jenkins master), click Save and get back to agent’s configuration (try to connect the agent to Jenkins by clicking the Launch button, and then verify that agent’s status is “Connected via JNLP agent”)

jenkins jnlp port