{"push_id":714572401,"size":2,"distinct_size":2,"ref":"refs/heads/development","head":"4cb8f4c9641fb431bda5cc6e5a6efeee8fb1e331","before":"aa1d164b619492dc435343f53dcb8ff212fbe43d","commits":[{"sha":"e60fce879b9fa7eab22767ef2b83271a3a9e0c6f","author":{"email":"67b24c01a161b227e9c963705b840eabb84aa5fc@gmail.com","name":"Noah Lorang"},"message":"Fix next execution time on non-scheduled cluster member\n\ntrigger.getNextFireTime() returns null if the trigger hasn't been added to a schedule (or more\nprecisely, if the start time hasn't been set yet). This meant that in a clustered rundeck installation,\nthe non-scheduled cluster member would show jobs as being scheduled \"never\". Using trigger.getFireTimeAfter()\nwill properly calculate the next execution","distinct":true,"url":"https://api.github.com/repos/rundeck/rundeck/commits/e60fce879b9fa7eab22767ef2b83271a3a9e0c6f"},{"sha":"4cb8f4c9641fb431bda5cc6e5a6efeee8fb1e331","author":{"email":"4757c2725c0ad867bf62aa1b563f5ff6d0b9b4ee@gmail.com","name":"Greg Schueler"},"message":"Merge pull request #1280 from noahhl/development\n\nFix next execution time on non-scheduled cluster member","distinct":true,"url":"https://api.github.com/repos/rundeck/rundeck/commits/4cb8f4c9641fb431bda5cc6e5a6efeee8fb1e331"}]}