Dedicated build workspaces

When you create a build definition, you have the option to create a dedicated repository workspace for the build. Dedicated build workspaces enable you to identify changes and work items that go into a build, and to create snapshots of the build source content.

When your build definition specifies a build repository workspace, the Jazz™ Build Engine, which is connected to the Jazz repository, uses this repository workspace to identify the content to build. The build engine accepts any incoming changes from the team's stream and then loads the repository workspace contents into the local file system for processing.

There is a Jazz Source Control pre-build step which can be added to a build that makes it easy to fetch files from a Jazz repository workspace or stream. The Source Control step will add a page to the build definition and allow you to configure how to fetch the files.

It's possible to create read-only Source Control builds which fetch files from a Stream. These builds are not auditable since they won't record the set of files that were built. But these are useful for continuous builds.

The snapshot and baselines created by the build are private to the build workspace. If you want to make them official, you can promote and rename them to a stream to make them easier to find by team members.

If you already have a build script and don't want to migrate to a Jazz Source Control build, you can use the fetch Ant task to fetch code from the Jazz repository from within your script (note: forward pointer to task description).


Feedback