Oryx/platforms
Saipriya-1144 1d4a577914 updated constants.yml from pipeline 2024-09-09 10:54:14 +00:00
..
dotnet updated constants.yml from pipeline 2024-09-09 10:54:14 +00:00
golang Wali/support new version of php node go 1786787 (#1955) 2023-04-19 18:13:11 -04:00
java Upload defaultversion.txt for stretch as well (#1796) 2023-01-10 09:35:37 -05:00
nodejs updated constants.yml from pipeline 2024-09-09 10:54:14 +00:00
php updated constants.yml from pipeline 2024-09-09 10:54:14 +00:00
python updated constants.yml from pipeline 2024-09-09 10:54:14 +00:00
ruby User/priya/passing versions as args (#2478) 2024-08-22 09:53:49 +05:30
README.md Pauld/1559705 improve cli to detect viable sdks based on debian flavor (#1484) 2022-08-15 13:35:32 -04:00
__common.sh Changes for Oryx pipeline migration. (#2430) 2024-05-31 16:30:11 +05:30

README.md

How to add a new release version and publish to Azure Blob Storage?

Add a new version, its SHA, and GPG keys information to {language}/versions/{ostype}/versionsToBuild.txt file for any operating systems that you would like the version to be available. Update version constants in constants.yaml and other files. If it's a default version, reset defaultVersion.txt file. Manually trigger the platform binary build pipeline after sent PR and update related tests.

Options to overwrite platform binaries when publishing SDKs to dev or prod storage account

We set up environment variable during the pipeline execution. When trigger a new build in Oryx-PlatformBinary- in Azure DevOps pipelines, click the 'run pipeline'->'Advanced options'->'Variables' and add the variable name and value there. Set up OVERWRITE_EXISTING_SDKS="true" to overwrite SDKs in all platforms. Set up OVERWRITE_EXISTING_SDKS_="true" to overwrite SDKs in a specific platform.