Release 15.3 proposal
zabil opened this issue · 6 comments
CD features
Installers
- #1388 - Automate installer testing
- #1342 - Solaris installer - Issues
- #1308 - Implement a plugin and Go update check
UI/UX enhancements
- #1404 - Redesign the pipeline configuration page
API enhancements
- #1392 - New dashboard JSON API optimizations
- #775 - API to trigger stage and job (carry over from 15.2)
Plugins
- #884 - Plugin response should get logged in go-server log
Bug fixes
- #917 - SCM end-point - backend issues
- #1026 - [READ ONLY] Some actions not disabled
- #1008 - Read only mode Go server issues
- #933 - Without server restart server health messages do not get removed when plugins are deleted
- #1335 - Console log - scroll to end of logs does not happen by default
- #1058 - Temporary console log issues - part 2
- #1376 - New console log - Grunt (time-grunt) output not rendered correctly
- #1349 - New console log - last lines obscured
- #1343 - Cannot delete user with special character
- #1321 - Inconsistent & Incomplete error messages on editing environment variables.
- #1279 - Add user needs a spinner while searching for user
- #1272 Environment variables fields get cleared on validation errors
- #1275 - Standard out and standard error continues to write to an old log file
- #1233 - Agent has no cookie set / AgentNoCookieSetException after updating GUID
- #1154 - Restarting Go server causes Perforce materials to stop functioning
- #1132 The entirety of JUnit XML files is skipped if they are minified
- #1277- SVN cleanup doesn't clean the working dir
- #1235 - Use jQuery to build html and not string concatenation on the VSM page
- #1115 - VSM does not get displayed for SVN with externals
- #1243 - Pipeline does not use latest material
Performance fixes
- #838 - Fix cruise config xml save performance issues [on going - across releases]
- #1044 - Incompatible revisions causing 100% CPU load
- #234 - Upgrade to TFS SDK 12.0.1
- #1256 - 100% CPU and Memory utilisation when creating a fetch artifact task in a template
Technical debt
- #1085 - Migrate from twist tests to gauge (carry over from 15.2)
- #1086 - Support for JDK 8 (carry over from 15.2)
- #1088 - Add a performance pipeline to build.go.cd (carry over from 15.2)
- #1373 - Get rid of jetty6
See also -
- Release 15.2 for the previous release.
#1133 shouldn't be under 'Performance fixes' . It does not improve xml performance, it only provides a way to not use xml at all.
It is definitely a feature. It could also be under plugins because it introduces new extension point.
Feature request: Order tasks in alphabetical order (and ability to remove tasks you don't want)
Feature request: Assigning pipelines to an environment permissions. Users besides System Administrators, should be able to assign pipelines to an environment.
Feature request: AD integration and user permissions. With LDAP integration enabled, you should be able to manage user permissions with AD security groups as well as individual users. Unfortunately, currently GO does not recognize security groups.
@cholmes1111: Here are some GitHub issues where those features have been brought up before:
#1441 - Roles for assigning pipelines to environments
#134 - AD groups and integration
#1404 and #1496 - Probably the right places for talking about ordering tasks
As I've said before in other tickets, this is an open-source project (yes, some core contributors and infrastructure are supported by an organization, but all development to the core happens out in the open) and contributions are key. Not everything asked by everyone will get done, unfortunately. But, as a project, pull requests are always welcome and we help people work on anything they're interested in (by pairing with them, by explaining how they can start and helping them with setup if needed).
Currently, for 15.3, this is the work in progress and that is a lot of work. Hope that makes sense. Thanks!
Not to say your requests and ideas are not valuable, of course. :) I think what you say about ordering makes complete sense. My response was more about slotting that work in, and deciding what to work on.