2020-09-23 21:23:21 +03:00
## How to add a new release version and publish to Azure Blob Storage?
Pauld/1559705 improve cli to detect viable sdks based on debian flavor (#1484)
* save point: splitting up versions to build by ostype
* restructured and modified the platforms scripts and updated the shared code generator to account for the new versions
* updated constants to include ostype change and newer python version
* added support for new file structure to the python dockerfiles and publishing from dev to prod sdks
* save point, starting to enrich all storage items with version number, and modifying tests for new logic
* clean up platforms shell scripts
* finish modifying scripts to add version to the metadata, regardless of OSType
* beginning to update cli to support pulling only relevant sdks
* added constants that relate to the different debian flavors we may see
* save point, added to constants yaml file to start adding support for pulling debian flavor sdks
* added debian flavor option to the build command, and starting to update tests to be compatible
* renamed the vso focal directories to focal scm, and fixed the sdk storage tests
* added a number of comments for the second PR and some tests to cover dotnet and node pulling the correct images
* added php and python tests for installing based on the available sdks
* updated sdk storage provider and platform installer to have bullseye images use buster sdks, since there are currently no bullseye sdks
* self reviewed pr: added comments, fixed some bugs and typos, and updated the pipeline scripts to correctly handle stretch images
* added default sdk storage metadata to be used for determining versions available
* added legacy versions to stretch version directories, so that the supported md file will contain the best information
* updated shared code generator to allow for the legacy versions text files
* update platform installation scripts to enrich the sdks with an updated version metadata name and the OS type
* some fixes for generating the platform binaries locally, and a fix for generating the maven binaries
* added legacy version metadata to storage constants
* updated the metadata names so that they exist in constants file and can be used throughout oryx
* saved leftover merge conflict file
* removed old default and versions to build files
* updated php fpm configuration to be in the constants.yaml file so that we support the generate constants script
* updated the debian flavor arg in the python template
* fix failing githubaction and vso focal tests
* saved file and added comment to version comparer
* fixed some spacing and added comments and a todo
* updated dotnet runtime version metadata to be backwards compatible
* use version info from elsewhere in oryx to streamline version comparing
* pr feedback, using constants during platform installation and sdk storage provider, and trimming whitespace from version files
* pr feedback: use constants for file names and renamed the new sdk versions metadata to be consistent
* limit bullseye sdks we push to storage to the ones that we know will be used by bullseye
* regenerated constants with updated bullseye versions, and removed extra logic in VersionInfo
* include all defaultVersion.txt files in the upload
* fixed spacing for vsts pipeline
* updated the maven base url to point to a source that contains legacy versions
* fixed php version sha
* use correct get pip url when version 3.6 and stretch
* add bullseye maven job
* added support to still build php 7.2 binaries
* allow enough time for php to generate and upload all sdks
* give php jobs 24 hours to run, as they have not been able to generate all versions in the given time
* updated python sdk generation to use the correct stretch buildpack for non-3.10 or greater versions
* updated logic so that python version 3.10 and above will have the correct prerequisites built
* updated common script to ignore whitespace differently
* readded deleted line and ran generate constants
* Pauld/1559705 PR2 cleanup and utilize bullseye images (#1497)
* initial pass at adding support for bullseye by resolving the PR2 todos
* allow build
* added test for php default versions
* added dotnetcore and python tests for invalid versions
* added more tests for correct pulling functionality
* support for finding default version with no debain flavor
* add working python versions
* whitespace
* added comments explaining the supported version logic, and fixed a statement to ensure that stretch images check for correct dotnet metadata
* add preview 7
* addressed PR comments by deleting un-needed method and adding comment
2022-08-15 20:35:32 +03:00
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.
2020-09-23 21:23:21 +03:00
If it's a default version, reset `defaultVersion.txt` file.
2022-04-08 22:45:06 +03:00
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-< PlatformName > 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_< PlatformName > ="true" to overwrite SDKs in a specific platform.
