Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-67650

"Master" -> "Built-in" migration has no effect

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • core

      After migration, no difference in node naming and when declaring to run on "built-in" node in pipelines, it waits for ever.

      In the first migration run, the master node had the label "built-in". Could this be the cause?

      I have tried two additional migrations (shut Jenkins down, set <nodeRenameMigrationNeeded>true</nodeRenameMigrationNeeded> in config.xml, start Jenkins, migrate again) without the label on master, stopping all builds before, but no difference.

      I see no error in the Jenkins log during the migration. There is no log entry for the migration at all with loglevel INFO or higher.

          [JENKINS-67650] "Master" -> "Built-in" migration has no effect

          Daniel Beck added a comment -

          The "migration" is simply an internal flag that changes what the built-in node declares to be its "self label", i.e. a label based on the node name. As an example, your agent "a1" has the self label "a1", the built-in node had the self label "master" and now has the self label "built-in". That's it.

          Jobs aren't reconfigured or similar (which is why it's opt in – Jenkins won't be able to edit Jenkinsfiles in SCM).

          Note that there need to be executors configured for the built-in node for this to matter. Care needs to be taken to not accidentally cause security issues when doing that, see the first half of https://www.jenkins.io/doc/book/security/controller-isolation/

          Daniel Beck added a comment - The "migration" is simply an internal flag that changes what the built-in node declares to be its "self label", i.e. a label based on the node name. As an example, your agent "a1" has the self label "a1", the built-in node had the self label "master" and now has the self label "built-in". That's it. Jobs aren't reconfigured or similar (which is why it's opt in – Jenkins won't be able to edit Jenkinsfiles in SCM). Note that there need to be executors configured for the built-in node for this to matter. Care needs to be taken to not accidentally cause security issues when doing that, see the first half of https://www.jenkins.io/doc/book/security/controller-isolation/

            Unassigned Unassigned
            dominikkv Dominik Vorreiter
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: