Forum Discussion
So Now I am launching the jenkins server from the testexecute machine . I have attached the screenshot.
When I press the lauch button I get the following error
Sep 27, 2018 9:54:20 AM hudson.remoting.jnlp.Main createEngine
INFO: Setting up agent: slave_pretty
Sep 27, 2018 9:54:20 AM hudson.remoting.jnlp.Main$CuiListener <init>
INFO: Jenkins agent is running in headless mode.
Sep 27, 2018 9:54:20 AM hudson.remoting.Engine startEngine
INFO: Using Remoting version: 3.23
Sep 27, 2018 9:54:20 AM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir
INFO: Using C:\Users\nisgupta\Documents\TestComplete\remoting as a remoting work directory
Sep 27, 2018 9:54:20 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Locating server among [http://microcar.ttu.edu:8080/]
Sep 27, 2018 9:54:20 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve
INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]
Sep 27, 2018 9:54:25 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver isPortVisible
WARNING: connect timed out
Sep 27, 2018 9:54:25 AM hudson.remoting.jnlp.Main$CuiListener error
SEVERE: http://microcar.ttu.edu:8080/ provided port:60540 is not reachable
java.io.IOException: http://microcar.ttu.edu:8080/ provided port:60540 is not reachable
at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:286)
at hudson.remoting.Engine.innerRun(Engine.java:523)
at hudson.remoting.Engine.run(Engine.java:474)
The error is showing that your test execute machine cannot connect to the remote jenkins master whichs sounds like a network / filewall issue. You would probably have to work with your infrastructure team to determine why you are being blocked.
- cunderw7 years agoCommunity Hero
Looks like the same proble someone else had:
Solved by running jenkins as a local account.
- shankar_r7 years agoCommunity Hero
It is not the Jenkins confluence publisher plugin limitation.
The default rule for Jenkins is, each build step checks the previous step status if it is not SUCCESS then it won't go to next build/post build step and it stops where an error occurs. Some plug-ins might have override options so that irrespective of previous step status it will run.
From Document:
-
Action on warnings - Specifies whether Jenkins should mark the entire build as failed or unstable when the TestComplete test log contains warnings.
-
Action on errors - Specifies whether Jenkins should mark the entire build as failed or unstable when the TestComplete test log contains errors.
Answer to question is,
Make the two drop-down boxes in the TestComplete build step advanced options to None as like below image then you are all set.
-
- cunderw7 years agoCommunity Hero
You're getting an out of memory error, which probably means your mht is way too big. I would look into Log.LockEvents(); to reduce the number of events being logged and images which is likely what's causing the huge file size.
- nisgupta7 years agoValued Contributor
Here is the update
we launched the agent from the commandline and it get connected . and it ran successfully.After connection I set up the Jenkins Project to run the TestComplete Project Suite . So it run the Project Suite located on testexecute machine.
But Here is one thing I was looking at the command line which is being used for connection to Jenkins master and get the following exception when I press Build Now
Oct 08, 2018 10:06:34 AM hudson.Util getWin32ErrorMessage
WARNING: Failed to find resource bundle
java.util.MissingResourceException: Can't find bundle for base name /hudson/win3
2errors, locale en_US
at java.util.ResourceBundle.throwMissingResourceException(Unknown Source
)
at java.util.ResourceBundle.getBundleImpl(Unknown Source)
at java.util.ResourceBundle.getBundle(Unknown Source)
at hudson.Util.getWin32ErrorMessage(Util.java:662)
at hudson.util.jna.JnaException.<init>(JnaException.java:37)
at hudson.util.jna.RegistryKey.check(RegistryKey.java:124)
at hudson.util.jna.RegistryKey.open(RegistryKey.java:223)
at com.smartbear.jenkins.plugins.testcomplete.TcInstallationsScanner$Sca
nnerCallable.scanForInstallations(TcInstallationsScanner.java:82)
at com.smartbear.jenkins.plugins.testcomplete.TcInstallationsScanner$Sca
nnerCallable.call(TcInstallationsScanner.java:69)
at com.smartbear.jenkins.plugins.testcomplete.TcInstallationsScanner$Sca
nnerCallable.call(TcInstallationsScanner.java:58)
at hudson.remoting.UserRequest.perform(UserRequest.java:212)
at hudson.remoting.UserRequest.perform(UserRequest.java:54)
at hudson.remoting.Request$2.run(Request.java:369)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecut
orService.java:72)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93)
at java.lang.Thread.run(Unknown Source)
Any idea what is causing this ?
Thanks
NG
- nisgupta7 years agoValued Contributor
we still have this warning but our testcomplete projects are running fine on testexecute machines. At this time I am not sure what will be the long term impact of those warnings.
I have attached the screenshots for slave agent configurations
jenkins job configurations
Now oour goal is to export the mht file after the TestComplete tests get finished . Right now I have mentioned in the script itself . is there a way that we can put in Jenkins after post build ?
Thanks
NG
- cunderw7 years agoCommunity Hero
The jenkins plugin provides a Test Complete Results on the build page, is this not what you are looking for?
- nisgupta7 years agoValued Contributor
*.mht report and I need to push this report to our Confluence as you can see in the screenshot which we have set up in PostBuild . But In order to make this work we have to write thiss code at the end
Log.SaveResultsAs("C:\\ ...\\...\\...\\ScholarshipTrackingSystemStatusHSC.mht",lsMHT)
Thanks
NG
- shankar_r7 years agoCommunity Hero
It is not the actual MHT report, it is the UI rendered data with help of .htmlx and .tclogx files.
For each build, .htmlx and .tclogx files will be in below path. you can upload these files into Wiki, whenever you want you can open it via TestComplete.
{Jenkins_Home}\jobs\{job_name}\builds\{build_number}\tcreports
As of now option to export as MHT format from the build view
- nisgupta7 years agoValued Contributor
@shakar_r
Yes
- shankar_r7 years agoCommunity Hero
Just now got remembered, We have option to generate MHT file from the job.
Generate MHT log file - If this option is enabled, TestComplete exports test results to a .mht file after the build is over. You can download this file from the Jenkins page displaying test results.
If this option is disabled, TestComplete does not export test results in the MHT format, but you can still examine results in Jenkins. See Viewing TestComplete Test Results in Jenkins.
{Jenkins_Home}\jobs\{job_name}\builds\{build_number}\tcreports
Now you have MHT file you can do your pulgins to upload the MHT file into Confulense page - nisgupta7 years agoValued Contributor
yes we have the check box option to gnerate the MHT file. I always check this check box as we need to publish this report to confluence which is wiki .
I have attached the Post build actions from jenkins I am looking whether we have the option in Jenkins that can push this MHT report automatically to Confluence Wiki ?
Thanks
NG
- shankar_r7 years agoCommunity Hero
No, We have to use the external plug-in (like you are using currently) to do the upload or other kinds of stuff.
- nisgupta7 years agoValued Contributor
ok
I am concerned about the path of the MHT file on master jenkins. Attached the screenshot with the path.
Thanks
NG
- shankar_r7 years agoCommunity Hero
Things to note here,
MHT file always generates in the Jenkins master node whereas job runs on the Slave node. Post-build will be triggered in the slave.
Before triggering the upload results to Confluence, MHT needs to be placed in the workspace of Slave from Master node. No plug-ins found to copy the file from Master node to salve workspace after a build.
Me too having the same kind of problem, I'm trying to solve it. Hope will find a solution soon.
- nisgupta7 years agoValued Contributor
Thank you
Yes you are right till now we have not find the way to copy the MHT file from master node to slave node.
So what I did is Through testcomplete script I am exporting the MHT log . But there is issue jenkins build willl not post the MHT file to confluence or wiki if there are errors in the script. If there are no errors then it will post the MHT file to confluence
I have just attached the Post build actions - where I am using plugin Publish to confluence . Other attachment is related to console log showing the script has errors and jenkins detects it as unstable due to which MHT file do not get published to confluence.
I am not sure do we have any limitation in jenkins confluence publisher plugin ?
Thanks
NG
- nisgupta7 years agoValued Contributor
We are getting when uploading the testcomplete result - MHT to confluence like wiki
Attach the log file.
- nisgupta7 years agoValued Contributor
We are getting when uploading the testcomplete result - MHT to confluence like wiki
Attach the log file.
- nisgupta7 years agoValued Contributor
we are getting out of memory error when uploading the testcomplete results to confluence like wiki.
Attached the log files
- cunderw7 years agoCommunity Hero
Let's you limit the number of events posted to the test complete log.
- nisgupta7 years agoValued Contributor
Ok,
I got this. This is how we can limit the logging.
We have a case here
Our functional users want to see the results in MHT format which is the best way . The functional users do not have the knowledge of TestComplete. They want to see the how the application behave and from the start to end of the test case.
My concerns is limiting the logging will not allow the functional users to miss some steps .
Thanks
Nishchal
- cunderw7 years agoCommunity Hero
You can specify how far back the events will be captured when an error occurs which is the crucial piece. You can aslo include more verbose log messages, or completely eclude all images. You could also split up your tests into multiple projects. There are plenty of options to reduce the size.