Hello Zuulers,
I have identified a minor bug in the way that the current
helm-template role handles Helm v3 naming of releases:
https://storyboard.openstack.org/#!/story/2010783
I would like to propose a fix but I am wondering whether we should
strive to keep Helm v2 compatibility at this point as it's very
outdated and not supporting modern Kubernetes either.
If we can drop Helm v2 support then it makes it really simple to fix
and avoids version parsing.
Kind regards,
Radek
-yoctozepto
Dear Zuulers,
I am confused about the behaviour of requires-provides and wonder
whether this is on purpose (and then why?) or by accident.
I noticed that the job which *requires* something from another job
that *provides* it does **not** wait for this other job if it's run
**on the same change** (i.e., in the same buildset), only on earlier
changes/buildsets.
While this works as explained in the docs [1], I find it confusing.
For example, I have a Dockerfile and Helm chart in the same repo …
[View More]and I
would like to check how changes to the image affect the chart
deployment.
Currently, only subsequent changes would consume the result.
I.e., by this design, I am forced to artificially split the repo into
a separate one for chart and a separate one for the image.
[1] https://zuul-ci.org/docs/zuul/latest/config/job.html
Kind regards,
Radek
-yoctozepto
[View Less]
Join members of the community for ice cream after the Marketplace
Mixer on Wednesday at Soft Peaks in Gastown! Soft Peaks is known for
using organic milk and their unique topics! For those with dairy
related dietary needs who register we will have an alternative for you
so don't feel left out!
https://eventyay.com/events/231a963f