-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Build CMSSW_14_1_5_O2OTest #46643
Comments
Request received. I will start to build the release after one of the following approve the issue: @mandrenguyen, @sextonkennedy, @rappoccio, @smuzaffar, @antoniovilela. You can do this by writing "+1" in a comment. |
+1 |
Release created: https://github.com/cms-sw/cmssw/releases/tag/CMSSW_14_1_5_O2OTest. The tag was created on top of branch: https://github.com/cms-sw/cmssw/tree/CMSSW_14_1_O2OTest_X |
Queuing Jenkins build for the following architectures: el8_amd64_gcc12 |
The build has started for el8_amd64_gcc12 in vocms011. |
The build has started for el8_amd64_gcc12 in cmsbuild190-rh8. |
The build has finished successfully for the architecture el8_amd64_gcc12 and is ready to be uploaded. |
The tests have finished for el8_amd64_gcc12 Tests results: |
upload all |
Queing Jenkins upload for el8_amd64_gcc12 |
The upload has started for el8_amd64_gcc12 in cmsbuild190-rh8. |
The upload has successfully finished for el8_amd64_gcc12 |
release-notes since CMSSW_14_1_5 |
Generating release notes since CMSSW_14_1_5. |
You can use this template for announcing the release: Hi all, The production release CMSSW_14_1_5_O2OTest is now available for the following architectures: el8_amd64_gcc12 (production) The release notes of what changed with respect to CMSSW_14_1_5 can be found at: https://github.com/cms-sw/cmssw/releases/CMSSW_14_1_5_O2OTest CMSSW_14_1_O2OTest_X branch, including #46632. Cheers, You can also click here to send the email. |
The release notes are ready: https://github.com/cms-sw/cmssw/releases/tag/CMSSW_14_1_5_O2OTest |
CMSSW_14_1_O2OTest_X branch, including #46632.
The text was updated successfully, but these errors were encountered: