Page 3 of 11. Showing 103 results (0.008 seconds)
My Changes
The My Changes page displays a listing of changes you've made to any of the repositories in Continua. For your changes to be picked up as yours, you may need to first configure Repository User Mappings. Note: Any modifications to the repository user mappings won't affect changesets currently in Continua.Build Workspace
in the workspace. Each stage of the build defines what gets put in the workspace using Workspace Rules and Repository Rules. By default, all repositories will have their contents copied to the Source directory and any files placed in the Output directory will be synced between stages. Using a copy of the repository means that weProperty Collectors
you use a build tool or access a repository through Continua. Most of the time you will be unaware property collectors are in use due to the extensive list … a File Version property collector for that file. Accessing properties from property collectors using the query syntax is described below. RepositoriesImport Jenkins into Existing Environment
to the existing Configuration in Continua CI. Importing Repositories All Jenkins' source control management systems are added as repositories on the matching configuration. When source control management systems are converted to Continua CI repositories, they are given the name <repository type>-<Configuration nameBuild Logs
so if an action is failing and it is hard to determine why, then check if you can increase the action's log level. Repository Syncing Repository syncing will list every file that is pulled from your repository and sent to the agent workspace every time a stage is executed. This information can be extremely usefulMercurial
image2018-12-19_10-23-39.png Source Path Enter the location of your mercurial repository. This is the value of the SOURCE parameter that gets passed to the clone command line option. For instructions on how to get Continua working with a SSH mercurial repository, see Mercurial over SSH. Examples: C:\my_hg_repoIssue Connectors
Continua gets the latest changesets from your source repository, it automatically retrieves all commit/checkin messages associated with that changeset. If your source repository is linked to an issue connector then it will also try to parse the commit/checkin messages for issue Ids. It will then take those issue Ids fromSystem Server Properties
These properties define how fields are displayed on the Queue Options, Requeue Options, Stage Promotion and Configuration Repository Branch Mappings dialogs. Server.QueueOptionsDialog.SortBranchesByDescendingLastCommitDate: Set to True to sort branch lists on the Configuration Repository Branch Mappings dialogExpression Objects (1.9 and below)
$ "New_Project_1" $Source Name Description Type Usage Example N/A A list of repositories associated with the current configuration Repository … $ 5 2 1906529119 Repository (used by $Source ) Name Description Type Usage Example Branch The full name of the branch associatedVault
image2018-12-19_10-37-28.png Host The URL of the Vault server. Enable SSL Tick to enable SSL. Repository Name The name of the Repository on the Vault server. Path The path of the directory within the repository you would like monitored. Write changeset details to file Tick to write changeset details