创建Jenkins Blue Ocean流水线时无Agent选项问题求助

Hey there! I’ve run into these exact hiccups when starting out with Blue Ocean, so let’s break down how to fix them step by step:

1. No Agent Options Available When Setting Up a Pipeline #

This is super common when you first spin up the Blue Ocean container—here’s what to check:

• Check the Built-in Master Node
  By default, Jenkins has a built-in "master" node that can act as an agent, but sometimes it’s not enabled. Head over to the main Jenkins dashboard (not Blue Ocean), go to Manage Jenkins > Manage Nodes and Clouds. Look for the "master" node—if it’s marked as offline, click into it and hit Launch agent to bring it online. Once it’s up, you’ll see it as an option in Blue Ocean.

• Configure Docker Cloud for Dynamic Agents
  Since you’re already mounting /var/run/docker.sock to the container, you can set up Jenkins to spin up Docker agents on demand:

  1. Go to Manage Jenkins > Manage Nodes and Clouds > Configure Clouds
  2. Click Add a new cloud and select Docker
  3. In the Docker Host URL field, enter unix:///var/run/docker.sock, then click Test Connection to confirm it works
  4. Add a Docker Agent Template: Name it something like "blueocean-agent", use an image like jenkins/inbound-agent (it’s lighter than the full Blue Ocean image), add a tag like docker, and save the configuration. Now when you get to the Agent selection step in Blue Ocean, this template will show up.

• Ensure Your Jenkinsfile Specifies an Agent
  If you’re using a Jenkinsfile (either from your repo or generated in Blue Ocean), make sure it includes an agent directive. For example:

  pipeline {
      agent any // Uses any available agent
      stages {
          stage('Build') {
              steps {
                  echo 'Building...'
              }
          }
      }
  }
  

  This tells Jenkins to automatically assign an agent without you having to select one manually.

2. Save Button Exception ("save &amp...") #

That weird &amp is probably a frontend rendering glitch—let’s fix this:

• Refresh & Clear Browser Cache
  First, try hard-refreshing the page (Ctrl+Shift+R or Cmd+Shift+R) or clearing your browser’s cache. Sometimes stale frontend assets cause button text to get messed up and functionality to break.

• Check Jenkins Logs for Errors
  If the issue persists, check the Jenkins container logs to see what’s going on. Run:

  docker logs <your-container-name-or-id>
  

  Look for errors related to permissions, GitHub token validation, or pipeline configuration. Since you ran the container as root, double-check that the jenkins-data volume has the right permissions—you can exec into the container with docker exec -it <container-id> bash and verify /var/jenkins_home is readable/writable.

• Verify All Required Fields Are Filled
  Make sure you’ve completed all mandatory steps: your GitHub token is correctly added, the repository URL is valid, and you’ve selected a branch. Missing required fields can prevent the save button from working as expected.

• Check Jenkinsfile Syntax
  If you’re using a custom Jenkinsfile, even a small syntax error can cause save failures. Use the Pipeline Syntax tool in Jenkins (under Manage Jenkins) to validate your script before saving.

内容的提问来源于stack exchange，提问作者Christopher Francisco