[JIRA] (JENKINS-36075) Gitlab oauth does not display in Security Realm

2016-08-26 Thread mohamed.el-habib+jenk...@digitas.fr (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mohamed El Habib resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed starting from version 1.0.5  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-36075  
 
 
  Gitlab oauth does not display in Security Realm   
 

  
 
 
 
 

 
Change By: 
 Mohamed El Habib  
 
 
Status: 
 Open Resolved  
 
 
Assignee: 
 Mohamed El Habib summer nguyen  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are 

[JIRA] (JENKINS-37030) Plugin does not support SSL SNI

2016-08-26 Thread mohamed.el-habib+jenk...@digitas.fr (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mohamed El Habib resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed into version 1.0.6  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-37030  
 
 
  Plugin does not support SSL SNI   
 

  
 
 
 
 

 
Change By: 
 Mohamed El Habib  
 
 
Status: 
 Open Resolved  
 
 
Assignee: 
 Mohamed El Habib Thorsten Kunz  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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 

[JIRA] (JENKINS-37517) Gitlab Oauth Plugin fails after login to server with groups with ldap_access set to null

2016-08-26 Thread mohamed.el-habib+jenk...@digitas.fr (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mohamed El Habib resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Hello, can you please test the version 1.0.7 This is an issue into java-gitlab-api 1.0.5, I think this is fixed into 1.0.6 Thanks  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-37517  
 
 
  Gitlab Oauth Plugin fails after login to server with groups with ldap_access set to null   
 

  
 
 
 
 

 
Change By: 
 Mohamed El Habib  
 
 
Status: 
 Open Resolved  
 
 
Assignee: 
 Mohamed El Habib Patrick Cherry  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 
   

[JIRA] (JENKINS-37518) Gitlab oath plugin docs advise incorrect API URL

2016-08-26 Thread mohamed.el-habib+jenk...@digitas.fr (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mohamed El Habib resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed into 1.0.7 version by @wzxjohn  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-37518  
 
 
  Gitlab oath plugin docs advise incorrect API URL   
 

  
 
 
 
 

 
Change By: 
 Mohamed El Habib  
 
 
Status: 
 Open Resolved  
 
 
Assignee: 
 Mohamed El Habib Patrick Cherry  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are 

[JIRA] (JENKINS-37049) GitLab OAuth plugin forked without preserving license

2016-08-26 Thread mohamed.el-habib+jenk...@digitas.fr (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mohamed El Habib resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Thanks you for reporting this issue. This is a copy paste error. Thanks for @wzxjohn for the fix. Please tell me if i make any other mistake this  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-37049  
 
 
  GitLab OAuth plugin forked without preserving license   
 

  
 
 
 
 

 
Change By: 
 Mohamed El Habib  
 
 
Status: 
 Open Resolved  
 
 
Assignee: 
 Mohamed El Habib Sam Gleske  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

 

[JIRA] (JENKINS-36043) Saving/Applying multi-branch job config causes NullPointerException hudson.scm.SCMS.parseSCM

2016-06-18 Thread mohamed.el-habib+jenk...@digitas.fr (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mohamed El Habib commented on  JENKINS-36043  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Saving/Applying multi-branch job config causes NullPointerException hudson.scm.SCMS.parseSCM   
 

  
 
 
 
 

 
 i have the same error with jenkins 2.9  
 

  
 
 
 
 

 
 
 

 
 
 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] [maven2] (JENKINS-3273) Maven build aborted before execution due to SocketTimeoutException

2014-07-25 Thread mohamed.el-habib+jenk...@digitas.fr (JIRA)














































Mohamed El Habib
 commented on  JENKINS-3273


Maven build aborted before execution due to SocketTimeoutException















ERROR: Aborted Maven execution for InterruptedIOException
java.net.SocketTimeoutException: Accept timed out
	at java.net.PlainSocketImpl.socketAccept(Native Method)
	at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:398)
	at java.net.ServerSocket.implAccept(ServerSocket.java:530)
	at java.net.ServerSocket.accept(ServerSocket.java:498)
	at hudson.maven.AbstractMavenProcessFactory$SocketHandler$AcceptorImpl.accept(AbstractMavenProcessFactory.java:211)
	at hudson.maven.AbstractMavenProcessFactory.newProcess(AbstractMavenProcessFactory.java:270)
	at hudson.maven.ProcessCache.get(ProcessCache.java:235)
	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:759)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:518)
	at hudson.model.Run.execute(Run.java:1710)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:231)
Finished: ABORTED



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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] [maven2] (JENKINS-3273) Maven build aborted before execution due to SocketTimeoutException

2014-07-25 Thread mohamed.el-habib+jenk...@digitas.fr (JIRA)












































 
Mohamed El Habib
 edited a comment on  JENKINS-3273


Maven build aborted before execution due to SocketTimeoutException
















Same error into Jenkins ver. 1.566

ERROR: Aborted Maven execution for InterruptedIOException
java.net.SocketTimeoutException: Accept timed out
	at java.net.PlainSocketImpl.socketAccept(Native Method)
	at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:398)
	at java.net.ServerSocket.implAccept(ServerSocket.java:530)
	at java.net.ServerSocket.accept(ServerSocket.java:498)
	at hudson.maven.AbstractMavenProcessFactory$SocketHandler$AcceptorImpl.accept(AbstractMavenProcessFactory.java:211)
	at hudson.maven.AbstractMavenProcessFactory.newProcess(AbstractMavenProcessFactory.java:270)
	at hudson.maven.ProcessCache.get(ProcessCache.java:235)
	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:759)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:518)
	at hudson.model.Run.execute(Run.java:1710)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:231)
Finished: ABORTED



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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] [openid] (JENKINS-23312) ClassNotFoundException: org.apache.xerces.parsers.DOMParser

2014-06-04 Thread mohamed.el-habib+jenk...@digitas.fr (JIRA)














































Mohamed El Habib
 created  JENKINS-23312


ClassNotFoundException: org.apache.xerces.parsers.DOMParser















Issue Type:


Bug



Affects Versions:


current



Assignee:


Kohsuke Kawaguchi



Attachments:


xerces-missing-for-openid.txt



Components:


openid, openid4java



Created:


04/Jun/14 12:10 PM



Description:


After updating to the new version of openid plugin login fail with the following error. ClassNotFoundException: org.apache.xerces.parsers.DOMParser
attached the complte stack trace.

To make it work we have added xercesImpl.jar and xml-apis.jar into plugins/openid4java/WEB-INF/lib/




Environment:


java version 1.7.0_45

Java(TM) SE Runtime Environment (build 1.7.0_45-b18)

Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)



Jenkins version 1.566



OS : Linux






Project:


Jenkins



Priority:


Blocker



Reporter:


Mohamed El Habib

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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.