Hi, thanx for your hints. The node´s URL is already URL /manage/computer/(built-in)/ - but it´s still showing up as "master".
I read about the migration button, but it looks like someone has disabled this action in URL/jenkins/manage/ under " *Administrative monitors configuration*" After enabling all administrative warnings and applying the update, everything was fine...... Things could get complicated if there´s too much to be configured :-) Best regards, Torsten db...@cloudbees.com schrieb am Dienstag, 30. Mai 2023 um 11:28:14 UTC+2: > On Tue, May 30, 2023 at 11:04 AM Torsten Reinhard <tosc...@gmail.com> > wrote: > >> I´m wondering why I´m still seeing >> "master" in the list of all nodes at >> https://...../jenkins/manage/computer/ >> > > Weird. Is that node's URL /manage/computer/(master)/ (i.e, with the > parentheses)? If not, that's an agent with the name 'master'. Check whether > a node exists that is called "Built-In Node". It may have 0 executors, > which would explain why no builds are starting. > > >> What step needs to be performed, so everything is properly switched to >> "built-in" instead of "master"? >> > > Migration needs to be triggered manually, an admin message will be shown > on /manage for this. Did you follow the steps at > https://www.jenkins.io/doc/upgrade-guide/2.319/#migration ? > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/a2ea36a2-af55-49df-9a94-9e70a4464307n%40googlegroups.com.
