Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Jenkins extension
-
I tried to configure jenkins extension.
the jenkins is on the same aws ec2 instance with the build master.
i created a user in Jenkins, gave him all the permission, took the api code from the jenkins user managment and put http://localhost:8080 (this is indeed the jenkins URL) and every time i try to create build step i get error 403 (forbidden) alert.
what can be the problem? what am i missing?
Thanks.Product: BuildMaster
Version: 4.7.4
-
Can you verify that the extension configuration profile you created is checked as "use this profile as the default"?
Once you've verified that, what happens if you browse to an API URL directly in your browser, entering the same credentials?
Example API URL: http://localhost:8080/view/All/api/xml
-
I get XML view about the details of my jenkins.
Another thing, when i gave Anonymous user the permissions and put its name on the username field, it worked.
Something about the username / API Token combination i can't understand.Thanks.
-
I should double check, when you checked the API URL, were you logged in as yourself? Make sure you open up a private browsing session when testing access. If you can access it that way, there's no reason that BuildMaster should not either... it just makes a web request to that URL.
-
What token does it use?
i've turned on Incognito and i wasn't logged in and this URL still gave me all the details about the server.
-
It uses the anonymous user, so if you still have permissions for that enabled it will work without credentials.
-
Right, silly me :)
so ilogged in with the user i wanted to put on buildmaster, and yet, same result.
-
When you say same result, do you mean you get a 403 or that it works in the browser?
-
Works.
It seems like that something in the combination of username and API token doesn't come up right.
-
Hm, anything is possible, but I have seen a custom API endpoint causing problems, and a one without privileges set for an API key.
Perhaps you can explore the code a little, to see what might be an issue? It's basically just simple HTTP calls to various URLS using Basic HTTP authentication:
https://github.com/Inedo/bmx-jenkins/blob/master/JenkinsClient.cs