Re: "Restrict where this project can be run" not saving...

https://issues.jenkins-ci.org/browse/JENKINS-14197 submitted >

Re: Differences in Jenkins master behavior between host operating systems

I don't believe the symlinks exist to make builds more easily accessible. I don't believe the builds are meant to be accessed directly from the file system under $JENKINS_HOME. If you access the builds using the Web UI, you will always have the same interface, regardless where you run Jenkins.

Re: Publish over ssh using tunneling (ProxyCommand)

Even though having all these hundreds of plugins is a great thing, I believe people sometimes forget there is an amazing amount of flexibility and power in a simple Free-style job that executes a Shell build step. You can do just about anything with that. You can even call the real scp command t

Re: Setting up Jenkins with xcode build with CI server

Arnaud, I thought the Xcode plugin solved all the issues about keychain management? I tried to open up a discussion about it some time ago but I was assured there really is no problem if people just use the Xcode plugin. Recent Jenkins Max OS X installers have the option to create a new account

Re: Build hang at start while cleaning up

Jenkins usually isn't much slower checking out source code. I do not use many SVN repositories but I do know I had problems with one SVN repo that had a couple of gigabytes of files. Jenkins was running out of memory. You should check the output of the Jenkins process and/or the system logs unde

Re: Multiple Plug-ins Conflicting?

You might want to take this to jenkins-dev list. There's people who can probably help you better. -- Sami Larry Gadallah kirjoitti 23.6.2012 kello 0.13: > We are running Jenkins 1.462 on an Ubuntu 10.04 LTS server, and we are using > two plugins: > > 1. Gerrit trigger (https://wiki.jenkins-ci

RE: "Restrict where this project can be run" not saving...

I don’t think it is just you. I just noticed that we had a number of jobs waiting for executors, but the master and all slaves were idle. Restarting the master did not help. Moreover, I think that the affected jobs previously had “restrict where this project can run” set, but now it’s unset. I’m

RE: M2 release build and Trigger build

No – by trigger I meant a job step that executed curl. If you have any reported/publishers that effect the build outcome then you would need to write your own publisher that then performed the http post (or seeing as you are already inside Jenkins called the job with the m2release). /James Fro

Re: M2 release build and Trigger build

I take it that you are referring to using "Trigger/Call builds on other projects". This takes project name as input. I don't see any obvious way to include action to kickoff. Am I missing something? I guess I could use remote trigger instead and put action on the URL. This approach seem to have

RE: M2 release build and Trigger build

You can add a trigger on the upstream job to post to the action to kick off a build. However you will need to post the data (developmentURL etc). /James > -Original Message- > From: jenkinsci-users@googlegroups.com [mailto:jenkinsci- > us...@googlegroups.com] On Behalf Of Eskay > Sent: