There's no minimally required duration for builds. They always show up no matter how long they took. When displayed in the calendar they're always big enough so that the name of the job can be displayed. Example:

My guess is that the problem is somewhere else. Some things to check:
1. See if the [Jenkins logfile](https://wiki.jenkins.io/display/JENKINS/Logging) shows any exceptions coming from the calendar-view plugin.
2. Create a List View where everything is configured the same as for the Calendar View. Does the job show up in the List View? (CalendarView is a subtype of ListView and inherits much of its behaviour. If a job doesn't display in ListView, its builds won't show up in CalendarView either).
3. Open /job/NAME_OF_YOUR_JOB/api/json in a browser. This should give information about the type of job we're talking about as well as its builds.
There's no minimally required duration for builds. They always show up no matter how long they took. When displayed in the calendar they're always big enough so that the name of the job can be displayed. Example:
My guess is that the problem is somewhere else. Some things to check:
1. See if the [Jenkins logfile](https://wiki.jenkins.io/display/JENKINS/Logging) shows any exceptions coming from the calendar-view plugin.
2. Create a List View where everything is configured the same as for the Calendar View. Does the job show up in the List View? (CalendarView is a subtype of ListView and inherits much of its behaviour. If a job doesn't display in ListView, its builds won't show up in CalendarView either).
3. Open /job/NAME_OF_YOUR_JOB/api/json in a browser. This should give information about the type of job we're talking about as well as its builds.