cms-sw / cmssw

CMS Offline Software
http://cms-sw.github.io/
Apache License 2.0
1.08k stars 4.3k forks source link

Build CMSSW_7_4_5_ROOT5 #9604

Closed davidlange6 closed 9 years ago

davidlange6 commented 9 years ago

+1

cmsbuild commented 9 years ago

Request received. I will start to build the release after one of the following approve the issue: @smuzaffar, @degano, @davidlange6. You can do this by writing "+1" in a comment. You can also ask me to begin to build cmssw-tool-conf first ( Cannot be done for patch releases ). To do this write "build cmssw-tool-conf" in a comment. I will start to build cmssw-tool-conf and then wait for the "+1" to start the build of the release.

cmsbuild commented 9 years ago

Release created: https://github.com/cms-sw/cmssw/releases/tag/CMSSW_7_4_5_ROOT5. The tag was created on top of branch: https://github.com/cms-sw/cmssw/tree/CMSSW_7_4_ROOT5_X

cmsbuild commented 9 years ago

Queuing Jenkins build for the following architectures: slc6_amd64_gcc491 You can abort the build by writing "Abort" in a comment. I will delete the release, the cmssw and cmsdist tag, and close the issue. You can't abort the upload once at least one achitecture is being uploaded. If you are building cmssw-tool-conf first, I will wait for each acrhitecture to finish to start the build of cmssw.

cmsbuild commented 9 years ago

The build has started for slc6_amd64_gcc491 in cmsbuild15. You can see the progress here: https://cmssdt.cern.ch/jenkins/job/build-release/341/console CMSDIST Branch: IB/CMSSW_7_4_X/stable, PKGTOOLS Branch: V00-22-XX

cmsbuild commented 9 years ago

The was an error for slc6_amd64_gcc491. You can see the log here: https://cmssdt.cern.ch/SDT/jenkins-artifacts/auto-build-release/CMSSW_7_4_5_ROOT5-slc6_amd64_gcc491/341

davidlange6 commented 9 years ago

abort

cmsbuild commented 9 years ago

Deleting CMSSW_7_4_5_ROOT5:

-Release successfully deleted

-cmssw tag CMSSW_7_4_5_ROOT5 successfully deleted.

-I was not able to delete the cmsdist tag REL/CMSSW_7_4_5_ROOT5/slc6_amd64_gcc491. Probably it had not been created.

You must create a new issue to start over the build.