Have Geek Brain

What are you using for artifact staging / deploying servers?

I am thinking about writing my own release storage server and before I do I would like to know what people are using to see integration instead of building.

So what do you use to store your collectors for internal access?

I'm looking for a web app that allows me to download artifacts and then reference them with various tags so that I can group them together using a component or release. I also want the assembly access controls to be provisioned on readiness or in progress.

I define stage as hosting embedded artifacts on a server for user communities to access . Artifacts are usually zip files containing either applications or libraries + documentation. User Communities - Developers, QA and Services / Operations. Essentially creators, checkers and outside users.

We release artifacts individually and as groups in a release vehicle (for example, release 1.1 contains foo 1.0.1 and bar 1.0.7). Depending on the artifact, we can restrict access. Operations should not have access to pre-released builds and we can track who downloads the limited availability version.

So, I'm hoping to find a tool that does most of what I want with a nice extensible design, so I can add what I don't have.

Does anyone know of a good tool for managing the post build of an assembly?

Examples might be:

  • quickbuild / lunt assembly
  • Team Forge
  • build a forge
  • Jira and merge as a set
  • Nexus type sonata
  • home growth
  • SVN repository using branching to push builds with dev-> Qa-> GA
+1


a source to share


2 answers


Peter

Since you have few answers, I will let you know about AnthillPro , the developer of which, Urbancode, I work for.

Ok, disclaimer, AnthillPro is designed to serve exactly the wider audience you are discussing - dev, checkers and operations. Compared to the tools you list, AnthillPro is something like BuildForge (our key competitor) or a fast build with a tightly integrated repository of artifacts (like nexus). This way the builds are done and you can view your build results - and build artifacts - on a nice ui web. Users with the correct permissions can run a secondary process like deploying or testing against previous builds - and artifacts from the selected build.

The goal is to manage the lifecycle of an entire assembly from creation, through various test tools and deployment environments, from release to production. It's not a big nasty set, instead we're integrating tools like Subversion and Jira to make sure each version has a change manifest for the original and problem ticket.



Your release packages will render well for AnthillPro's built in dependency system. We often see customers create virtual projects that have little or no source code, but instead bundle or bundle components into a release package.

In cases where AnthillPro might be missing you, you should enable build operations before release. However, you can add rules that will fire immediately or block operations from attempting to free any assembly that is not marked as previewed. AnthillPro's status system allows the team to mark a build with customizable markers such as "In QA" or "Approved for Release". Combined with workflow rules that should give you the control you need. If some projects are particularly sensitive, you simply use role-based security to block them.

Hope you need to learn a thing or two.

- Eric

0


a source


My parameters

build automation systems like AntHill, QuickBuild, TeamForge, BuildForge

  • file server
  • version control server
  • maven repository manager (nexus, archiva)

My goals



  • the group is built according to several criteria (artifact type, vehicle release, stage / phase)
  • push build with dev -> qa -> released
  • provide access control for dev builders, qa ready builds, production ready builds.

I'm going to focus on any control source like file server (using svn) or maven repository as file server using nexus. The rational is as follows:

  • minimize effort.
  • minimize cost
  • use something that I can easily extend when needed (because I'm sure my requirements will shift).
  • The use of maven is growing and will eventually become the dominant build technology.

Thanks for the info.

0


a source






More articles:


All Articles