? Did you
have a single keystore containing both self-signed and CA issued
certificates? What params did you pass to Jenkins at start-up?
--
JC
Le lundi 25 février 2013 17:11:24 UTC+1, David Doughty a écrit :
I've beening running jenkins 1.466.12.1 as jenkins on RHEL6.2 (we don't
have root
I've beening running jenkins 1.466.12.1 as jenkins on RHEL6.2 (we don't
have root access), under https for a few weeks now, using a self signed
certificate, no problems, other than than the issues for end users and
their browsers. We have now been issued an offical certificate CA chain
I've got some users who are trying as a post build action to deploy artefacts
to Nexus
Using the maven goal deploy the build picks up the settings.xml from the maven
install on the build box.
Using the plugin, it appears to be trying to access the user settings.xml
(jenkins user in
Natalie,
Can you not install ClearCase on the build box?
dD
On 21/08/2012 13:34, natalie_pub...@gmx.net natalie_pub...@gmx.net
wrote:
Hi there,
I'm trying to use Jenkins to build a C++ application. Since ClearCase and
compilation run on different operation systems, I created two jobs: The
Does anyone know if there is a capability currently in Jenkins (or as part of
the roadmap) to extend ACL to individual build jobs? Or perhaps if there is a
plugin that can provide such a capability already.
What I'm looking for is the ability to limit who can modify/run existing build
jobs, as
Cool, having looked at your website/presentation that looks exactly what I'm
looking for.
However, its bundled with the enterprise Jenkins release, can we get it
un-bundled?
dD
