It sounds like a common scenario a lot of us face, especially when working with multi-service repositories! Based on what you’re describing, it seems like you need to specify both the context for your Docker build and the path to your Dockerfile in your Jenkins pipeline.

Yes, you’ll likely want to edit your Jenkinsfile manually. In your pipeline definition, you can use the docker.build command to specify the Dockerfile location. Here’s a simple example:

pipeline {
        agent any 
        stages {
            stage('Build') {
                steps {
                    script {
                        def customImage = docker.build("my-app-image", "-f path/to/your/Dockerfile path/to/context")
                    }
                }
            }
            stage('Deploy') {
                steps {
                    // your deploy steps here
                }
            }
        }
    }

In the code above, replace path/to/your/Dockerfile and path/to/context with the actual paths in your repository. The context is usually the directory where your application code for that service resides, and that’s where Docker will look for files when building the image.

If you’re using the Blue Ocean UI, you might not have an explicit field for that, so the manual way will definitely be cleaner and give you more control. As a tip, when dealing with multiple services, keeping Dockerfiles organized in their respective service folders can help a lot. Some people even have a dedicated docker directory at the root to keep things tidy.

When it comes to maintaining clarity, naming conventions can play a big role! Consistently naming your services and their corresponding Dockerfiles can make a big difference. And documenting your build process via comments in your Jenkinsfile can help keep everything straight.

Hope this helps clear up the confusion! Good luck with your pipeline setup!