* feat: report to bench
* fix: output json
* chore: own the code
* temp: limit files to test for faster iteration
* temp: force bench to run for testing purposes
* fix: bench has been merged to main
* fix: correct file name
* temp: remove temp
* feat: pin the tparse binary
Co-authored-by: Matheus Macabu <macabu@users.noreply.github.com>
---------
Co-authored-by: Matheus Macabu <macabu@users.noreply.github.com>
* baldm0mma/ parallelize tests for reporting
* baldm0mma/ update combining non-existant outputs
* baldm0mma/ remove duplicate logic
* baldm0mma/ rem any unnecessary logging
* baldm0mma/ add workflow path for test coverage test
* baldm0mma/ cache ent
* baldm0mma/ update with crucial comments
* baldm0mma/ generate go files
* baldm0mma/ cache enterprise only once
* baldm0mma/ adjust coverage threshholds
* baldm0mma/ remove temp artifacts from storage to save $$$
* baldm0mma/ remove strict coverage for unit tests
* baldm0mma/ pass coverage go opts
* baldm0mma/ update run backend tests action to composite
* baldm0mma/ separate make gen go into it's own composite step
* baldm0mma/ move options to workflow
* baldm0mma/ remove use of action
* baldm0mma/ remove unsed action
* baldm0mma/ update codeowners
* baldm0mma/ add edition logic
* baldm0mma/ set env vars in determine-edition action
* baldm0mma/ make test
* baldm0mma/ debug sequential
* baldm0mma/ debugging by removing unit tests
* baldm0mma/ TRY SOMETHING DIFFERENT!!!
* baldm0mma/ uploading ent from within the workspace
* baldm0mma/ revert run-backend-tests action
* baldm0mma/ move edition to job level
* baldm0mma/ update WIRE_TAGS
* baldm0mma/ move the enterprise code to the correct location after extracting it
* baldm0mma/ rem packaging/extracting of enterprise code
* baldm0mma/ test makefile
* baldm0mma/ add ent setup to coverage
* baldm0mma/ rem backend test action
* baldm0mma/ add wire and go steps to coverage job
* baldm0mma/ remove make installation, as it is already present in the "ubuntu-latest" package
* baldm0mma/ convert to matrix testing strategy
* baldm0mma/ update separate test coverage to only a day
* baldm0mma/ add setup-common-backend-testing-env action
* baldm0mma/ add setup env
* baldm0mma/ update naming
* baldm0mma/ updade codeowners
* baldm0mma/ rem ent
* baldm0mma/ update naming
* baldm0mma/ remove multiline syntax in report-coverage
* baldm0mma/ make gen-go
* baldm0mm/ remove integration tests
* baldm0mma/ update coverage params
* baldm0mma/ streamline workflow
* baldm0mma/ update codeowners
* baldm0mma/ update naming
* baldm0mma/ simplify logic
* baldm0mma/ remove uneeded trigger
* baldm0mma/ remove conditional coverage step
* baldm0mma/ debug coverage
* baldm0mma/ update file name
* baldm0mma/ remove artifact upload
* baldm0mma/ update atrifact params in the workflow
* baldm0mma/ simplify processing logic
* feat: report to codecov
* fix: use webhook domain
* chore: force coverage check
* fix: use token
* fix: pass in token from workflow
* feat: remove codecov coverage force
The project board github.com/grafana/grafana/projects/21 has been deleted
as far as I can tell (or never existed).
I can't see an obvious candidate-team to receive `area/editor`, so I
propose we delete it instead.
* baldm0mma/ create backend-code-checks workflow
* baldm0mma/ update to validate backend configs
* baldm0mma/ rem unused dir
* baldm0mma/ update codeowners
* baldm0mma/ update naming
* baldm0mma/ update case
* baldm0mma/ update workflow name
* baldm0mma/ rem action and run the commands directly
* baldm0mma/ update codeownders
* baldm0mma/ update codeowners for workflow
* baldm0mma/ update workflow name in codeowners
* Create the frontend test workflow
* Give .github/workflows/test-frontend to frontend platform group
* Remove file filter
* rename workflow
* frontend unit tests
* add yarn install
* update CODEOWNERS
* Run on 8 core machines?
* use parallelization?
* add sharding
* update package.json to allow sharding jest
* update workflow name
* yarn generate-apis
* update naming
* CI: Track backend code coverage
This is a super rudimentary way to track this coverage. The important bit for me is the ability to extract the coverage
files.
* CI: Allow tests to fail
* Codeowners: Assign ownership of coverage tracking
* CI: Join coverage info in the job
* CI: Attempt to parallellise tests
* CI: Upload despite failures
* CI: Pattern is not regex
* CI: Set up repository and Go before merging
* CI: Generate go before checking coverage
* CI: Multi-line string
* CI: Backticks execute commands; avoid them
* CI: Make the output a bit prettier
Tabs are absurdly large.
* CI: Remove comment on retention
* basic setup
* update CODEOWNERS
* update name
* add temp test that ensures we are loading schema V2 json in the UI
* update language
* test with yarn cache and combine steps
* revert combine
* remove commented out code
* Run current dashboard suite, make workflow optional
* make job always succeed
* Remove temp v2 suite
* don't run on draft PRs
* command for old arch
We use Vulnerability Observability for Docker images. The current comments say we simply don't scan them at all, so
let's make it clear for future readers that we do, in fact, scan Docker images, too.
Jev Forsberg
Mariell Hoversholm
Sam Jewell
Josh Hunt
Matheus Macabu
Kevin Minehart
Yuri Tseretyan
Jack Baldry
Leonor Oliveira
Piotr Jamróz
Ashley Harrison
Ethan
Haris Rozajac
Kevin Yu
Esteban Beltran
Sven Grossmann
Todd Treece