[JIRA] (JENKINS-61818) AUTH: IllegalStateException: Singleton is called recursively returning different results

2020-05-08 Thread 'lan...@yandex.ru (JIRA)' via Jenkins Issues
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-61818  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: AUTH: IllegalStateException: Singleton is called recursively returning different results   
 

  
 
 
 
 

 
 Got that in 2.222.3 Downgrading to 2.222.1 helped. Until that, jobs were enable to start  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.205668.1586157546000.23922.1588976340177%40Atlassian.JIRA.


[JIRA] (JENKINS-55453) Github PR creating job but not building

2019-02-01 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-55453  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Github PR creating job but not building   
 

  
 
 
 
 

 
 github plugin itself does nothing with PR webhooks, so it can be something wrong with other plugins. In case you use pipeline - thats full responsibility of Github Branch Source plugin  
 

  
 
 
 
 

 
 
 

 
 
 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-38674) GitHubCommitStatusSetter unusable in pipeline with multiple checkout steps

2017-03-31 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-38674  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GitHubCommitStatusSetter unusable in pipeline with multiple checkout steps   
 

  
 
 
 
 

 
 Thanks, Marc. Added your example to plugin's wiki  
 

  
 
 
 
 

 
 
 

 
 
 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.


[JIRA] (JENKINS-43181) Unable to use the same buildWithParameter variable webhook across different repositories

2017-03-29 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43181  
 
 
  Unable to use the same buildWithParameter variable webhook across different repositories   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Component/s: 
 github-plugin  
 

  
 
 
 
 

 
 
 

 
 
 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.


[JIRA] (JENKINS-43181) Unable to use the same buildWithParameter variable webhook across different repositories

2017-03-29 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev assigned an issue to huybrechts  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43181  
 
 
  Unable to use the same buildWithParameter variable webhook across different repositories   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Assignee: 
 Kirill Merkushev huybrechts  
 

  
 
 
 
 

 
 
 

 
 
 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.


[JIRA] (JENKINS-42597) Percent character (%) in filenames is not url-encoded in the CHANGES page

2017-03-09 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev assigned an issue to Mark Waite  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42597  
 
 
  Percent character (%) in filenames is not url-encoded in the CHANGES page   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Assignee: 
 Kirill Merkushev Mark Waite  
 

  
 
 
 
 

 
 
 

 
 
 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.


[JIRA] (JENKINS-42597) Percent character (%) in filenames is not url-encoded in the CHANGES page

2017-03-09 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42597  
 
 
  Percent character (%) in filenames is not url-encoded in the CHANGES page   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Component/s: 
 git-plugin  
 
 
Component/s: 
 github-plugin  
 

  
 
 
 
 

 
 
 

 
 
 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.


[JIRA] (JENKINS-42562) Error: JAVA_HOME not found in your environment

2017-03-08 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42562  
 
 
  Error: JAVA_HOME not found in your environment   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Assignee: 
 Kirill Merkushev  
 

  
 
 
 
 

 
 
 

 
 
 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.


[JIRA] (JENKINS-42562) Error: JAVA_HOME not found in your environment

2017-03-08 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42562  
 
 
  Error: JAVA_HOME not found in your environment   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Component/s: 
 support-core-plugin  
 
 
Component/s: 
 github-plugin  
 

  
 
 
 
 

 
 
 

 
 
 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.


[JIRA] (JENKINS-42562) Error: JAVA_HOME not found in your environment

2017-03-08 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42562  
 
 
  Error: JAVA_HOME not found in your environment   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Priority: 
 Blocker Trivial  
 

  
 
 
 
 

 
 
 

 
 
 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.


[JIRA] (JENKINS-42562) Error: JAVA_HOME not found in your environment

2017-03-08 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-42562  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Error: JAVA_HOME not found in your environment   
 

  
 
 
 
 

 
 Job configuration will be very helpful, and please choose components carefully. Gihub plugin knows nothing about your path and maven  
 

  
 
 
 
 

 
 
 

 
 
 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.


[JIRA] (JENKINS-39482) GitHub commit status not working with GitHubCommitStatusSetter on first build of branch in multi-branch pipeline

2017-02-25 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-39482  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GitHub commit status not working with GitHubCommitStatusSetter on first build of branch in multi-branch pipeline   
 

  
 
 
 
 

 
 JENKINS-41795 is not related to this issue. How it works with defaults - pipeline is a just text for jenkins and jenkins knows nothing about content of the script before first evaluation. Status step tries to find defined repos with dedicated jenkins api. But when jenkins dont know about script content - it can't provide info about repos to the status setter step. As a workaround for short-living jobs you can define repo with manual provider (as in Peter Springsteen's example)  
 

  
 
 
 
 

 
 
 

 
 
 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-42208) cannot save build trigger selector 'GitHub hook trigger for GITScm polling'

2017-02-22 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42208  
 
 
  cannot save build trigger selector 'GitHub hook trigger for GITScm polling'   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Labels: 
 GITScm GitHub for hook polling trigger  
 

  
 
 
 
 

 
 
 

 
 
 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-42208) cannot save build trigger selector 'GitHub hook trigger for GITScm polling'

2017-02-22 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42208  
 
 
  cannot save build trigger selector 'GitHub hook trigger for GITScm polling'   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Component/s: 
 core  
 
 
Component/s: 
 github-plugin  
 

  
 
 
 
 

 
 
 

 
 
 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-42208) cannot save build trigger selector 'GitHub hook trigger for GITScm polling'

2017-02-22 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42208  
 
 
  cannot save build trigger selector 'GitHub hook trigger for GITScm polling'   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Assignee: 
 Kirill Merkushev  
 

  
 
 
 
 

 
 
 

 
 
 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-42208) cannot save build trigger selector 'GitHub hook trigger for GITScm polling'

2017-02-22 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-42208  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: cannot save build trigger selector 'GitHub hook trigger for GITScm polling'   
 

  
 
 
 
 

 
 Cool, but why you think its a github-plugin bug?  
 

  
 
 
 
 

 
 
 

 
 
 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-39477) Github Plugin with Two Factor Authentication (2FA)

2017-02-15 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev resolved as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39477  
 
 
  Github Plugin with Two Factor Authentication (2FA)   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Status: 
 Reopened Resolved  
 
 
Resolution: 
 Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 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-39477) Github Plugin with Two Factor Authentication (2FA)

2017-02-15 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev edited a comment on  JENKINS-39477  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Github Plugin with Two Factor Authentication (2FA)   
 

  
 
 
 
 

 
 Github plugin already uses oauth tokens  to  for  authentication.And can help to fetch such token with required scopes in Jenkins Global configuration UI (by creating token using login+password).But it can't fetch token by itself if you use 2fa. If u use 2fa, you should create token manually and provide it in the global 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-39477) Github Plugin with Two Factor Authentication (2FA)

2017-02-15 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-39477  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Github Plugin with Two Factor Authentication (2FA)   
 

  
 
 
 
 

 
 Github plugin already uses oauth tokens to authentication. And can help to fetch such token with required scopes in Jenkins Global configuration UI (by creating token using login+password). But it can't fetch token by itself if you use 2fa. If u use 2fa, you should create token manually and provide it in the global 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-40150) Git operations fail after global lib is loaded

2017-02-12 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-40150  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git operations fail after global lib is loaded   
 

  
 
 
 
 

 
 Can you add more detailed example? I'm not very familiar with pipeline ecosystem, so it will be very helpful if i can reproduce exact your usecase.  
 

  
 
 
 
 

 
 
 

 
 
 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-40150) Git operations fail after global lib is loaded

2017-02-12 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-40150  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git operations fail after global lib is loaded   
 

  
 
 
 
 

 
 I'll add provider  
 

  
 
 
 
 

 
 
 

 
 
 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-40814) Jenkins Github trigger doesnt work unless build start manually

2017-02-02 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev edited a comment on  JENKINS-40814  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins Github trigger doesnt work unless build start manually   
 

  
 
 
 
 

 
 Its a pipeline trait. GH plugin uses scm part to get the exact github repo url. But there is no any information about scm before first evaluation of your script. If it doesn't work after first build, please provide logs as mentioned in plugin docs  
 

  
 
 
 
 

 
 
 

 
 
 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-40814) Jenkins Github trigger doesnt work unless build start manually

2017-02-02 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-40814  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins Github trigger doesnt work unless build start manually   
 

  
 
 
 
 

 
 Its a pipeline trait. GH plugin uses scm part to get the exact github repo url. But there is no any information about scm before first evaluation of your script.  
 

  
 
 
 
 

 
 
 

 
 
 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-41561) Pullrequest github executes Jenkinsfile of origin branch

2017-01-31 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev assigned an issue to Jesse Glick  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41561  
 
 
  Pullrequest github executes Jenkinsfile of origin branch   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Assignee: 
 Kirill Merkushev Jesse Glick  
 

  
 
 
 
 

 
 
 

 
 
 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-41561) Pullrequest github executes Jenkinsfile of origin branch

2017-01-31 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-41561  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pullrequest github executes Jenkinsfile of origin branch   
 

  
 
 
 
 

 
 seems its not a problem of github-plugin (it does nothing with jenkinsfile and PRs)  
 

  
 
 
 
 

 
 
 

 
 
 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-41561) Pullrequest github executes Jenkinsfile of origin branch

2017-01-31 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41561  
 
 
  Pullrequest github executes Jenkinsfile of origin branch   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Component/s: 
 pipeline-github-lib-plugin  
 
 
Component/s: 
 github-plugin  
 

  
 
 
 
 

 
 
 

 
 
 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-26886) Variables not being substituted in github URLs for $JOB_NAME

2017-01-25 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-26886  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Variables not being substituted in github URLs for $JOB_NAME   
 

  
 
 
 
 

 
 Now it knows nothing about env vars of jenkins. It should be implemented.  
 

  
 
 
 
 

 
 
 

 
 
 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-41172) Build when a change is pushed to GitHub No longer available after update of plugin

2017-01-19 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41172  
 
 
  Build when a change is pushed to GitHub No longer available after update of plugin   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Status: 
 Open Closed  
 
 
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 "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-41172) Build when a change is pushed to GitHub No longer available after update of plugin

2017-01-19 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-41172  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Build when a change is pushed to GitHub No longer available after update of plugin   
 

  
 
 
 
 

 
 Yep, Github hook trigger for GITscm polling is the new name. Will add this renaming to release notes   
 

  
 
 
 
 

 
 
 

 
 
 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-39590) Switch to `GitHub.parseEventPayload` for event parsing

2017-01-12 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-39590  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Switch to `GitHub.parseEventPayload` for event parsing   
 

  
 
 
 
 

 
 released as 1.25.1  
 

  
 
 
 
 

 
 
 

 
 
 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-39590) Switch to `GitHub.parseEventPayload` for event parsing

2017-01-12 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev updated  JENKINS-39590  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39590  
 
 
  Switch to `GitHub.parseEventPayload` for event parsing   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Status: 
 In Review Resolved  
 
 
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 "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-41026) Jenkins failed to connect to GIT repository

2017-01-12 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41026  
 
 
  Jenkins failed to connect to GIT repository   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Status: 
 Open Closed  
 
 
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 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-41026) Jenkins failed to connect to GIT repository

2017-01-12 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-41026  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins failed to connect to GIT repository   
 

  
 
 
 
 

 
 Not a github-plugin issue. ssh checkout url requires credentials. Or you can just use https url instead.  
 

  
 
 
 
 

 
 
 

 
 
 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-41026) Jenkins failed to connect to GIT repository

2017-01-12 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41026  
 
 
  Jenkins failed to connect to GIT repository   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Priority: 
 Blocker Trivial  
 

  
 
 
 
 

 
 
 

 
 
 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-41026) Jenkins failed to connect to GIT repository

2017-01-12 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41026  
 
 
  Jenkins failed to connect to GIT repository   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Component/s: 
 github-plugin  
 

  
 
 
 
 

 
 
 

 
 
 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-40522) "Started by" link on downstream jobs does not work correctly

2016-12-20 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40522  
 
 
  "Started by" link on downstream jobs does not work correctly   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Priority: 
 Minor Major  
 

  
 
 
 
 

 
 
 

 
 
 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-40522) "Started by" link on downstream jobs does not work correctly

2016-12-20 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-40522  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Started by" link on downstream jobs does not work correctly   
 

  
 
 
 
 

 
 Thanks for the report - accepted  
 

  
 
 
 
 

 
 
 

 
 
 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-39845) GitHub project URL property should not trim off tree/branch

2016-12-14 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-39845  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GitHub project URL property should not trim off tree/branch   
 

  
 
 
 
 

 
 This property is used (programmatically) in most places as a link to root of projects and expected to be without any additional path. If u want exact branch - you can send us PR with additional field that can point to exact place in UI. But we will not change current behavior of existing field ever.  
 

  
 
 
 
 

 
 
 

 
 
 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-39632) Unselecting "Build when a change is pushed to GitHub" results in NullPointerException and breaks all builds in Jenkins

2016-12-12 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-39632  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unselecting "Build when a change is pushed to GitHub" results in NullPointerException and breaks all builds in Jenkins   
 

  
 
 
 
 

 
 Unmarshalling for job which contains null tag  
 

  
 
 
 
 

 
 
 

 
 
 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-38277) The webhook registration didn't register the push hook

2016-12-12 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev assigned an issue to Kohsuke Kawaguchi  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38277  
 
 
  The webhook registration didn't register the push hook   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Assignee: 
 Kirill Merkushev Kohsuke Kawaguchi  
 

  
 
 
 
 

 
 
 

 
 
 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-39482) GitHub commit status not working with GitHubCommitStatusSetter on first build of branch in multi-branch pipeline

2016-11-18 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev edited a comment on  JENKINS-39482  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GitHub commit status not working with GitHubCommitStatusSetter on first build of branch in multi-branch pipeline   
 

  
 
 
 
 

 
 Thx, xianjun zhu! Will add  ypur  your  example to the docs  
 

  
 
 
 
 

 
 
 

 
 
 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-39482) GitHub commit status not working with GitHubCommitStatusSetter on first build of branch in multi-branch pipeline

2016-11-18 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-39482  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GitHub commit status not working with GitHubCommitStatusSetter on first build of branch in multi-branch pipeline   
 

  
 
 
 
 

 
 Thx, xianjun zhu! Will add ypur example to the docs  
 

  
 
 
 
 

 
 
 

 
 
 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-38937) GitHub API cache is not working

2016-11-17 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38937  
 
 
  GitHub API cache is not working   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Assignee: 
 Kirill Merkushev  
 

  
 
 
 
 

 
 
 

 
 
 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-38937) GitHub API cache is not working

2016-11-17 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-38937  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GitHub API cache is not working   
 

  
 
 
 
 

 
 Yep, gh-branch-source creates and uses own gh client, so i can't help in gh-plugin with issue   
 

  
 
 
 
 

 
 
 

 
 
 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-38937) GitHub API cache is not working

2016-11-17 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38937  
 
 
  GitHub API cache is not working   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Component/s: 
 github-branch-source-plugin  
 
 
Component/s: 
 github-plugin  
 

  
 
 
 
 

 
 
 

 
 
 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-38937) GitHub API cache is not working

2016-11-11 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev edited a comment on  JENKINS-38937  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GitHub API cache is not working   
 

  
 
 
 
 

 
 You can check that cache is used by following steps:1. Click on "Reregister hooks for all jobs"2. Check that there is a folder in cache:{code}$ du -h /opt/jenkins/org.jenkinsci.plugins.github.GitHubPlugin.cache/796K /opt/jenkins/org.jenkinsci.plugins.github.GitHubPlugin.cache/76c844e5800K /opt/jenkins/org.jenkinsci.plugins.github.GitHubPlugin.cache/{code}3. Set cache size to 0, then save global config4. Now cache should be cleared:{code}$ du -h /opt/jenkins/org.jenkinsci.plugins.github.GitHubPlugin.cache/4.0K /opt/jenkins/org.jenkinsci.plugins.github.GitHubPlugin.cache/{code}5. Set cache to any positive num back and resave global config. Then check steps 1-2.Then please write results . Also please provide full list of plugins (maybe some of them eat your limits without using cache from GitHub plugin's client?)   
 

  
 
 
 
 

 
 
 

 
 
 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-38937) GitHub API cache is not working

2016-11-11 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-38937  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GitHub API cache is not working   
 

  
 
 
 
 

 
 You can check that cache is used by following steps: 1. Click on "Reregister hooks for all jobs" 2. Check that there is a folder in cache: 

 

$ du -h /opt/jenkins/org.jenkinsci.plugins.github.GitHubPlugin.cache/
796K	/opt/jenkins/org.jenkinsci.plugins.github.GitHubPlugin.cache/76c844e5
800K	/opt/jenkins/org.jenkinsci.plugins.github.GitHubPlugin.cache/
 

 3. Set cache size to 0, then save global config 4. Now cache should be cleared: 

 

$ du -h /opt/jenkins/org.jenkinsci.plugins.github.GitHubPlugin.cache/
4.0K	/opt/jenkins/org.jenkinsci.plugins.github.GitHubPlugin.cache/
 

 5. Set cache to any positive num back and resave global config. Then check steps 1-2. Then please write results  
 

  
 
 
 
 

 
 
 

 
 
 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 

[JIRA] (JENKINS-39632) Unselecting "Build when a change is pushed to GitHub" results in NullPointerException and breaks all builds in Jenkins

2016-11-10 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-39632  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unselecting "Build when a change is pushed to GitHub" results in NullPointerException and breaks all builds in Jenkins   
 

  
 
 
 
 

 
 Cool, but how did you get that  in config?  Can't reproduce it  
 

  
 
 
 
 

 
 
 

 
 
 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-39482) GitHub commit status not working with GitHubCommitStatusSetter on first build of branch in multi-branch pipeline

2016-11-04 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Please read docs for pipeline plugin. On first run there is no information about git (pipeline doesn't provide it)  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-39482  
 
 
  GitHub commit status not working with GitHubCommitStatusSetter on first build of branch in multi-branch pipeline   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 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 

[JIRA] (JENKINS-39477) Github Plugin with Two Factor Authentication (2FA)

2016-11-04 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 2FA auth requires pin which can't be retrieved automatically. Nobody use 2FA and store all creds in jenkins, where u can fetch any creds with help of groovy console  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-39477  
 
 
  Github Plugin with Two Factor Authentication (2FA)   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 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 

[JIRA] (JENKINS-39254) Add possibility to change commit URL

2016-10-26 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-39254  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add possibility to change commit URL   
 

  
 
 
 
 

 
 Its already released  
 

  
 
 
 
 

 
 
 

 
 
 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-39254) Add possibility to change commit URL

2016-10-26 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39254  
 
 
  Add possibility to change commit URL   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Status: 
 Open Closed  
 
 
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 "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-38935) GitHub Plugin settings not surviving Jenkins restart

2016-10-12 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-38935  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GitHub Plugin settings not surviving Jenkins restart   
 

  
 
 
 
 

 
 thanks for the report  
 

  
 
 
 
 

 
 
 

 
 
 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-34144) Don't fail the job if setting the GitHub status fails

2016-10-12 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34144  
 
 
  Don't fail the job if setting the GitHub status fails   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Status: 
 In Progress Closed  
 
 
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 "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-34144) Don't fail the job if setting the GitHub status fails

2016-10-12 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-34144  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Don't fail the job if setting the GitHub status fails   
 

  
 
 
 
 

 
 handler added  
 

  
 
 
 
 

 
 
 

 
 
 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-38929) testcase

2016-10-12 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev closed an issue as Incomplete  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38929  
 
 
  testcase   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Incomplete  
 

  
 
 
 
 

 
 
 

 
 
 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-36961) GithubCommitStatusSetter intermittently doesn't set status update in Jenkins Pipeline

2016-10-12 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36961  
 
 
  GithubCommitStatusSetter intermittently doesn't set status update in Jenkins Pipeline   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 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-36961) GithubCommitStatusSetter intermittently doesn't set status update in Jenkins Pipeline

2016-10-12 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-36961  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GithubCommitStatusSetter intermittently doesn't set status update in Jenkins Pipeline   
 

  
 
 
 
 

 
 Github plugin can find your repo automatically only by scm. With pipeline it populated only after first build. You can define repo url and sha manually  
 

  
 
 
 
 

 
 
 

 
 
 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-36510) GitHubCommitStatusSetter doesn't allow setting status url

2016-10-12 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev edited a comment on  JENKINS-36510  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GitHubCommitStatusSetter doesn't allow setting status url   
 

  
 
 
 
 

 
 now you can setup backref provider and define any link manually (see https://github.com/jenkinsci/github-plugin/pull/138 for details)  
 

  
 
 
 
 

 
 
 

 
 
 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-36510) GitHubCommitStatusSetter doesn't allow setting status url

2016-10-12 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-36510  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GitHubCommitStatusSetter doesn't allow setting status url   
 

  
 
 
 
 

 
 now you can setup backref provider and define any link manually  
 

  
 
 
 
 

 
 
 

 
 
 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-36510) GitHubCommitStatusSetter doesn't allow setting status url

2016-10-12 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36510  
 
 
  GitHubCommitStatusSetter doesn't allow setting status url   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Status: 
 Open Closed  
 
 
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 "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-35011) GitHub Plugin allows unauthenticated access despite global security configuration

2016-10-12 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-35011  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GitHub Plugin allows unauthenticated access despite global security configuration   
 

  
 
 
 
 

 
 Now plugin allows you to define hook secret on github side, so only those who knows secret can trigger build. Otherwise they can do nothing. This url can't be secured with password as github expects full access to this endpoint  
 

  
 
 
 
 

 
 
 

 
 
 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-35011) GitHub Plugin allows unauthenticated access despite global security configuration

2016-10-12 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-35011  
 
 
  GitHub Plugin allows unauthenticated access despite global security configuration   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Status: 
 Open Closed  
 
 
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 "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-38024) GithubLinkAnnotator NPE

2016-10-12 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38024  
 
 
  GithubLinkAnnotator NPE   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Priority: 
 Major Minor  
 

  
 
 
 
 

 
 
 

 
 
 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-38937) GitHub API cache is not working

2016-10-12 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev started work on  JENKINS-38937  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 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-38937) GitHub API cache is not working

2016-10-12 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev stopped work on  JENKINS-38937  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 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-38937) GitHub API cache is not working

2016-10-12 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev assigned an issue to Kirill Merkushev  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38937  
 
 
  GitHub API cache is not working   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Assignee: 
 Kirill Merkushev  
 

  
 
 
 
 

 
 
 

 
 
 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-38935) GitHub Plugin settings not surviving Jenkins restart

2016-10-12 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 should be fixed in 1.22.2  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-38935  
 
 
  GitHub Plugin settings not surviving Jenkins restart   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Status: 
 Open Resolved  
 
 
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 "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-38937) GitHub API cache is not working

2016-10-12 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38937  
 
 
  GitHub API cache is not working   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Component/s: 
 github-api-plugin  
 

  
 
 
 
 

 
 
 

 
 
 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-38937) GitHub API cache is not working

2016-10-12 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-38937  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GitHub API cache is not working   
 

  
 
 
 
 

 
 shipped fix in 1.22.2 - try it please  
 

  
 
 
 
 

 
 
 

 
 
 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-38935) GitHub Plugin settings not surviving Jenkins restart

2016-10-12 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-38935  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GitHub Plugin settings not surviving Jenkins restart   
 

  
 
 
 
 

 
 same  http://codepaste.net/6sbmwn  
 

  
 
 
 
 

 
 
 

 
 
 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-35132) Pipeline: GitHub webhook received but nothing happens

2016-10-12 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-35132  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline: GitHub webhook received but nothing happens   
 

  
 
 
 
 

 
 With pipeline job you should start first build manually  
 

  
 
 
 
 

 
 
 

 
 
 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-38935) GitHub Plugin settings not surviving Jenkins restart

2016-10-12 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38935  
 
 
  GitHub Plugin settings not surviving Jenkins restart   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 

  
 
 
 
 

 
 This is occurring on the new LTS version of Jenkins, with all plugins updated to latest levels available on stable plugins list:The configuration of the GitHub values are not surviving a restart of Jenkins.  Each time the server is restarted, the configuration must be recreated in the "Manage Jenkins" -> "Configure System" panelsAt server start time, the following is in the logs: {code:java} WARNING: Failed to load /var/lib/jenkins/github-plugin-configuration.xmljava.io.IOException: Unable to read /var/lib/jenkins/github-plugin-configuration.xmlat hudson.XmlFile.unmarshal(XmlFile.java:165)at hudson.model.Descriptor.load(Descriptor.java:885)at org.jenkinsci.plugins.github.config.GitHubPluginConfig.(GitHubPluginConfig.java:77)at org.jenkinsci.plugins.github.config.GitHubPluginConfig$$FastClassByGuice$$cfc1c5a3.newInstance()at com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40)at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:61)at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:108)at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:88)at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:269)at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1058)at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)at com.google.inject.Scopes$1$1.get(Scopes.java:65)at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:424)at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:1005)at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1051)at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:1001)at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:386)at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:377)at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:478)at hudson.ExtensionList.load(ExtensionList.java:349)at hudson.ExtensionList.ensureLoaded(ExtensionList.java:287)at hudson.ExtensionList.iterator(ExtensionList.java:156)at jenkins.model.Jenkins.getDescriptorByType(Jenkins.java:1430)at hudson.plugins.copyartifact.BuildSelectorParameter.initAliases(BuildSelectorParameter.java:156)at 

[JIRA] (JENKINS-38674) GitHubCommitStatusSetter unusable in pipeline with multiple checkout steps

2016-10-05 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-38674  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GitHubCommitStatusSetter unusable in pipeline with multiple checkout steps   
 

  
 
 
 
 

 
 You can use variables and not hardcode  
 

  
 
 
 
 

 
 
 

 
 
 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-38611) If 'Set status for GitHub commit [universal]' in config, 'Apply' changes gets an exception

2016-10-03 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev assigned an issue to Kirill Merkushev  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38611  
 
 
  If 'Set status for GitHub commit [universal]' in config, 'Apply' changes gets an exception   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Assignee: 
 Kirill Merkushev  
 

  
 
 
 
 

 
 
 

 
 
 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-38611) If 'Set status for GitHub commit [universal]' in config, 'Apply' changes gets an exception

2016-10-03 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-38611  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: If 'Set status for GitHub commit [universal]' in config, 'Apply' changes gets an exception   
 

  
 
 
 
 

 
 fixed in 1.22.1  
 

  
 
 
 
 

 
 
 

 
 
 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-38665) GitHub plugin Set status for GitHub commit throws exception on job save

2016-10-03 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38665  
 
 
  GitHub plugin Set status for GitHub commit throws exception on job save   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

 
 
 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-38665) GitHub plugin Set status for GitHub commit throws exception on job save

2016-10-03 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-38665  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GitHub plugin Set status for GitHub commit throws exception on job save   
 

  
 
 
 
 

 
 Released as 1.22.1  
 

  
 
 
 
 

 
 
 

 
 
 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-38611) If 'Set status for GitHub commit [universal]' in config, 'Apply' changes gets an exception

2016-10-03 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev closed an issue as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38611  
 
 
  If 'Set status for GitHub commit [universal]' in config, 'Apply' changes gets an exception   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 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-38665) GitHub plugin Set status for GitHub commit throws exception on job save

2016-10-03 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev started work on  JENKINS-38665  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 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-38665) GitHub plugin Set status for GitHub commit throws exception on job save

2016-10-03 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-38665  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GitHub plugin Set status for GitHub commit throws exception on job save   
 

  
 
 
 
 

 
 thx for the report, will fix that in few hours  
 

  
 
 
 
 

 
 
 

 
 
 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-38665) GitHub plugin Set status for GitHub commit throws exception on job save

2016-10-03 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38665  
 
 
  GitHub plugin Set status for GitHub commit throws exception on job save   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Priority: 
 Minor Blocker  
 

  
 
 
 
 

 
 
 

 
 
 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-38665) GitHub plugin Set status for GitHub commit throws exception on job save

2016-10-03 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38665  
 
 
  GitHub plugin Set status for GitHub commit throws exception on job save   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 

  
 
 
 
 

 
 When I add a "Set status for GitHub commit [universal]: with Status result set to "One of default messages and statuses" then I get the following error that prevent me from saving the job. {code:java} javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class org.jenkinsci.plugins.github.status.GitHubCommitStatusSetter from {"":["0","0","0","1","0"],"commitShaSource":{"stapler-class":"org.jenkinsci.plugins.github.status.sources.BuildDataRevisionShaSource","$class":"org.jenkinsci.plugins.github.status.sources.BuildDataRevisionShaSource"},"reposSource":{"stapler-class":"org.jenkinsci.plugins.github.status.sources.AnyDefinedRepositorySource","$class":"org.jenkinsci.plugins.github.status.sources.AnyDefinedRepositorySource"},"contextSource":{"stapler-class":"org.jenkinsci.plugins.github.status.sources.DefaultCommitContextSource","$class":"org.jenkinsci.plugins.github.status.sources.DefaultCommitContextSource"},"statusResultSource":{"stapler-class":"org.jenkinsci.plugins.github.status.sources.DefaultStatusResultSource","$class":"org.jenkinsci.plugins.github.status.sources.DefaultStatusResultSource"},"statusBackrefSource":{"stapler-class":"org.jenkinsci.plugins.github.status.sources.BuildRefBackrefSource","$class":"org.jenkinsci.plugins.github.status.sources.BuildRefBackrefSource"},"errorHandling":false,"stapler-class":"org.jenkinsci.plugins.github.status.GitHubCommitStatusSetter","$class":"org.jenkinsci.plugins.github.status.GitHubCommitStatusSetter"} at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at 

[JIRA] (JENKINS-38368) github book for github pull request plugin is throwing the below issue

2016-09-20 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38368  
 
 
  github book for github pull request plugin is throwing the below issue   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 

  
 
 
 
 

 
 When I click the use github book check box it is throwing the below errorA problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened.Stack trace {code:java} javax.servlet.ServletException: java.lang.ArrayIndexOutOfBoundsException: 1 at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585) at 

[JIRA] (JENKINS-38368) github book for github pull request plugin is throwing the below issue

2016-09-20 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38368  
 
 
  github book for github pull request plugin is throwing the below issue   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Component/s: 
 ghprb-plugin  
 
 
Component/s: 
 github-plugin  
 

  
 
 
 
 

 
 
 

 
 
 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-38368) github book for github pull request plugin is throwing the below issue

2016-09-20 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev assigned an issue to Honza Brázdil  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38368  
 
 
  github book for github pull request plugin is throwing the below issue   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Assignee: 
 Kirill Merkushev Honza Brázdil  
 

  
 
 
 
 

 
 
 

 
 
 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-38277) The webhook registration didn't register the push hook

2016-09-19 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38277  
 
 
  The webhook registration didn't register the push hook   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Component/s: 
 github-branch-source-plugin  
 
 
Component/s: 
 github-organization-folder-plugin  
 

  
 
 
 
 

 
 
 

 
 
 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-38277) The webhook registration didn't register the push hook

2016-09-19 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-38277  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: The webhook registration didn't register the push hook   
 

  
 
 
 
 

 
 I can't help with push event adding on re-register (it's a bug in multipipeline + branch-source or org-folder plugin) But will try to look at removing manually added PUSH event (it should not be so)  
 

  
 
 
 
 

 
 
 

 
 
 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-38277) The webhook registration didn't register the push hook

2016-09-19 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38277  
 
 
  The webhook registration didn't register the push hook   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Environment: 
 Jenkins (2.7.3)github-plugin ( latest 1.20.1 )  
 

  
 
 
 
 

 
 
 

 
 
 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-38277) The webhook registration didn't register the push hook

2016-09-19 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-38277  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: The webhook registration didn't register the push hook   
 

  
 
 
 
 

 
 Github-plugin doesn't remove any events from webhook - it merges them with new ones.  Here is the test: https://github.com/jenkinsci/github-plugin/blob/master/src/test/java/org/jenkinsci/plugins/github/webhook/WebhookManagerTest.java#L153-L165 So please provide your plugin list and simple job configuration wich can help to reproduce 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-38277) The webhook registration didn't register the push hook

2016-09-19 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-38277  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: The webhook registration didn't register the push hook   
 

  
 
 
 
 

 
 Then it's not a github-plugin bug. This plugin works with only this setting. What exact list of plugins do you have? How do you add webhook manually (Via service integration or directly as webhook)?  
 

  
 
 
 
 

 
 
 

 
 
 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-38075) Github Plugin build strategy improvement

2016-09-19 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-38075  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Github Plugin build strategy improvement   
 

  
 
 
 
 

 
 What exact plugins list do you have?  
 

  
 
 
 
 

 
 
 

 
 
 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-38277) The webhook registration didn't register the push hook

2016-09-19 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev edited a comment on  JENKINS-38277  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: The webhook registration didn't register the push hook   
 

  
 
 
 
 

 
 Did you  have  enabled  in job  "Build when a change is pushed to GitHub"  in job ?  
 

  
 
 
 
 

 
 
 

 
 
 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-38277) The webhook registration didn't register the push hook

2016-09-19 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-38277  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: The webhook registration didn't register the push hook   
 

  
 
 
 
 

 
 Did you enabled in job "Build when a change is pushed to GitHub"?  
 

  
 
 
 
 

 
 
 

 
 
 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-38024) GithubLinkAnnotator NPE

2016-09-07 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38024  
 
 
  GithubLinkAnnotator NPE   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Priority: 
 Minor Major  
 

  
 
 
 
 

 
 
 

 
 
 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-37956) Missing notification about request with bad secret for GitHub plugin

2016-09-05 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-37956  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Missing notification about request with bad secret for GitHub plugin
 

  
 
 
 
 

 
 Good point  
 

  
 
 
 
 

 
 
 

 
 
 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-37920) DefaultPushGHEventSubscriber does not pass important details of the webhook to GitHubWebHook.Listener

2016-09-02 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev closed an issue as Done  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37920  
 
 
  DefaultPushGHEventSubscriber does not pass important details of the webhook to GitHubWebHook.Listener   
 

  
 
 
 
 

 
Change By: 
 Kirill Merkushev  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Done  
 

  
 
 
 
 

 
 
 

 
 
 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-37920) DefaultPushGHEventSubscriber does not pass important details of the webhook to GitHubWebHook.Listener

2016-09-02 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-37920  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: DefaultPushGHEventSubscriber does not pass important details of the webhook to GitHubWebHook.Listener   
 

  
 
 
 
 

 
 GitHubWebHook.Listener is a deprecated extension point and not recommended to use. It exists only for backward compatibility. If you want to receive more events and payload, then you should extend this class: https://github.com/jenkinsci/github-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github/extension/GHEventsSubscriber.java The working example is DefaultPushGHEventSubscriber and https://github.com/jenkinsci/github-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github/webhook/subscriber/PingGHEventSubscriber.java One more example can be found here: https://github.com/KostyaSha/github-integration-plugin/blob/master/github-pullrequest-plugin/src/main/java/org/jenkinsci/plugins/github/pullrequest/webhook/GHPullRequestSubscriber.java  
 

  
 
 
 
 

 
 
 

 
 
 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-35132) Pipeline: GitHub webhook received but nothing happens

2016-08-31 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-35132  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline: GitHub webhook received but nothing happens   
 

  
 
 
 
 

 
 GH Organization Folder is not a Github-plugin  
 

  
 
 
 
 

 
 
 

 
 
 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-37813) The remote project from github is not getting downloaded

2016-08-31 Thread lan...@yandex.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Merkushev commented on  JENKINS-37813  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: The remote project from github is not getting downloaded   
 

  
 
 
 
 

 
 You should define git url in your scm section  
 

  
 
 
 
 

 
 
 

 
 
 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.


  1   2   3   4   >