Build History Missing in Jenkins
I just set up a new Jenkins instance for my project (Version 2.19.4). But when I try to generate several builds for testing I find that the Build History only shows me one historical build.
Before upgrading, it showed at least two or more. Is there a place in Jenkins I can set the number of historical builds which should show up?
Solution
In the job configuration page, you can set the number of historic builds to maintain in the history. You've probably got it set to 0. If you have admin rights on that job, you should be able to change that.
- From which branch is the Jenkinsfile loaded
- Docker cloud agent - Can I use local image instead of publishing to Docker hub
- Terraform version error when deploying to AWS through jenkins?
- Sonarqube: Missing blame information for the following files
- jenkins pipeline not complete after npm start
- Jenkins pipeline trigger build on code changes from specific branch
- Jenkins groovy postbuild alternative
- Running Selenium in headless mode via Linux causes errors
- Jenkins build agent docker specify docker file name
- Suppress Scripted Pipelines Output in Jenkins
- How do I list all of my Jenkins credentials in the script console?
- Jenkins Host key verification failed
- Attach Volume EFS in ECS
- Git Plugin for Jenkins Fails to Connect to Repository
- Flutter Jenkins flutter not found issue
- How to add a file I create in groovy in Jenkinsfile to the artifacts?
- Jenkins sudo: a terminal is required to read the password
- how to disable jenkins pipeline job
- Jenkins active choices from the cli
- Jenkins slave and Maven Project
- Failed to connect to repository : Error performing git command: git ls-remote -h ***public github url *** HEAD
- Continue Build on Jenkins when JUnit stage fails
- Jenkins: Using external scripts vs coding the job in Groovy
- Jenkins in-process script approval
- How to get Jenkins lockable resources parameters with matrix plugin
- How to deploy war file to Tomcat from Jenkins without using plugin
- Managing artifacts locally
- Jenkins timeout/abort exception
- Jenkins run sh in remote docker agent stuck
- Is there any way for QA to do the feature testing before each feature merged to sacred branches?