kubesphere / kubesphere/ks-devops

the user to replay pipeline is not current user

Open
#1,042 0 comments 0 reactions 0 assignees View on GitHub
kind/bug
Dominant language
Go
Stars
164
Forks
140
PR merge metrics
No merged PRs in 30d

Description

### What is version of KubeSphere DevOps has the issue?

3.5.0

### How did you install the Kubernetes? Or what is the Kubernetes distribution?

_No response_

### What happened?

1. the user to replay pipeline is not current user:
![image](https://github.com/kubesphere/ks-devops/assets/14155338/954f3cbb-aa2a-477c-9ec5-8718a0295292)
the pipelinerun#5 is created by replay pipelinerun#2 by current user dong,but last message is ‘Started by user admin’ that not current user dong;
URL: POST /kapis/clusters/host/devops.kubesphere.io/v1alpha2/devops/proj1t4knk/pipelines/pl1/runs/2/replay/

2. the last message should be latest item in causes: Replayed #2
![image](https://github.com/kubesphere/ks-devops/assets/14155338/7338ad26-ca6d-4628-83b5-deade3c46cee)

### Relevant log output

_No response_

### Additional information

_No response_

Contributor guide

Open the contributing guide

Research direction

Start at POST /kapis/clusters/host/devops.kubesphere.io/v1alpha2/devops/proj1t4knk/pipelines/pl1/runs/2/replay/ and trace how the replay creates pipelinerun #5 and populates its causes. Compare the displayed creator with the current user dong and verify that the latest causes item is “Replayed #2”; done means both messages show the correct current user and latest replay cause.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
backend-api-design, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.