Skip to content
This repository has been archived by the owner on May 17, 2021. It is now read-only.

Can't edit job command. Only name and user. #120

Closed
Huron opened this issue May 27, 2015 · 4 comments
Closed

Can't edit job command. Only name and user. #120

Huron opened this issue May 27, 2015 · 4 comments
Assignees

Comments

@Huron
Copy link

Huron commented May 27, 2015

image

@Huron Huron changed the title Cant edit job command. Only name and user. Can't edit job command. Only name and user. May 27, 2015
@jamesrwhite
Copy link
Owner

This is actually by design, the way jobs are stored does not allow the command to be edited because a hash of the command/host is used to identify the job.

@jamesrwhite jamesrwhite added this to the future milestone Jun 27, 2015
@jamesrwhite
Copy link
Owner

Going to re-open this to serve as a reminder for something to investigate if it can be achieved in future versions.

@jamesrwhite jamesrwhite reopened this Jun 27, 2015
@jamesrwhite jamesrwhite modified the milestones: 0.8, future Sep 9, 2015
@jamesrwhite
Copy link
Owner

Moment of inspiration, this is possible after all!

@jamesrwhite jamesrwhite self-assigned this Sep 9, 2015
@jamesrwhite jamesrwhite modified the milestones: future, 0.8 Sep 19, 2015
jamesrwhite added a commit that referenced this issue Nov 8, 2015
@jamesrwhite
Copy link
Owner

So 30f6db1 makes this possible now with the caveat that this is a permanent change to the job so for example when you go back and look at an old execution it will be confusing now as it is tied to the latest copy of the job.

e.g

job 1 command = "echo 1"
job 1 execution 1 output = "1"
update job 1 command to = "echo 2"
go back and view job execution 1 and it now says the command is "echo 2" even though the output remains as "1"

I can think of a few different ways to handle this:

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants