Difference between revisions of "Gridexport"

Latest revision as of 18:14, 20 July 2024

This page is obsolete. Making tarballs of locally-built code is now done using Muse#Tarball.

This page will be deleted once we are sure that nothing links to it.

Revision as of 16:34, 29 January 2018 (view source) Kutschke (talk \| contribs) (Created page with "The ups package gridexport will export a build of Mu2e Offline or a build of a satellite release for use on a grid worker node. Until January 2018, the bluearc disk /mu2e/app...")		Latest revision as of 18:14, 20 July 2024 (view source) Kutschke (talk \| contribs)
(22 intermediate revisions by 4 users not shown)
Line 1:		Line 1:
−	~~The ups package gridexport will export a build of Mu2e Offline or a build~~ of ~~a satellite release for use on a grid worker node~~.	+	<font size=+2>This page is obsolete. Making tarballs of locally-built code is now done using [[Muse#Tarball]].</font>

−	~~Until January 2018, the bluearc disk /mu2e/app was mounted on worker nodes on Fermigrid; it was possible to build code on~~ that ~~disk and run it on Fermigrid. That is no longer possible. If you have a build of Mu2e code on /mu2e/app, or in your home directory on the mu2egpvm machines, you can use gridexport~~ to ~~produce a bzipped tar file of your build area. You can then submit a grid job that copies the bzipped tar file, unpacks it and runs the code that~~ it ~~finds inside~~.	+	This page will be deleted once we are sure that nothing links to it.