Average Ratings 0 Ratings
Average Ratings 0 Ratings
Description
Utilize Subversion to manage versions of individual projects or entire repositories outside of ODI, incorporating automated dependency management for ODI. The automated build process generates a release for either a single project or a full repository, resulting in an archive that can be stored for future reference. The automated deployment initiates from this archive, allowing for the restoration of the project to any designated test or production repository. Repositories are created automatically, providing a streamlined environment. As developers version their code and support for parallel development is enabled, the overall code base becomes more robust. This efficient management of various releases and hot fixes enhances speed, transparency, and reliability. Once a developer commits their code to the version control system, a comprehensive and automated workflow encompassing build, deployment, approval, and notification is activated. This entire process is designed to be dependable, reproducible, and traceable, enabling more frequent deployments and smoother transitions. By adopting this automated system, organizations can significantly improve their development cycles and overall project management efficiency.
Description
Packagist serves as the primary repository for Composer, consolidating public PHP packages that can be installed via Composer. To define your project dependencies, you need to create a composer.json file located in the root directory of your project. Serving as the default repository, Packagist allows users to discover packages while informing Composer where to retrieve the corresponding code. Composer is essential for managing dependencies for your project or libraries effectively. A crucial initial step is selecting a unique package name, which is vital because it cannot be altered later and must be distinct to avoid future conflicts. The naming convention for a package includes a vendor name and a project name, separated by a forward slash (/), with the vendor name designed to help avert naming disputes. Your composer.json file should be positioned at the top level of your package's version control system (VCS) repository, serving as a descriptor for both Packagist and Composer about your package's details. Additionally, any new versions of your package are automatically retrieved based on the tags you create within your VCS repository, ensuring that updates are seamlessly integrated. This setup streamlines the process of package management and fosters better organization within your development workflow.
API Access
Has API
No
API Access
Has API
Yes
Integrations
Bitbucket
No
GitHub
No
GitLab
No
Pricing Details
No price information available.
Free Trial
Yes
Free Version
No
Pricing Details
No price information available.
Free Trial
No
Free Version
No
Deployment
Web-Based
Yes
On-Premises
No
iPhone App
No
iPad App
No
Android App
No
Windows
Yes
Mac
No
Linux
No
Chromebook
No
Deployment
Web-Based
No
On-Premises
No
iPhone App
No
iPad App
No
Android App
No
Windows
Yes
Mac
Yes
Linux
Yes
Chromebook
No
Customer Support
Business Hours
Yes
Live Rep (24/7)
No
Online Support
Yes
Customer Support
Business Hours
No
Live Rep (24/7)
No
Online Support
Yes
Types of Training
Training Docs
Yes
Webinars
No
Live Training (Online)
No
In Person
No
Types of Training
Training Docs
Yes
Webinars
No
Live Training (Online)
No
In Person
No
Vendor Details
Company Name
RedBridge Software
Founded
2003
Country
Belgium
Website
www.redbridgesoftware.com
Vendor Details
Company Name
Packagist
Website
packagist.org
Product Features
Application Lifecycle Management
Administrator Level Control
No
Defect Tracking
Yes
Iteration Planning
No
Project Management
Yes
Release Management
Yes
Requirements Review
No
Task Management
Yes
Test Case Tracking
No
User Level Management
No
Version Control
Yes