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

DO NOT MERGE | changes required in CS components to build automate via LTS channel #8770

Open
wants to merge 9 commits into
base: main
Choose a base branch
from

Conversation

talktovikas
Copy link
Collaborator

@talktovikas talktovikas commented Feb 3, 2025

🔩 Description: What code changed, and why?

While building Automate components in chef-server pipeline these changes were required.
the problem during testing:
Lets say the package:
core/coreutils/8.32/20240105213308
that is https://bldr.habitat.sh/#/pkgs/core/coreutils/8.32/20240105213308
is not in LTS and apart from that since we are using Fallback_channel as 'dev' to tackle the problem of chef-scaffolding
not in LTS, this version of coreutils would be installed.
Now this package have common dependencies with other packages which are from LTS, for example
glibc.
This will cause having same package with different versions during build and hence due to circular direct or transitive dependency build won't happen.

⛓️ Related Resources

👍 Definition of Done

👟 How to Build and Test the Change

✅ Checklist

All PRs must tick these:

With occasional exceptions, all PRs from Progress employees must tick these:

  • Is the code clear? (complicated code or lots of comments--subdivide and use well-named methods, meaningful variable names, etc.)
  • Consistency checked? (user notifications, user prompts, visual patterns, code patterns, variable names)
  • Repeated code blocks eliminated? (adapt and reuse existing components, blocks, functions, etc.)
  • Spelling, grammar, typos checked? (at a minimum use make spell in any component directory)
  • Code well-formatted? (indents, line breaks, etc. improve rather than hinder readability)

All PRs from Progress employees should tick these if appropriate:

  • Tests added/updated? (all new code needs new tests)
  • Docs added/updated? (all customer-facing changes)

Please add a note next to any checkbox above if you are NOT ticking it.

📷 Screenshots, if applicable

Signed-off-by: talktovikas <vikas.yadav@progress.com>
Signed-off-by: talktovikas <vikas.yadav@progress.com>
Signed-off-by: talktovikas <vikas.yadav@progress.com>
Signed-off-by: talktovikas <vikas.yadav@progress.com>
Signed-off-by: talktovikas <vikas.yadav@progress.com>
Signed-off-by: talktovikas <vikas.yadav@progress.com>
Signed-off-by: talktovikas <vikas.yadav@progress.com>
Signed-off-by: talktovikas <vikas.yadav@progress.com>
Signed-off-by: talktovikas <vikas.yadav@progress.com>
Copy link

netlify bot commented Feb 3, 2025

👷 Deploy Preview for chef-automate processing.

Name Link
🔨 Latest commit dc93c83
🔍 Latest deploy log https://app.netlify.com/sites/chef-automate/deploys/67a0f156e44a3b0009e04e3c

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant