Archives/OpenTTD-patches
2
0
Fork 0
mirror of https://github.com/JGRennison/OpenTTD-patches.git synced 2024-11-17 21:25:40 +00:00
Code Issues Packages Projects Releases Wiki Activity
3f678ade03
OpenTTD-patches/.github/workflows/release.yml

84 lines
1.6 KiB
YAML
Raw Normal View History

Add: [Actions] release workflow for both releases and nightlies This has several ways of being triggered: - When creating a new release via the GitHub interface. Fully automated that will produce new binaries, upload them, and it will even update the website to tell about the new version. - When triggered in an automated way from OpenTTD/workflows to start a nightly. - Manually via the Release workflow, which accepts branches, Pull Requests and tags to build. Rerunning a job is safe and should be without issues. Everything retriggers and updates what-ever might have been broken. In fact, except for dates, it should produce identical results. Co-authored-by: Charles Pigott <charlespigott@googlemail.com>
2020-12-12 15:32:05 +00:00
name: Release
on:
workflow_dispatch:
inputs:
ref:
description: 'Ref to build (for Pull Requests, use refs/pull/NNN/head)'
required: true
Github: Re-add changes to upstream release workflows
2023-06-20 17:25:03 +00:00
# repository_dispatch:
# # client_payload should be the same as the inputs for workflow_dispatch.
# types:
# - Build*
# release:
# types:
# - published
Add: [Actions] release workflow for both releases and nightlies This has several ways of being triggered: - When creating a new release via the GitHub interface. Fully automated that will produce new binaries, upload them, and it will even update the website to tell about the new version. - When triggered in an automated way from OpenTTD/workflows to start a nightly. - Manually via the Release workflow, which accepts branches, Pull Requests and tags to build. Rerunning a job is safe and should be without issues. Everything retriggers and updates what-ever might have been broken. In fact, except for dates, it should produce identical results. Co-authored-by: Charles Pigott <charlespigott@googlemail.com>
2020-12-12 15:32:05 +00:00
jobs:
source:
name: Source
Github: Change release workflows to match upstream
2023-06-20 16:43:12 +00:00
uses: ./.github/workflows/release-source.yml
secrets: inherit
Add: [Actions] release workflow for both releases and nightlies This has several ways of being triggered: - When creating a new release via the GitHub interface. Fully automated that will produce new binaries, upload them, and it will even update the website to tell about the new version. - When triggered in an automated way from OpenTTD/workflows to start a nightly. - Manually via the Release workflow, which accepts branches, Pull Requests and tags to build. Rerunning a job is safe and should be without issues. Everything retriggers and updates what-ever might have been broken. In fact, except for dates, it should produce identical results. Co-authored-by: Charles Pigott <charlespigott@googlemail.com>
2020-12-12 15:32:05 +00:00
docs:
name: Docs
needs: source
Github: Change release workflows to match upstream
2023-06-20 16:43:12 +00:00
uses: ./.github/workflows/release-docs.yml
secrets: inherit
Add: [Actions] release workflow for both releases and nightlies This has several ways of being triggered: - When creating a new release via the GitHub interface. Fully automated that will produce new binaries, upload them, and it will even update the website to tell about the new version. - When triggered in an automated way from OpenTTD/workflows to start a nightly. - Manually via the Release workflow, which accepts branches, Pull Requests and tags to build. Rerunning a job is safe and should be without issues. Everything retriggers and updates what-ever might have been broken. In fact, except for dates, it should produce identical results. Co-authored-by: Charles Pigott <charlespigott@googlemail.com>
2020-12-12 15:32:05 +00:00
Github: Change release workflows to match upstream
2023-06-20 16:43:12 +00:00
with:
version: ${{ needs.source.outputs.version }}
Add: [Actions] release workflow for both releases and nightlies This has several ways of being triggered: - When creating a new release via the GitHub interface. Fully automated that will produce new binaries, upload them, and it will even update the website to tell about the new version. - When triggered in an automated way from OpenTTD/workflows to start a nightly. - Manually via the Release workflow, which accepts branches, Pull Requests and tags to build. Rerunning a job is safe and should be without issues. Everything retriggers and updates what-ever might have been broken. In fact, except for dates, it should produce identical results. Co-authored-by: Charles Pigott <charlespigott@googlemail.com>
2020-12-12 15:32:05 +00:00
linux:
Feature: [Actions / CMake] support for generic linux builds (#8641) These bundles can be opened on any "modern" Linux machine with a driver that SDL2 supports. Machines needs at least glibc 2.15, which was released 10 years ago. It is build with CentOS 7 as base, and only assumes the following libraries are available on the system: - libc - libdl - libgcc_s - libpthread - librt - libstdc++ All other libraries the game depends on are bundled together with the game, so users don't need any library installed to use this bundle. The downside of course is that this increases the binary size a bit: 30 MiB of libraries are in this bundle. RPATH is used to make ld-linux find the folder libraries are stored in; however, system libraries are always used before these, in the assumption libraries on the user system are more up-to-date. Using -DOPTION_PACKAGE_DEPENDENCIES=ON switches on packaging of libraries in the "lib" folder. This requires CMake 3.16 to be installed; otherwise it will fail.
2021-02-05 11:31:27 +00:00
name: Linux (Generic)
needs: source
Github: Change release workflows to match upstream
2023-06-20 16:43:12 +00:00
uses: ./.github/workflows/release-linux.yml
secrets: inherit
Merge branch 'master' into jgrpp # Conflicts: # .github/workflows/release-linux.yml # .github/workflows/release-macos.yml # src/industry_cmd.cpp # src/industry_cmd.h # src/network/core/http_curl.cpp # src/network/core/tcp_http.cpp # src/network/core/tcp_http.h # src/network/network_content.h # src/script/api/script_goal.cpp # src/script/api/script_industry.cpp # src/script/api/script_league.cpp # src/script/api/script_story_page.cpp # src/script/api/script_town.cpp # src/train.h # src/train_cmd.cpp
2023-03-04 01:11:51 +00:00
Github: Change release workflows to match upstream
2023-06-20 16:43:12 +00:00
with:
survey_key: ${{ needs.source.outputs.survey_key }}
Add: [Actions] release workflow for both releases and nightlies This has several ways of being triggered: - When creating a new release via the GitHub interface. Fully automated that will produce new binaries, upload them, and it will even update the website to tell about the new version. - When triggered in an automated way from OpenTTD/workflows to start a nightly. - Manually via the Release workflow, which accepts branches, Pull Requests and tags to build. Rerunning a job is safe and should be without issues. Everything retriggers and updates what-ever might have been broken. In fact, except for dates, it should produce identical results. Co-authored-by: Charles Pigott <charlespigott@googlemail.com>
2020-12-12 15:32:05 +00:00
Github: Re-add changes to upstream release workflows
2023-06-20 17:25:03 +00:00
linux_distros:
name: Linux (Distros)
needs: source
uses: ./.github/workflows/release-linux-distros.yml
secrets: inherit
with:
survey_key: ${{ needs.source.outputs.survey_key }}
Add a linux-dedicated release target Based on linux-legacy
2024-01-25 01:12:10 +00:00
linux-dedicated:
name: Linux (Dedicated)
needs: source
uses: ./.github/workflows/release-linux-dedicated.yml
secrets: inherit
with:
survey_key: ${{ needs.source.outputs.survey_key }}
Add: [Actions] release workflow for both releases and nightlies This has several ways of being triggered: - When creating a new release via the GitHub interface. Fully automated that will produce new binaries, upload them, and it will even update the website to tell about the new version. - When triggered in an automated way from OpenTTD/workflows to start a nightly. - Manually via the Release workflow, which accepts branches, Pull Requests and tags to build. Rerunning a job is safe and should be without issues. Everything retriggers and updates what-ever might have been broken. In fact, except for dates, it should produce identical results. Co-authored-by: Charles Pigott <charlespigott@googlemail.com>
2020-12-12 15:32:05 +00:00
macos:
name: MacOS
needs: source
Github: Change release workflows to match upstream
2023-06-20 16:43:12 +00:00
uses: ./.github/workflows/release-macos.yml
secrets: inherit
Feature: [Actions] Create .zip for macOS build
2021-01-28 12:54:56 +00:00
Github: Change release workflows to match upstream
2023-06-20 16:43:12 +00:00
with:
survey_key: ${{ needs.source.outputs.survey_key }}
Add: [Actions] release workflow for both releases and nightlies This has several ways of being triggered: - When creating a new release via the GitHub interface. Fully automated that will produce new binaries, upload them, and it will even update the website to tell about the new version. - When triggered in an automated way from OpenTTD/workflows to start a nightly. - Manually via the Release workflow, which accepts branches, Pull Requests and tags to build. Rerunning a job is safe and should be without issues. Everything retriggers and updates what-ever might have been broken. In fact, except for dates, it should produce identical results. Co-authored-by: Charles Pigott <charlespigott@googlemail.com>
2020-12-12 15:32:05 +00:00
windows:
name: Windows
needs: source
Github: Change release workflows to match upstream
2023-06-20 16:43:12 +00:00
uses: ./.github/workflows/release-windows.yml
secrets: inherit
Add: [Actions] Automatically upload releases to Steam (#8644)
2021-02-05 19:58:15 +00:00
Github: Change release workflows to match upstream
2023-06-20 16:43:12 +00:00
with:
is_tag: ${{ needs.source.outputs.is_tag }}
survey_key: ${{ needs.source.outputs.survey_key }}
Reference in New Issue Copy Permalink