Closed Crosse closed 2 years ago
At a minimum it might be a good idea to get the CasC example updated
done : https://github.com/jenkinsci/configuration-as-code-plugin/pull/1960
It sounds like this was an undesired consequence of #826
In hindsight, maybe we shouldn't have removed support for volumes and simply added support for mounts so that both are supported - they're very similar in function, but mounts are not quite a like-for-like replacement. e.g. I personally discovered (albeit too late, when parts of my build environment stopped working) that mounts require things to exist whereas volumes are more fault-tolerant. Lesson learned - never ever remove functionality...
So, if anyone wants to make a PR that re-adds support for volumes (ideally adding a warning in the UI that folks should use probably use mounts instead, maybe even using the existing migration code to tell the user exactly how to do that), that could make all these issues go away.
While I no longer use Jenkins, I'm sure this will be a welcome fix for other users. Thank you!
Version report
Jenkins and plugins versions report:
(Click here for full plugins list)
Controller and agents are running under Linux (specifically Fedora CoreOS 34)
Reproduction steps
Prior to v1.2.3, the following CasC snippet worked (ref):
Due to #826 (I think), this syntax stopped working with v1.2.3 of this plugin. I had to change all of my
volumes
andvolumesString
references tomounts
andmountsString
, respectively.Results
Expected result:
Jenkins to restart and CasC to process my configuration successfully.
Actual result:
I didn't see a change log or other indication that I needed to change my Configuration as Code syntax for this release, so the stack trace Jenkins threw at me on restart was unexpected. 😄
At a minimum it might be a good idea to get the CasC example updated. I can put a PR in for that if necessary.