Nexus Professional's LDAP Integration
In this video, I introduce the LDAP integration and I provide a demonstration of the LDAP integration using the default database from the Apache Directory LDAP server. Nexus Professional’s LDAP integration is highly configurable, watch this video to get a sense of how Nexus supports User and Group mapping.
Nexus Professional LDAP Integration from Sonatype on Vimeo.
For more information about Nexus Professional, go to http://www.sonatype.com/products/nexus.
m2e roadmap
I just wanted to let people know what’s been happening with m2e recently and what we’ll be focusing on in the near term. Recently, there has been a lull in the number of releases because we have decided that testing and quality are the priority so we had to take a step back and figure out a plan of action. The primary outcome is that we feel that the infrastructure for the testing needs to take precedence in order for everything else to fall into place. New feature development has to take a back seat to make sure the current functionality is flawless in execution. Quality is our primary concern, and this means that all new features have to be backed by a completely automated tests (including automated UI tests). As we have discovered, this is an extraordinarily difficult task to accomplish. Provisioning target platforms, meshing Tycho with Hudson for CI/Releases, and automating UI tests is not simple by any stretch of the imagination.
Nonetheless we’re committed to the task and we’ve hired Rich Seddon to create the testing framework and infrastructure. Our goal is to reach the standard set by Nexus which has so many integration tests that virtually nothing regresses and we can refactor and add new features without introducing new bugs. Unfortunately, we know from experience in our training classes and feedback from users that m2eclipse has not reached this level of quality and we are fully addressing this fact by committing ourselves to testing and quality. We probably should have pursued fewer features and more testing, but what’s done is done. From this point forward, testing is our primary concern. We will be able to add some new features, and do some architectural work to help stabilize m2e for the 1.0 but we’re basically going to be eradicating defects and adding the testing which will facilitate the convergence of m2e with the current Maven trunk and ultimately the Maven 3.0 final release. In this post, I’ll walk through what we’re doing at a high level and then try to layout a schedule for what’s going to happen in the next few months.
The Hudson Build Farm Experience, Volume I
I’ve been working on a Hudson-based build farm for Sonatype and Maven open source builds since sometime in September of 2008. I’ve learned a lot as a result, so I thought I’d share some experiences from the trenches. In this first installment, I’m only going to cover our goals and outline the basic setup of our farm; I’ll save discussion of specific hurdles and advantages offered by our environment for the next post.
Nexus Professional: What is Staging?
Here’s a video that discusses the benefits of Hosted Repositories and how Nexus Professional’s Staging Suite introduces the concept of the managed release. With the Staging Suite, you can configure filters that will automatically intercept a deployment to a Hosted Repository. Once the staging suite intercepts these artifacts, they will be placed in a temporary staging repository and a QA or administrative user will be sent a notification that a staged release is ready for approval or disposal. This mechanism allows a QA group to certify a release, once a release has been certified it can be promoted, and the contents of the temporary staging repository will be published to the hosted repository.
Nexus Professional: What is Staging? from Sonatype on Vimeo.
Best Practices for releasing with 3rd party SNAPSHOT dependencies
The Maven Release plugin enforces best practices for releasing Maven artifacts. In summary, the release plugin performs the following steps:
- Validate no local changes against your SCM
- Validate that there are no SNAPSHOT dependencies
- Convert the modules to the to-be released version
- Ensure the build and Unit/Integration tests succeed
- Commit the changes to SCM, then Tag the release
- Checkout the tag to a clean location and build/deploy the artifacts
Dealing with failures on Step #2 is where I want to focus today. (more…)
