jaward916
Occasional Contributor
Joined 5 years ago
User Profile
User Widgets
Contributions
Re: Jenkins Integration - Command Line Argument
Thank you for this, your approaches should work for me, I'm not sure how I've missed the /pv: params this is likely the solution I need, as I'm assigning to project variables anyway! I agree the position thing is a little restrictive but has worked for nearly 2 years until I tried to be clever and sort all our pipelines out!!Jenkins Integration - Command Line Argument
Hi, I am running TC 15 latest version, Jenkins Latest version and the plugin. I have my TC machine set up as a Jenkins Slave node and can see my QA step starting to execute, but it is failing with: [TestComplete] Test runner exit code: 3. [TestComplete] [WARNING] Error: Unable to create a project item of the 'Tested Applications' type, because the specified file does not exist. The item to be created is a child of the following project item: CSG_ExtendedSolutions\MenuUsageTracker Missing file: C:\TestComplete\tc-extendedsolutions\MenuUsageTracker\TestedApps\TestedApps.tcTAs.~$tcUnsaved$. I think what is happening is I currently pass in an "environment name" parameter which is read as a variable which forms part of the tested application's path, however, the plugin is adding an additional command/parameter at the end of the string, and my test code reads the last parameter sent to the command line, can you see the issue here... I can see from the Jenkins log that the command run includes this extra param (JenkinsTCPluginVersion) which means my environment name variable is now that string, rather than 'MyQAEnvironment' - I don't really want to change the test code, as this would break my manually run PowerShell scripts (and I do similar for 5 products in total). I would like to use the TestComplete Jenkins plugin so test results are published in my pipeline. So the question is, can we suppress or move this additional parameter, so I can ensure that my Jenkinsfile included 'commandLineArguments' are in fact passed as the very last item in the command? Some images to help explain, hopefully: This shows the Jenkinsfile pipeline commands for QA Stage with my commandLineArguments This shows the error and full command that was input (not the additional plugin version param) This shows the code I use to set up the TestedApp "dynamically" based on the last param being the environment name, which I think was code someone on these forums helped with a while ago! Open to ideas on how to get around this?GreaterThanOrEqual to on Dates no longer working
Hi there, since upgrading to 14.61 this week my tests are failing on comparison of a date time. I have a timestamp set as: var timestamp = dotNET["System"]["DateTime"]["Now"]["UtcNow"]["OleValue"]; this is then compared to a value extracted from a grid: aqObject.CheckProperty(Grid.DataSource.DataSource.Item(RowId).Row, "StartedOn", cmpGreaterOrEqual, timestamp); last week this worked absolutely fine, however today I get: As you can see it is equal to, not less than, and I am using greater or equal as my qualifier!! Help, please?!validate wValue against Project Variable in UltraGrid
Hi there, I have an UltraGrid with one row, I want to make sure a column in that row is the JobNumber I created earlier on and is stored as a Project Variable. I have the Property Checkpoint setup as wValue(0,2) equals Project.Variable.JobNum but it want's an explicit value (which I don't know before the test, hence variable) how can I get this to work? Checkpoint Setup: Error: I'm having one of those days, I'm sure this is an easy one for the gurus!
