-
-
Notifications
You must be signed in to change notification settings - Fork 382
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
Rename build
to pipeline
in code
#1224
Conversation
nah please not rename CI_BUILD env vars! you have no idea how much work breaking env vars is ... sep if they are many |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
BUILD
This comment was marked as outdated.
This comment was marked as outdated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again, crazy job. I absolutely love it.
server/store/datastore/migration/008_rename_builds_to_pipeline.go
Outdated
Show resolved
Hide resolved
Co-authored-by: Anbraten <anton@ju60.de>
Co-authored-by: Anbraten <anton@ju60.de>
Co-authored-by: Anbraten <anton@ju60.de>
@anbraten I would keep the migrations how they are now, so only rename tables and not columns. I also added some notes to the migration docs that show what really has been changed - maybe you could give them a special look. |
This should be 100% backwards compatible again, except the Prometheus Gauge which has been renamed. Should I do something to stay backwards compatible here too? (I don't really know anything about Prometheus) |
Deployment of preview was successful: https://woodpecker-ci-woodpecker-pr-1224.surge.sh |
I think that's it - as you can see tests etc passed, I it tested locally and didn't find any occurrences that can be replaced of What has not been changed:
Breaking changes:
@6543 Do you want to develop a linter that warns about deprecated envs first before merging? |
yes ... |
I think we shouldn't change JSON fields in this PR. Let's do this in a followup, I should be able to do this. |
In that case please fix the frontemd code |
I did already. |
Whoever will merge this: because it renames a translation key, weblate will remove the old translations and we have to translate them again. To prevent this, I recommend you to do the following:
Then, weblate should contain the translations with the new keys and will update the files once the repo is synced again. |
I have downloaded the current translation files so we could reuse them after merging. |
Ref: woodpecker-ci#745 Co-authored-by: Anbraten <anton@ju60.de> Co-authored-by: 6543 <6543@obermui.de>
Closes woodpecker-ci#1282 Follow-up to woodpecker-ci#1224, addresses woodpecker-ci#745 - changes JSON fields - adds migration to rename columns - fixes some comments
regression of woodpecker-ci#1224
ref #745
TODO