Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

A wrong configuration of CasC yaml kills Jenkins startup

See original GitHub issue

Your checklist for this issue

🚨 Please review the guidelines for contributing to this repository.

Jenkins version 2.60.1, 2.164.1,2.165
Plugin version 2.20-snapshot, 2.19
OS Linux

Description

While testing the CasC plugin I’ve found that if the yaml is wrong, Jenkins stop restarting, leaving you with an unoperational instance.

Steps to reproduce:

Cre

ate a yaml with ssh credentials
Import this yaml
Remove credentials and ssh-credentials
Restart Jenkins

Expected: Some settings are established, others not.

Current behavior: Jenkins doesn’t start.

Also filed in Jira: https://issues.jenkins-ci.org/browse/JENKINS-57862

Issue Analytics

State:
Created 4 years ago
Reactions:3
Comments:10 (9 by maintainers)

Top GitHub Comments

8reactions

uhafnercommented, Jun 15, 2019

I think it makes sense to look at Jenkins core on how to handle errors in configuration files, maybe you can adapt that part of the code. If a config.xml is broken then we get nice error messages in the UI rather than a bricked instance.

1reaction

Smasherrcommented, Jun 12, 2019

I am with the AdministrativeMonitor-team.