[JIRA] (JENKINS-57351) Support for making Jenkins a "GitHub App"

2019-12-19 Thread ojacqu...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Jacques commented on  JENKINS-57351  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support for making Jenkins a "GitHub App"   
 

  
 
 
 
 

 
 Not finished yet, but some have in progress work to have Jenkins act as a GitHub app. See https://github.com/github-api/github-api/issues/570#issuecomment-562200472  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199127.1557217283000.13658.1576755120428%40Atlassian.JIRA.


[JIRA] (JENKINS-56773) High master CPU usage introduced by Blue Ocean 1.14.0

2019-04-03 Thread ojacqu...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Jacques commented on  JENKINS-56773  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: High master CPU usage introduced by Blue Ocean 1.14.0   
 

  
 
 
 
 

 
 Thanks Gavin Mogan.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-56773) High master CPU usage introduced by Blue Ocean 1.14.0

2019-03-27 Thread ojacqu...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Jacques commented on  JENKINS-56773  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: High master CPU usage introduced by Blue Ocean 1.14.0   
 

  
 
 
 
 

 
 /cc Craig Rodrigues - in case this can indeed be caused by JENKINS-52825.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-56773) High master CPU usage introduced by Blue Ocean 1.14.0

2019-03-27 Thread ojacqu...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Jacques created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56773  
 
 
  High master CPU usage introduced by Blue Ocean 1.14.0   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 image-2019-03-27-10-31-38-911.png, image-2019-03-27-10-35-23-276.png  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2019-03-27 09:37  
 
 
Environment: 
 BlueOcean 1.14.0  Jenkins 1.168  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Olivier Jacques  
 

  
 
 
 
 

 
 We went from BO 1.13.2 to BO 1.14.0. After the upgrade, we have seen a major CPU increase on our Jenkins master, leading to really slow UI and job execution, with threads being locked - see screenshot.Our master is configured to not run any job ("only build jobs with label _expression_ matching this node"). Using Jenkins monitor, we saw that ~90% of the CPU time was consumed by calls to the rest endpoint /blue/rest/organizations/jenkins/computers - see screenshot.   Looking at the release notes from 1.14.0, it seems that JENKINS-52825 has introduced that endpoint and should be an area to investigate. We had to rollback BO to 1.13.2 which does not exhibit that behavior.  
 

  
 
 
 
 

 
 
 
   

[JIRA] (JENKINS-56480) Threads in TIMED_WAITING causing build agents to hold on to completed tasks

2019-03-12 Thread ojacqu...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Jacques commented on  JENKINS-56480  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Threads in TIMED_WAITING causing build agents to hold on to completed tasks   
 

  
 
 
 
 

 
 Although not Bitbucket (we are a pure GitHub shop), we observe a similar symptom: task do get through the end, but worker never releases them.  {{In the slave thread dump, we get }} "jenkins WAITING on On Slaves: java.util.concurrent.locks.AbstractQueuedSynchronizer" Not to pollute your issue, we have a separate one: JENKINS-56441   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-56480) Threads in TIMED_WAITING causing build agents to hold on to completed tasks

2019-03-12 Thread ojacqu...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Jacques commented on  JENKINS-56480  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Threads in TIMED_WAITING causing build agents to hold on to completed tasks   
 

  
 
 
 
 

 
 Although not Bitbucket (we are a pure GitHub shop), we observe a similar symptom: task do get through the end, but worker never releases them.  {{In the slave thread dump, we get }} "jenkins WAITING on On Slaves: java.util.concurrent.locks.AbstractQueuedSynchronizer" Not to pollute your issue, we have a separate one: JENKINS-56441   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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-42509) authenticated team members should have read/build permissions when using Github Committer Authorization Strategy

2018-03-14 Thread ojacqu...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Jacques commented on  JENKINS-42509  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: authenticated team members should have read/build permissions when using Github Committer Authorization Strategy   
 

  
 
 
 
 

 
 Thanks Sam Gleske. Do we have an ETA on the next release?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





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