[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project

2017-01-23 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-40596  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 400 upon opening direct link of project in a GitHub organization project   
 

  
 
 
 
 

 
 The rev proxy mon issue is tracked as JENKINS-31068.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project

2017-01-23 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Unfortunately the way we URL encode things like branch names and organization names you do have to make this config change to Tomcat for it to work correctly. Tomcat isn't the recommended way of deploying Jenkins and most people use Jetty.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-40596  
 
 
  400 upon opening direct link of project in a GitHub organization project   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the 

[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project

2017-01-23 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-40596  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 400 upon opening direct link of project in a GitHub organization project   
 

  
 
 
 
 

 
 Unless we're rewriting this to "make RPM detect this again", this is Not A Defect.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project

2017-01-23 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-40596  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 400 upon opening direct link of project in a GitHub organization project   
 

  
 
 
 
 

 
 Yes. It's misconfiguration of the reverse proxy. As I wrote above, the reverse proxy monitor used to detect this, but doesn't anymore.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project

2017-01-22 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-40596  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 400 upon opening direct link of project in a GitHub organization project   
 

  
 
 
 
 

 
 Daniel Beck Stephen Connolly wouldn't this also be an issue in Jenkins Classic too? I suspect this isn't a Blue Ocean problem.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project

2017-01-22 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40596  
 
 
  400 upon opening direct link of project in a GitHub organization project   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 release candidate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project

2017-01-21 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40596  
 
 
  400 upon opening direct link of project in a GitHub organization project   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 release candidate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project

2017-01-09 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40596  
 
 
  400 upon opening direct link of project in a GitHub organization project   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
Sprint: 
 release candidate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project

2017-01-09 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-40596  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 400 upon opening direct link of project in a GitHub organization project   
 

  
 
 
 
 

 
 

You can change this behaviour through the following flag
 Since https://github.com/jenkinsci/jenkins/commit/cffe9df0176b0ff895554ce7f2ea4d2f20062351#diff-8e93a62dbd0a8a2c62604d3cdd0b9526L59 the reverse proxy monitor I mentioned no longer detects this. Jesse Glick any particular reason why?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project

2017-01-08 Thread patrice.bouil...@novatec-gmbh.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrice Bouillet commented on  JENKINS-40596  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 400 upon opening direct link of project in a GitHub organization project   
 

  
 
 
 
 

 
 Solved it ... The problem is, apache tomcat (by default) does not allow to pass on encoded forward slashes in the URL path. You can change this behaviour through the following flag: https://tomcat.apache.org/tomcat-8.0-doc/config/systemprops.html#Security (org.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true). But as tomcat really seems to be used by many, maybe you should consider changing the encoded slash somehow so that others don't have to change the default option (there seems to be a valid security reason why it should behave like this). Anyway, thank you for your help! Now I'm happy that it works   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project

2017-01-08 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-40596  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 400 upon opening direct link of project in a GitHub organization project   
 

  
 
 
 
 

 
 Patrice Bouillet not off the top of my head. If your workspace was free of secrets then perhaps could zip it up and share it with one of us to try locally.  If you set up a different instance of jenkins say on your desktop, are you able to see this? I wonder if there is a plugin causing this. (there is also the support core plugin, which can provide a list of installed plugins and help with things, but it may also involve sharing logs and other things, which is not the best thing to do via JIRA).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project

2017-01-08 Thread patrice.bouil...@novatec-gmbh.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrice Bouillet commented on  JENKINS-40596  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 400 upon opening direct link of project in a GitHub organization project   
 

  
 
 
 
 

 
 Sorry for the late reply! No message about anything related to a reverse proxy is there (as mentioned before, we do have quite an easy setup: nothing more than a tomcat running jenkins). I tried to delete and initialize the github organization again, still no luck. Even with the newest version of Jenkins and your plugin. Furthermore, I don't see anything in the logs that could help here. Any other idea what I could do to further analyze the problem?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project

2016-12-23 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-40596  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 400 upon opening direct link of project in a GitHub organization project   
 

  
 
 
 
 

 
 Patrice Bouillet On the /manage URL, for administrators, is there a message about reverse proxy being broken? Not correctly handling URL encoded forward slashes is specifically tested by this test. If so, follow the instructions and fix your configuration.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project

2016-12-22 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey commented on  JENKINS-40596  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 400 upon opening direct link of project in a GitHub organization project   
 

  
 
 
 
 

 
 Michael Neale Cliff Meyers Don't think its stapler related. Here is what I did: 
 
Create cloudbeers GitHub org project, then load up dashboard and click on "CloudBeers, Inc. /  PR-demo" link that is: http://localhost:8080/jenkins/blue/organizations/jenkins/cloudbeers%2FPR-demo/activity/ 
Reload (press Cmd+R) to reload and it reloads just fine. 
 Could this be something else, like a proxy server as such misbehaving?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project

2016-12-22 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-40596  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 400 upon opening direct link of project in a GitHub organization project   
 

  
 
 
 
 

 
 Vivek Pandey that error is from stapler - it doesn't even get to executing client code, server just says 400 immediately.. odd.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project

2016-12-22 Thread cmey...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cliff Meyers commented on  JENKINS-40596  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 400 upon opening direct link of project in a GitHub organization project   
 

  
 
 
 
 

 
 So apparently any request that makes it to the server with "%2F" in the URL will bomb out. Perhaps this a core Stapler issue? For example this request yields a 400 response as well: http://jenkins.inspectit.rocks/blue/%2F/  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project

2016-12-22 Thread cmey...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cliff Meyers commented on  JENKINS-40596  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 400 upon opening direct link of project in a GitHub organization project   
 

  
 
 
 
 

 
 Got to be some issue then with BlueOceanUI from blueocean-web. For some reason it's rejecting the request.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project

2016-12-22 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-40596  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 400 upon opening direct link of project in a GitHub organization project   
 

  
 
 
 
 

 
 Cliff Meyers it happens when you open it from the dashboard - ie not even keyed in. if you open dashboard, then click on that pipeline, it loads fine. Try to refresh that browser tab - boom - that malformed error.  Super odd...   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project

2016-12-22 Thread cmey...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cliff Meyers commented on  JENKINS-40596  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 400 upon opening direct link of project in a GitHub organization project   
 

  
 
 
 
 

 
 So when I request this URL I receive an immediate 400 from the server: http://jenkins.inspectit.rocks/blue/organizations/jenkins/inspectIT-GitHub%2inspectIT/ But if I request this other project's URL, it renders as normal: http://jenkins.inspectit.rocks/blue/organizations/jenkins/inspectIT%20-%20Integration/ When navigating within the UI, the URl that is build to the first project is: http://jenkins.inspectit.rocks/blue/organizations/jenkins/inspectIT-GitHub%2FinspectIT Comparing the first and third URL's, the first URL it appears to be malformed: %2 is not a valid URI encoding. It should use %2F to escape a forward slash. Perhaps Patrice Bouillet could give some insight as to where that first URL came from? Was it copied from browser window, or from a particular part of the Blue Ocean UI... or perhaps someone keyed it in by hand in error?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project

2016-12-22 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey commented on  JENKINS-40596  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 400 upon opening direct link of project in a GitHub organization project   
 

  
 
 
 
 

 
 Michael Neale REST API corresponding to this job looks ok, http://jenkins.inspectit.rocks/blue/rest/organizations/jenkins/pipelines/inspectIT-GitHub/pipelines/inspectIT/. 400 is caused when http://jenkins.inspectit.rocks/blue/organizations/jenkins/inspectIT-GitHub%2inspectIT/ is accessed, its outside of REST API, guess its handled by UI code somewhere? Cliff Meyers do you know whats going on?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project

2016-12-22 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-40596  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 400 upon opening direct link of project in a GitHub organization project   
 

  
 
 
 
 

 
 Yes I can build it now - but I don't see that problem... you can remove my access now. There is something else going on, not specific to your repo. Sorry can't think of anything right now (if there are server side logs, would be good to see).  Maybe Vivek Pandey may know what case could trigger a 400 response (bad request) like this...   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project

2016-12-22 Thread patrice.bouil...@novatec-gmbh.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrice Bouillet commented on  JENKINS-40596  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 400 upon opening direct link of project in a GitHub organization project   
 

  
 
 
 
 

 
 I anyway forgot to add the repository to this team ... Now you have r/w access to the inspectit repository.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project

2016-12-22 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-40596  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 400 upon opening direct link of project in a GitHub organization project   
 

  
 
 
 
 

 
 Hrm, no I seem to need push access to get collaborators (github permissions problem)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project

2016-12-22 Thread patrice.bouil...@novatec-gmbh.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrice Bouillet commented on  JENKINS-40596  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 400 upon opening direct link of project in a GitHub organization project   
 

  
 
 
 
 

 
 You should have an invite. Let me know if you need more.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project

2016-12-22 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-40596  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 400 upon opening direct link of project in a GitHub organization project   
 

  
 
 
 
 

 
 Patrice Bouillet I think it may... think... worth a try. Still puzzled.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project

2016-12-22 Thread patrice.bouil...@novatec-gmbh.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrice Bouillet commented on  JENKINS-40596  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 400 upon opening direct link of project in a GitHub organization project   
 

  
 
 
 
 

 
 Read access to the project is sufficient (or do you need the access to the organization)? No proxy. It's a very simple setup. Tomcat with jenkins.war. Nothing more.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project

2016-12-22 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-40596  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 400 upon opening direct link of project in a GitHub organization project   
 

  
 
 
 
 

 
 Patrice Bouillet annoyingly I can't reproduce this. This is most strange. It seems somehow a service side originating error. Are there any other repos you can try?  Alternatively, could you add my github user michaelneale temporarily to your inspectIT project so I can set it up locally and see if I get the same thing?  Really puzzled by this. Are you using a proxy at all?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project

2016-12-22 Thread patrice.bouil...@novatec-gmbh.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrice Bouillet commented on  JENKINS-40596  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 400 upon opening direct link of project in a GitHub organization project   
 

  
 
 
 
 

 
 Sure, can leave the jobs as they are for now. If you want me to test something, let me know .  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project

2016-12-21 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale edited a comment on  JENKINS-40596  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 400 upon opening direct link of project in a GitHub organization project   
 

  
 
 
 
 

 
 Wow, that is a good one. Not as obvious as I thought (thought it was a malformed URL). This will take some investigating - thanks for making jenkins available - mind if you keep it open for a while? (we will probably want to make an acceptance test for this, which usually takes longer than the fix)Annoyingly I can't see the 400 error, it flashes past and disappears - do you happen to have the error text and can paste it in?EDIT: nevermind - I can see it when clicking direct, sorry!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project

2016-12-21 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40596  
 
 
  400 upon opening direct link of project in a GitHub organization project   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 release candidate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project

2016-12-21 Thread mne...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-40596  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 400 upon opening direct link of project in a GitHub organization project   
 

  
 
 
 
 

 
 Wow, that is a good one. Not as obvious as I thought (thought it was a malformed URL).  This will take some investigating - thanks for making jenkins available - mind if you keep it open for a while?  (we will probably want to make an acceptance test for this, which usually takes longer than the fix) Annoyingly I can't see the 400 error, it flashes past and disappears - do you happen to have the error text and can paste it in?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40596) 400 upon opening direct link of project in a GitHub organization project

2016-12-21 Thread patrice.bouil...@novatec-gmbh.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrice Bouillet created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40596  
 
 
  400 upon opening direct link of project in a GitHub organization project   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Dec/21 1:21 PM  
 
 
Environment: 
 Jenkins: 2.23, Blue Ocean: 1.0.0-b14  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Patrice Bouillet  
 

  
 
 
 
 

 
 I created a job of type "GitHub organization" named "inspectIT-GitHub" and added a the GitHub project "inspectIT" to it. The problem is, that I cannot use the links from the browser directly (or pressing F5), I do get a 400 back from Jenkins. If I open the links directly from blue ocean, it seems to be working fine. You can take a look at the problem in our running system: This is the base blue ocean url: http://jenkins.inspectit.rocks/blue/pipelines This is one of the links that is not working: http://jenkins.inspectit.rocks/blue/organizations/jenkins/inspectIT-GitHub%2FinspectIT/activity The standard pipeline test I created works on the other hand. So it could be related to this job type.