Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Doony "build now" button misbehaving (wrong permission?) #73

Open
ghost opened this issue Jul 23, 2014 · 8 comments
Open

Doony "build now" button misbehaving (wrong permission?) #73

ghost opened this issue Jul 23, 2014 · 8 comments

Comments

@ghost
Copy link

ghost commented Jul 23, 2014

As seen here: https://www.dropbox.com/s/wdo1b8zb6n2y02r/jenkins-doony-no_build_permission.PNG

This occurs while using the Role-based Strategy Plugin (I use this to manage permissions on my Jenkins instance.)

It suggests that I might need the build permission, but I have that permission already as seen here: https://www.dropbox.com/s/h81pjgc40g38h6q/jenkins-doony-build_permission_present.PNG

I'm not completely sure if this is a doony problem, but it makes sense since doony is the one adding the extra "build now" buttons.

Thanks!
@kevinburke
Copy link
Owner

It's possible. Can you check for errors in your console and paste any
relevant messages here?

Kevin Burke
phone: 925.271.7005 | kev.inburke.com

On Wed, Jul 23, 2014 at 4:21 PM, Jake Andersen [email protected]
wrote:

As seen here:
https://www.dropbox.com/s/wdo1b8zb6n2y02r/jenkins-doony-no_build_permission.PNG

This occurs while using the Role-based Strategy Plugin (I use this to
manage permissions on my Jenkins instance.)

It suggests that I might need the build permission, but I have that
permission already as seen here:
https://www.dropbox.com/s/wdo1b8zb6n2y02r/jenkins-doony-no_build_permission.PNG

I'm not completely sure if this is a doony problem, but it makes sense
since doony is the one adding the extra "build now" buttons.

Thanks!

—
Reply to this email directly or view it on GitHub
#73.

@ghost
Copy link
Author

ghost commented Jul 24, 2014

Here is what pops up when I click "Build Now"

Jul 23, 2014 10:57:38 PM hudson.security.csrf.CrumbFilter doFilter
WARNING: No valid crumb was included in request for /job/LogCommands/build. Returning 403.

Now, the "No valid crumb ..." message was resolved (or so I thought) when I changed the Jenkins crumb from .crumb to JCrumb. I had to do this because NGINX sees the default .crumb as an error as ignores it. I'm not sure why it would think it was invalid now, as this is the only part of Jenkins now seeing this as invalid.

@kevinburke
Copy link
Owner

Gah, it's possible the server is now checking CSRF.

Can you provide some more details? I assume you need to be logged in to do builds on your machine?

@kevinburke
Copy link
Owner

can you check whether it still fails in the same way without the strategy plugin? i think it might have to do with logged-in users.

@ghost
Copy link
Author

ghost commented Jul 24, 2014

Sure, one sec.

@ghost
Copy link
Author

ghost commented Jul 24, 2014

I set it to "Anyone can do anything" and the problem persisted. Yes, to do builds you need to be logged in on my machine.

This was referenced Jan 20, 2016
Open
Open
@tolidano
Copy link

This is now happening for me as well.

<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>
<title>Error 403 No valid crumb was included in the request</title>
</head>
<body><h2>HTTP ERROR 403</h2>
<p>Problem accessing /job/deploy-production-all-deals/build. Reason:
<pre>    No valid crumb was included in the request</pre></p><hr><a href="http://eclipse.org/jetty">Powered by Jetty:// 9.4.z-SNAPSHOT</a><hr/>

</body>
</html>

@tolidano
Copy link

Ah - and we have found the issue. It's because the job has parameters. And by hitting Build Now, none are passed.

You should make it smart enough to see if there are parameters and have that link go to the "Build With Parameters" page if there are any (or let me pick, or something).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kevinburke @tolidano