I am trying to execute job using local system as slave.
When I try to launch slave-agent.jnlp from jenkins as well as through command line it doesn't starts. Also, through command line it doesn't shows any error.
please let me know how to fix this issue.
The jenkins slave is started from the system where the job is expected to run later on.
Open the nodes page in firefox and click on the Launch button.
For more information:
https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds#Distributedbuilds-LaunchslaveagentviaJavaWebStart
Related
here is my problem:
I can launch a jenkins job which launches an automated Test. When this job fails and I go to the log.html, I don't see the screenshots. However when I go to the folder that hosts my Jenkins in localhost, and I open my log.html file, the screenshots appear correctly. Can you tell me why I can't see them on Jenkins please?
enter image description here
I tried to configure output path in Jenkins but nothing change this...
enter image description here
Thanks for reading this :)
I am using docker to run my Jenkins instance.
The version which we are using was 2.121. Since last Saturday after the container restart, all my pipeline got vanished. After several hit and trial, when I updgraded to version 1.121.1. All my job got visible again. But when I tried to run any jobs. It is not getting started, after clicking on the build button nothing is happening.
What should I do? any suggestion would be helpful. Thanks
I am trying to launch Protractor-cucumber script from Jenkins but while running tests browser size it not getting maximized.
Tried all possible solutions provided and it doesnot work. Below command tried to run from Jenkins window Batch command
protractor cucumber.conf.js --capabilities.chromeOptions.args="--safe-mode" --capabilities.chromeOptions.args="--window-size=1280,1024"
just add in protractor.config this:
browser.driver.manage().window().setSize(1600, 1200);
with your desired resolution
I got the solution for issue. This problem was due to the way slave machine is set up. Currently Jenkins slave is running as Window services which is creating problem.
When I have stopped this Jenkins slave services and started again from command line with below command then its working fine.
Command: java -jar slave.jar -jnlpUrl https://Jenkins Instance url/slave-agent.jnlp
Thank you very much for comment and support.
In the jenkins applications ,I accidentally clicked on the " Build Now " instead of "Build with Parameters" link while trying to Build the application and now its stuck . I am unable to cancel this Build. I tried building the application again however I am unable to promote my new build because the previous Build is still not complete. Is there any way I can abort the previous build ?
in Jenkins Script console (/jenkins/script) try:
Jenkins.getInstance().getItemByFullName(jobName,Job.class).getBuildByNumber(jobNumber).doStop()
Check if you are logged in and you have permissions for aborting the build (should be at job's configuration page)
Jenkins could need some time to process the abortion request.
If you notice that Jenkins is definitely stacked, check the reason.
It could be memory, CPU or space issue.
These Linux commands are highly recommended:
top
df -h
The last and the most unpleasant way is rebooting Jenkins and starting the new job. NEVER try that on production machine :)
I've just installed at local a Jenkins server in order to execute some tests using Selenium Webdriver.
When I execute the tests, the initial steps are executing well (maven calls, access to repo,...) but when the first selenium step have to be executed, I get this error:
(java.lang.InternalError: Can't connect to window server - not enough permissions.)
What permissions are refered?
I'm executing from my main user in my computer in a MacOSX.
I've looked information in jenkins site and google, but I can get anything.
Add JVM options -Djava.awt.headless=true
On the instance I use, the "JVM Options" field is only visible from the "Advanced..." button under the Launch Method sub-heading.
Have you tried adding a different JDK to your box and using that for your build? I had a similar issue with a Jenkins build job on my mac and was able to correct it:
Jenkins build failed on OSX