GitPython is trying to be nice and thinks that we want the head '<name>' when trying
to create the head 'refs/heads/<name>'.

Avoid this by always prepending 'refs/heads/'.

Change-Id: I90768fd678b02a7fbfc0675456dc4105b51d7f06

This also moves the build "slice" of our redux state into an
initialState variable that allow using the same state for testing.

We should move the others slices to the initialState later on as well.

Change-Id: Id1a476a3b82df530a859732f8dab9ef7c11939e5

When loading the buildset page, we now first check if the buildset is
already in the redux state.

Additionally, this change uses mapStateToProps and mapDispatchToProps
to make the state-to-props handling on the buildset page a little more
explicit.

Change-Id: Ibd8ee3644108a4371e74008b800723b9d6d8e70d

Currently, when retrieving a buildset from the API we also store the
builds that are contained in the buildset's API result in the redux
store. In case those builds were already present (because e.g. the
build page was visited before) they are overwritten but with less
information. This results in missing links and properties on the build
depending on how the page was accessed.

Since the buildset page is anyways using the builds that are contained
in the buildset directly and the build page fetches the necessary build
by itself in case it's not present already, we could simply remove the
relevant part in the fetchBuildset() action and avoid weird behaviour in
the UI.

Change-Id: I90ffd7f8b3fbd13d623ac94ddfd63b5b58cbffe6

This removes some unused parameters from the various fetchBuild...()
actions, introduces async/await to avoid function chaining and improves
the state-to-props handling on the BuildPage.

The last one is done by using the mapStateToProps() function which
allows us to explicitly map the parts of the redux state in which we are
interested to properties of our React component (BuildPage). This way we
keep the mapping in a single place and don't need to "unpack" the redux
state in various places in our component. In addition we use
mapDispatchToProps to automatically wrap all actions we use in our React
component into a dispatch call.

This change also fixe a bug when trying to call substr() on a missing
log_url. Additionally, a missing log url and a missing manifest file are
no longer treated as failure to avoid showing toast notifications for
those. This mainly applies to noop builds, which by definition don't
provide any log at all.

Change-Id: I056448b8735ac4ed5d271a7f55ca558fe9bf317f

When updating the redux state one should not directly touch the state
but rather create a copy of the object first, so redux can efficiently
check if anything has changed and the UI components should be updated.

This avoids mutating the state.builds property directly and uses the
spread operators instead to copy the builds dictionary and replace (or
enhance) the data of the build in question.

Since the build reducers are doing rather simple state changes, I also
decided to drop the usage of the immutability-helper library here and
use plain JavaScript instead as I find this much more readable and
straightforward.

Change-Id: I88c68fed99b21bc9a3682e952499fb4fdf74e2d0

This enables the redux developer tools for the browser. To make use of
this, one must also install the Redux DevTools extension which is
available for various browsers. The extension visualize all state
transitions in the redux store and also allows changing them manually to
see the effects.

Additionally, this change makes use of the third-party library called
"redux-immutable-state-invariant", which throws exception in development
mode whenever a state is mutated directly within an action or reducer.

Change-Id: I8a8588cd7f5f1b17b247d9700a492e5c1e27f040

This version breaks the k8s connection plugin [1].

[1] https://github.com/ansible/ansible/issues/72171

Change-Id: I76647df20e0b23dc3701cb45666774a7dfcfa4d0

Change-Id: I1d788c15d2a64e96ecd82435dcdaef211c3c9d97

Each scheduler in tests needs its own connection registries.

This change only affects tests.

Change-Id: I2ad188cf5a72c46f7486c23ab653ff574123308b
Story: 2007192

The kubic repo has changed it signature key so update it to unbreak
container builds.

Change-Id: I3edc9bebfc6807fb2ed76e615fc9eeff48c03911

Change-Id: Ia4eca66fc8fa19ca0464b79083ad0ba0cf8c3367

This allows the new javascript log viewing functionality to work
in the quickstart configuration.

Change-Id: Iecdff40ddae9f2e5080613e6c289bd84d6f1bb29

Zuul 3.19 requires check run permissions which was an oversight when
creating the release. Therefore update the upgrade notes to add this.

Change-Id: Ibaaa9474d0a537fe25ef8a1024badf4902e3cc77

This reverts commit fe58e85bb1.

We resolved the twine issue with https://review.opendev.org/#/c/755670/

Depends-On: https://review.opendev.org/#/c/755670/
Change-Id: Iab73cf93dd7556609f7bddb13ab06ac7ab879d6b

The entrypoint script in the Gerrit image has changed.  This is the
new way to specify the canonical URL.  The other entries we were
setting are either no longer necessary or not critical.

Change-Id: I6d8979a5fdb204b9a3a12acf05a56a13413379c1

This breaks ensure-twine in opendev which is currently incompatible
with py38.

This reverts commit 429d73e93d.

Change-Id: I983b871d6b42b6d190bc055b57ba0a5f1a4618c0

Test the integration with zuul-client when testing changes on zuul.

Change-Id: I5bf73246497e1b9d7b2d3a8cf72f78c9ddc8f7f7
Depends-On: https://review.opendev.org/751264

The driver provides features parity compared to other drivers.
We can safely remove that notice.

Change-Id: Ie39ef4e54883906eecab08ae7a8e4f9a49f5d544

Using github3py for merging a pull request there is always one extra
request to get the pull request before the merge can be done due to the
github3py data model.

Since merging is done synchronously in in the scheduler main loop, it
makes sense to save the extra API request by building and executing the
merge call directly.

Change-Id: I48dbb5fc1b7e7dec4cb09c779b9661d82935d9df

While upgrading tox37 to tox38, those lines were not updated/removed
they can be removed as:
-tox-py3X jobs specify python version to install during ensure-python
-other jobs are most likely using ensure-pip, which on ubuntu-bionic
install python3-venv and python3.6

Change-Id: I0abfa76d4a7057c8b9154cc111bb0aa20f4fe0bb

Define unit testing for the zuul-client CLI. The actual
testing job will be defined in a subsequent patch to
the zuul-client project.

These tests are stored in the zuul repository rather than in
zuul-client's because we rely on zuul's test framework to bootstrap
zuul and zuul-web, which is not available through zuul's python
package. This is similar to what is done for nodepool's functional
testing with zuul.

Change-Id: I156162279c5d638ef39d22fcfb043655890c2d6e
Depends-On: https://review.opendev.org/751291