-
Notifications
You must be signed in to change notification settings - Fork 184
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
Update tag for CalibPPS-ESProducers to V01-04-00 #7282
Update tag for CalibPPS-ESProducers to V01-04-00 #7282
Conversation
A new Pull Request was created by @cmsbuild for branch IB/CMSSW_12_1_X/master. @cmsbuild, @smuzaffar, @mrodozov, @iarspider can you please review it and eventually sign? Thanks. |
Hi @mrodozov just for my education, what does |
@cmsbuild , please test |
for every merged cms-data PR, we make a new tag after it's merged where V01-04-00 is V01-03-00 + cms-data/CalibPPS-ESProducers#5 changes https://github.com/cms-data/CalibPPS-ESProducers/tags |
thanks @mrodozov ! |
in this particular case the change will just add the new files from the PR and all will be tested which doesn't change anything and just adds few files. thats why this PR will go fine but it wont test anything. to test it with the cmssw pr - which was already done, use since most of the data PRs are already tested against their relevant cms-sw changes, this cmsdist PRs are only "making the change for the release" and thats why we (mostly) don't test them |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-2c4a30/18394/summary.html Comparison SummarySummary:
|
+1 |
merge |
Move CalibPPS-ESProducers data to new tag, see
cms-data/CalibPPS-ESProducers#5