-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Add placeholders of phase2 geometry config files #43476
Add placeholders of phase2 geometry config files #43476
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-43476/38038
|
A new Pull Request was created by @srimanob (Phat Srimanobhas) for master. It involves the following packages:
@mdhildreth, @cmsbuild, @bsunanda, @Dr15Jones, @civanch, @srimanob, @makortel can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-06cd8b/36267/summary.html Comparison SummarySummary:
|
+Upgrade No change is expected from this PR. After this PR is merged, I will scan obsolete configs, i.e. D49 and migrate them to Default Geometry if possible. |
+1 |
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @sextonkennedy, @rappoccio, @antoniovilela (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
As discussed in #42945, we currently have obsolete config files which can't run because geometry config is old. This PR introduces the default config file so that any scripts which do not need specific geometry can use. Those scripts will be forwarded port every time we update the baseline. No change on geometry-specific configs.
PR validation:
No test. No change is expected as the introduced configs are not used anywhere.
If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:
No need of backport.