Opened 10 years ago

Last modified 9 years ago

#731 new defect

IZ3158: job context should be exported into job's environment

Reported by: templedf Owned by:
Priority: low Milestone:
Component: sge Version: 6.2u3
Severity: Keywords: execution
Cc:

Description

[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=3158]

        Issue #:      3158             Platform:     All      Reporter: templedf (templedf)
       Component:     gridengine          OS:        All
     Subcomponent:    execution        Version:      6.2u3       CC:    None defined
        Status:       NEW              Priority:     P4
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    pollinger (pollinger)
      QA Contact:     pollinger
          URL:
       * Summary:     job context should be exported into job's environment
   Status whiteboard:
      Attachments:

     Issue 3158 blocks:
   Votes for issue 3158:


   Opened: Mon Oct 5 07:02:00 -0700 2009 
------------------------


The job context settings for a job should be exported into that job's environment so that the prolog, epilog, and the job itself can easily
make use of them.

   ------- Additional comments from reuti Mon Oct 5 07:18:51 -0700 2009 -------
Looks similar to http://gridengine.sunsource.net/issues/show_bug.cgi?id=315

Problem with an export is: you can change the content of a context variable while the job is running from the command line (and this would be to keep and change the job's behavior).
So instead of exporting it, it would be better accessible with a local command without the need of making the exec host a submit host. Also related to:

http://gridengine.sunsource.net/issues/show_bug.cgi?id=1259

regarding the fact, to have a subset of SGE commands available inside the jobscript while disregarding the $JOB_ID as it's implicit.

   ------- Additional comments from joga Tue Dec 1 03:51:05 -0700 2009 -------
see also IZ 315

Change History (0)

Note: See TracTickets for help on using tickets.