I recently updated jenkins, I believe by accident actually, by running yum
update on my linux EC2 instance. Since I did this, if the user defined in
/etc/sysconfig/jenkins is "root", jenkins launches fine. If I try to keep
user="jenkins" though, as it was before the update, the service doesn't
Currently I have a slave setup that I am manually launching from a windows
machine from the command line via jnlp. I have also tried launching from a
browser. In both cases, the issue I am running into is that the slave
machines stdout is not printing to the master's console output. So, I can't
Currently I'm using the parameterized build plugin to run the same job
multiple times. This downstream job, however, takes different parameters
for each build, so I have accomplished this by choosing the option to
"trigger a build for each file." The later builds then read their parameter
files
Currently I have a build that creates and updates a bunch of files which
are loaded into our IDE to customize it to display all our internal
libraries. This build is triggered on commits. After the build completes, I
commit and push these files back to my git repo on bitbucket via a Jenkins
ste
"The only thing missing is that they don't automatically have access to
newly created projects, which seems a very unusual requirement (and
surprising to your users?)."
Sorry, this was unclear. This is what I'm currently seeing (Demo user is
seeing new projects), but *not *what I want. I'll loo
As far as I can tell, if I am using the built in project based security, I
*HAVE
*to give users overall read permissions, then in the security for a
particular project, I can modify the settings? This seems really dumb. What
I want to do is have a "Demo" user, who can see nothing but the projec
