Skip to content
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

STF 1.5.4 release ops #20

Merged
merged 7 commits into from
Feb 14, 2024
Merged

STF 1.5.4 release ops #20

merged 7 commits into from
Feb 14, 2024

Conversation

vkmc
Copy link

@vkmc vkmc commented Feb 8, 2024

No description provided.

leifmadsen and others added 7 commits October 18, 2022 22:29
When I rebased I inadvertently added an invalid reference which breaks
cachito. Imports require requirements.txt to be pinned to a version.

Signed-off-by: Leif Madsen <[email protected]>

Signed-off-by: Leif Madsen <[email protected]>
* Clean up hadolint output

Clean up hadolint output which causes failures testing in GitHub
Actions. Remove unnecessary upgrades (which are reverted by requirements
files) and package installation (satisfied by requirements).

Resolves: STF-1256

* Syncronize versions across requirements files
* Extend available options to prometheus-webhook-snmp

Related: STF-559

* Adjust Dockerfile to conform to hadolint checks

* Set pip installation version

* Various fixes for linting and build warnings

- Complete clean up of the linting and verify everything continues to
  build
- Clean up the Dockerfile for python package updates which were just
  being overridden by the requirements-built.txt

* Use proper .hadolint.yaml file

* Don't Dockerfile lint error on info
* Allow shell meta-characters in SNMP vars
Instead of updating the .zuul.yaml file everytime
infrawatch/service-telemetry-operator adds a new job, the
project-template can be updated in STO, which will
propogate the change to the project and avoid leaving gaps
in testing.

Depends-On: http://github.com/infrawatch/service-telemetry-operator/pull/514
@vkmc vkmc changed the title Release prep 1.5.4 STF 1.5.4 release ops Feb 8, 2024
Copy link
Member

@leifmadsen leifmadsen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hrmmm I'm a bit confused on the history here with the 7 commits over 2 years and only 1 file being changed...

@csibbitt
Copy link

csibbitt commented Feb 8, 2024

Hrmmm I'm a bit confused on the history here with the 7 commits over 2 years and only 1 file being changed...

It looks to me like the first 4 were previously squash+merged during the STF 1.5.1 release prep, and now they are being merged again without the squash, which produces additional history but ends up being a no-op in the code. The next 2 are the zuul additions, and the 7th is this one.

It did strike me as a bit odd on first glance, but I think everything is fine.

@vkmc vkmc merged commit b07a806 into stable-1.5 Feb 14, 2024
4 checks passed
@vkmc vkmc deleted the release-prep-1.5.4 branch February 14, 2024 18:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants