5.11.2

Bug Fixes

1. Update node init timeout to 45 minutes so that aarch64 custom nodes can be init successfully in first attempt.
2. UI should not create any views while the delete is processing
3. clicking on deleted branch name shows appropriate error message
4. Console error when we select dry run
5. Build Job console window scroll issue
   • Console window does not scroll to the last section when viewing an already processed job
   • Console window does not jump to the last processed section when expanding a section that has been processed in a processing job
6. Test tab on the runs page does not show console errors.
7. Error in sync when http is disabled for bbs
   • BBS normalized project fields are parsed more carefully to avoid any exception error
8. Gitlab triggered by column showing incorrect values
9. Job dashboard displays correct "started at" and duration
10. Dockerhub integration does not export Url environment variable
11. Add System Node (Admin) page is broken
    • WWW now queries for the sshKey system integration without passing a master integration name
12. Use caller's api token instead of serviceUser's token while deleting subscriptions
13. UI sidebar is now an Angular directive
14. API parsing wrong hostname when posting state files

Features

1. runSh jobs can be triggered for PR closed webhooks from GitHub, BitBucket and GitLab

   • A new setting buildOnPullRequestClose: true on gitRepo resources enables this feature
   • Please refer to docs-gitRepo for more information

2. Build status can be updated to cancelled/timeout/failed by super users

New Integrations

As we continue to clean up our integrations, several existing integrations have been deprecated and replaced with more generic/flexible versions. No action is necessary

Updated integrations:

1. Azure Keys Integration next generation launched

   • The current Azure integration will be replaced by the next generation of Azure integration of type generic. This is being done as part of standardizing how Shippable works with integrations and allows us to use it in a generic fashion as opposed to duplicating it for every implementation. All existing functionality works as it is and the new azure integration will work exactly the same way as the deprecated integrations would work.

   • If you are using the deprecated integration in your Assembly lines, it will continue to work without any disruptions. You can update it or delete it, but a new instance of the deprecated version cannot be created.

   • Refer Docs Links