History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-3690
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Robert Saladra
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
QuickBuild

Unable to set empty value for 'Commit Status Context' field (GitHub repository) and 'Commit Status Name/Context' (GitLab repository)

Created: 25/Mar/21 02:25 PM   Updated: 01/Jun/21 03:03 PM
Component/s: None
Affects Version/s: 10.0.28, 11.0.1
Fix Version/s: 11.0.3

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
File Attachments: None
Image Attachments:

1. repos.png
(66 kb)
Environment: Ubuntu 20.04 docker image


 Description  « Hide
Steps to reproduce for GitHub repository:
1. Go to configuration's Repositories tab
2. Add new repository, select type GitHub
3. Fill mock value in 'Fetch URL' field
4. Delete default value in 'Commit Status Context' field
5. Save repository

Expected result:
Field 'Commit Status Context' is empty.

Actual result:
Value in 'Commit Status Context' field is filled with default value: ${configuration.name}.

Workaround:
Fill field with value ${""}

Same behavior is observed for repository type GitLab (with different default value), and when filling field with spaces. Corresponding field are not present in configuration XML obtained via REST API.

 All   Comments   Work Log   Change History      Sort Order:
Robin Shen [26/Mar/21 12:24 AM]
This works fine at my side. Do you have any auto-fill plugin running in your browser to fill the cleared value automatically again?

Robert Saladra [26/Mar/21 08:24 AM]
No, I have autofill disabled on all sites. Field is not filled when checking Configuration XML (/rest/configurations/<config_id>), please check attached screenshot

Change by Robert Saladra [26/Mar/21 08:24 AM]
Field Original Value New Value
Attachment repos.png [ 10880 ]

Robin Shen [26/Mar/21 08:38 AM]
Which browser and OS you are accessing QB from?

Robert Saladra [26/Mar/21 08:53 AM]
Chrome 89, Windows 10 20H2. Same story on MS Edge and Windows Server 2019 + IE

Robin Shen [26/Mar/21 10:27 AM]
Got it reproduced now. Will be addressed in next patch release.

Thx!

Change by Steve Luo [01/Jun/21 03:03 PM]
Status Open [ 1 ] Resolved [ 5 ]

Change by Steve Luo [01/Jun/21 03:03 PM]
Fix Version/s 11.0.3 [ 12015 ]