Project

General

Profile

Actions

Feature #8754

closed

Require unique job names

Added by Evgeny Novikov over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Urgent
Category:
Bridge
Target version:
Start date:
03/13/2018
Due date:
03/14/2018
% Done:

0%

Estimated time:
Published in build:

Description

A long ago we found that in general using job names to reflect all job settings is an awful practice. That's why in Klever in the production mode jobs come with all settings and specifications. Nevertheless, using job names to reflect the most important distinguishing characteristics of corresponding jobs seem to be a valid and useful practice. Moreover, this assumes that all jobs should have unique names. Otherwise, somebody does useless work launching undistinguishable jobs.

I forgot that this feature is required for automated starting job solutions when one knows job names but doesn't know artificial job identifiers.


Related issues 3 (0 open3 closed)

Related to Klever - Feature #8757: Keep job titles in historyClosedVladimir Gratinskiy03/15/201807/11/2019

Actions
Blocks Klever - Feature #8297: Support command-line interfaceClosedVladimir Gratinskiy07/14/201703/05/2018

Actions
Blocks Klever - Feature #8706: Permanent (pretty) URLs for error tracesClosedVladimir Gratinskiy02/06/2018

Actions
Actions

Also available in: Atom PDF