Jenkins an error occurred during installation no such plugin cloudbees folder - Исправление ошибок и поиск оптимальных решений проблем

I ran:

docker run -d --name=jenkins -p 8080:8080 -p 50000:50000 -v ~/jenkins:/var/jenkins_home jenkins

I got as far as the plugin config screen. Clicked on «Install selected plugins», got this error:

An error occurred during installation: No such plugin: cloudbees-folder

Only worked when I manually configured and deselected them all.

Docker version:

Client:
 Version:      1.13.0
 API version:  1.25
 Go version:   go1.7.3
 Git commit:   49bf474
 Built:        Tue Jan 17 09:58:26 2017
 OS/Arch:      linux/amd64

Server:
 Version:      1.13.0
 API version:  1.25 (minimum version 1.12)
 Go version:   go1.7.3
 Git commit:   49bf474
 Built:        Tue Jan 17 09:58:26 2017
 OS/Arch:      linux/amd64
 Experimental: false

Update: I removed the -v ~/jenkins:/var/jenkins_home and didn’t run into any problems. Seems to be a problem with mounting the jenkins_home as a volume.

I verified that ~/jenkins exists in my home directory, and it does.

well, it depends on what you have in ~/jenkins that is breaking the installation

MikeDX, rvernica, carlossg, WoodenGlaze, wheelerlaw, AlexanderStanciu, bldr-mobile-dev, zhuke945, Mowgly777, shuixiya1999, and 3 more reacted with thumbs down emoji

@carlossg There’s nothing in it, it’s a new folder created for the purpose of starting the container. It should not be erroring.

I ran into the same problem after installing Jenkins in Windows (not in Docker), and in my case I got the same error with another plugin after I deselected cloudbees. Shutting down Jenkins and restarting it fixed the issue and plugins installed fine.

hmhka, EmoBurrito, yidazh, zia, mostafazs, zivu, arielmorry, chen-chao, lalozouter, jahodogit, and 5 more reacted with thumbs up emoji
resotto and anhduy97a6 reacted with thumbs down emoji

I ran into this error as well with jenkins:2.32.3-alpine and without mounting any volume on Linux.

In my case the issue was the http proxy was not set.

I could see the following warning:

ci_1     | Mar 21, 2017 11:54:14 AM hudson.model.UpdateCenter updateDefaultSite
ci_1     | WARNING: Upgrading Jenkins. Failed to update the default Update Site 'default'. Plugin upgrades may fail.
ci_1     | net.sf.json.JSONException: Unquotted string 'h1'
ci_1     | 	at net.sf.json.util.JSONTokener.nextValue(JSONTokener.java:432)
ci_1     | 	at net.sf.json.JSONObject._fromJSONTokener(JSONObject.java:955)
ci_1     | 	at net.sf.json.JSONObject._fromString(JSONObject.java:1145)
ci_1     | 	at net.sf.json.JSONObject.fromObject(JSONObject.java:162)
ci_1     | 	at net.sf.json.JSONObject.fromObject(JSONObject.java:132)
ci_1     | 	at hudson.model.UpdateSite.updateData(UpdateSite.java:206)
ci_1     | 	at hudson.model.UpdateSite.updateDirectlyNow(UpdateSite.java:190)
ci_1     | 	at hudson.model.UpdateCenter.updateDefaultSite(UpdateCenter.java:2193)
ci_1     | 	at jenkins.install.SetupWizard.init(SetupWizard.java:168)
ci_1     | 	at jenkins.install.InstallState$3.initializeState(InstallState.java:105)
ci_1     | 	at jenkins.model.Jenkins.setInstallState(Jenkins.java:1057)
ci_1     | 	at jenkins.install.InstallUtil.proceedToNextStateFrom(InstallUtil.java:96)
ci_1     | 	at jenkins.model.Jenkins.<init>(Jenkins.java:947)
ci_1     | 	at hudson.model.Hudson.<init>(Hudson.java:85)
ci_1     | 	at hudson.model.Hudson.<init>(Hudson.java:81)
ci_1     | 	at hudson.WebAppMain$3.run(WebAppMain.java:231)

The solution was to set the proxy in JAVA_OPTS:

JAVA_OPTS=-Dhttp.proxyHost=${proxy_host} -Dhttp.proxyPort=${proxy_port} -Dhttps.proxyHost=${proxy_host} -Dhttps.proxyPort=${proxy_port}

I had the same error.
The origin of the problem was the JVM (java -version was java 7).
Once switched to Java 8 (.bash_profile), everything was resolved.

@wheelerlaw if you are saying that this command fails

docker run -d --name=jenkins -p 8080:8080 -p 50000:50000 -v ~/jenkins:/var/jenkins_home jenkins

and this command succeeds

docker run -d --name=jenkins -p 8080:8080 -p 50000:50000 jenkins

then it boils down to what permissions or content your ~/jenkins dir has. Have you checked the logs of jenkins for errors ?

TasminAfroz, avishekroy63, GlennSeymon, chrisdawguj, mostafazs, PronomitaDey, mmyoji, willmeierart, programmingwheels, mitjaresek, and 17 more reacted with thumbs up emoji
abhishekbhakat, NTtanh, and wuchuheng reacted with thumbs down emoji
avijju, Benstaar, Kennytian, ruslanyussupov, and jaderbittencourt reacted with hooray emoji

Restart worked here as well (in osx)

CameronHudson8, chacles, sakmon, konghuachao001, YeQuan94, athondapu, smithyj, ytianzaishui, NetanelAvrhami, traw, and 5 more reacted with thumbs up emoji

Changing this line
JAVA_CMD=»$JENKINS_JAVA_CMD $JENKINS_JAVA_OPTIONS -DJENKINS_HOME=$JENKINS_HOME -jar $JENKINS_WAR»
to
JAVA_CMD=»$JENKINS_JAVA_CMD -Dhudson.model.DownloadService.noSignatureCheck=true $JENKINS_JAVA_OPTIONS -DJENKINS_HOME=$JENKINS_HOME -jar $JENKINS_WAR»

in /etc/init.d/jenkins
should fix the problem…
worked on fedora 28

Please check the NTP. If the system runs with incorrect time, this error could occur.

I met the config error after I ran the command docker run -u root --restart always -d -p 8090:8080 --name jenkins -p 50000:50000 -v jenkins-data:/var/jenkins_home -v /var/run/docker.sock:/var/run/docker.sock jenkinsci/blueocean serveral times when I was fixing docker network problem. I think there’s must be something wrong with the directries in the volume.

So I delete volume jenkins-data through docker. And the error disappeared.

This did the trick for me, ty!

it works for me

I set the JAVA_HOME in ~/.bash_profile like export JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.8.0_192.jdk/Contents/Home works

I faced the same issue while installing plugins in my docker container, it turned out to be a proxy issue. Changed proxy settings on my docker and it worked

restart is not work in mac.

Restart is not working on window 10…what should I do??

modify /var/lib/docker/volumes/jenkins-data/_data/hudson.model.UpdateCenter.xml from https->http fix the problem

It work for me!
System Environment: centos 8
jenkins installation method:
wget http://pkg.jenkins-ci.org/redhat-stable/jenkins-2.7.3-1.1.noarch.rpm
rpm -ivh jenkins-2.7.3-1.1.noarch.rpm

worked for me , centos8

Hi Bros,
I also have the same issue, please help me. thanks,
* cat docker-compose.yml
version: ‘3’
services:
jenkins:
container_name: jenkins
image: jenkins:2.60.3
ports:
— «8080:8080»
— «50000:50000»

command run: docker-compose up -d
OS: «Ubuntu 20.04.3 LTS (Focal Fossa)»

jenkinsci

locked as spam and limited conversation to collaborators

Dec 6, 2021

Источник

An error occurred during installation: No such plugin: cloudbees-folder (While installing Jenkins suggested plugins getting the error on windows 10)

Henry

42.6k7 gold badges63 silver badges79 bronze badges

asked Nov 19, 2018 at 7:02

For Windows users, restarting the Jenkins service will resolve the issue.

For that Open Task Manager (Ctrl+Sft+Esc) -> Services -> right-click on Jenkins service and choose the option restart

answered May 18, 2020 at 17:25

Jinu P CJinu P C

3,02620 silver badges28 bronze badges

If you are using the Jenkin’s image in Docker if you see this error just try to execute the below command:
http://localhost:8080/safeRestart
you will get a prompt do you need to restart don’t click on yes just ignore then start creating your jobs by clicking on NEW, it’s just a plugin

answered May 31, 2021 at 5:41

nizamnizam

211 bronze badge

For the docker version

1-open the browser

2- write your_ip_address:your_docker_port/restart

Note: you must have the password generated by your Jenkins server
if you do have click here

answered Jul 23, 2021 at 14:51

As a comment suggested: always look for official images mentioned here jenkins.io/download.

I faced the same issue when using the docker image jenkins:2.60.3, it turned out that this image isn’t an official one, the official images look like jenkins/jenkins:<something>, you can find them here: https://hub.docker.com/r/jenkins/jenkins

answered Dec 29, 2021 at 9:11

If you are behind a firewall (local or through a VPN), there’s a good chance that it’s failing to download files correctly.

Try installing from another location or disabling the VPN.
Or request your network admin to allow the connections.

When I initially started my server while on a VPN there were two connection failure stack traces.

answered Jan 14, 2020 at 18:47

ScrappyDevScrappyDev

2,0998 gold badges38 silver badges56 bronze badges

I am running Jenkins on Ubuntu in AWS.

I had this initial problem after booting up the box.

Ran the following:

sudo service jenkins restart

All working for me now.

answered Apr 6, 2020 at 11:59

I just Unchecked all the plugins and clicked on the install button. After that, it successfully takes me to the inside.

answered Nov 19, 2018 at 8:30

nareshnaresh

791 gold badge1 silver badge4 bronze badges

Just restart the machine. It successfully worked for me.

answered Apr 23, 2021 at 0:23

Источник

Содержание

«An error occurred during installation: No such plugin: cloudbees-folder» #424
Comments
Hi Bros, I also have the same issue, please help me. thanks, ************* cat docker-compose.yml************ version: ‘3’ services: jenkins: container_name: jenkins image: jenkins:2.60.3 ports: — «8080:8080» — «50000:50000»
Footer
Невозможно настроить Jenkins (Cloudbees)
2 ответа
Произошла ошибка при установке: Нет такого плагина: cloudbees-folder
DevOps2.1: Jenkins CI/CD #2
Comments
A note to Windows users

«An error occurred during installation: No such plugin: cloudbees-folder» #424

I got as far as the plugin config screen. Clicked on «Install selected plugins», got this error:

Only worked when I manually configured and deselected them all.

The text was updated successfully, but these errors were encountered:

Update: I removed the -v

/jenkins:/var/jenkins_home and didn’t run into any problems. Seems to be a problem with mounting the jenkins_home as a volume.

I verified that

/jenkins exists in my home directory, and it does.

well, it depends on what you have in

/jenkins that is breaking the installation

@carlossg There’s nothing in it, it’s a new folder created for the purpose of starting the container. It should not be erroring.

I ran into this error as well with jenkins:2.32.3-alpine and without mounting any volume on Linux.

In my case the issue was the http proxy was not set.

I could see the following warning:

The solution was to set the proxy in JAVA_OPTS :

I had the same error.
The origin of the problem was the JVM (java -version was java 7).
Once switched to Java 8 (.bash_profile), everything was resolved.

@wheelerlaw if you are saying that this command fails

and this command succeeds

then it boils down to what permissions or content your

/jenkins dir has. Have you checked the logs of jenkins for errors ?

This work for me:
http://localhost:8080/restart
OR
service jenkins restart on Ubuntu 16.04

@techyaura : thanks, restart works for me.

Restart worked here as well (in osx)

http://localhost:8080/restart worked on blueocean running in docker container running on Mac .

Restart jenkins worked!

in /etc/init.d/jenkins
should fix the problem.
worked on fedora 28

Same problem with Mac

Please check the NTP. If the system runs with incorrect time, this error could occur.

I met the config error after I ran the command docker run -u root —restart always -d -p 8090:8080 —name jenkins -p 50000:50000 -v jenkins-data:/var/jenkins_home -v /var/run/docker.sock:/var/run/docker.sock jenkinsci/blueocean serveral times when I was fixing docker network problem. I think there’s must be something wrong with the directries in the volume.

So I delete volume jenkins-data through docker. And the error disappeared.

in /etc/init.d/jenkins
should fix the problem.
worked on fedora 28

This did the trick for me, ty!

/jenkins:/var/jenkins_home and didn’t run into any problems. Seems to be a problem with mounting the jenkins_home as a volume.

I verified that

/jenkins exists in my home directory, and it does.

it works for me

I set the JAVA_HOME in

/.bash_profile like export JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.8.0_192.jdk/Contents/Home works

I faced the same issue while installing plugins in my docker container, it turned out to be a proxy issue. Changed proxy settings on my docker and it worked

restart worked for me.

restart is not work in mac.

Restart is not working on window 10. what should I do??

modify /var/lib/docker/volumes/jenkins-data/_data/hudson.model.UpdateCenter.xml from https->http fix the problem

in /etc/init.d/jenkins
should fix the problem.
worked on fedora 28

It work for me!
System Environment: centos 8
jenkins installation method:
wget http://pkg.jenkins-ci.org/redhat-stable/jenkins-2.7.3-1.1.noarch.rpm
rpm -ivh jenkins-2.7.3-1.1.noarch.rpm

in /etc/init.d/jenkins
should fix the problem.
worked on fedora 28

worked for me , centos8

Hi Bros,
I also have the same issue, please help me. thanks,
* cat docker-compose.yml
version: ‘3’
services:
jenkins:
container_name: jenkins
image: jenkins:2.60.3
ports:
— «8080:8080»
— «50000:50000»

command run: docker-compose up -d
OS: «Ubuntu 20.04.3 LTS (Focal Fossa)»

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Невозможно настроить Jenkins (Cloudbees)

Я пытаюсь установить Jenkins на моем сервере Tomcat 9. Я скачал файл войны и получил его развернутым. Это дало много шума на консоли, но на этом этапе я новичок в Дженкинс, поэтому не знаю, ошибки они или что-то ожидаемое. Мой Tomcat настроен на использование порта SSL (8443). Я развернул Jenkins и открыл Jenkins, но после выбора стандартных плагинов я получаю сообщение об ошибке:

Единственное изменение, которое я сделал до этого, было в hudson.model.UpdateCenter.xml , изменил URL с:

2 ответа

Ах, это оказалось проблемой прокси! Так как я был в моей сети офиса. То, что я сделал, было:

Удалите папку Jenkins из папки веб-приложений Tomcat.
Удалите все папки, связанные с Jenkins.
Затем снова разверните Jenkins.war.
На этот раз при запуске Jenkins я получил сообщение об ошибке «Кажется, что Jenkins не в сети» или что-то в этих строках, а также возможность настроить прокси, что я и сделал, и установил все плагины без каких-либо проблем!

Спасибо за помощь!

Я пробовал с обоими URL-адресами, это работает для меня. может быть, вы можете попробовать выполнить обновление из пользовательского интерфейса Jenkins. Идти к Управление Jenkins -> Управление плагинами -> Дополнительно
Вы можете увидеть поле «Обновить сайт» и проверить, обновлен ли ваш URL-адрес, вы можете легко изменить URL-адрес отсюда, а также можете нажать кнопку «Проверить сейчас», чтобы получить информацию об обновлении.

Источник

Произошла ошибка при установке: Нет такого плагина: cloudbees-folder

Во время установки произошла ошибка: такого плагина нет: папка cloudbees (при установке Jenkins предложил плагины, получающие ошибку в Windows 10)

ИЛИ service jenkins restart на моем Ubuntu

Для пользователей Windows перезапуск службы Jenkins решит проблему.

Для этой открытой Task Manager (Ctrl+Sft+Esc) -> Services -> right-click on Jenkins службы выберите вариант перезагрузки.

Если вы используете образ Jenkin в Docker, если вы видите эту ошибку, просто попробуйте выполнить следующую команду: http://localhost:8080/safeRestart вы получите приглашение, вам нужно перезапустить, не нажимайте «да», просто игнорируйте, затем начните создавать свои рабочие места, нажав NEW, это просто плагин

Для докер версии

2- написать your_ip_address:your_docker_port/restart

Примечание: у вас должен быть пароль, сгенерированный вашим сервером Jenkins, если у вас есть нажмите здесь

Я просто снял все плагины и нажал кнопку установки. После этого он успешно ведет меня внутрь.

Если вы находитесь за брандмауэром (локальным или через VPN), есть большая вероятность, что он не сможет правильно загрузить файлы.

Попробуйте установить из другого места или отключить VPN. Или попросите администратора сети разрешить подключения.

Когда я впервые запустил свой сервер в VPN, было две трассировки стека сбоев соединения.

Я запускаю Jenkins на Ubuntu в AWS.

У меня была эта первоначальная проблема после загрузки коробки.

Все работает у меня сейчас.

Проверьте контекстный путь в tomcat для Jenkins, который вы указали во время развертывания, а затем перезапустите/safeRestart с этого пути.

Например: путь на приведенном ниже снимке экрана — «/jenkins», поэтому URL-адрес перезапуска будет

Источник

DevOps2.1: Jenkins CI/CD #2

I’m following along with the leanpub DevOps2.1 Toolkit. So far so good, but now the Jenkins CI/CD setup is proving difficult. With the swarm running:

.
docker service ps jenkins reports an error for the service («invalid bind mount source, source path not found. «). However, the directory $PWD/docker/jenkins exists on local host.

I find a reference to this issue here: https://github.com/docker/docker/issues/25912. Still I can’t resolve it.

Feels like I’m missing something obvious. Any help greatly appreciated. Thanks for sharing your work.

The text was updated successfully, but these errors were encountered:

The command you posted should not be necessary in most cases. Which OS are you using (Windows, OSX, Linux)?

I’m using Ubuntu 16.04. I just deleted the command I posted in my reply, because I couldn’t replicate the result. For posterity, it was docker-machine ssh swarm-1 «mkdir -p docker/jenkins» .

Docker Machine mounts user’s directory from the host inside the VMs it creates. That allows us to share the files. However, that feature does not work in Docker Machine running on Linux. The easiest workaround is, for now, to remove the —mount argument. Later on, when we reach persistent storage, you’ll see how to mount volumes more effectively.

The good news is that the problem will be fixed soon. Please see the issue #1376 for the discussion. Once the pull request #2122 is merged, you will be able to use automatic mounting on Linux.

Awesome! Thank you so so much. Love the books.

Seems that docker/machine#2122 is merged. Can you try it out and let me know if it works?

I was able to work around this by creating a host mount in VirtualBox, auto-mounting it to «jenkins-agent «-labelled nodes at the time of swarm creation and finally mounting to Compose-created containers with the usual volume mount syntax.

I’ll take the more direct approach when I find some free time and report back.

I have the same issue as above and I’m unable to mount the drive. I even skipped the same step in the previous chapter.
I’m using Windows 10 and Docker ToolBox.
I have attached my screen grab and also the command I ran

docker service create —name jenkins -p 8082:8080 -p 50000:50000 -e JENKINS_OPTS=»—prefix=/jenkins» —mount «type=bind,source=/c/Users/rames/cloud-provisioning/docker/jenkins,target=/var/jenkins_home» —reserve-memory 300m jenkins:2.7.4-alpine

@rpchili Can you create Jenkins from a VM? That would be only a workaround until I figure out the cause of the problem.

@vfarcic So, create jenkins from a VM and then follow the book??

@rpchili Yes. That should (probably) avoid any problems cause by Windows.

@rpchili Actually, now when I look at it again, running it from a VM will probably not fix the problem. I’ll try to replicate it tomorrow and get back to you. If I do not manage to reproduce the same situation, I’ll ask you for a chat session with screen sharing so that we can try to solve it together. Would that be OK?

That would be extremely helpful. Thank You.

@vfarcic Any luck with the issue? I cannot get past it. I’m Sorry to bother you again.

@rpchili First of all, sorry for the late reply.

I managed to reproduce the problem and found the fix. Actually, the fix is in the book if you have a version from a few weeks ago (or newer). The comment is directly above the command that creates the service.

A note to Windows users

Git Bash has a habit of altering file system paths. To stop this, execute the following before running the code block.

Can you please remove the service, export the env. var and create the service again?

Please let me know if that fixed the problem.

Also, it would be useful to know where you both the book (LeanPub.com or Amazon.com) and whether it’s paperback or eBook. In case it’s paperback, please join http://slack.devops20toolkit.com and contact me on the private channel and I’ll send you the latest eBook version (you’ll also receive updates whenever I make them).

Thank you for your response. Unfortunately I still have the same issue

Do you think I should ssh into swarm-1 machine and mount the drive first as you suggested in the previous chapter?

Can you join http://slack.devops20toolkit.com/ and ping me there? We can take a look at it together. Windows is not one of my strong skills but I’m sure that we’ll find a solution together.

Can I join in 30min? Will you be available?

Thank You. See you soon

Using export MSYS_NO_PATHCONV=1 fixes mounting on Windows.

The problem @rpchili experienced is different than the original issue so I’m closing this ticket.

Please reopen if you experience a problem with mounting a volume on Windows after using the export command

I have the same problem on latest Mac OSX.

Can’t seem to find the docker/jenkins folder used as source?

Any idea what I could be missing?

bind : Paths on the host that get mounted into the container. Paths must exist prior to creating the container. If you want docker to create a path for you, then use a volume .

I thought I had created the dir via mkdir -p but somehow missed it. Make sure the folder is there.

Then it will run:
xkncxntyy82b jenkins.1 jenkins:2.7.4-alpine swarm-2 Running Running about a minute ago

and open «http://$(dm ip swarm-1):8082/jenkins» will open up jenkins Getting started/Unlock screen:

Where password should be found in: cat docker/jenkins/secrets/initialAdminPassword (relative to /cloud-provisioning root)

Clicking install suggested plugins I get: An error occurred during installation: No such plugin: cloudbees-folder Ooops! Tricky.

Best to remove all swarm nodes and start over with the folders in place

Yup, a fresh restart of the swarm and the jenkins server worked!

Now use the new generated initial password and the plugins should install just fine 🙂

A fresh restart of the whole swarm is necessary? How does one restart an entire swarm efficiently?

Try the gists The jenkins gist worked for me.

Try docker service rm or using a for loop to remove all nodes in a swarm, sth like:

Not sure if there is a better way?

(Windows) I am following along in the book and could not get the mount to work under PowerShell or Git bash. May be related to the comments above regarding the directory had to exist. I was using command on page 80.

docker service create —name registry -p 5000:5000 —reserve-memory 100m —mount «type=bind,source=/var,target=/var/lib/registry» registry:2.5.0

and when running ‘docker service ps registry’, I would get error message «invalid mount config for type…» for the service.

If I specified a known directory in the docker machine, it would work..

$docker service create —name registry -p 5000:5000 —reserve-memory 100m —mount «type=bind,source=/var,target=/var/lib/registry» registry:2.5.0

Is the problem that the $PWD is being evaluated in the context of my local GitBash, but then attempted to be applied to my docker machine, where the directory does not exist?

Источник

docker run -u root -itd -p 8080:8080 -p 50000:50000 -v /var/jenkins_home:/var/jenkins_home -v /var/run/docker.sock:/var/run/docker.sock --name jenkins-master jenkinsci/blueocean

When I start a Jenkins container through the image for the first time, when I access the server’s public network ip: 8080 and choose to install the recommended plugin when accessing the Jenkins web interface

Error: An error occurred during the installation process: No such plugin: cloudbees-folder

This is because the cloudbees-folderplugin , we can download it: cloudbees-folder download address

After downloading, we will get the cloudbees-folder.hpifile , then we just need to copy it to the plugin directory of Jenkins The location of the plugin directory is in the host directory /war/WEB-INF/detached-plugins that was mounted when we started the Jenkins container:

here:/var/jenkins_home/war/WEB-INF/detached-plugins

We can use the scpcommand to copy, note that the user name, ip address, and copy path here should be replaced with the corresponding information of our own server!

scp cloudbees-folder.hpi [email protected]:/var/jenkins_home/war/WEB-INF/detached-plugins

Then it can be seen in the Jenkins plugin directory cloudbees-folder.hpi

and we restart the container

[[email protected] ~]# docker ps
CONTAINER ID   IMAGE                 COMMAND                  CREATED             STATUS         PORTS                                                                                      NAMES
34326090ece5   jenkinsci/blueocean   "/sbin/tini -- /usr/…"   About an hour ago   Up 5 minutes   0.0.0.0:8080->8080/tcp, :::8080->8080/tcp, 0.0.0.0:50000->50000/tcp, :::50000->50000/tcp   jenkins-master
[[email protected] ~]# docker restart 34326090ece5
34326090ece5

Then visit the public network ip: 8080 again, the following interface may appear at this time, we will wait a moment, it will automatically refresh

and then enter the login interface again, we enter the password as above to log in again and choose to install the recommended plugin. success

Источник

Hi Bros, I also have the same issue, please help me. thanks, ************* cat docker-compose.yml************ version: ‘3’ services: jenkins: container_name: jenkins image: jenkins:2.60.3 ports: — «8080:8080» — «50000:50000»

«An error occurred during installation: No such plugin: cloudbees-folder» #424

Hi Bros, I also have the same issue, please help me. thanks, ************* cat docker-compose.yml************ version: ‘3’ services: jenkins: container_name: jenkins image: jenkins:2.60.3 ports: — «8080:8080» — «50000:50000»

Невозможно настроить Jenkins (Cloudbees)

2 ответа

Произошла ошибка при установке: Нет такого плагина: cloudbees-folder

DevOps2.1: Jenkins CI/CD #2

A note to Windows users

Читайте также:

Hi Bros,
I also have the same issue, please help me. thanks,
* cat docker-compose.yml
version: ‘3’
services:
jenkins:
container_name: jenkins
image: jenkins:2.60.3
ports:
— «8080:8080»
— «50000:50000»

Hi Bros,
I also have the same issue, please help me. thanks,
* cat docker-compose.yml
version: ‘3’
services:
jenkins:
container_name: jenkins
image: jenkins:2.60.3
ports:
— «8080:8080»
— «50000:50000»