alphagov / backdrop / 2151

Builds Branch Commit Type Ran Committer Via Coverage
2151 feature/dry-auth-checks Extract common checks to decorator push jabley travis-ci pending completion   set done
2150 feature/dry-auth-checks Extract common checks to decorator push jabley travis-ci pending completion   set done
2149 feature/dry-auth-checks Extract common checks to decorator push jabley travis-ci pending completion   set done
2148 feature/dry-auth-checks Extract common checks to decorator push jabley travis-ci pending completion   set done
2147 feature/dry-auth-checks Extract common checks to decorator DRY code. push jabley travis-ci pending completion   set done
2146 master Allow _start_at and _end_at fields on a record Sometimes we store data that represents an event that happened at a point in time, sometimes that data represents an aggregate period. We should be able to store both kinds without having to falsify ... Pull #391 tombooth travis-ci pending completion   set done
2145 feature/aggregate-data-parity <a href="https://github.com/alphagov/backdrop/commit/08d149327">&lt;a href=&quot;https://github.com/alphagov/backdrop/commit/</a><a class="double-link" href="https://github.com/alphagov/backdrop/commit/&lt;a class=&q... push tombooth travis-ci pending completion   set done
2142 feature/write-start-end-at <a href="https://github.com/alphagov/backdrop/commit/7efd91983">&lt;a href=&quot;https://github.com/alphagov/backdrop/commit/</a><a class="double-link" href="https://github.com/alphagov/backdrop/commit/&lt;a class=&q... push tombooth travis-ci pending completion   set done
2144 master Allow _start_at and _end_at fields on a record Sometimes we store data that represents an event that happened at a point in time, sometimes that data represents an aggregate period. We should be able to store both kinds without having to falsify ... Pull #391 tombooth travis-ci pending completion   set done
2141 master Don't dispatch task if there is no data I've pulled out the triggering of tasks to a separate function, this then handles avoiding dispatch if there is no data. I have also removed dispatching of tasks from PUT as this is only used for cleaning ... Pull #389 tombooth travis-ci pending completion   set done
2141 bugfix/no-data-transforms Don't dispatch task if there is no data I've pulled out the triggering of tasks to a separate function, this then handles avoiding dispatch if there is no data. I have also removed dispatching of tasks from PUT as this is only used for cleaning ... push tombooth travis-ci pending completion   set done
2139 feature/better-ranges Improve transform date range handling When a collector is run it will generally POST a single record into backdrop. This will mean that the earliest and latest values sent through to the transform will be identical. When working with data that is... push tombooth travis-ci pending completion   set done
2140 master Improve transform date range handling When a collector is run it will generally POST a single record into backdrop. This will mean that the earliest and latest values sent through to the transform will be identical. When working with data that is... Pull #390 tombooth travis-ci pending completion   set done
2138 master Don't dispatch task if there is no data I've pulled out the triggering of tasks to a separate function, this then handles avoiding dispatch if there is no data. I have also removed dispatching of tasks from PUT as this is only used for cleaning ... Pull #389 tombooth travis-ci pending completion   set done
2137 bugfix/no-data-transforms Don't dispatch task if there is no data I've pulled out the triggering of tasks to a separate function, this then handles avoiding dispatch if there is no data. I have also removed dispatching of tasks from PUT as this is only used for cleaning ... push tombooth travis-ci pending completion   set done