I upgraded the Jenkins war file from 2.252.1 to 2.452.4. I logged into the Jenkins console it shows nothing, all pipelines, jobs, and build history are missing. I tried with backup config.xml and still no luck. Most of the plugins are up to date. What’s wrong? It never happened before.
The Jenkins log file will usually tell you what is wrong.
If Jenkins is running, then it is available from “Manage Jenkins” → “System log”.
If Jenkins is not running, then you’ll need to locate the log file on the file system. The Jenkins documentation will guide you to find the logs on your installation.
There is also a video from Darin Pope that may help:
Sorry. I already checked before I posted.
It only says, Loaded all jobs; Configuration for all jobs updated; Completed initialization; Jenkins is fully up and running.
I don’t see any error or any clue.
Maybe something in your upgrade steps inadvertently changed the location of the Jenkins home directory?
Not really. It only takes minutes to stop Jenkins service, rename the old war, upload the new war, and start the service. I never had this issue before.
If you installed with a Linux package manager, you should upgrade with the Linux package manager. I doubt that will change this case, but it is the only suggestion I have to offer.
I generally download the rpm, extract the war, upload to S3 and copy the war from S3 location.
Just throwing an idea here. Create a new job from the UI, call it a very unique name such as ‘my-brand-new-job’, then go to your filesystem check if it shows up under your jobs folder. If not find . my-brand-new-job and try to locate it.
I’m just guessing that somehow you got your jenkins home directory to move somewhere else, as @MarkEWaite suggested in his second reply.
By the way under “Manage Jenkins / System” (or the /manage/configure url), the home directory is the very first entry. On our instances it is /var/jenkins_home.
Once you confirm the folder has not changed, check the permissions and the the folders and files are owned by the same user that is running the controller’s java process.