-
Notifications
You must be signed in to change notification settings - Fork 264
use cmsswdata.xml to find the changes data packages #2522
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
Conversation
|
A new Pull Request was created by @smuzaffar for branch master. @akritkbehera, @cmsbuild, @iarspider, @smuzaffar can you please review it and eventually sign? Thanks. |
|
cms-bot internal usage |
|
please test with cms-sw/cmsdist#9959 for CMSSW_15_0_X |
|
please test with cms-sw/cmsdist#9959 for CMSSW_15_0_X |
|
Pull request #2522 was updated. |
|
please test with cms-sw/cmsdist#9959 for CMSSW_15_0_X |
|
Pull request #2522 was updated. |
|
+externals bot properly found changed data package |
|
This pull request is fully signed and it will be integrated in one of the next master IBs after it passes the integration tests. This pull request will now be reviewed by the release team before it's merged. @mandrenguyen, @rappoccio, @sextonkennedy, @antoniovilela (and backports should be raised in the release meeting by the corresponding L2) |
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-05f38c/47026/summary.html Comparison SummarySummary:
|
Use cmsswdata.xml to find out the changed data package instead of
cms-data/RepoPRs. Thsi way bot can find out changed data packages via cmsdist PR too