vcs
Bazaar VCS 1.8 RC1 / 1.7.1
Free and open source application that adapts to the workflows you want to use more>> <<less
VOODOO Server 2.1.4
Version control system for CodeWarrior. more>>
VOODOO Server and the plug-in included, CodeWarrior, provide reliable and robust version control without adding the administrative overhead that often accompanies version control.
Its cubic project mart structure builds the robust foundation for version management without limits. VOODOO Servers CodeWarrior plug-in lets you track all your files from inside the CodeWarrior IDE.
Its object-oriented branching makes it unique in the competitive arena.
Enhancements:
Problems Fixed:
- Mac OS X 10.4 (Tiger) compatibility
- This version has been prepared for Mac OS X 10.4 (Tiger). Incompatibilities (e.g., permission errors upon opening the database) have been fixed.
- CW Plug-in: disconcerting conflict alerts
- The CW plug-in is more careful about showing conflict alerts when performing check-in/check-out operations.
- CW Plug-in: compare helper popup menu doesnt show any options The compare helper popup menu in the "Browse History" and "Check In" dialog didnt show any options for files with an unspecified file type (i.e., ????). The plug-in now uses both the file type and the file extension to determine the set of possible compare helper applications for a file.
- CW Preferences Panel: Error -10814 The panel no longer treats error -10814 (kLSApplicationNotFoundErr) as a generic error, but shows a meaningful error message instead.
- Server: privilege check when adding part to project
The server application didnt correctly check for privileges when trying to add a part to a project.
- Server: users with "read access" cannot fetch files
Under certain circumstances the server did not allow a file to be fetched, if a user had only read access to a part.
- AppleScript "Setup Version Control" fails
The "Setup Version Control" script failed, because the VCS panel erroneously returned a "parameter missing" error.
Releaser 0.2.4
Set of scripts to help manage and automate software package releases more>> Set of scripts to help manage and automate software package releases
Releaser is a set of scripts to help manage and automate software package releases. Every software package should have a .pkg file containing necessary information about the project and modules to be used.
The prerel script runs the selected pre/ modules and uses the .pkg information and the input from the user to generate a release specific .rel file. Typical tasks in pre modules include generation of changelogs, building of tarballs from vcs repositories, etc.
postrel uses the .rel and other output of the pre scripts to actually execute the release by running the post modules, this usually includes uploading tarballs, sending announcements to m ailing lists, uploading news page in website, freshmeat submission, etc.
TracGViz 1.3.4
TracGViz is a complete and useful package (plugin) which provides components so that Trac be able to use widgets and related technologies offered by Google. more>>
TracGViz 1.3.4 is a complete and useful package (plugin) which provides components so that Trac be able to use widgets and related technologies offered by Google.
Major Features:
- It allows to feed data managed by Trac to widgets based on Google Visualization API.
- It allows embedding iGoogle Gadgets in wiki pages using WikiFormatting.
Enhancements:
- New ! GVizQuickJumpEntries offers data about interesting places in the repository (a.k.a. quick jump entries). This includes tags and branches, for instance. The data is provided by VersionControlRPC.
- Bug fixed: Formerly all revisions were included in the revision log if only individual revisions were requested. Now the result sets include just the information for the particular changesets supplied in rev parameter. Tested with both hg and svn.
- Bug fixed: Exception with message Invalid list index was raised when using Subversion backend when requesting the log for individual revisions. This works OK now for both hg and svn.
- Bug fixed: Wrong default value for fmt parameter in GVizChangesetDetails. Now it's OK.
- Bug fixed: Formerly undocumented column in GVizTimelineFilters provider now contains appropriate description.
- WikiFormatting may be used to document the data sources. It may be included in the documentation written for parameters, columns, and the data source itself.
- Bug fixed: Documentation for providers having dynamic schemas was not previously rendered. This has been fixed and a new property has been added in docs to highlight whether the data source returns always the same columns or if they can vary depending upon run-time conditions.
- Milestones may be filtered by name by providing a UNIX pattern in filter_by parameter.
- UNIX filename patterns are compiled using REs for better performance.
- Bug fixed: When using Hg backend, the code in version 1.3.3 in order to revisions iterator (VCS RPC) entered infinite loop (under certain conditions apparently related to branching or version numbers). This doesn't happen anymore.
- Bug fixed: Now VCS RPC retrieves all changesets when using Hg backend. The implementation doesn't guess anymore the revision order and retrieves all that information directly from the underlying VCS connector in use. The former algorithm was weak because it only considered the first parent of a given revision. Therefore many others (especially all those in different branches) were missing from the result set.
- Individual revisions (and not just intervals like before) may be selected in GVizChangesets (i.e. to obtain the revision log).
- Bug fixed: As a consequence of the changes introduced in version 1.3.3 (especially in ReportRPC and VersionControlRPC) together with bug #5586@TH.org in XmlRpcPlugin, made impossible to render the main displaying documentation about the different RPC handlers. Both docstrings have been modified and everything is back to normal right now.
Parabuild 4.0.0 EAP Build 1670 / 3.2.35
Software build and release management system more>>
Note: Parabuild is free for non-commercial use.
Major Features:
- Software Release Management:
- Release builds
- Practically unbreakable nightly builds
- Continuous integration
- Multi-platform remote builds
- Parallel builds
- Manual patch builds
- Fine-grained scheduling
- Shell scripts, make, ANT, NAnt, MSBuild, Perl, qmake, ElectricAccelerator, MSDEV, nmake,Maven, Jam and VB
- Version Control Integration:
- Support for Perforce, Subversion, CVS, Surround SCM, ClearCase, Serena ChangeMan (PVCS), Visual SourceSafe, Borland StarTeam, SourceGear Vault, and MKS Source Integrity
- Change lists
- Multi-line VCS repository paths
- Build labeling/tagging
- Web User Interface:
- Fast, easy to use Web user interface (UI)
- No more digging through configuration files
- Dashboard and detailed views of builds statuses
- Integration with Cenqua FishEye
- Integration with ViewCVS/ViewVC
- Statistics And Build Telemetry:
- Build time
- Build and change trends
- Build breakage distribution
- Test statistics
- Build Archive and Search:
- Text, HTML, Clover, Cobertura, JUnit, PMD, and findbugs logs
- Searchable build log archive
- Online build results access
- Automatic archive cleanup
- Notification:
- RSS
- Windows system tray
- Instant messaging (IM)
- Simple Administration:
- Simple three minutes installation
- Low to zero administration overhead
- Management through Web UI
- System stability monitoring
- Group based security
- LDAP authentication
- Issue Tracking Systems Integration:
- Jira
- Bugzilla
- Perforce jobs
- Integration with ViewCVS and P4Web
- Test Tools Integration:
- Rendering JUnit reports
- JUnit statistics charts
- Compliance And IT Governance:
- Know who, when, what, how and why.
- Build configuration audit
- Change lists
- Build Management:
- Build load balancing and failover through clusterization of remote build agents
- Sticky build agents
- Clean checkout on agent change
- Online charts with build agent statuses and load
- Keeping paused status after re-start
- Queuing serialized builds if all agents are busy
- Page to monitor remote agents
- Environment variables PARABUILD_PROJECT_ID, PARABUILD_PROJECT_NAME, PARABUILD_BUILD_ID, PARABUILD_LAST_GOOD_BUILD_NUMBER, PARABUILD_LAST_GOOD_BUILD_TIME, PARABUILD_LAST_GOOD_CHANGE_LIST_NUMBER and PARABUILD_LAST_GOOD_CHANGE_LIST_TIME
- Stopping and resuming a group of builds
- Converting build schedule from manual to automatic and from automatic to manual
- Web UI:
- Pop-up editor for build commands
- Builder drop-down on the build configuration screen
- Displaying builds assigned to a particular agent machine
- Build instructions section
- Display group to show only scheduled builds
- IP Address and next build time on build list
- Allowing higher number for cool-down interval
- Information on who stopped the build to build status screens
- Colored markers for stdout logs
- Notification settings in the read-only build run configuration view
- Throbbers on detailed build status
- Change list number in build history table
- Simplified navigation for system administration
- Wide layout and notes for builds history
- Build name and host in the error messages
- Build name and host on the error list page
- Notifying all administrators about build errors
- Support for configuring MKS dates
- Version Control Integration:
- Perforce: Graceful handling of erroneous double slashes in Perforce depot path
- Accurev: Added integration with AccuRev VCS
- Subversion:
-
- Accepting the SSL certificate automatically when accessing https location
- Watching non-recursive Subversion paths recursively for changes
- Delay between polling multiple Subversion paths
- Cleaning up workspace on agent change
- Notification:
-
- Global VCS user to e-mail map
- Global setting for ignoring user name case when resolving e-mails of Perforce users
- Improved option "Send failures only once"
- Log Management:
-
- Ignoring directory time stamp for logs
- Integration with Boost Unit Test Framework
- Generic test result handler
- Installation & Environment:
-
- Ability to start and stop Parabuild service from Parabuild program group under Windows
- Enabling running remote builder under Windows under Administrator user
- Support for 8GB database files
- Security: Allow users with edit or start rights on any build to see system errors
- Page: 1 of 1
- 1