|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [JIRA] (JENKINS-14032) No jobs showi... [email protected] (JIRA)
- [JIRA] (JENKINS-14032) No jobs ... [email protected] (JIRA)
- [JIRA] (JENKINS-14032) No jobs ... [email protected] (JIRA)
- [JIRA] (JENKINS-14032) No jobs ... [email protected] (JIRA)
- [JIRA] (JENKINS-14032) No jobs ... [email protected] (JIRA)
- [JIRA] (JENKINS-14032) No jobs ... [email protected] (JIRA)

Hi,
First step would be to look for startup errors in the Jenkins logs. You should be able to see this from the "All Jenkins Logs" thing immediately after startup. For details how to access the logs from the web admin interface see
https://wiki.jenkins-ci.org/display/JENKINS/Logging
When you find the error a little bit of Google searching may help to identify the problem/solution but do update this report with relevant log entries/findings.