Home / Companies / JFrog / Blog / January 2016

January 2016 Summaries

2 posts from JFrog

Filter
Month: Year:
Post Summaries Back to Blog
Following the holiday season, JFrog released Artifactory 4.4, introducing several significant updates aimed at enhancing functionality and security. This release includes support for the Opkg package format, allowing users to work seamlessly with local and remote Opkg repositories, which is crucial for the expanding Internet of Things (IoT) ecosystem. It also features security improvements such as SSH integration, login protection against brute force attacks, and OAuth support for Docker clients, which enhance user authentication and data protection. Additionally, the introduction of a "Trash Can" feature allows users to recover accidentally deleted items within a specified period, mirroring the familiar recycle bin concept. These updates, along with other enhancements like RubyGems license extraction and Docker label display, reflect JFrog's commitment to improving user experience and maintaining robust security measures.
Jan 18, 2016 672 words in the original blog post.
The survey on Developer and DevOps Trends 2015 highlights the complexity developers face when using multiple technologies, particularly with dependency resolution and artifact deployment. Artifactory addresses this by allowing developers to use virtual repositories, which aggregate several local and remote repositories of the same type, simplifying the process by offering a single URL for both resolving dependencies and deploying artifacts. This approach not only streamlines developers' workflow by reducing the need to configure multiple repositories but also enhances convenience in configuring reverse proxies for Docker, as the virtual repository functions as a complete Docker registry. Additionally, Artifactory administrators retain control over the system's back-end by managing target repositories and enforcing security policies without impacting developers' operations, ensuring a seamless user experience.
Jan 11, 2016 580 words in the original blog post.