summaryrefslogtreecommitdiff
path: root/tests/unit/test_push_reqs.py
Commit message (Collapse)AuthorAgeFilesLines
* Make test setup_config more pureJan Kubovy2020-02-281-3/+0
| | | | | | | | | | Setup config will not set the base test config object rather return a new one. This allows to setup multiple config objects which is needed in order to instantiate mutliple schedulers enabling them to have different configs, e.g. command socket. Change-Id: Icc7ccc82f7ca766b0b56c38e706e6e3215342efa Story: 2007192
* Ensure ref-updated jobs run with their refJames E. Blair2017-08-021-4/+5
| | | | | | | | We were incorrectly preparing the current state of the repo for ref updated (eg, post) jobs. This ensures that we run with the actual supplied ref, even if the remote has moved on since then. Change-Id: I52f05406246e6e39805fd8365412f3cb77fe3a0a
* Extend in-repo config update support to githubJesse Keating2017-06-071-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | The code that would look for in-repo config changes was gerrit specific. Turn the gerrit specific bit into a generic that drivers can implement. Implement the generic in the github driver, which required accounting for files that are part of a push event (where code is landing in the repo we care about). Also remove an unnecessary fake pull request method of getPushEvent, as there was already one in the fake github class. Move the real updatesConfig function from the Change object to the Ref object (since we can get a change from a ref) and move the files attribute as well. Introduce a test for github to verify that the tenant is reconfigured. This required introducing a new Scheduler object attribute to track when each tenant is reconfigured. The existing reconfiguration time tracker was generic, and not updated via dyanmic updates. Change-Id: Ibf59f91fa3701c15d93d859920fe3070478fe457 Story: 2000774 Task: 4664
* Handle change related reqs on push like eventsJesse Keating2017-06-051-0/+53
Push and ref-updated events do not have an associated change or pull-request. Thus, requirements that are specific to changes or pull-requests cannot possibly be met. To make this work, Ref filters should only be applied to changes that come from a matching connection. This was not previously enforced when filters became connection specific. Change-Id: I5d67bef264db0ad5ba3a7180ce74e3670ba822ce Story: 2000774 Task: 4624