Variables for global/project/config repositories

Continua CI Discussion
1
I setup a global repo and noticed that it was stored at the following location:


M:\CI_WS\Repos\3a296204

Is there a variable in CCI that will reference this path?  My build routine requires the build directory to have a copy of the repository.  Right now I'm doing a "double pull" to get around this, but it would be nice if I could just pull it from the repo CCI uses.

2

Yes, you can refer repository files using $Source

e.g. $Source.RepoName$\Subfolder

The repository is cloned to the M:\CI_WS\Repos\3a296204 on the agent. The Repository Rules are then used to copy to the workspace folder on the agent e.g. M:\CI_WS\Ws\3a296204. By default they are copied to M:\CI_WS\Ws\3a296204\Source which can be accessed via $Workspace$\Source.

Read more about Repository Rules and Workspace Rules in the wiki under Stage Options




3

Dave,

Thanks.

My build routine requires that the working directory to have a copy of the repository, as my build script uses issues hg commands to get the changeset of the version being built. I’ve no desire to change this procedure.

When CCI does it’s stuff, the repo is cloned to the agent at: M:\CI_WS\Repos\4aea1efe
Then the Repository Rules creates the workspace on the agent at: M:\CI_WS\Ws\10\Source

However M:\CI_WS\Ws\10\Source is a copy, not a clone, and therefore doesn’t have the .hg folder so I can’t build from there. Is there way to clone this with the Repo rules instead of copy?


As a workaround, I’ve created a M:\build directory, and I have my buildrunner pull/update from the online repo. If I can’t fix the above issue (workspace being a repo) then I’d like to have my buildrunner (FB7) pull/update from M:\CI_WS\Repos\4aea1efe using a variable.


$Source.RepoName$ evalutes to M:\CI_WS\WS\10, which appears to be the workspace files and not the repo path.


4

Hi Igor,

One of the advantages on Continua CI is that it manages the repository automatically and updates the workspace with the latest changeset on the branch when running a build. You should not need to run any hg commands in your Finalbuilder script and we do not want to encourage accessing the Repository cache as this is key to the internal workings of Continua.

Can you provide more details of what hg commands your script needs to run?

If you just need information about the changeset being built, the following variables are available in input boxes which support expressions:

$Source.RepoName.Branch$
$Source.RepoName.BranchName$
$Source.RepoName.LatestChangesetID$
$Source.RepoName.Path$
$Source.RepoName.Type$
$Source.RepoName.Url$



5

One step forward, two steps back.

If I want to do a manual build, how can I tell CCI that I want to use a specific changeset hashcode? CCI always updates to the latest named branch. Sometimes I need to build prior versions.

6

At this time, you cannot. It’s on the todo list, but I can’t say when it would be done.

7

As a workaround I’m cloning the ContinuaCI repo to a working directory with FBS then updating that with the proper changeset. Seems to work.