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
We have duplication of ways to represent a similar process.
A while ago we introduced Build.IsInvalid to be used when a build fails to start but has already been created in the database, such as if the Jenkins call fails.
Suggest instead to only use the Failed build status. Migration could be done easily by a single SQL query of something like:
UPDATE build SET status=3WHERE isInvalid=1
And then drop the isInvalid column
We could introduce a FailedStatus column that is a free-text field of why it failed, and then we could use that to show to the user the reason for it failing (when we know the cause, such as connection refused on contacting Jenkins).
The text was updated successfully, but these errors were encountered:
applejag
added
prio/1
Low priority. "Nice to have"
chore
Routine task, refactoring, or other changes not affecting end-users directly.
labels
Feb 28, 2022
We have duplication of ways to represent a similar process.
A while ago we introduced
Build.IsInvalid
to be used when a build fails to start but has already been created in the database, such as if the Jenkins call fails.Suggest instead to only use the
Failed
build status. Migration could be done easily by a single SQL query of something like:And then drop the
isInvalid
columnWe could introduce a
FailedStatus
column that is a free-text field of why it failed, and then we could use that to show to the user the reason for it failing (when we know the cause, such as connection refused on contacting Jenkins).The text was updated successfully, but these errors were encountered: