Project

General

Profile

Feature #8754

Require unique job names

Added by Evgeny Novikov over 1 year ago. Updated over 1 year 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

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

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

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

Actions

History

#1

Updated by Evgeny Novikov over 1 year ago

#2

Updated by Evgeny Novikov over 1 year ago

  • Blocks Feature #8706: Permanent (pretty) URLs for error traces added
#3

Updated by Vladimir Gratinskiy over 1 year ago

  • % Done changed from 0 to 100
  • Status changed from New to Resolved
  • Due date set to 03/14/2018

Implemeted in branch "manage-extension". But now job names are not saved in versions.

#4

Updated by Evgeny Novikov over 1 year ago

  • % Done changed from 100 to 0
  • Status changed from Resolved to Open

Vladimir Gratinskiy wrote:

Implemeted in branch "manage-extension". But now job names are not saved in versions.

Perhaps, this is the reason why after migration I don't see job names (titles) when editing or copying jobs. Moreover, I have to enter each time when performing these operations. This seems strange. Besides, I suggest that all previously specified job names/titles are silently removed that also doesn't match the job history idea. Why did you miss job names in job versions?

#5

Updated by Vladimir Gratinskiy over 1 year ago

The bug with editing job names was fixed. I miss job names in versions because of, for example, uploading jobs. When you populated jobs (before unique jobs patch) second time, you had some jobs with the same names. Then you rename populated jobs, and then names become unique. But if you try to upload one of these jobs, you get an error as the algorithm of uploading is creating job with first version and then applying other versions one by one. And on 1st step names are not unique. To fix all such problems I need to reqrite a lot of functions from zero.

#6

Updated by Evgeny Novikov over 1 year ago

  • Status changed from Open to Closed

Okay, let's do this one day later. I merged the branch to master in 80bae96b.

#7

Updated by Evgeny Novikov over 1 year ago

Also available in: Atom PDF