How to restart jenkins

Running Pipelines

Running a Pipeline

Multibranch

Parameters

Restarting or Rerunning a Pipeline

There are a number of ways to rerun or restart a completed Pipeline.

Replay

Restart from a Stage

You can restart any completed Declarative Pipeline from any top-level stage which ran in that Pipeline. This allows you to rerun a Pipeline from a stage which failed due to transient or environmental considerations, for example. All inputs to the Pipeline will be the same. This includes SCM information, build parameters, and the contents of any stash step calls in the original Pipeline, if specified.

How to Use

No additional configuration is needed in the Jenkinsfile to allow you to restart stages in your Declarative Pipelines. This is an inherent part of Declarative Pipelines and is available automatically.

Restarting from the Classic UI

Once your Pipeline has completed, whether it succeeds or fails, you can go to the side panel for the run in the classic UI and click on «Restart from Stage».

Once you choose a stage to restart from and click submit, a new build, with a new build number, will be started. All stages before the selected stage will be skipped, and the Pipeline will start executing at the selected stage. From that point on, the Pipeline will run as normal.

Restarting from the Blue Ocean UI

Restarting stages can also be done in the Blue Ocean UI. Once your Pipeline has completed, whether it succeeds or fails, you can click on the node which represents the stage. You can then click on the Restart link for that stage.

Blue Ocean will not receive further functionality updates. Blue Ocean will continue to provide easy-to-use Pipeline visualization, but it will not be enhanced further. It will only receive selective updates for significant security issues or functional defects.

Alternative options for Pipeline visualization, such as the Pipeline: Stage View and Pipeline Graph View plugins, are available and offer some of the same functionality. While not complete replacements for Blue Ocean, contributions are encouraged from the community for continued development of these plugins.

Preserving `stash`es for Use with Restarted Stages

Normally, when you run the stash step in your Pipeline, the resulting stash of artifacts is cleared when the Pipeline completes, regardless of the result of the Pipeline. Since stash artifacts aren’t accessible outside of the Pipeline run that created them, this has not created any limitations on usage. But with Declarative stage restarting, you may want to be able to unstash artifacts from a stage which ran before the stage you’re restarting from.

To enable this, there is a job property that allows you to configure a maximum number of completed runs whose stash artifacts should be preserved for reuse in a restarted run. You can specify anywhere from 1 to 50 as the number of runs to preserve.

This job property can be configured in your Declarative Pipeline’s options section, as below:

When a Pipeline completes, it will check to see if any previously completed runs should have their stash artifacts cleared.

Scheduling jobs in Jenkins

The scheduling function lets you schedule jobs to run automatically during off-hours or down times. Scheduling jobs can help you to scale your environment as Jenkins usage increases. This video provides insight on the scheduling function and its various configuration options.

Как перезапустить Jenkins вручную

Я только начал работать с Дженкинсом и столкнулся с проблемой. После установки нескольких плагинов он сказал, что его нужно перезапустить и перешел в режим «выключения», но никогда не перезапускается.

Как сделать ручной перезапуск?

30 ответов

чтобы перезапустить Jenkins вручную, вы можете использовать любую из следующих команд (введя их URL в браузере):

Если вы установили как об / мин или деб, потом service jenkins restart будет работать также.

на Ubuntu или Debian, при установке через apt-get / dpkg :

на Плагин SafeRestart необходимо упомянуть. Это довольно полезно (Безопасно Перезапустить). Он добавляет ссылку, чтобы иметь возможность перезагрузки из главного меню:

приведенные ниже команды работали для меня в Red Hat Linux и также должен работать для Ubuntu.

чтобы узнать статус Дженкинса:

чтобы начать Дженкинс:

чтобы остановить Дженкинса:

чтобы перезапустить Jenkins:

демо в командной строке:

в Windows, Если вы установили его как службу, перейдите в службы (старт → выполнить: services.msc ), найти Дженкинса, щелкните правой кнопкой мыши → перезагрузка.

Если это не помогает (пользовательский интерфейс не отвечает) откройте Диспетчер задач Windows → процессы убейте java.exe process и перезапустите службу еще раз.

Если вы используете Jenkins в Mac OS X, вы можете вручную остановить службу, выполнив эту команду:

Это также можно сделать с помощью Дженкинс командной строки:

на вместе с полным списком команд можно ознакомиться по адресу:!—2—>.

это зависит от того, как Дженкинс был запущен.

), и возобновить его.

Если вы хотите просто обновить файл конфигурации, можно сделать

это быстрее, если вы сделали некоторые небольшие изменения в конфигурационный файл, как config.xml непосредственно в файловой системе, или копии задания через файловую систему (не через браузер).

Если вы запустите FreeBSD:

На Windows

перейдите к установке Jenkins, откройте cmd и запустите:

Если вы используете его как службу, войдите на свой сервер и выполните команду:

Для Mac

Остановить Дженкинс

Запустить Дженкинс

для перезапуска Дженкинса вручную с помощью браузера:

введите www.jenkins-ip/restart (например, http://localhost:8080/restart ) в браузере. Дженкинс перезапустится и загрузит страницу входа автоматически после перезагрузки.

несколько человек упомянули о необходимости перезапуска контейнера сервлета, если Jenkins не работает как автономный. Но Tomcat (или то, что используется) не нужно перезапускать. Tomcat может принудительно перезапустить контекст Дженкинса, если ваш перезапуск Дженкинса зависает.

но чтобы обратиться к другому комментарию, когда вы поместите Дженкинса в режим» выключения», он фактически не выключится. Он останавливает выполнение новых заданий и размещает гигантский красный баннер на системных страницах, чтобы все знает, что администратор хочет в конце концов снять его. Существуют плагины для запуска перезапуска контейнера сервлета для этого контекста после завершения всех сборок.

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

если он развернут как файл войны, перезапустите сервер приложений, например Tomcat.

How to Restart Jenkins Manually

Home » DevOps and Development » How to Restart Jenkins Manually

While working in Jenkins, users may be in a situation where they need to restart it manually. This can occur due to different reasons, such as troubleshooting issues or installing plugins. Luckily, Jenkins offers several methods to perform a manual restart.

In this tutorial, we will go through the different methods used to restart Jenkins manually.

Restart Jenkins via URL

If you are using the Jenkins dashboard in a web browser, restart Jenkins by entering the appropriate URL. Using the default restart URL forces Jenkins to restart without waiting for any builds to complete:

To complete all currently running jobs before the restart, use the safe restart option. New jobs will queue up and run after the restart is complete:

Both options require confirming the restart by clicking the Yes button:

The Jenkins URL contains the system’s hostname and the port Jenkins is running on (default port is 8080). If you are logging into the Jenkins dashboard on your system, use:

If you are logging in on another system, use:

Note: Check out our in-depth guide on how to change port for Jenkins in Windows, MacOS, and Linux.

Restart Jenkins via Safe Restart Plugin

The Safe Restart plugin for Jenkins allows you to perform a safe restart from the Jenkins dashboard.

1. To add the plugin, start by clicking the Manage Jenkins link on the left-hand side of the dashboard:

2. Under the System Configuration section, click the Manage Plugins button:

3. Under the Available tab, search for «safe restart» and check the box next to the Safe Restart plugin name.

4. Click the Install without restart button to add the plugin:

5. Once the plugin is installed, return to your dashboard. There is now a Restart Safely link on the left-hand side:

6. Clicking the link initiates a safe restart of Jenkins. You need to confirm the restart by clicking the Yes button:

Note: Find everything you need to know about using Jenkins in our Jenkins tutorial.

Restart Jenkins via CLI

Jenkins CLI (Command Line Interface) is a Java file that works as an extension of the local terminal shell. It allows you to use Java commands to manage Jenkins from a terminal window or command prompt.

2. Open the Jenkins dashboard in your web browser and click the Manage Jenkins link on the left-hand side.

3. Scroll down and click the Jenkins CLI button under the Tools and Actions section.

4. Download jenkins-cli.jar using the provided link.

Note: The Jenkins CLI page also offers an overview of the commands available for use.

5. Once the download is complete, open the terminal window or command prompt and use the following command syntax to restart Jenkins:

For instance, using the jenkins-cli.jar file in the Downloads folder on a Windows system:

How to Restart the Jenkins in Linux, Windows & Mac

Once installed, Jenkins runs as a background service. This means you can restart it with the same commands used to restart any other service.

Restart the Jenkins Service in Linux

On a Linux system, initiate a restart of the Jenkins service with:

Another method is to use:

Note: Using the second method may make the Jenkins service unreliable because it picks up the environment from the root user. In contrast, restarting the service using the systemctl command provides a blank environment.

Restart the Jenkins Service in Windows

Restart the Jenkins service in the Windows command prompt by using the net command to stop and then start the service:

Another method is to move to the Jenkins installation folder and restart jenkins.exe. For instance:

Restart the Jenkins Service in MacOS

To restart the Jenkins service in MacOS, stop the service and start it again using the launchctl command:

After reading this tutorial, you should be able to use one of the methods outlined above to restart Jenkins manually.

How to safe restart Jenkins?

I need to make some configuration changes on our Jenkins instance that will involve restarting Jenkins a couple of times. However, our developers are committing frequently enough that I haven’t seen Jenkins without jobs running in three days.

Is there a native way (either through the GUI or via command line) to safe-restart Jenkins? IE: wait for current jobs to finish before going down, and keep track of queued jobs to start once Jenkins comes back up.

I know there’s a plugin but in order to install it I need to restart Jenkins.

7 Answers 7

Here you can check Restart Jenkins when installation is complete and no jobs are running which should be fairly safe.

Visiting https://youjenkinsdomain/safeRestart will set it in the mode when it waits for jobs to stop and then restarts.

You can execute the safeRestart command using either the Jenkins Rest API ([jenkins_url]/safeRestart) or you can execute the command via the Jenkins CLI.

The general syntax is as follows (the design is similar to tools like svn/git):

NOTE: When running the safeRestart command, any jobs set to be executed during the restart will be queued up and executed when the server is back online. Make sure this does not cause any conflicts upon reboot!

Start/Stop and Restart Jenkins service on Windows

I have extracted zip file and installed Jenkins on Windows 7 successfully. Jenkins runs at http://localhost:8080/ well. I want to stop Jenkins service from console. How can I do that? What’s the way to start and restart through console/command line?

9 Answers 9

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

to stop:
jenkins.exe stop

to start:
jenkins.exe start

to restart:
jenkins.exe restart

To stop Jenkins Please avoid shutting down the Java process or the Windows service. These are not usual commands. Use those only if your Jenkins is causing problems.

Use Jenkins’ way to stop that protects from data loss.

where [command] can be any one of the following

Example: if my local PC is running Jenkins at port 8080, it will be

So by default you can open CMD and write

But if your port 8080 is already is in use,so you have to change the Jenkins port number, so for that open Jenkins folder in Program File and open Jenkins.XML file and change the port number such as 8088

Now Open CMD and write

To start Jenkins from command line

Go to the directory where your war file is placed and run the following command: