Replies: 1 comment
-
|
Thanks for sharing! I am surprised this failure state occurs as well. I'd expect the old var style to be treated as a string and not cause any errors. I'm glad nothing else broke and you were able to update your pipelines. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
General FYI for those migrating from 7.x to 8.x, if you have pipeline definitions with older
{{ var }}style variables, the exhibited behavior post upgrade is:flyCLI works 100% fine, can login, get-pipeline, trigger-job, etc…The quick solution is to drop any pipelines with the older variable type (or move them to a different team via an UPDATE statement in the db).
I know the release notes mentions that these types of variable has been deprecated but I had only expected the associated pipeline to be broken, not the whole web ui front end. The deprecation is also mentioned in https://github.com/orgs/concourse/discussions/9184 but doesn't reference the symptoms of not having done this.
Wanted to leave this nugget behind for anyone else who runs into this problem. Could not find any logs that indicated this was the problem.
Beta Was this translation helpful? Give feedback.
All reactions