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
Add: [AzurePipeline] introducing a release pipeline #7027
Conversation
Keep forgetting to remind myself: still missing, meta files:
and possibly an index.html, which has the style of our website. (would like to merge this PR without those, as they will be an addition) |
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.
Nothing major. I suspect the only way to test this properly is to actually use it :)
868a753
to
7ba4856
Compare
Added tons of stuff. Only thing "missing" now is an index.html. But that is something for another PR.
|
3c64b60
to
51f27ac
Compare
|
51f27ac
to
3a2dd73
Compare
|
3f35fb0
to
e3c1dfe
Compare
This release pipeline creates all the official release binaries, and publishes them as artifacts. Currently it can only produce nightlies and custom builds; stable/testing release binaries are untested. This commit also splits up the pipeline in small bits, to both improve readability, and to share code with the CI pipeline where possible.
e3c1dfe
to
10f6f84
Compare
Second attempt, this with better workish. This splits up the azure pipelines in small templates, for easier maintenance.
Examples:
https://dev.azure.com/truebrain/OpenTTD/_build/results?buildId=241
This is what a nightly would be. The branch is now called 'azure_pipelines', but imagine it reading 'master'
https://dev.azure.com/truebrain/OpenTTD/_build/results?buildId=242
This is what a release would be. Because I used a branch ('azure_pipelines') to compile it, Windows exe and .deb files have the wrong version number (it is hardcoded), so please do not use these artifacts. But normally, if the release procedure is followed, that would result in something like '1.9.0-beta1' as version number.