Create build with rest api curl --data "@job.json" -H "Authorization: Bearer <token>" -H "Content-Type: application/json" -H "Accept: application/json" -X POST http://<teamcity url>/app/rest/buildQueue The property value in the message body shouldn’t include whitespace if executing with paramters, or use ==Custom Script== instead Sample job.json file { "branchName": "master", "buildType": { "id": "TestBuild" }, "comment": { "text": "Test Build" }, "properties": { "property": [ { "name": "Environment", "value": "SIT" } ] } } Check build status curl -H "Authorization: Bearer <token>" http://<teamcity url>/app/rest/builds/?
In this exercise, we will try to setup git and use ssh to connect the repo.
Download and install git Open Git bash window Generate the keys ssh-keygen # this will generate an private key (id_rsa) and public key (id_rsa.pub) Add the content of public key (id_rsa.pub) to git profile settings Run git clone git clone ssh://git@git_repo_url:7999/test.git
Bitbucket permission can be assigned at project level or repository level for a group and user.
The SQL (MSSQL Server) below can be used to check all projects & repositories permission for a given user, include the access assigned to an individual user or a group.
with repo_access as ( select distinct p.id as "Project ID", p.name as "Project Name", r.name as "Repo Name", cu.id as "User ID (Individual)", cu.user_name as "Username (Individual)", Concat(cu.
Sometimes, we wish to check if a BitBucket user has actually used his account or not. There is a post Query for inactive or idle users which has explained few different ways. I will try the API method.
In this exercise, I try to achieve few things below with Python
Send request to BitBucket server and get the list of users Convert the Unix timestamp to readable date time Export the user data to a csv file This is the sample code to get the information and export to csv file.
In TOSCA Distributed Execution, we discussed how to integrate TOSCA Distributed Execution with Team City, which we have two steps for triggering the execution. Since we need to use them for multiple build configuration, so considering to wrap them one step with Team City Meta-Runner.
The Meta-Runner can be extracted from an existing build configuration. In this case, open the build configuration to be extracted, and go to Actions -> Extract Meta-Runner, Enter or adjust values for Project, Name, ID, Description, and then click Extract button, then make changes if required.
This exercise will try out TOSCA Distributed Execution, the benefits of using it are
Supports untended execution, creates RDP connection automatically while execution Splits the execution load to multiple agent system Monitors the actual test execution with Test Event Monitor After installing the TOSCA 9.3, the Distributed execution components are under C:\Program Files (x86)\TRICENTIS\Tosca Testsuite\ToscaCommander\DistributedExecution
Distribution Server For installing the distribution server, InstallServer.bat under DistributedExecution\Server should be executed,
parameter IP address & Port can be assigned if required.
After installing TOSCA 9.3, TOSCA CI related program should be under C:\Program Files (x86)\TRICENTIS\Tosca Testsuite\ToscaCommander\ToscaCI.
Preparation in TOSCA work space Create a execution list folder and set attribute ContinuousIntegrationBuildRootFolder to True Create execution list with attribute ContinuousIntegration=True and a desired value for Executiontype Add test cases which you plan to execute to this execution list. TOSCA CI Client TOSCA CI professional license is required for using CI configuration file.
Since we will trigger the execution from TeamCity, the TOSCA CI client could be triggered under system account, under that the UI automation will be blocked.
