`tkn ct start <cluster-task-name> -L` does not use the `--timeout` value of previous run

[VeereshAradhya]

Versions and Operating System

• Kubernetes version:

  Output of kubectl version:

  Client Version: version.Info{Major:"1", Minor:"10+", GitVersion:"v1.10.0+b3b92b2", GitCommit:"b3b92b2", GitTreeState:"clean", BuildDate:"2020-07-15T09:27:21Z", GoVersion:"go1.14.3", Compiler:"gc", Platform:"linux/amd64"}
  Server Version: version.Info{Major:"1", Minor:"18+", GitVersion:"v1.18.3+08c38ef", GitCommit:"08c38ef", GitTreeState:"clean", BuildDate:"2020-07-30T18:43:47Z", GoVersion:"go1.13.4", Compiler:"gc", Platform:"linux/amd64"}
  

• Tekton Pipeline version:

  Output of tkn version or kubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'

  $ tkn version
  Client version: 0.11.0
  Pipeline version: v0.14.3
  Triggers version: v0.6.1
  
  

• Operating System:

  Linux
  

Expected Behavior

tkn ct start <cluster-task-name> -L should consider timeout value of previous taskrun

Actual Behavior

tkn ct start <cluster-task-name> -L is not considering timeout value of previous taskrun

Steps to Reproduce the Problem

1. Start a cluster task providing timeout value tkn ct start <cluster-task-name> --timeout
2. Start the same cluster task using -L option tkn ct start <cluster-task-name> -L
3. Check the timeout values in the taskruns

Additional Info

Command execution logs

$ tkn ct start first-cluster-task -p first-param=check --timeout 5m
TaskRun started: first-cluster-task-run-jljmf

In order to track the TaskRun progress run:
tkn taskrun logs first-cluster-task-run-jljmf -f -n veeresh-testing-windows
[varadhya@localhost testing]$ 
[varadhya@localhost testing]$ 
[varadhya@localhost testing]$ tkn tr describe first-cluster-task-run-jljmf
Name:              first-cluster-task-run-jljmf
Namespace:         veeresh-testing-windows
Task Ref:          first-cluster-task
Service Account:   pipeline
Timeout:           5m0s
Labels:
 app.kubernetes.io/managed-by=tekton-pipelines
 tekton.dev/clusterTask=first-cluster-task
 tekton.dev/task=first-cluster-task

🌡️  Status

STARTED          DURATION    STATUS
22 seconds ago   ---         Running

📨 Input Resources

 No input resources

📡 Output Resources

 No output resources

⚓ Params

 NAME            VALUE
 ∙ first-param   check

🦶 Steps

 NAME         STATUS
 ∙ step-one   Running

🚗 Sidecars

No sidecars
[varadhya@localhost testing]$ 
[varadhya@localhost testing]$ 
[varadhya@localhost testing]$ tkn ct start first-cluster-task -L
TaskRun started: first-cluster-task-run-5cr67

In order to track the TaskRun progress run:
tkn taskrun logs first-cluster-task-run-5cr67 -f -n veeresh-testing-windows
[varadhya@localhost testing]$ 
[varadhya@localhost testing]$ 
[varadhya@localhost testing]$ tkn tr describe first-cluster-task-run-5cr67
Name:              first-cluster-task-run-5cr67
Namespace:         veeresh-testing-windows
Task Ref:          first-cluster-task
Service Account:   pipeline
Timeout:           1h0m0s
Labels:
 app.kubernetes.io/managed-by=tekton-pipelines
 tekton.dev/clusterTask=first-cluster-task
 tekton.dev/task=first-cluster-task

🌡️  Status

STARTED          DURATION    STATUS
17 seconds ago   ---         Running

📨 Input Resources

 No input resources

📡 Output Resources

 No output resources

⚓ Params

 NAME            VALUE
 ∙ first-param   check

🦶 Steps

 NAME         STATUS
 ∙ step-one   Running

🚗 Sidecars

No sidecars

[danielhelfand]

Should be similar to #863. Just need to add the timeout property from the last run.

[danielhelfand]

/assign