AgileSCM Release 4.1. AgileSCM Release 4.0. AgileSCM Release 3.2. New Features. Bug Fixes. New Features. Bug Fixes

Transcription

1

2 AgileSCM Release 4.1 Project Dashboard - get a complete overview of the status of your project. View the SSH public key through the AgileSCM interface. This allows you to post the key to Git and Mercurial hosting services such as Bitbucket, GitHub or Atlassian Stash. New JIRA plugin configuration for the AgileSCM JIRA Driver. Configure the JIRA plugin directly through the JIRA interface. JIRA plugin now compatible with JIRA5. You can now install directly in the JIRA plugin manager from the Atlassian Marketplace. ReviewBoard 1.6 support. Long titles in list views are now truncated and expanded when you hover over the text. UCM-438: Delivery of hotfix activities with merge conflicts causes baseline issue. UCM-338, UCM-342: Unable to create Git and Mercurial components with Tomcat-deployed AgileSCM. UCM-449: Licence not working with AgileSCM deployed on port 443 via HTTPS. UCM-437: Problem with hotfix tag creation for read-only Mercurial components. UCM-433: Change of initial revisions not recognised. UCM-407: Make merge conflicts in root directory more obvious, previously not always clear if a merge conflict is detected at the root directory of an activity branch. UCM-404: Disabling ReviewBoard for a running project with outstanding reviews causes Integration tab to fail. UCM-323: Multiple "None" baselines displayed for component revisions. AgileSCM Release 4.0 Introducing the all new interface! Restrictive mode, allowing people without the time to request an evaluation license to quickly get up and running! New installer, to remove some of the headaches of the old one. New 'in browser' configuration editor available to database administrators! Eclipse plugin no longer shows deleted activities API Get checkout commands - no longer requires a workspace, as this was never used API Get Activities no longer returns deleted activities API Get Projects no longer returns deleted projects API Get Changeset was returning invalid svn diff's in certain situations After creating a git repository Agile SCM now runs "git update-server-info" to update git ready for http requests The Jira driver used to fall over when an issue was created from Jira, then deleted in Agile SCM then a new issue created again from the same ticket, this is no longer the case AgileSCM Release 3.2

3 AgileSCM 3.2 is a roll-up release, providing minor fixes and enhancements. Please note that this release is currently only supported with the standalone SQLite database. Support for mysql and tomcat servers will be incoming in the next release. On the manage project page, truncated displayed portion of link and show full link as tool-tip Added 2 new api functions: Get Latest Baseline For Project Get List Of Activities To Be Baselined For Project Added the ability to delete users Made Jira links clickable on the import external issues page Improved the search functionality on the edit user page Improved an error message on jira driver for a non Agile SCM user Fixed a bug which when disabling ReviewBoard breaks Edit Activity Fixed an issue with internet explorer not sending the correct post data on the Selective checkout page Made pulled external issue assign to no-one if user is not a member of the project for which the issue is being pulled Re-assign activity page had an unnecessary column Made the releases page default to a single project Fixed a bug with editing a project with the same name as a previously deleted project Fixed an issue with Reviewboard and hotfixes Fixed a rare case when Reviewboard could create erroneous reviews when a delivery failed Fixed a rare case in which hotfixes could have incorrect content when a conflict happend Fixed an issue with incorrect changeset for hotfixes on hotfixes being reported AgileSCM Release 3.1 AgileSCM 3.1 is a roll-up release, providing minor fixes and enhancements. Please note that this release is currently only supported with the standalone SQLite database. Support for mysql and tomcat servers will be included in an upcoming release. The Eclipse plugin has been updated to integrate the functionality of the Java Checkout GUI. This gives you more control over the checkout process such as where to place files and also allows you to switch existing workspaces. The Java Checkout GUI has seen some minor improvements: Browse button now starts from the currently selected workspace folder (if it exists). Pressing enter in the password field now starts the checkout operation. The Open Folder button is now always accessible (it was previously greyed out until you pressed Checkout). Project Link - All projects now have access to a blank text field to place the address or location of a project homepage.

4 UCM-362: Improve handling of errors from the CM backend. UCM-366: Disabling ReviewBoard for a project with pending reviews impacts Edit Activity view. UCM-375: Pass/fail buttons appear for passed reviews on Integrate Tab. UCM-361: Addressed issue with assignments in API function getactivity. AgileSCM Release 3.0 AgileSCM 3.0 is a feature release providing Mercurial support, pluggable database back-ends (both MySQL and Oracle 10 are supported) and the all new platform-independent WAR distribution, which can be deployed on Tomcat application servers. Mercurial Support AgileSCM now provides full support for components stored in Mercurial repositories. Mercurial is a distributed version control system, similar in functionality to Git. Pluggable Database Back-ends AgileSCM now allows you to store its data in a MySQL or Oracle database. Previously, all data was stored in a local database file maintained by SQLite3. Note that the SQLite3 solution will still be suitable for most environments. However, in environments where MySQL and Oracle is used to store company data, it may be worth using the enterprise class database system and benefit from existing backup strategies and better scalability (i.e. dealing with a large number of parallel requests). WAR Distribution The all-new WAR distribution is a fully platform-independent solution, which should run on all platforms providing Java and the Tomcat application server. The WAR distribution has the same look-and-feel and functionality as the standalone version of AgileSCM. However, please note that you must use a MySQL or Oracle database with the WAR distribution. You cannot use an SQLite3 database file. Improved Deliver/Integrate Performance The performance of deliver and integrate operations has been improved substantially. If you have large components containing a lot of files or large files, you should see a substantial increase in performance on delivery and integration of activities. Fewer Conflicts on Rebased Activities You will now see fewer conflicts when rebased activities are integrated. The way AgileSCM merges activities has been changed such that all merge operations are now performed on the activity branch. This allows AgileSCM to merge activities back to the integration branch using the "--reintegrate" option of Subversion, which greatly reduces the risk of spurious conflicts. In previous versions of AgileSCM, rebasing from the integration branch into an activity branch would result in reflective merge conflicts for the rebased changes when the activity was integrated. Performing all merges on the activity branch solves this issue.

5 Another benefit is that all manually resolved merge issues now become part of the changeset of the activity and are therefore much more traceable. Group Baselines Into Releases As the number of baselines grow, the Manage Baseline page can become harder to understand. AgileSCM now allows you to group baselines into product releases, allowing you to visualise which release a baseline was created for. Switch Development Workspace To New Branch Instead of performing a full checkout, you now have the option to switch an existing workspace for another activity on the same project to a new activity. This gives much better performance for large repositories. Improved List Sorting For all list views such as Manage Project, Edit Component, Edit Activity and Edit User, you can now click a number of table headings to sort the table based on that column. Click twice to sort in reverse order. Other You can now allow AgileSCM to automatically create a Subversion repository for you when you create a Subversion component. Please note that you must specify in the config file the URL to the base directory under which these repositories will be served. You can now see the changeset of an activity as Subversion diffs using the Java checkout GUI. If you have configured Subversion on your machine to use a graphical diff tool, it will pop up a diff window per changed file. Otherwise, the differences will simply be displayed in the log window of the Java checkout GUI. When your AgileSCM licence expires, AgileSCM will now redirect to you a view indicating that your licence is invalid rather than shutting down the AgileSCM server. Integrators can now check out a merge workspace prior to performing a merge. This allows you to review the results of a merge operation prior to actually performing the merge. Improved support for foreign language characters. AgileSCM has now been qualified to support special characters in all places in AgileSCM itself as well as Subversion, Git and Mercurial. However, please note the limitations of Git with respect to cross-platform support for special characters in file names. Please see /git.wiki.kernel.org/index.php/gitfaq#does_git_convert_encodings_of_file_names.3f You can now rebase activities from other activities of the same project, not just the project integration branch. You can now perform a rebase of an activity from the Integration tab. Edit Component now also lists the projects a component appears in. AgileSCM now makes sure that the database version is suitable on startup. This ensures that the database schema has been upgraded and makes upgrade issues much more obvious. Edit activity page now shows what baseline an activity is in (if any) ZD-18: Show if a component is shared - this is now displayed correctly on the Edit Project page. ZD-19: Read-only status not shown for shared components - this is now displayed correctly on the Edit Project page. ZD-23: Do not show the superfluous warning message about ifconfig not found in a certain path on Redhat and CentOS systems. ZD-45 (edit user should update the authz file) CB-2296: If you use two browser windows to show the To-do page for the same user, and if you then attempt to close or deliver the same activity from both browser windows, AgileSCM will now show a better error message, which indicates that the activity has already been closed/delivered.

6 CB-2224: Developer level activity status - AgileSCM will now show if a Developer has accepted or closed an activity on a per-developer basis in the Edit Activity list view. UCM You should be able to reuse component and project names of deleted projects/components UCM-306: Eclipse plugin fails on startup if there are activities in AgileSCM containing special characters. CB-2350: Unify checkout buttons on all pages - the buttons have been changed on all pages to look the same as on the To-do page. CB-2313: The Deliver option is now no longer visible until all other Developers assigned to the activity have closed it. The behaviour has not changed from previous releases of AgileSCM, where Deliver would act as Close until the last Developer. However, not showing the button makes the behaviour much clearer. UCM-295: Search fails on Edit Activity if you are not on the first page. UCM-286: Authz generation should use the configured SVN user name from the user's profile. Agile SCM Release 2.6 Agile SCM 2.6 is mainly a service release providing extensions to the Git integration as well as fixes for a number of issues. A limited number of smaller new features has also been included. The Agile SCM documentation can now be accessed directly through the web interface via the Help link. Both HTML and PDF documentation are available this way. For read-only components, project managers can now change the baseline used for a read-only component at any time during the life-time of the project. This allows you to switch to newer versions of a read-only component without having to start a new project in Agile SCM. You can now delete activities. This will hide activities from all views. You can now delete components. This will hide them from view but will not affect any existing projects that use those components. Agile SCM now requires all assignees of an activity to close before the activity can be integrated. Partial deliveries have now been disallowed to avoid confusion. The Agile SCM version number is now displayed in the web interface. This allows you to confirm the version that you have installed without referring to the log file. Links to edit activities have been added to the Assign Activity view. The Java checkout GUI will now prompt the user to create the workspace directory, if it does not exist. Select All buttons have been added to the Import User and Import Activity screens. Extensions to Git Integration: The change-set for an activity will now also show changes in Git components. Previously this had been explicitly excluded. Added ReviewBoard support for Git components. You can now rebase Git components. The Checkin button on the Java Checkout GUI has returned and now fully supports Git components. The Eclipse plugin now supports Git components. Completion of Rebranding to Agile ACM Eclipse plugin has been rebranded. Validator names for JIRA driver have been updated. Added support for both old UCM4SVN and new Agile SCM licences. Changed hotfix activities for previous hotfixes to now start from the previous hotfix's baseline rather than the previous hotfix's activity. Whilst this does not change the end result, it provides better traceability through the

7 Subversion branches. Error messages from the Git back-end have been improved. Edit Repository now supports domain-less repository URLs. Corrected top-level folder names for selective checkout. The browse button on the Java Checkout GUI now starts browsing from the folder selected in the GUI rather than always starting from the user's home directory. The sample database generator has been updated to support latest features of the database. Corrected Review tab to show external ReviewBoard ids rather than internal ids. Fixed error seen by Developers when attempting to view activities from other developers by clicking the link on the Manage Baseline page. Fixed problem where user-errors on the create component page (such as forgetting to provide a component description) could cause an incorrect form to be shown for a Git component. Improved rebase functionality such that when rebasing from another project it will no longer include baselines from the current project in the list. Fixed bug related to Custom Rebase and merge conflicts. The conflicts checkout script would not always select the correct baselines. Changed Git integration to use workspace config setting for all temporary data created. Removed redundant is_discarded field from Edit Repository view. Fixed problem in Java Checkout GUI where the overwrite warning would sometimes not be shown. Fixed problem with checkout of project integration branch for projects with spaces in their name. Removed spurious shared-component activities from the hofix-baseline view on the Manage Baseline tab. In the JIRA plugin made sure that projects that have been deleted in Agile SCM do not show up. Fixed help text for Trac integration fields on the New Project tab. Improved Delete Project confirmation message if no activities are affected. Added Agile SCM favicon for tabbed browsers. For Developers delivering activities, fixed problem with non-functional to-do page after confirming a merge following a merge conflict. Fixed checkout scripts for read-only shared components. Fixed issue with more than the expected ten recently completed reviews being shown on Review Tab. Fixed corner-case issue of inconsistent states being shown for some activities depending on which tab is opened. Agile SCM Release 2.5 UCM4SVN has been renamed to Agile SCM to better reflect its purpose. As of the 2.5 release, Agile SCM is no longer tied to Subversion as its only configuration management interface and now also supports the Git configuration management system. Git Components Agile SCM 2.5 introduces support for components managed in Git repositories. Projects can be purely Git or Subversion, or they can consist of a mix of Subversion and Git components. Fore more details on Git, please see Hotfix Activities Hotfix activites allow you to branch off from an existing baseline and apply changes on top of the baseline in order to provide a hotfix or service releases. Hotfix activities allow you to minimise the changes to a baseline such that you can provide targeted fixes without picking up other changes that have been integrated to the project integration

8 branch since the baseline was originally made. Rebase from Other Projects Agile SCM now allows you to selectively rebase some components in an activity from another project. This allows you to selectively share information between projects without having to go as far as using a shared integration branch (i.e. use a shared component). Display only Relevant Information Agile SCM will now limit information it displays based on your project membership. Information about items relating to a project will only be shown if the user is a member of the project. Secure HTTPS Access You now have the option to secure access to Agile SCM though HTTP. See the Administration Guide for details on how to configure this setting. Deleting Projects It is now possible to delete projects in Agile SCM, which will hide any information associated with a deleted project from view. This includes activities and baselines associated with the project. Other Enhancements Java checkout GUI will now create the workspace directory if it does not exist yet. You can now pass or fail reviews directly from Integrate tab. Improved load performance of Integrate tab for installations with a large number of activities. Edit checkout links to the Edit Activity page. Now showing activity status on the Edit Activity page. Improved display of changeset information on the Edit Activity page. The Agile SCM logo now links to the current server instance rather than the Clearvision CM Home Page. Addressed issues with some activities imported from JIRA with special characters not merging until the description was changed. Prevent Eclipse plugin from hanging during checkout of very large activities. Fixed issue with Search filters on list pages such as Manage Project and Edit User not returning correct results. UCM4SVN Release Orchestra Build Bug fixes: This build was a re-pack of the existing build to remove the search buttons from the template as a bug was located, there have been no code changes whatsoever. UCM4SVN Release 2.4 UCM4SVN 2.4 is the latest feature release providing exciting new features including a JIRA plugin that allows Developers to work with UCM4SVN entirely through the JIRA user interface, as well as an Eclipse plugin for Eclipse-based developers.

9 JIRA plugin, which allows you to drive UCM4SVN developer actions from JIRA. Eclipse plugin, providing to-do list and basic developer actions. Java Checkout GUI improvements:- Open Folder after checkout Allow user to save Subversion password in encrypted format. You can now clone activities for another project. This makes it easier to create an activity with the same title and description in another project. Improved display for activities with long titles. You can now see all activities awaiting integration from all projects on the Integrate tab. Baseline names can now contain a wider set of special characters including '.', '+' and '-'. For Subversion repositories with UCM4SVN-managed authz-based access control, allow developers to resolve merge conflicts on the project integration branch whilst the activity is being merged. The UCM4SVN server port number was missing from some notifications. This has been corrected. Edit user page no longer reverts the displayed settings to previous settings after an update to a user profile. Intermittent error with ReviewBoard settings not being shown on the Edit Project page. Fixed issue with disabling ReviewBoard integration for projects with existing reviews. Addressed issue with Edit Activity changing the state of the activity under certain conditions. Improved display of login page for Internet Explorer 7 users. Addressed issue with Loading page refreshing rapidly. UCM4SVN Release 2.3 UCM4SVN 2.3 is a feature release providing new functionality and some bug fixes. Existing customer upgrading from earlier releases must upgrade their database after the installation of UCM4SVN 2.3. Please make sure you back up your database before upgrading to UCM4SVN 2.3. Once the database has been upgraded, it will be incompatible with previous releases, and you will not be able to go back. Shared Components Shared components allow you to share changes on some components between projects. This can be useful for shared code such as class libraries or third-party deliveries, for which you would like to use the same version across all of your products. Activities performed on shared components are visible in all projects that share the component, and they are integrated into the same shared integration branch. As a result, activities performed on shared components appear in the baselines of all projects sharing the component. To use a component in shared mode, click the Shared tick box for the component when you create a new project. Password Encryption in Configuration Files In previous releases of UCM4SVN, passwords for Subversion, and other external systems such as Trac and JIRA had to be provided in configuration files in plain text, making it possible for anyone with read access to a

10 configuration file to see the passwords contained in it. It is now possible to encrypt passwords using the ucm4svn_passwd utility. Please see Admin Guide for details. UCM4SVN Information in Subversion Logs UCM4SVN now logs activity-related information in Subversion log messages as actions such as Accept, Close, Deliver or Integrate are performed. This makes it easier to identify UCM4SVN activities in the Subversion repository and allows you to track who performed actions and why on the Subversion side. Confirm Merge After Conflict If merge conflicts occur during the integration or delivery of an activity, you can now resolve the conflicts outside of UCM4SVN and mark the activity as integrated. This will ensure that the manually integrated activity correctly appears in the list of activities for the next baseline. A new button is shown at the bottom of the Merge Conflict page which allows you to mark the activity as merged. Other Changes ENH-2223: s notifications will now only be sent to members of the project that the notification relates to. In particular, this affects notifications to integrators regarding new activities ready for integration. ENH-2204: UCM4SVN now provides direct links to JIRA, if JIRA activities cannot be transitioned to their next state. A direct link to the transition being performed can also be included. Please see the Admin Guide for details on the new jira_show_transition_links option. ENH-2170: UCM4SVN now records additional information including stack traces, if internal errors occur. ENH-2171: Resolved issue with reassigning activities from the Edit Activity tab. UCM-128: Resolved issue with the pull-down select list on the Assign Activity tab for Google Chrome users. UCM-143: Fixed problem with the Edit Project page not always displaying review settings correctly. UCM-144: Made it possible to have users who are only Reviewers and do not have any other roles. Previously, reviewers without any additional roles were unable to log in. UCM4SVN Release 2.2 UCM4SVN 2.2 is a feature release providing new functionality and some bug fixes. Please make sure you back up your database before upgrading to UCM4SVN 2.2. Once the database has been upgraded, it will be incompatible with previous releases, and you will not be able to go back. ReviewBoard Integration The 2.2 release provides a new integration with the Open-Source ReviewBoard code-review management system. This allows you to automatically post reviews to a Review Board server and track progress of reviews within UCM4SVN. UCM4SVN will also automatically create fix activities for any activities that have failed a review. Please see [ ReviewBoard.org] for more information on ReviewBoard.

11 Trac Integration A new integration with the Trac change management system has been implemented, adding to the existing integrations with Jira and ClearQuest. Selective Checkout UCM4SVN can now generate checkouts scripts that cover only parts of a project, baseline or activity. This is particularly useful for developers working on a small part of a product and not needing the complete project to be checked out. Improved Merge-conflict Handling If there are any conflicts during the merge of an activity or a rebase, UCM4SVN will provide checkouts scripts (for Linux, Windows and Java), which will set up a workspace for you showing the merge conflict and allowing you to resolve the issue and commit the changes to Subversion. Automatic Subversion Access Control for Activity and Project Branches UCM4SVN can now manage access to the Subversion repository based on Subversion authz rules. This allows you to limit access to project and integration branches Other Changes Improved configuration file checking will alert you of serious issues in your configuration file. API Changes New API functions to get and close activities. An XML schema is now provided for the UCM4SVN API responses. UCM4SVN will now return id of newly created element on all creation functions. For some users, merging large activities could cause timeout messages in the browser. All pages with lengthy operations are now routed through an intermediate "Loading" page such that timeouts will no longer occur. UCM4SVN now provides support for Subversion access through svnserve. UCM4SVN Release 2.1 UCM4SVN 2.1 is a minor enhancement and bug-fix release, which is compatible with the UCM4SVN 2.0 database format. New API functions to Create components Create projects Create activities If both ClearQuest and JIRA integrations were disabled but allow_multiple_activity_sources was set to 1 in the config file, projects created with these settings would not allow you to create new activities.

12 UCM4SVN Release 2.0 UCM4SVN 2.0 is a major release, which refines many of the concepts of previous UCM4SVN releases. Projects have attained a more important role as they are now the central focus point for UCM4SVN operations. In particular, activities now stretch across projects rather than components and changes are integrated back onto project integration branches rather than the trunk of individual components. Projects now have their own project integration branch. It is now possible to baseline projects, which creates Subversion tags and baseline information in UCM4SVN for all components in the project. New projects can be started from another project's baselines, making it possible to create follow-on projects based on previous projects. For each component in the new project, you can choose a project baseline to use for the creation of the new project. Activities now stretch across projects. When an activity is started, all components of a project become part of the activity. New mechanisms for checking out data have been introduced. Where previously the only option was to cut-and-paste 'svn checkout' commands into a shell window, you now additionally have the option to download activity-specific checkout scripts:- Java checkout application with graphical user interface (requires Java to be installed client-side) Windows checkout batch file Linux shell script Read-only components in projects. A read-only component cannot be changed with activities. It is a reference component (e.g. an external component) that cannot be updated as part of a project. Baselines can be labelled with a status to indicate their status, e.g. in terms of quality (Good, Bad, Tested,...) A number of forms have been fixed such that data entered by the user is retained on errors. When creating activities, you can now assign multiple users. Previously this was only possible through the Reassign Activity tab. UCM4SVN Release 1.4 Features of release: UCM4SVN now supports JIRA behind a protocol. Use exactly as before except add Fixed a bug which prevented delivery from working in some cases when subversion authentication was turned on. UCM4SVN Hotfix Release 1.3 Release 1.3 is a hotfix release to fix some bugs introduced by the latest 1.2 Release. : Changing a NON JIRA user's username and/or password failed. Editing an activities description with a non-project manager account resulted in an error The server port number was missing from the notifications UCM4SVN Release 1.2

13 Release 1.2 is a major release providing support for the integration between UCM4SVN and JIRA. Release Highlights: 1. Import users directly from JIRA Use your JIRA user name and password to log into UCM4SVN Create UCM4SVN activities directly from JIRA Change the state of an issue in JIRA in parallel to its stage of development in UCM4SVN Receive updates whenever you are assigned a new activity or an activity is available for integration Edit your user profile Please note that UCM4SVN 1.2 is incompatible with previous releases. Existing users of UCM4SVN 1.0, please contact sales@clearvision-cm.com for upgrade information. UCM4SVN Release 1.0 Release 1.0 is the initial release of UCM4SVN. CentOS 5.2 is the first supported platform for the server (others will be supported in the future). UCM4SVN is delivered as a web service, so clients can usue any platform that supports a web browser. Known Issues There are a couple of known issues with UCM4SVN v1.0, but neither of these should prevent normal usage, they are listed here for your information. When creating an Activity, if the "do nothing" option is selected (ie the "---" separator), a message box is displayed with the error "Problem retrieving components for this project: INTERNAL SERVER ERROR (500)". To rectify this issue, click on the 'OK' button of the message box, and then select a valid project. This error doesn't cause any issues with your database and will be fixed in the next release of UCM4SVN. 1. When Integrating, it's possible to not select any activities to be merged, and try to merge. In this case, it will appear that a merge has happened, but in reality, nothing happens in Subversion.