Skip to content

trunk-io/mergequeue

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

light-complex (3)

Welcome

This repository is used to demonstrate the performance characteristics of a merge graph under different simulated loads.

How does it work

The load imparted onto the connected queue is controlled by the mq.toml file in the .config folder. The PR Factory workflow is set on a cron schedule to call mq which is then responsible for generating the pull requests and enqueueing them.

The configuration system allows for setting the desired load on the queue, the flake rate and the interdependence element of the pull requests.

# parallelqueue - will push deps information to the service to take advantage of trunk merge dynamic parallel queues # singlequeue - single traditional queueu mode = "singlequeue" # Default value: "singlequeue" #mode = "singlequeue" # Default value: "none" #build = "none" [git] # Default value: "Jane Doe" #name = "Jane Doe" # Default value: "bot@email.com" #email = "bot@email.com" [pullrequest] # Default value: "" #labels = "" # Default value: "" #comment = "" # Default value: "This pull request was generated by the mq tool" #body = "This pull request was generated by the mq tool" # Default value: 10 #requests_per_hour = 10 # Default value: 1 #max_deps = 1 # Default value: 1 #max_impacted_deps = 1 [test] # Default value: 0.1 #flake_rate = 0.1 # Default value: "1 second" #sleep_for = "1 second" [merge] # Default value: "" #labels = "" # Default value: "" #comment = ""

About

Demonstration of trunk.io/merge in realtime

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Contributors 8