Allow access controlled job in the scheduler

Registered by Paul Larson on 2011-11-03

For tests that have restrictions on their results distribution, we can't run them in the scheduler currently without making the raw output public. For these to maintain privacy, the scheduler job has to be restricted to disallow public display.

This is needed for toolchain testing for instance

Blueprint information

Status:
Complete
Approver:
Paul Larson
Priority:
High
Drafter:
Michael Hudson-Doyle
Direction:
Approved
Assignee:
Michael Hudson-Doyle
Definition:
Approved
Series goal:
Accepted for trunk
Implementation:
Implemented
Milestone target:
milestone icon 2012.03
Started by
Michael Hudson-Doyle on 2012-03-09
Completed by
Michael Hudson-Doyle on 2012-04-02

Related branches

Sprints

Whiteboard

Meta:
Headline: LAVA now supports running access restricted jobs in the scheduler
Acceptance: Private jobs can be submitted such that the details of the job are restricted to only those who would otherwise have access to the results.
Roadmap id: LAVA2012-DATA-PUBLISHING-POLICY

(?)

Work Items

Work items:
make testjob a restrictedresource: DONE
enforce permissions on job view: DONE
copy access control fields from target bundle stream at submit time: DONE
check that user can submit to target bundle stream at submit time: DONE

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.