Re: jenkins building when it shouldn't
Did you wipe the workspaces after changing the git configuration? On 30 October 2014 00:05, Mark Waite mark.earl.wa...@gmail.com wrote: Were you using multiple repositories in the job? Had the job been through any special changes which might be relevant to understand why the code which asks the question what needs to be built to decide that more than one SHA1 needed to be built? Mark Waite On Wed, Oct 29, 2014 at 8:15 AM, michaelw michael.wi...@gmail.com wrote: Thanks... So I think I've solved it... The message : *Scheduling another build to catch up with XXX *crept into the build logs. This of course was scheduling a build (and doing it on _every_ build). The branch to build is */master and this is what it has been for a while but at some point having this branch spec caused multiple builds to be registered. I removed the * and made it remotes/origin/master and now I only get ONE build. I am very glad I have solved the problem. It would be nice to know why this *Scheduling another build to catch up with XXX *occurs (for what use case) because it only caused me major headaches. On Tuesday, 28 October 2014 22:09:36 UTC+2, michaelw wrote: Wow... that would be great. I'm busy confirming it is unique to bitbucket. I suspect it is. When I've narrowed it down I'll submit. Thanks On 28 October 2014 13:24, Mark Waite mark.earl.wa...@gmail.com wrote: I'm not sure what else could be happening in that job. Could you submit a bug report, and attach the job definition for the failing job, and the build logs for the cases where multiple jobs are being executed to catch up, yet the same SHA1 is used in each case during the catch up? Thanks, Mark Waite On Tue, Oct 28, 2014 at 1:45 AM, michaelw michael.wi...@gmail.com wrote: Sha1's for all the builds are exactly the same. On Tuesday, 21 October 2014 22:34:47 UTC+2, Mark Waite wrote: If polling is not configured, then you'll need to read the build log of each job that was run, and extract the differences between those jobs. Usually, changes detected means that the git plugin believes that the remote repository includes a branch which matches the branches to build in the job definition and which points to a SHA1 which has not yet been built. It queues a build to run a job using that SHA1. Thanks, Mark Waite On Tue, Oct 21, 2014 at 4:43 AM, michaelw michae...@gmail.com wrote: There is nothing in my polling log and I have no polling configured. On Monday, 6 October 2014 18:26:21 UTC+2, Mark Waite wrote: If you've configured branches to build to use a wild card, and if there are changes on those branches compared to the last time they were built, then a bunch of builds will be queued for the changes on those branches. You might post your git polling log to show what changes it has detected, or the early part of the build log to show the state of the repository. Mark Waite On Mon, Oct 6, 2014 at 9:55 AM, michaelw michae...@gmail.com wrote: Hi All... Whenever I kick off a build in jenkins it queues up a bunch of builds claiming that it is doing so because changes are detected. I have disabled all polling etc. I did have the commit hook on but is also disabled. The only change is that we have moved our git repositories to bit bucket... again no commit hook configured there. I have also monitored the logs during a build and I don't see anything unusual... Please can someone help me trouble shoot this. Maybe I can dial up the logging so that I can work out why jenkins is behaving like this? Thanks -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Thanks! Mark Waite -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Thanks! Mark Waite -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Thanks! Mark Waite -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- see my blog: http://analysis102.blogspot.com http://audiblethoughts.blogspot.com http://outsideofficehours.blogspot.com -- You received this
Selenium plugin couldn't register this node : Hub is down or not responding: Connect to ... failed: Connection refused
Hello, I use the Selenium plugin of Jenkins. On my Jenkins master (Ubuntu) I created a slave. This slave is launched by JNLP on a VM (VirtualBox Ubuntu). The communication between the master and the slave is OK. I created a Selenium node configuration. When I go to the Selenium Grid on Jenkins I see : No RCs have checked in yet. Have you started some slaves? When I watch the logs of the slave I see : 09:37:22.618 INFO - couldn't register this node : Hub is down or not responding: Connect to ... failed: Connection refused The firewall is off. I decided to test Selenium Grid without Jenkins. I launch manually the Selenium hub on my computer and the Selenium node on my VM and it's work perfectly. So I supposse it's not a network problem but a Jenkins configuration problem. I tried with a Windows 8 and a VM Ubuntu and I have the same error couldn't register this node When I do this command : nmap -p -sT IPmaster I get : Port /tcp State Closed Service krb524 Closed = nothing uses this port. If I launch the same command when I launch the Selenium hub manually (without Jenkins), the port is openned. Wat kind of Jenkins slave I should creat? Do you think there is an issue wirth the Selenium plugin? Thanks for your help. Julien -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Jenkins update hangs on CentOS
Hi Jason, YMMD! :-) I investigated a little deeper what's going on during yum update. The update seems to stuck at the command chown -R jenkins /var/lib/jenkins but as there are a lot of jobs with huge svn checkouts, it just takes very long to touch every single file. Might be an improvement point because I do not see if this is neccessary on every update. Jenkins is the only user which uses these files. Kind regards, Yves -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: jenkins building when it shouldn't
I suspect that was the issue... having the same git repository whose end point gets changed. Now you have the old master and the new master. Though I still find it weird that it wanted to build twice. On Thursday, 30 October 2014 08:10:05 UTC+2, Corneil du Plessis wrote: Did you wipe the workspaces after changing the git configuration? On 30 October 2014 00:05, Mark Waite mark.ea...@gmail.com javascript: wrote: Were you using multiple repositories in the job? Had the job been through any special changes which might be relevant to understand why the code which asks the question what needs to be built to decide that more than one SHA1 needed to be built? Mark Waite On Wed, Oct 29, 2014 at 8:15 AM, michaelw michae...@gmail.com javascript: wrote: Thanks... So I think I've solved it... The message : *Scheduling another build to catch up with XXX *crept into the build logs. This of course was scheduling a build (and doing it on _every_ build). The branch to build is */master and this is what it has been for a while but at some point having this branch spec caused multiple builds to be registered. I removed the * and made it remotes/origin/master and now I only get ONE build. I am very glad I have solved the problem. It would be nice to know why this *Scheduling another build to catch up with XXX *occurs (for what use case) because it only caused me major headaches. On Tuesday, 28 October 2014 22:09:36 UTC+2, michaelw wrote: Wow... that would be great. I'm busy confirming it is unique to bitbucket. I suspect it is. When I've narrowed it down I'll submit. Thanks On 28 October 2014 13:24, Mark Waite mark.ea...@gmail.com javascript: wrote: I'm not sure what else could be happening in that job. Could you submit a bug report, and attach the job definition for the failing job, and the build logs for the cases where multiple jobs are being executed to catch up, yet the same SHA1 is used in each case during the catch up? Thanks, Mark Waite On Tue, Oct 28, 2014 at 1:45 AM, michaelw michae...@gmail.com javascript: wrote: Sha1's for all the builds are exactly the same. On Tuesday, 21 October 2014 22:34:47 UTC+2, Mark Waite wrote: If polling is not configured, then you'll need to read the build log of each job that was run, and extract the differences between those jobs. Usually, changes detected means that the git plugin believes that the remote repository includes a branch which matches the branches to build in the job definition and which points to a SHA1 which has not yet been built. It queues a build to run a job using that SHA1. Thanks, Mark Waite On Tue, Oct 21, 2014 at 4:43 AM, michaelw michae...@gmail.com wrote: There is nothing in my polling log and I have no polling configured. On Monday, 6 October 2014 18:26:21 UTC+2, Mark Waite wrote: If you've configured branches to build to use a wild card, and if there are changes on those branches compared to the last time they were built, then a bunch of builds will be queued for the changes on those branches. You might post your git polling log to show what changes it has detected, or the early part of the build log to show the state of the repository. Mark Waite On Mon, Oct 6, 2014 at 9:55 AM, michaelw michae...@gmail.com wrote: Hi All... Whenever I kick off a build in jenkins it queues up a bunch of builds claiming that it is doing so because changes are detected. I have disabled all polling etc. I did have the commit hook on but is also disabled. The only change is that we have moved our git repositories to bit bucket... again no commit hook configured there. I have also monitored the logs during a build and I don't see anything unusual... Please can someone help me trouble shoot this. Maybe I can dial up the logging so that I can work out why jenkins is behaving like this? Thanks -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Thanks! Mark Waite -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Thanks! Mark Waite -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- Thanks! Mark Waite -- You received this message because you are subscribed to the Google
Re: Jenkins CI and the accessibility of it's UI
On 29 October 2014 14:15, R. Tyler Croy ty...@monkeypox.org wrote: (replies inline) On Wed, 24 Sep 2014, laura1fxj...@gmail.com wrote: I?m not sure if this is the right forum for this request, but I was hoping someone might be able to point me in the right direction? I was hoping someone might be able to provide a Voluntary Product Accessibility Template (VPAT) or similar accessibility statement for Jenkins CI. I have included a blank VPAT for reference. What's the goal of such statements? Not being too informed on software accessibility challenges and requirements, I'd like to have an understanding of the cost/benefit for the Jenkins project to release/publish such a statement. It's fairly narrow for Jenkins I think. A commercial provider might consider it for large government contracts. Given Jenkins itself is API accessible and otherwise has a convenient web interface, adoption of WAI guidelines is probably sufficient. Half the time these statement requirements boil down to less than a page. It's there to ensure the supplier is aware of their responsibilities. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Correct Access Control with Apache frontend after upgrade ?
Some week ago I upgraded to version 1.584 and access control doesn't work well anymore, please some advice. I use Apache Frontend through ajp proxy as explained in the Jenkins wiki page (linke https://wiki.jenkins-ci.org/display/JENKINS/Apache+frontend+for+security) . Jenkins is run as a war in an existing tomcat instance. I use Apache Basic Authentication with Jenkins own user db. I know that this could conflict (as explained in the wiki) but it always seem to work as the delegate doesn't seem to work. However, after the upgrade it doesn't well anymore. I can browse Jenkins as a logged in user, but then when I click certain functionality like the PMD plugin, the browser comes with the login popup (with the text Jenkins popup footer text) and I can fill in whatever I want, I can't login. If I then open another browser, it starts over again: I can browse jenkins till I hit some functionality like PMD that shows the popup... I then have to restart Tomcat to have access again. Because of this conflict I tried the Jenkins security option to use Delegate to server container as Security Realm, but then I do get a http 302 error and the browser complaints that it performs too many redirect loops :(... (that's probably why I didn't use it in the past). It the same as the reported jenkins issue here: linke https://issues.jenkins-ci.org/browse/JENKINS-7278 So I am a bit lost now and not sure how to solve this, please some advice on this? Some details: httpd -v output: I noticed that the server build shows a date recently, maybe because of the auto update feature of the linux pacakges, but the latest is 2.2.29 currently Server version: Apache/2.2.15 (Unix) Server built: Oct 16 2014 14:48:21 My Apache snippets (I played with the settings but they had no effect): -- ProxyRequests Off ProxyPreserveHost Off AllowEncodedSlashes Off ProxyPass /jenkins ajp://127.0.0.1:8055/jenkins nocanon ProxyPassReverse /jenkins ajp://127.0.0.1:8055/jenkins Location / AuthType Basic AuthName Development AuthUserFile /etc/httpd/password/passwords AuthGroupFile /etc/httpd/password/groups Order allow,deny Allow from all Require group developers /Location - -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Jenkins update hangs on CentOS
Tracked as https://issues.jenkins-ci.org/browse/JENKINS-23273 On 30.10.2014, at 09:50, Yves Schumann starwarsfanl...@gmail.com wrote: Hi Jason, YMMD! :-) I investigated a little deeper what's going on during yum update. The update seems to stuck at the command chown -R jenkins /var/lib/jenkins but as there are a lot of jobs with huge svn checkouts, it just takes very long to touch every single file. Might be an improvement point because I do not see if this is neccessary on every update. Jenkins is the only user which uses these files. Kind regards, Yves -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Correct Access Control with Apache frontend after upgrade ?
This looks like a known issue tracked as https://issues.jenkins-ci.org/browse/JENKINS-25144 On 30.10.2014, at 11:26, Edbras post2edb...@gmail.com wrote: Some week ago I upgraded to version 1.584 and access control doesn't work well anymore, please some advice. I use Apache Frontend through ajp proxy as explained in the Jenkins wiki page (linke) . Jenkins is run as a war in an existing tomcat instance. I use Apache Basic Authentication with Jenkins own user db. I know that this could conflict (as explained in the wiki) but it always seem to work as the delegate doesn't seem to work. However, after the upgrade it doesn't well anymore. I can browse Jenkins as a logged in user, but then when I click certain functionality like the PMD plugin, the browser comes with the login popup (with the text Jenkins popup footer text) and I can fill in whatever I want, I can't login. If I then open another browser, it starts over again: I can browse jenkins till I hit some functionality like PMD that shows the popup... I then have to restart Tomcat to have access again. Because of this conflict I tried the Jenkins security option to use Delegate to server container as Security Realm, but then I do get a http 302 error and the browser complaints that it performs too many redirect loops :(... (that's probably why I didn't use it in the past). It the same as the reported jenkins issue here: linke So I am a bit lost now and not sure how to solve this, please some advice on this? Some details: httpd -v output: I noticed that the server build shows a date recently, maybe because of the auto update feature of the linux pacakges, but the latest is 2.2.29 currently Server version: Apache/2.2.15 (Unix) Server built: Oct 16 2014 14:48:21 My Apache snippets (I played with the settings but they had no effect): -- ProxyRequests Off ProxyPreserveHost Off AllowEncodedSlashes Off ProxyPass /jenkins ajp://127.0.0.1:8055/jenkins nocanon ProxyPassReverse /jenkins ajp://127.0.0.1:8055/jenkins Location / AuthType Basic AuthName Development AuthUserFile /etc/httpd/password/passwords AuthGroupFile /etc/httpd/password/groups Order allow,deny Allow from all Require group developers /Location - -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Correct Access Control with Apache frontend after upgrade ?
@Daniel, thanks, sorry I missed that Any idea how to solve the redirect loop issue when using Jenkins Delegate to server container? -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: HowTo save the last successful build?
Thanks for your answer. My problem is that I can only see the workspace with the built files of my current build (I can download them as zip). But where can I download former builds? Am Mittwoch, 29. Oktober 2014 09:51:07 UTC+1 schrieb matthew...@diamond.ac.uk: As far as I know, Jenkins always keeps the last successful build, even if you are using “discard old builds”. Are you observing something different? *From:* moni.sch...@googlemail.com javascript: [mailto: moni.sch...@googlemail.com javascript:] *Sent:* 29 October 2014 08:00 *To:* jenkins...@googlegroups.com javascript: *Subject:* HowTo save the last successful build? Hello, if a failed build follows follows on a successful build, the successful build isn´t available anymore. Is there any possibility to save the last successful build? Thanks! Monika -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
RE: HowTo save the last successful build?
Jenkins retains the build log and any artifacts that the build “archives”. It reuses the workspace each time you build. So each build must either archive artifacts to the Jenkins server or copy them away someplace. From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of moni.schaefer@googlemail.com Sent: Thursday, October 30, 2014 8:46 AM To: jenkinsci-users@googlegroups.com Subject: Re: HowTo save the last successful build? Thanks for your answer. My problem is that I can only see the workspace with the built files of my current build (I can download them as zip). But where can I download former builds? Am Mittwoch, 29. Oktober 2014 09:51:07 UTC+1 schrieb matthew...@diamond.ac.ukmailto:matthew...@diamond.ac.uk: As far as I know, Jenkins always keeps the last successful build, even if you are using “discard old builds”. Are you observing something different? From: moni.sch...@googlemail.comjavascript: [mailto:moni.sch...@googlemail.comjavascript:] Sent: 29 October 2014 08:00 To: jenkins...@googlegroups.comjavascript: Subject: HowTo save the last successful build? Hello, if a failed build follows follows on a successful build, the successful build isn´t available anymore. Is there any possibility to save the last successful build? Thanks! Monika -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.comjavascript:. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How does one get the basic jenkins mailer to send raw console?
I have the same question. The conversion of pathnames in the mailed out logs makes them unreadable on smartphones. I would like to mail out the log as is, with no conversion. Does anyone know where (approximately) the code that makes this change would live? I don't mind a little hacking JLM On Wednesday, February 13, 2013 8:11:32 PM UTC-5, Rodney Stanton wrote: There is a builtin , very clever, log filter, that is replacing paths to artifacts inside logs with the path to the Jenkins artifact. Is there a way to send Raw console? Rodney -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Jenkins Jobs Hang Intermittently
Hi All, I was curious if anyone else has run into this issue. Our Jenkins server will intermittently get hung jobs where they appear to be executing but the console log displays no output except for the pinwheel and no progress of the job is made. Clicking on the View as plain text link displays the following: No such file: /jenkins/jobs/JOB NAME/builds/DATE/log Going to that directory showed that the log directory in the path above does not exist. (The rest of the directory path exists.) Any thoughts as to what is going on or some way to debug this? Any help would be greatly appreciated. Thanks! Lew -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Jenkins on Windows: BSoD and Fortify
On 28/10/14 16:56, j.g.wess...@rn.rabobank.nl wrote: From the Jenkins-ci.org website we understand that the BSoD problem has been worked around in Jenkins version 1.580.x or higher. This means that upgrading to one of the latest (non LTS) versions would be a (temporary) solution for our problem. But, to solve BSoD’s is not the only challenge. FWIW, Jenkins LTS 1.580.1 was released yesterday (despite the website still saying 1.565.3). Regards, Chris -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: JOB_NAME not being passed correctly with Parametrized Trigger Plugin
If you're building on the same node, why not pass in the full path to the libraries as a parameter? On Oct 27, 2014, at 11:04 AM, Adam Mercer r...@gravity.phys.uwm.edu wrote: Hi Anyone? Surely the plugin shouldn't be stripping information when passing it on to downstream jobs? Cheers Adam On Thu, Oct 23, 2014 at 5:15 PM, Adam Mercer r...@gravity.phys.uwm.edu wrote: Hi I'm trying to tie a couple of jobs together using the Parametrized Trigger Plugin and am running into problems with the second job finding the libraries built by the first job. When the first job completes successfully I trigger a build of the second job, I'm forcing it to use the same node so that it can find the libraries. In the first job I install the libraries to a location on the build slave dependent upon the JOB_NAME and BUILD_NUMBER variables. I use the Parametrized Trigger Plugin to pass these onto the second job. However it look like that value of JOB_NAME that is getting passed on is incorrect and as such the library can't be found by the second job and the build fails. In order to start debugging this I printed out the value of JOB_NAME from the first job and the value that was passed to the second job, they differed. In the first job JOB_NAME is set to LALSuite/LAL/label=sl6 whereas is the second job it is seeing LALSuite/LAL, i.e. the label=sl6 is being dropped. Any ideas why this label information is not being passed along? Cheers Adam -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
HP Automation Automation Tool plugin TDConnectivity issue on Jenkins
Hello JenkinsUsers, My organization uses Jenkins for auto build and deployment purpose. Automation team has request to run functional test from Jenkins on designated Windows7 64-bit system on nightly basis. To achieve this, I have downloaded HP Application Tool plugin (version: 3.0.6). Current Jenkins version:1.571. Description about issue: so after downloading pluing into Jenkins, I made free style job to execute functional test periodically. Please find the attachment for more details. Two attachments: 1) Job configuration 2) Result I have installed TDConnectivity plugin on designated machine where Jenkins suppose to run funcational tests but seems like Jenkins is unable to detect it. Any help or guidance would be greatly appreciated. Thank you in advance. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Jenkins can no longer connect to the internet
I've had a Jenkins server running for about 6 months. I have updated plugins on many occasions, even updating Jenkins itself to the latest a few times. It has been a couple of months since I updated and I needed to update a plugin. Now when I try to update plugins, I get to the Installing Plugins/Upgrades page, but it gets stuck on Preparation - Checking internet connectivity This used to work. I tried: backreving to an older version of Jenkins. Using the latest version Running Jenkins on a different unix machine. A ping to www.google.com shows the machines I'm using have internet connectivity. I run Jenkins like this: nohup java -jar jenkins.war --httpPort=8080 jenkins_out.log I do not have any proxy server setup. This was not needed in the past. Any clue on where I can start debugging this further? Thanks. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: JOB_NAME not being passed correctly with Parametrized Trigger Plugin
You have two jobs, Job1 calling Job2. The parameter $JOB_NAME is local to each job, so in Job2 the value of $JOB_NAME is Job2. Add an additional param in Job1 ($JOB_1_NAME=$JOB_NAME) and use it in Job2. FYI, any value that's empty means that the parameter value is undefined. Check spellings too. On Thursday, October 23, 2014 3:16:46 PM UTC-7, Adam Mercer wrote: Hi Hi I'm trying to tie a couple of jobs together using the Parametrized Trigger Plugin and am running into problems with the second job finding the libraries built by the first job. When the first job completes successfully I trigger a build of the second job, I'm forcing it to use the same node so that it can find the libraries. In the first job I install the libraries to a location on the build slave dependent upon the JOB_NAME and BUILD_NUMBER variables. I use the Parametrized Trigger Plugin to pass these onto the second job. However it look like that value of JOB_NAME that is getting passed on is incorrect and as such the library can't be found by the second job and the build fails. In order to start debugging this I printed out the value of JOB_NAME from the first job and the value that was passed to the second job, they differed. In the first job JOB_NAME is set to LALSuite/LAL/label=sl6 whereas is the second job it is seeing LALSuite/LAL, i.e. the label=sl6 is being dropped. Any ideas why this label information is not being passed along? Cheers Adam -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Jenkins can no longer connect to the internet
Do a netstat command and that should show you whether the connection is being established or being dropper by a firewall or similar. Richard On 31/10/2014 7:26 AM, Mark Sinclair msincl...@juniper.net wrote: I've had a Jenkins server running for about 6 months. I have updated plugins on many occasions, even updating Jenkins itself to the latest a few times. It has been a couple of months since I updated and I needed to update a plugin. Now when I try to update plugins, I get to the Installing Plugins/Upgrades page, but it gets stuck on Preparation - Checking internet connectivity This used to work. I tried: backreving to an older version of Jenkins. Using the latest version Running Jenkins on a different unix machine. A ping to www.google.com shows the machines I'm using have internet connectivity. I run Jenkins like this: nohup java -jar jenkins.war --httpPort=8080 jenkins_out.log I do not have any proxy server setup. This was not needed in the past. Any clue on where I can start debugging this further? Thanks. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
RE: Jenkins Jobs Hang Intermittently
Hi Lew, Just a few thoughts: where are the jobs running – on the server or on a node? When you log into the machine actually running the job, what do you observe? What does the process monitor say? Terry From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Lew Sent: Thursday, October 30, 2014 10:23 AM To: jenkinsci-users@googlegroups.com Subject: Jenkins Jobs Hang Intermittently Hi All, I was curious if anyone else has run into this issue. Our Jenkins server will intermittently get hung jobs where they appear to be executing but the console log displays no output except for the pinwheel and no progress of the job is made. Clicking on the View as plain text link displays the following: No such file: /jenkins/jobs/JOB NAME/builds/DATE/log Going to that directory showed that the log directory in the path above does not exist. (The rest of the directory path exists.) Any thoughts as to what is going on or some way to debug this? Any help would be greatly appreciated. Thanks! Lew -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
script trigger plugin seems broken
Hi, I was using the script trigger plugin successfully however I think a recent update broke it (or I did something stupid). Looking for a way to debug it. Right now I get a very unhelpful: Polling on master. The expected script execution code is 0 [ERROR] - Polling error... I grabbed the source and have tried a few things but to no avail. Does anyone know how to extract more useful information out of it? thanks, Greg -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
How to tweak the sizes of the items on left pane of the homepage?
We modified names for certain jobs to let people easily find out what is running on a specific slave. After I upgraded to the latest version yesterday, the new CSS doesn't work well with the long names. I don't want the long name to be wrapped on high resolution screen. I managed to treak the width of the pan, but it still wraps the name even though there is still enough space. Also the Cancel cross icon took too much space than it should. How should I tweak it? -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Issue with Jenkins on CentOS 7 creating symbolic link to Windows Share using CIFS
To whom it may concern,
I have recently set up a Jenkins instance running on CentOS 7. I have also
mounted a Windows Share to this box and am able to read and write to it. I
have then configured the “Build Record Root Directory” parameter to use the
mounted Windows Share (/mnt/qsrfs/builds/Jenkins/${ITEM_FULLNAME}).
The issue I am having is that for every build that rights to this location
it firstly creates a time-stamped directory and then attempts to create a
symbolic link between the build number and the time-stamped directory. This
results in the builds reporting the following error:
Started by user Kosta Tenedios
ln 2014-10-31_15-17-05 /mnt/qsrfs/builds/Jenkins/NVivo_11_Win_NIGHTLY/36
failed
java.nio.file.FileSystemException:
/mnt/qsrfs/builds/Jenkins/NVivo_11_Win_NIGHTLY/36: Operation not supported
at
sun.nio.fs.UnixException.translateToIOException(UnixException.java:91)
at
sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
at
sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
at
sun.nio.fs.UnixFileSystemProvider.createSymbolicLink(UnixFileSystemProvider.java:456)
at java.nio.file.Files.createSymbolicLink(Files.java:996)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at hudson.Util.createSymlinkJava7(Util.java:1202)
at hudson.Util.createSymlink(Util.java:1118)
at hudson.model.Run.updateSymlinks(Run.java:1845)
at hudson.model.Run.execute(Run.java:1757)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at
hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
Note however that this does not cause the build to fail (thank goodness). I
have tried to rectify this by specifying the -Dhudson.Util.noSymLink=true
and -Dhudson.Util.symlinkEscapeHatch=true in the JENKINS_JAVA_OPTIONS
variable in /etc/sysconfig/Jenkins and have restarted the Jenkins daemon
but subsequent builds still report this error. Oddly enough though if you
query System Information in Jenkins I see these settings under System
Properties.
So I have two questions about this issue:
1. Is it possible to alter the behaviour of Jenkins when creating
symbolic links, or perhaps ask Jenkins to not create symbolic links?
2. Are there any samba/cifs options that I need to specify to stop
these errors from occurring?
Regards, Kosta Tenedios.
--
You received this message because you are subscribed to the Google Groups
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
