I'm a newbie in using Jenkins. I saw a tutorial that can bypass jenkins authentication by just changing the useSecurity from true to false in config.xml. By doing it, there will be no administrator or login attempt and anyone can access the "Manage Jenkins" and can configure it. Just wondering if there's a way to encrypt the config.xml and the jenkins can still recognize it, something like obfuscation?
Still, I can't find any solution.
Related
I'm trying to use JIRA Trigger Jenkins plugin. I've read maybe all similar issues but can't understand why it doesn't work.
I want to build when an issue status changed. I troubleshooted but it didn't help me. My web hook works I checked it as it shows in documentation, the plugin for Jenkins is installed, firewall checked (I have whitelisted 3 Jira cloud IPs for Jenkins instance on AWS), ssl checks on Jenkins passes. Also I configured logs on Jenkins from Jira, but can't get anything.
In trigger configuration I inserted my Jira user's email (my-email#gmail.com) as user and password. The user has administrator privileges. What else can be wrong? Please any idea.
I am trying to use the build failure analyzer plugin for Jenkins.
https://wiki.jenkins-ci.org/display/JENKINS/Build+Failure+Analyzer
In the documentation it says
The link is shown only if the permission UpdateCauses is set for the current user.
But it doesn't give any information on how what that is or how to set it.
I'm the only user for my Jenkins.
Thanks!
Go to Manage Jenkins > Configure Global Security and under the Access Control section on Authorization there will be the users and their permissions (if you use matrix base security) you will see the Build Failure Analyzer permissions:
So short answer, you configure the plugin permissions using Jenkins configurations.
I use Jenkins with Gerrit-Sonar plugin and face a very weird issue:
I configure the plugin to handle Gerrit REST API with my username\password
When I run the job the first time, it passes, but after it Jenkins goes to auto-restart, saying "Please wait, Jenkins is getting ready to work."
After this my credentials in plugin are reset to default ("jenkins"\"gibberish").
Build fails due to 401 to Gerrit
When I re-save the credentials, they are stored only till the next weird auto-restart.
Has anyone seen this issue before or what could be the cause of it?
Thanks!
It is not an answer for your question, but it may be a workaround: in the 1.0.8 version of Sonar-Gerrit plugin it has become possible to override Gerrit credentials on the plugin level.
Is there a way to setup a Jenkins from code (eg. AWS userscript) doing
configurations like setting up a user, configuring GIT and slack
plugins?
So far I can install the Jenkins and even add plugins but I'm not able to configure it. This is only possible doing manually afterwards.
I heard about the Jenkins-CLI but don't know how to obtain it, if I just setup the system? Is it also enough to configure the system as I would access it via the UI?
I'm completely stuck with Gerrit Trigger install. I installed Jenkins ver. 1.482 with the Gerrit Trigger (v2.6.0) plugin. I'm not able to configure it.
I installed a test gerrit server (v2.4.2). I have an admin user. I tried to configure Gerrit Trigger to use this access to build patches (this is a test system, I didn't want to bother to add real users).
In Gerrit Trigger options I configured gerrit access. Test connection button says conection is ok. Although I get The connection to Gerrit is not started yet. Check the Gerrit URL in the settings. warning on the top. I also tried to push restart at the bottom.
I've read documentation on both Hudson and Jenkins page of the plugin. I'm still unable to configure the plugin.
Do you have any idea what's wrong?
Probably Click the button to Save after testing, this is common mistake that you forget to save it !! I met this several times
See more explanation in https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger
Otherwise it is not clear what's your problem since this is a normal case.