RELEASED: Public: 2020-09-09
New features
-
Enable link to build in the first line of the message (STICKY-717)
Before, the initial line of the Slack message included a reference to the build number, but did not link to the build.
Now the build reference on the first line of the Slack message links to the build.
-
Verify if the user exists before adding a new user (STICKY-670)
When adding a new user, if a user is already configured or the user does not exist, the administrator will now receive a warning message. Also, if the user is already configured, the message will prevent the admin from adding the new user.
The same validation is checked if the admin is updating an existing user.
Resolved issues
-
Truncate the cause of failure when it is too long (STICKY-696)
When the build fails, the cause of failure is sent as part of the Slack notification. Sometimes the failure was returning an error trace instead of a summary message, which could have caused that notification section overflow and might have prevented the notification from being sent.
This fix truncates those traces that are too long so the message is always sent.
-
Improve build logs (STICKY-669, STICKY-682, STICKY-683)
The build logs are more consistent and accurate.
-
Improve build logs (STICKY-669, STICKY-682, STICKY-683)
The build logs are more consistent and accurate.
-
Remove direct link to Slack Integration config page from User configuration page (STICKY-662)
Within the User configuration page there is a section for Slack Integration that only provides a link to the Slack configuration page. Since there is a link in the left navigation menu, which is always available for the user, this internal link on the User configuration page is useless and unnecessary.
With this fix, the internal direct link on the User configuration page has been safely removed without breaking backward compatibility.
-
Internal changes to streamline development. Not user visible. (STICKY-681)