You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see in Jenkins frontend plugin the data for below cases is not coming properly
multibranch pipeline in case branch is deleted , the data is still showing in the plugin but data is not proper with links not working and no build data on click of build column.
In case a job is created and no build is triggered or no build exists the result is same as above.
👍 Expected behavior
I purpose to filter the data and get only those builds where there is even single build exists
👎 Current Behavior
I see in Jenkins frontend plugin the data for below cases is not coming properly
multibranch pipeline in case branch is deleted , the data is still showing in the plugin but data is not proper with links not working and no build data on click of build column.
In case a job is created and no build is triggered or no build exists the result is same as above.
👟 Reproduction steps
Go to any catalog and go to jenkins plugins TAB , make sure there is no build exists in Jenkins for the repo.
you will see the data is not proper and links are not working properly.
📃 Provide the context for the Bug.
No response
👀 Have you spent some time to check if this bug has been raised before?
The issue might be related to Jenkins marking the branches as deleted. Probably we would need to handle this corner case in the plugin. Contributions are welcome.
📜 Description
Hi Team
I see in Jenkins frontend plugin the data for below cases is not coming properly
👍 Expected behavior
I purpose to filter the data and get only those builds where there is even single build exists
👎 Current Behavior
I see in Jenkins frontend plugin the data for below cases is not coming properly
👟 Reproduction steps
Go to any catalog and go to jenkins plugins TAB , make sure there is no build exists in Jenkins for the repo.
you will see the data is not proper and links are not working properly.
📃 Provide the context for the Bug.
No response
👀 Have you spent some time to check if this bug has been raised before?
🏢 Have you read the Code of Conduct?
Are you willing to submit PR?
None
The text was updated successfully, but these errors were encountered: