| commit | 2a851fca9fcf6e1af53b7d494802b05069597787 | |
| author | Ani Sinha <anisinha@redhat.com> | |
| Sat, 6 May 2023 07:20:12 +0000 (6 12:50 +0530) | ||
| committer | Thomas Huth <thuth@redhat.com> | |
| Tue, 16 May 2023 07:14:18 +0000 (16 09:14 +0200) | ||
| tree | b393cb9fbe295ca4b834446614f224ab8f13c018 | treesnapshot (tar.gz zip) |
| parent | 88693ab2a53f2f3d25cb39a7b5034ab391bc5a81 | commitdiff |
docs/devel: remind developers to run CI container pipeline when updating images
When new dependencies and packages are added to containers, its important to
run CI container generation pipelines on gitlab to make sure that there are no
obvious conflicts between packages that are being added and those that are
already present. Running CI container pipelines will make sure that there are
no such breakages before we commit the change updating the containers. Add a
line in the documentation reminding developers to run the pipeline before
submitting the change. It will also ease the life of the maintainers.
Signed-off-by: Ani Sinha <anisinha@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Message-Id: <20230506072012.10350-1-anisinha@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
When new dependencies and packages are added to containers, its important to
run CI container generation pipelines on gitlab to make sure that there are no
obvious conflicts between packages that are being added and those that are
already present. Running CI container pipelines will make sure that there are
no such breakages before we commit the change updating the containers. Add a
line in the documentation reminding developers to run the pipeline before
submitting the change. It will also ease the life of the maintainers.
Signed-off-by: Ani Sinha <anisinha@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Message-Id: <20230506072012.10350-1-anisinha@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
| docs/devel/testing.rst | diffblobblamehistory |