pipelines

Commit Graph

Author	SHA1	Message	Date
Ajay Gopinathan	02de9c55e8	Add fake metadata store and fix tests. (#958 ) * Add fake metadata store and fix tests. Also, add instructions on how to build/run the backend with Bazel. Note that the fake metadata store works, but I need to add proper tests that exercise it. That'll be done in a separate PR. One thing I'm missing here is how to make Bazel run well in Travis. I will send a follow up PR for doing this. * move select for update to the db interface	2019-03-21 00:57:35 -07:00
Yasser Elsayed	ec4d7e8bd3	Return resource count from ListXXX calls (#595 ) * add count to protos and libs * close db rows before second query * count -> total_size * int32 -> int * move scan count row to util * add comments * add logs when transactions fail * dedup from and where clauses * simplify job count query * job count queries * run count queries * add job_store total size test * added tests for list util * pr comments * list_utils -> list * fix clients and fake clients to support TotalSize * added TotalSize checks in api integration tests	2019-01-31 11:15:54 -08:00
Ajay Gopinathan	163545b370	Use Bazel to build the entire backend and perform API code generation (#609 ) * Use Bazel to build the entire backend. This also uses Bazel to generate code from the API definition in the proto files. The Makefile is replaced with a script that uses Bazel to first generate the code, and then copy them back into the source tree. Most of the BUILD files were generated automatically using Gazelle. * Fix indentation in generate_api.sh * Clean up WORKSPACE * Add README for building/testing backend. Also fix the missing licenses in the generated proto files. * Add license to files under go_http_client	2019-01-04 17:17:20 -08:00

Author

SHA1

Message

Date

Ajay Gopinathan

02de9c55e8

Add fake metadata store and fix tests. (#958 )

* Add fake metadata store and fix tests.

Also, add instructions on how to build/run the backend with Bazel.

Note that the fake metadata store works, but I need to add proper tests
that exercise it. That'll be done in a separate PR.

One thing I'm missing here is how to make Bazel run well in Travis. I
will send a follow up PR for doing this.

* move select for update to the db interface

2019-03-21 00:57:35 -07:00

Yasser Elsayed

ec4d7e8bd3

Return resource count from ListXXX calls (#595 )

* add count to protos and libs

* close db rows before second query

* count -> total_size

* int32 -> int

* move scan count row to util

* add comments

* add logs when transactions fail

* dedup from and where clauses

* simplify job count query

* job count queries

* run count queries

* add job_store total size test

* added tests for list util

* pr comments

* list_utils -> list

* fix clients and fake clients to support TotalSize

* added TotalSize checks in api integration tests

2019-01-31 11:15:54 -08:00

Ajay Gopinathan

163545b370

Use Bazel to build the entire backend and perform API code generation (#609 )

* Use Bazel to build the entire backend.

This also uses Bazel to generate code from the API definition in the
proto files.

The Makefile is replaced with a script that uses Bazel to first generate
the code, and then copy them back into the source tree.

Most of the BUILD files were generated automatically using Gazelle.

* Fix indentation in generate_api.sh

* Clean up WORKSPACE

* Add README for building/testing backend.

Also fix the missing licenses in the generated proto files.

* Add license to files under go_http_client

2019-01-04 17:17:20 -08:00

3 Commits