Skip to content
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

PR check for terraform, redis, fdk-aac-free, opus and packer #12253

Open
wants to merge 10 commits into
base: 3.0-dev
Choose a base branch
from

Conversation

rikenm1
Copy link
Contributor

@rikenm1 rikenm1 commented Feb 7, 2025

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

  • The toolchain has been rebuilt successfully (or no changes were made to it)
  • The toolchain/worker package manifests are up-to-date
  • Any updated packages successfully build (or no packages were changed)
  • Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
  • Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
  • All package sources are available
  • cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
  • LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
  • All source files have up-to-date hashes in the *.signatures.json files
  • sudo make go-tidy-all and sudo make go-test-coverage pass
  • Documentation has been updated to match any changes to the build system
  • Ready to merge

Summary

What does the PR accomplish, why was it needed?
We are not letting some of the packages to be updated using this PR check gate.
i) redis cannot be updated to 7.4 and above
ii) packer cannot be updated to 1.10.0 and above
iii) terraform cannot be updated to 1.6.0 and above
iv) no version bump or addition of fdk-aac-free opus-file, and opus.

Change Log
  • Change: Gate for barring some of the package updates
  • Added a csv file to that shows what version of packages cannot be added to the Azure Linux
Does this affect the toolchain?

YES/NO
NO

Test Methodology
  • Pipeline build id: locally and using the PR checks

@rikenm1 rikenm1 marked this pull request as ready for review February 7, 2025 02:31
@rikenm1 rikenm1 requested a review from a team as a code owner February 7, 2025 02:31
@microsoft-github-policy-service microsoft-github-policy-service bot added the 3.0-dev PRs Destined for AzureLinux 3.0 label Feb 7, 2025

on:
push:
branches: [main, dev, 1.0*, 2.0*, 3.0*, fasttrack/*]
Copy link
Contributor

@jslobodzian jslobodzian Feb 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can probably disregard dev and 1.0 both above this comment and below this comment

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated

version=$(rpmspec --parse "$spec" | grep -E "^Version:\s*(.*)" | awk '{print $2}')

#if fdk-aac-free or opus are changed, check if the version is the same as the previous version
if [[ "$name" == "fdk-aac-free" || "$name" == "opus" ]]; then
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so we want to make sure that fdk-aac-free, opus and opus-file are NOT re-introduced. Not sure why we would be looking for a previous version,

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Similar comment here as below, we probably should take this from a simple data file that we can iterate through.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated. added a new csv file

fi
fi
# Check if the version is greater than the allowed version
if { [[ "$name" == "redis" && "$(printf '%s\n' "$version" "7.4" | sort -V | head -n1)" == "7.4" ]] || \
Copy link
Contributor

@jslobodzian jslobodzian Feb 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Python may have been a better language choice here. We should at least create an Associative Array where the package name can be the key and the version number it's maximum value. Then iterate through these. Even better, we might just have a CSV style data file to iterate through.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added a new csv file

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.0-dev PRs Destined for AzureLinux 3.0 Packaging
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants