Changes between Version 10 and Version 11 of Admin/StandardOperatingProcedures/InstallSoftwareFromSource

Timestamp:

May 10, 2019, 1:47:59 PM (6 years ago)

Author:

Mikael Brandström Durling

Comment:

--

Admin/StandardOperatingProcedures/InstallSoftwareFromSource

@@ -11 +11 @@
 Detailed procedure (not involving software specifics on how to set installation location).
 
+  1. Create a ticket regarding the software install, unless the user has already done so.
   1. `module load gridsw` to enable software installation related modules.
   1. Run the command `gridsw` to switch primare group to mykopat-grid-software. This must be done prior to any work on software in the shell you will be working with.
@@ -16 +17 @@
   1. Dowload software source or binaries archive to /opt/sources
   1. Unzip archive, and if necessary configure/compile whith correctly specified installation path
-  1. Install package into the the folder obtained at step 3. (This should be done as your ordinary user, in a shell where you have run the `gridsw` command.) If the install script/makefile/install procedure complains about denied permissions, DO NOT use sudo. You should rather check that all install paths etc are correct.
+  1. Install package into the the folder obtained at step 3. (This should be done as your ordinary user, in a shell where you have run the `gridsw` command.) If the install script/makefile/install procedure complains about denied permissions, DO NOT USE SUDO. You should rather check that all install paths etc are correct.
   1. Write a module file (copy and edit previous version or so) to reflect the new software version you have installed. The module file should be created in /opt/modulefiles_staging/ and named SOFTWARE/VERSION (or SOFTWARE/VERSION.lua if you prefer to write a Lua module).
   1. Add the module file to subversion with `svn add` (you might have to add the directory too, if you had to create it) and then commit the module file with svn commit.
-  1. Ask a system administrator to publish the newly installed software.
+  1. Update the wiki page for the software referenced from the software index found on [[Software]] (or create a new one). This page should, as a bare minimum, contain any local modifications or specifics, and a link to a manual for the software.
+  1. Document any deviations from the documented install procedure of the software in the ticket.
+  1. Ask a system administrator to publish the newly installed software by providing SOFTWARE and VERSION as per above, as well as ticket ID.
+
+=== Publishing of software
+This step needs a user with full sudo rights.
+
+  1. Verify the software (ie. load the module, ensure that commands are available after loading).
+  1. Publish software by running `grid-pubsw SOFTWARE VERSION TICKETID`. The script will ask for your password in order to commit some changes to the svn repository, as well as for setting permissions on software folders. This step will also close the software install ticket.
+