forked from go-vela/server
-
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Increase Starlark execution limit, abstract limit resolver #1
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…r rulesets (go-vela#630) * add edit to scm/webhook * populate event action field and use for rules if provided * get rid of event action setter for tag event - mistake * handle all types of edited actions Co-authored-by: Easton Crupper <[email protected]>
…a#622) * stash apply * handle webhook redelivery * fix merge conflict fallout Co-authored-by: David May <[email protected]>
Co-authored-by: Renovate Bot <[email protected]>
Co-authored-by: Renovate Bot <[email protected]>
Co-authored-by: Renovate Bot <[email protected]>
Co-authored-by: Renovate Bot <[email protected]>
…using claims (go-vela#901) * fix(api/schedule): make validateEntry more strict and set updated_by using claims * rm docker compose update * add test cases to validateEntry
* fix(schedules): ignore trigger for first time schedule * fix(schedules): determine trigger off current UTC time * chore: save work * cleanup: ignore inactive schedules * feat: add interval for schedules * chore: address slack feedback * chore: fix typos * fix: processing timed schedules * fix: processing schedules * fix: typo in comment * chore: address review feedback * temp: add test docker compose * fix: finalize * revert: add test docker compose --------- Co-authored-by: Easton Crupper <[email protected]> Co-authored-by: David May <[email protected]>
go-vela#902) Co-authored-by: dave vader <[email protected]>
* fix(deps): update deps (patch) * fix(deps): update deps (patch) --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: ecrupper <[email protected]>
…ela#907) * chore(release): upgrade types to v0.20.0 + gorm and starlark upgrade * update Dockerfile to pin to alpine version for certs * go get correct docker version syntax * every day I surprise myself with my foolishness * pin gorm to an actual tag
…a#913) * init commit * fix tests
…templates (go-vela#916) * fix(compiler): convert local templates to an engine field for nested templates * add WithLocalTemplates test
* chore(release): upgrade types to v0.20.1 * other deps
* enhance: getting visbility to match on vela and SCM * fix: modifying test cases to consider new visibility changes --------- Co-authored-by: Claire.Nicholas <[email protected]>
* refactor(db): return schedule on create and update * fix integration tests --------- Co-authored-by: David May <[email protected]>
* enhance: add context to Repos * chore: add WithContext test
) * init commit * adding db tests * compiled to build itinerary * add mock * itinerary -> executable * fix mock * update some extra db configs * pull in updated types * encrypt and decrypt * Update database/executable/interface.go Co-authored-by: dave vader <[email protected]> * pesky linter * add integration test for executables * try this * with encryption resource opt * Update database/executable/opts.go Co-authored-by: dave vader <[email protected]> --------- Co-authored-by: dave vader <[email protected]> Co-authored-by: David May <[email protected]>
* enhance: adding a branch field to scheduled builds * enhance: adding a branch field to scheduled builds * enhance: adding a branch field to scheduled builds * enhance: fixing merge conflicts for branch in scheduled builds * enhance: fixing merge conflicts for branch in scheduled builds --------- Co-authored-by: Claire.Nicholas <[email protected]> Co-authored-by: Kelly Merrick <[email protected]> Co-authored-by: Claire.Nicholas <[email protected]>
Co-authored-by: David May <[email protected]>
5,000 was too few to enable the example added to the testdata to work, so was 6,000. I chose 7,500 arbitrarily after a test at 10,000 and both worked. In the long term, this should probably be configurable so as not to require recompilation. For now, this kicks the can down the road while allowing this build matrix use case to exist.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
/stream
endpoints go-vela/server#799)GetBuildLogs
(feat(api/log)!: support paging onGetBuildLogs
go-vela/server#798)