[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub

6 views
Skip to first unread message

i@soar.name (JIRA)

unread,
Oct 17, 2018, 7:38:02 AM10/17/18
to jenkinsc...@googlegroups.com
Aleksey Smyrnov created an issue
 
Jenkins / Bug JENKINS-54126
Jenkinsfile not found in PR on GitHub
Issue Type: Bug Bug
Assignee: Kohsuke Kawaguchi
Components: github-api-plugin, github-organization-folder-plugin
Created: 2018-10-17 11:37
Environment: Jenkins ver. 2.138.2
Priority: Major Major
Reporter: Aleksey Smyrnov

Sometimes, when we create PR on GitHub - it is ignored by Jenkins. I've tried to re-scan organization - and see in logs:

  Getting remote pull requests...

    Checking pull request #128
      ‘Jenkinsfile’ not found
    Does not meet criteria

But Jenkinsfile is here! I see other bugs in your Jira and here is some additional information:

  • Repository is added to Jenkins via GitHub Organization Folder
  • We don't use forks
  • Commiter is a member of our organization and has full rights on this repository
  • Problem PRs are also very simple and doesn't touch Jenkinsfile at all
  • Source PR branch has Jenkinsfile
  • Branch which we want to merge - was created from source branch and also has Jenkinsfile
  • Jenkinsfile was not changed between merge commits
  • If I merge branches manually - result has Jenkinsfile
  • If we do merge on GitHub UI - result will have Jenkinsfile (and will be built)
  • If we recreate same pull request several times - it will be built

And more logs:

Examining our-organization/our-repo:  Checking branches...  Getting remote branches...    Checking branch master
      ‘Jenkinsfile’ found
    Met criteria
No changes detected: master (still at 923197f48be5cd8296b8ca95bd72a4a830a474f4)    Checking branch develop
      ‘Jenkinsfile’ found
    Met criteria
No changes detected: develop (still at 43c2cce36623a4af90b28d886dfb28ea8d813ab8)    Checking branch feature/198-video-verification
      ‘Jenkinsfile’ found
    Met criteria
No changes detected: feature/198-video-verification (still at 9126f0c6958db3c712078ed0d2587e96004d27c6)  3 branches were processed  Checking pull-requests...  Getting remote pull requests...    Checking pull request #128
      ‘Jenkinsfile’ not found
    Does not meet criteria

PR #128 - is between develop and feature/198-video-verification - and, as you can see, both have Jenkinsfile and were built successfully.

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

i@soar.name (JIRA)

unread,
Oct 17, 2018, 7:39:02 AM10/17/18
to jenkinsc...@googlegroups.com
Aleksey Smyrnov updated an issue
Change By: Aleksey Smyrnov
Sometimes, when we create PR on GitHub - it is ignored by Jenkins. I've tried to re-scan organization - and see in logs:
{code:java}

  Getting remote pull requests...

    Checking pull request #128
      ‘Jenkinsfile’ not found
    Does not meet criteria
{code}

But Jenkinsfile is here! I see other bugs in your Jira and here is some additional information:
* Repository is added to Jenkins via GitHub Organization Folder
* We don't use forks
* Commiter is a member of our organization and has full rights on this repository
* Problem PRs are also very simple and doesn't touch Jenkinsfile at all
* Source PR branch has Jenkinsfile
* Branch which we want to merge - was created from source branch and also has Jenkinsfile
* Jenkinsfile was not changed between merge commits
* If I merge branches manually - result has Jenkinsfile
* If we do merge on GitHub UI - result will have Jenkinsfile (and will be built)
* If we recreate same pull request several times - it will be built

And more logs:
{code:java}
Examining our-organization/our-repo:
  

  Checking branches...   
  Getting remote branches...   
  
    Checking branch master
      ‘Jenkinsfile’ found
    Met criteria
No changes detected: master (still at 923197f48be5cd8296b8ca95bd72a4a830a474f4)
    

    Checking branch develop
      ‘Jenkinsfile’ found
    Met criteria
No changes detected: develop (still at 43c2cce36623a4af90b28d886dfb28ea8d813ab8)
    

    Checking branch feature/198-video-verification
      ‘Jenkinsfile’ found
    Met criteria
No changes detected: feature/198-video-verification (still at 9126f0c6958db3c712078ed0d2587e96004d27c6)
  

  3 branches were processed   

  Checking pull-requests...   
  Getting remote pull requests...     

    Checking pull request #128
      ‘Jenkinsfile’ not found
    Does not meet criteria
{code}

PR #128 - is between develop and feature/198-video-verification - and, as you can see, both have Jenkinsfile and were built successfully.

i@soar.name (JIRA)

unread,
Oct 17, 2018, 1:06:02 PM10/17/18
to jenkinsc...@googlegroups.com
Aleksey Smyrnov commented on Bug JENKINS-54126
 
Re: Jenkinsfile not found in PR on GitHub

Today my colleague has faced same problem in another organization/repo.

jesse@puppet.com (JIRA)

unread,
Oct 25, 2018, 12:18:04 PM10/25/18
to jenkinsc...@googlegroups.com

Aleksey Smyrnov We had a similar issue and we were able to workaround the specific issue by deleting the contents of:

/var/lib/jenkins/org.jenkinsci.plugins.github_branch_source.GitHubSCMProbe.cache 

On our Jenkins server. We have not yet identified the underlying cause however.

i@soar.name (JIRA)

unread,
Oct 25, 2018, 1:07:02 PM10/25/18
to jenkinsc...@googlegroups.com

Looks like working branch rebasing causes this issue

josephmcollard@gmail.com (JIRA)

unread,
Nov 7, 2018, 9:22:02 AM11/7/18
to jenkinsc...@googlegroups.com

I am also experiencing this issue.

jonathan_tancer@colpal.com (JIRA)

unread,
Nov 7, 2018, 10:56:02 AM11/7/18
to jenkinsc...@googlegroups.com

Same issue here.  This is starting to happen more frequently and is becoming a nuisance.

jonathan_tancer@colpal.com (JIRA)

unread,
Nov 7, 2018, 11:14:01 AM11/7/18
to jenkinsc...@googlegroups.com
Jon Tancer edited a comment on Bug JENKINS-54126
Same issue here.  This is starting to happen more frequently and is becoming a nuisance.


As [~scotje] suggested, clearing the contents of $jenkins_home/org.jenkinsci.plugins.github_branch_source.GitHubSCMProbe.cache and trigger a rescan of the repository temporarily resolved the issue.

jason@waldrip.net (JIRA)

unread,
Nov 25, 2018, 11:34:03 PM11/25/18
to jenkinsc...@googlegroups.com

Same issue. Causing a lot of developer frustration on the team.

jonathan_tancer@colpal.com (JIRA)

unread,
Nov 27, 2018, 8:52:06 AM11/27/18
to jenkinsc...@googlegroups.com
Jon Tancer edited a comment on Bug JENKINS-54126
Same issue here.  This is starting to happen more frequently and is becoming a nuisance.

As [~scotje] suggested, clearing the contents of $jenkins_home/org.jenkinsci.plugins.github_branch_source.GitHubSCMProbe.cache and trigger triggering a rescan of the repository temporarily resolved the issue.

jonathan_tancer@colpal.com (JIRA)

unread,
Nov 27, 2018, 8:56:02 AM11/27/18
to jenkinsc...@googlegroups.com

@Aleksey Smyrnov It seems rebasing the working branch is causing the issue for us too.

dubrsl@gmail.com (JIRA)

unread,
Dec 10, 2018, 8:53:01 AM12/10/18
to jenkinsc...@googlegroups.com

The problem is very urgent and serious obstacle to our work. Every hour I have to clear the cache. Forced to do a job for this even

Maybe it makes sense to raise the priority to the blocker or critical?

awiddersheim@hotmail.com (JIRA)

unread,
Dec 19, 2018, 8:54:03 AM12/19/18
to jenkinsc...@googlegroups.com

I wonder if it has anything to do with the cache just being recently turned on again by default here:

 

https://github.com/jenkinsci/github-branch-source-plugin/commit/1b3a370d78a4f8b431a55bc79ee795f1d8cece88

 

The time when people started reporting this issue and when that changed happened in early October seem to line up.

 

https://wiki.jenkins.io/display/JENKINS/GitHub+Branch+Source+Plugin

 

The cache can be disabled by setting -Dorg.jenkinsci.plugins.github_branch_source.GitHubSCMSource.cacheSize=0. My guess is that will serve as a decent work around seeing as the cache wasn't on prior and shouldn't have any adverse affects AFAIK.

pruthvirajreddy.chukkannagari@cerner.com (JIRA)

unread,
Dec 21, 2018, 3:22:02 PM12/21/18
to jenkinsc...@googlegroups.com

Andrew Widdersheim  I have tried setting the JVM property but that does'nt  create the new job config for each branch source. Is there any alternative?

pruthvirajreddy.chukkannagari@cerner.com (JIRA)

unread,
Dec 21, 2018, 3:27:03 PM12/21/18
to jenkinsc...@googlegroups.com
[~awiddersheim]  I have tried setting the JVM property but that does'nt  create the new job config for each branch source. Hence, the Jenkinsfile changes are ginored though a scan on repository picks the change in commit SHA Is there any alternative?

pruthvirajreddy.chukkannagari@cerner.com (JIRA)

unread,
Dec 21, 2018, 3:27:07 PM12/21/18
to jenkinsc...@googlegroups.com
[~awiddersheim]  I have tried setting the JVM property but that does'nt  create the new job config for each branch source. Hence, the Jenkinsfile changes are ginored ignored though a scan on repository picks the change in commit SHA Is there any alternative?

pruthvirajreddy.chukkannagari@cerner.com (JIRA)

unread,
Dec 21, 2018, 4:05:02 PM12/21/18
to jenkinsc...@googlegroups.com
[~awiddersheim]  I have tried setting the JVM property but that does'nt  create the new job config for each branch source. Hence, the Jenkinsfile changes are ignored though a scan on repository picks the change in commit SHA Is there any alternative?

Branch source plugin is creating a stale job directory with the current builds folder job source. Appears like the fingerprints help to keep duplictaes on jenkins.

i@soar.name (JIRA)

unread,
Dec 29, 2018, 4:47:02 AM12/29/18
to jenkinsc...@googlegroups.com

I can confirm that -Dorg.jenkinsci.plugins.github_branch_source.GitHubSCMSource.cacheSize=0 doesn't help. Only cronjob which removes cache directory every one minute did the trick.

 

jglick@cloudbees.com (JIRA)

unread,
Jan 10, 2019, 10:21:02 PM1/10/19
to jenkinsc...@googlegroups.com
Jesse Glick assigned an issue to Stephen Connolly
 

Has been observed recently on ci.jenkins.io as well.

Change By: Jesse Glick
Component/s: github-branch-source-plugin
Component/s: github-api-plugin
Component/s: github-organization-folder-plugin
Assignee: Kohsuke Kawaguchi Stephen Connolly

batmat@batmat.net (JIRA)

unread,
Jan 11, 2019, 6:54:03 AM1/11/19
to jenkinsc...@googlegroups.com
Baptiste Mathus updated an issue
Change By: Baptiste Mathus
Priority: Major Critical

rsandell@cloudbees.com (JIRA)

unread,
Jan 11, 2019, 8:49:02 AM1/11/19
to jenkinsc...@googlegroups.com
rsandell commented on Bug JENKINS-54126
 
Re: Jenkinsfile not found in PR on GitHub

If you turn off the cache and clear the cache dir does the problem come back?

jbriden@cloudbees.com (JIRA)

unread,
Jan 11, 2019, 9:52:03 AM1/11/19
to jenkinsc...@googlegroups.com
Jenn Briden assigned an issue to Vivek Pandey
 
Change By: Jenn Briden
Assignee: Stephen Connolly Vivek Pandey

jbriden@cloudbees.com (JIRA)

unread,
Jan 11, 2019, 9:52:08 AM1/11/19
to jenkinsc...@googlegroups.com
Jenn Briden commented on Bug JENKINS-54126
 
Re: Jenkinsfile not found in PR on GitHub

Removing Stephen as the owner. Vivek Pandey, FYI. I believe you are already aware.

vivek.pandey@gmail.com (JIRA)

unread,
Jan 11, 2019, 10:08:03 AM1/11/19
to jenkinsc...@googlegroups.com
Vivek Pandey assigned an issue to rsandell
 
Change By: Vivek Pandey
Assignee: Vivek Pandey rsandell

vivek.pandey@gmail.com (JIRA)

unread,
Jan 11, 2019, 10:15:04 AM1/11/19
to jenkinsc...@googlegroups.com
Vivek Pandey commented on Bug JENKINS-54126
 
Re: Jenkinsfile not found in PR on GitHub

Stephen Connolly rsandell As reported above disabling cache (using -Dorg.jenkinsci.plugins.github_branch_source.GitHubSCMSource.cacheSize=0) doesn't help, removing the caching directory does. Perhaps, if caching is disabled, we should cleanup the caches as well in fail safe manner?

I am guessing, might be the case of cache is not getting correctly invalidated resulting in such behavior.

andrew.bayer@gmail.com (JIRA)

unread,
Jan 11, 2019, 12:00:04 PM1/11/19
to jenkinsc...@googlegroups.com
Andrew Bayer updated an issue
 
Change By: Andrew Bayer
Priority: Critical Blocker

vivek.pandey@gmail.com (JIRA)

unread,
Jan 29, 2019, 12:32:03 PM1/29/19
to jenkinsc...@googlegroups.com
Vivek Pandey started work on Bug JENKINS-54126
 
Change By: Vivek Pandey
Status: Open In Progress

dev@wolfplusplus.com (JIRA)

unread,
Jan 30, 2019, 2:36:03 PM1/30/19
to jenkinsc...@googlegroups.com
Nelson Wolf commented on Bug JENKINS-54126
 
Re: Jenkinsfile not found in PR on GitHub

As a workaround, is it safe to nuke $jenkins_home/org.jenkinsci.plugins.github_branch_source.GitHubSCMProbe.cache while jenkins is running as a workaround? Would this potentially cause us to miss any events?

vivek.pandey@gmail.com (JIRA)

unread,
Feb 1, 2019, 5:33:03 PM2/1/19
to jenkinsc...@googlegroups.com

Nelson Wolf On running Jenkins, it might. Well, you have to disable the cache anyways, that needs setting this jvm property -Dorg.jenkinsci.plugins.github_branch_source.GitHubSCMSource.cacheSize=0.

wdforson@gmail.com (JIRA)

unread,
Mar 6, 2019, 11:05:02 AM3/6/19
to jenkinsc...@googlegroups.com

We have hit this issue several times recently, and we'd really like to get something in place to mitigate it ASAP, even if it's a temporary measure. I would appreciate it very much if anyone here could clarify any of the following points:

  • When will rsandell's fix be available? (It looks like the newest currently-available version of the branch source plugin, 2.4.3-beta-1, was built on January 28th, while that PR was merged in late February)
  • Aleksey Smyrnov seems happy with a cron job that blows away the cache every minute, while Vivek Pandey suggests that nuking the cache while Jenkins is running could cause issues. What kinds of issues might be caused by disabling the cache in a running system?
  • Several people seem to have concluded that setting the cacheSize=0 JVM property does not help, but in the most recent comment in this thread, Vivek says that, "you have to disable the cache anyways, that needs setting this jvm property". Has anyone actually been able to mitigate this issue by setting that property?

Thanks!

yan@sutoiku.com (JIRA)

unread,
Mar 6, 2019, 11:29:02 AM3/6/19
to jenkinsc...@googlegroups.com

Yes, adding the JVM argument to disable the cache did the job for me.

awalls@cloudbees.com (JIRA)

unread,
Apr 10, 2019, 12:01:17 PM4/10/19
to jenkinsc...@googlegroups.com

Here are the steps we are using to reproduce the issue: 

  • create a branch
  • commit something
  • create a PR
  • merge the PR with master 
  • delete the branch on Github enterprise ui. 
  • create a branch with the same name from master, (the branch name is the same as the previous one, but that's ok since we deleted already from the github ui). 
  • now if we create another PR using this branch, even it shows up properly on the github UI, a scan in Jenkins shows no Jenkinsfile found thus the new PR could not be built.

e.moshaya@gmail.com (JIRA)

unread,
Apr 12, 2019, 4:54:04 AM4/12/19
to jenkinsc...@googlegroups.com

any update on a fix? we're having the same issue.

amirbarkal@sparkbeyond.com (JIRA)

unread,
Apr 29, 2019, 5:10:04 AM4/29/19
to jenkinsc...@googlegroups.com

Suffering from the same issue here.
Jenkins core 2.164.1
GitHub branch source 2.4.2

bantam2781@gmail.com (JIRA)

unread,
Apr 29, 2019, 5:47:03 AM4/29/19
to jenkinsc...@googlegroups.com

We use a pipeline script to clear the cache whenever there is an issue.

node('master'){
    stage('Clear cache'){
        sh "rm -r $jenkins_home/org.jenkinsci.plugins.github_branch_source.GitHubSCMProbe.cache"
    }
}

It's not ideal, but hopefully someone else finds it useful.

d.sanftenberg@cardano.com (JIRA)

unread,
Apr 29, 2019, 6:02:03 AM4/29/19
to jenkinsc...@googlegroups.com

This breaks the plugin for anyone doing PRs. Really shouldn't be any further releases until this is fixed. 

d.sanftenberg@cardano.com (JIRA)

unread,
Apr 29, 2019, 6:03:03 AM4/29/19
to jenkinsc...@googlegroups.com
David Sanftenberg edited a comment on Bug JENKINS-54126
This breaks the plugin for anyone doing PRs. Really shouldn't be any further releases until this is fixed. 


We have rolled back for now and are opting out of upgrades.

amirbarkal@sparkbeyond.com (JIRA)

unread,
Apr 29, 2019, 7:00:05 AM4/29/19
to jenkinsc...@googlegroups.com
Amir Barkal edited a comment on Bug JENKINS-54126
Suffering from the same issue here.
Jenkins core 2.164.1
GitHub branch source 2. 4.2 5

bitwiseman@gmail.com (JIRA)

unread,
Apr 29, 2019, 3:34:04 PM4/29/19
to jenkinsc...@googlegroups.com

David Sanftenberg
What did you roll back to that "fixed" this issue for you? Could you provide same additional details about your configuration and what output you're seeing?

bitwiseman@gmail.com (JIRA)

unread,
May 1, 2019, 10:02:04 PM5/1/19
to jenkinsc...@googlegroups.com

David Sanftenberg Amir Barkal
There is a new version v2.5.1 the fixes PRs from forks.

bitwiseman@gmail.com (JIRA)

unread,
May 1, 2019, 10:05:02 PM5/1/19
to jenkinsc...@googlegroups.com

If anyone is interested in trying it, I have an experimental version of the github-branch-source-plugin using okttp3.
https://drive.google.com/file/d/1VreeBlIG0RCbSI80wW2BBOmcVT9ZySNW/view?usp=sharing
If you have a test/staging Jenkins on which your are comfortable trying this out it would be helpful to know if this issue would be fixed by this upgrade.

bitwiseman@gmail.com (JIRA)

unread,
May 1, 2019, 10:09:03 PM5/1/19
to jenkinsc...@googlegroups.com
Liam Newman edited a comment on Bug JENKINS-54126
If anyone is interested in trying it, I have an experimental version of the github-branch-source-plugin using okttp3.
https://drive.google.com/file/d/1VreeBlIG0RCbSI80wW2BBOmcVT9ZySNW/view?usp=sharing
If you have a test/staging Jenkins on which your are comfortable trying this out it would be helpful to know if this issue would be fixed by this upgrade.  

bitwiseman@gmail.com (JIRA)

unread,
May 2, 2019, 10:38:04 AM5/2/19
to jenkinsc...@googlegroups.com
Liam Newman edited a comment on Bug JENKINS-54126
[~synalogik][~amirbarkal]
If anyone is interested in trying it, I have an experimental version of the github-branch-source-plugin using okttp3.
https://drive.google.com/file/d/1VreeBlIG0RCbSI80wW2BBOmcVT9ZySNW/view?usp=sharing
If you have a test/staging Jenkins on which your are comfortable trying this out it would be helpful to know if this issue would be fixed by this upgrade.  

The code can be seen at https://github.com/jenkinsci/github-branch-source-plugin/pull/223

bitwiseman@gmail.com (JIRA)

unread,
May 2, 2019, 10:38:16 AM5/2/19
to jenkinsc...@googlegroups.com
Liam Newman edited a comment on Bug JENKINS-54126
[~synalogik][~amirbarkal] [~dbsanfte]
If anyone is interested in trying it, I have an experimental version of the github-branch-source-plugin using okttp3.
https://drive.google.com/file/d/1VreeBlIG0RCbSI80wW2BBOmcVT9ZySNW/view?usp=sharing
If you have a test/staging Jenkins on which your are comfortable trying this out it would be helpful to know if this issue would be fixed by this upgrade.  

The code can be seen at https://github.com/jenkinsci/github-branch-source-plugin/pull/223

bitwiseman@gmail.com (JIRA)

unread,
May 2, 2019, 10:39:03 AM5/2/19
to jenkinsc...@googlegroups.com
Liam Newman edited a comment on Bug JENKINS-54126
[~synalogik][~amirbarkal][~dbsanfte] [~soar]
If anyone is interested in trying it, I have an experimental version of the github-branch-source-plugin using okttp3.
https://drive.google.com/file/d/1VreeBlIG0RCbSI80wW2BBOmcVT9ZySNW/view?usp=sharing
If you have a test/staging Jenkins on which your are comfortable trying this out it would be helpful to know if this issue would be fixed by this upgrade.  

The code can be seen at https://github.com/jenkinsci/github-branch-source-plugin/pull/223

jglick@cloudbees.com (JIRA)

unread,
May 2, 2019, 10:47:04 AM5/2/19
to jenkinsc...@googlegroups.com

Liam Newman maybe we can run this at least temporarily on ci.jenkins.io? I know R. Tyler Croy has a strict “no experimental code” rule for this server, but the current situation is badly broken to begin with.

bitwiseman@gmail.com (JIRA)

unread,
May 2, 2019, 10:53:04 AM5/2/19
to jenkinsc...@googlegroups.com
Liam Newman edited a comment on Bug JENKINS-54126
[~synalogik] , [~amirbarkal] , [~dbsanfte] , [~soar]

If anyone is interested in trying it, I have an experimental version of the github-branch-source-plugin using okttp3.
https://drive.google.com/file/d/1VreeBlIG0RCbSI80wW2BBOmcVT9ZySNW/view?usp=sharing
If you have a test/staging Jenkins on which your are comfortable trying this out it would be helpful to know if this issue would be fixed by this upgrade.  

The code can be seen at https://github.com/jenkinsci/github-branch-source-plugin/pull/223

jsoref+jenkins@gmail.com (JIRA)

unread,
May 2, 2019, 12:54:03 PM5/2/19
to jenkinsc...@googlegroups.com
Started by timer
Started by timer
java.lang.NoSuchMethodError: okio.BufferedSource.readUtf8LineStrict(J)Ljava/lang/String;
	at okhttp3.internal.http1.Http1Codec.readHeaderLine(Http1Codec.java:215)
	at okhttp3.internal.http1.Http1Codec.readResponseHeaders(Http1Codec.java:189)
	at okhttp3.internal.http.CallServerInterceptor.intercept(CallServerInterceptor.java:88)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
	at okhttp3.internal.huc.OkHttpURLConnection$NetworkInterceptor.intercept(OkHttpURLConnection.java:666)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
	at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:45)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
	at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:93)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
	at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
	at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:126)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
	at okhttp3.internal.huc.OkHttpURLConnection$UnexpectedException$1.intercept(OkHttpURLConnection.java:600)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
	at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:250)
	at okhttp3.RealCall.execute(RealCall.java:93)
	at okhttp3.internal.huc.OkHttpURLConnection.getResponse(OkHttpURLConnection.java:472)
	at okhttp3.internal.huc.OkHttpURLConnection.getResponseCode(OkHttpURLConnection.java:509)
	at okhttp3.internal.huc.DelegatingHttpsURLConnection.getResponseCode(DelegatingHttpsURLConnection.java:106)
	at okhttp3.internal.huc.OkHttpsURLConnection.getResponseCode(OkHttpsURLConnection.java:26)
	at org.kohsuke.github.Requester.parse(Requester.java:615)
	at org.kohsuke.github.Requester.parse(Requester.java:607)
	at org.kohsuke.github.Requester._to(Requester.java:285)
	at org.kohsuke.github.Requester.to(Requester.java:247)
	at org.kohsuke.github.GitHub.checkApiUrlValidity(GitHub.java:744)
	at org.jenkinsci.plugins.github_branch_source.Connector.checkApiUrlValidity(Connector.java:329)
	at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.checkApiUrlValidity(GitHubSCMSource.java:1377)
	at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:1430)
	at jenkins.scm.api.SCMSource.fetch(SCMSource.java:582)
	at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:98)
	at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:293)
	at hudson.model.ResourceController.execute(ResourceController.java:97)
	at hudson.model.Executor.run(Executor.java:429)
Finished: FAILURE 

bitwiseman@gmail.com (JIRA)

unread,
May 3, 2019, 7:34:03 PM5/3/19
to jenkinsc...@googlegroups.com

jsoref+jenkins@gmail.com (JIRA)

unread,
May 4, 2019, 10:04:03 PM5/4/19
to jenkinsc...@googlegroups.com

 I don't understand your question. We use the organization plug-in discover repositories and branches. This beta plug-in broke all of our builds immediately.

armantur@gmail.com (JIRA)

unread,
May 7, 2019, 3:50:03 AM5/7/19
to jenkinsc...@googlegroups.com

I observed behavior that Jenkins will ignore PR if  that PR has conflicting files.

bitwiseman@gmail.com (JIRA)

unread,
May 7, 2019, 10:20:03 AM5/7/19
to jenkinsc...@googlegroups.com
Liam Newman edited a comment on Bug JENKINS-54126
[~synalogik], [~amirbarkal], [~dbsanfte], [~soar]
If anyone is interested in trying it, I have an experimental version of the github-branch-source-plugin using okttp3.
If you have a test/staging Jenkins on which your are comfortable trying this out it would be helpful to know if this issue would be fixed by this upgrade.  

The code can be seen at https://github.com/jenkinsci/github-branch-source-plugin/pull/223

bitwiseman@gmail.com (JIRA)

unread,
May 7, 2019, 10:21:04 AM5/7/19
to jenkinsc...@googlegroups.com

bitwiseman@gmail.com (JIRA)

unread,
May 7, 2019, 10:22:04 AM5/7/19
to jenkinsc...@googlegroups.com

Arman Tursynbekov
Could you open a new issue for that, it is probably not related to this issue.

jsoref+jenkins@gmail.com (JIRA)

unread,
May 7, 2019, 11:40:03 AM5/7/19
to jenkinsc...@googlegroups.com

Liam Newman: I don't think it helped

bitwiseman@gmail.com (JIRA)

unread,
May 8, 2019, 4:22:05 PM5/8/19
to jenkinsc...@googlegroups.com

Josh Soref
Updated again. I manually tested it this time on my local jenkins. Builds run.
While there's infra issues, you can use https://drive.google.com/open?id=1xuxxEAerklY2jytUWLlNw5ViqnORoHqz
Thanks for your help!

bitwiseman@gmail.com (JIRA)

unread,
May 8, 2019, 5:32:04 PM5/8/19
to jenkinsc...@googlegroups.com
Liam Newman edited a comment on Bug JENKINS-54126
[~jsoref]
Updated again. I manually tested it this time  on my local jenkins.  Builds run.
While there's infra issues, you can use https:// drive repo . google jenkins-ci . com org / open?id=1xuxxEAerklY2jytUWLlNw5ViqnORoHqz
Thanks for your help!

incrementals/org/jenkins-ci/plugins/github-branch-source/2.5.3-rc841.52a0b90bff37/

jsoref+jenkins@gmail.com (JIRA)

unread,
May 8, 2019, 5:39:04 PM5/8/19
to jenkinsc...@googlegroups.com

Liam Newman: that one works!

I'll leave it running. And if anything explodes, I'll let you know. Otherwise, I look forward to finally upgrading to a working plugin.

Thanks

bitwiseman@gmail.com (JIRA)

unread,
May 9, 2019, 4:42:04 PM5/9/19
to jenkinsc...@googlegroups.com
Liam Newman edited a comment on Bug JENKINS-54126
[~jsoref], [~synalogik], [~amirbarkal], [~dbsanfte], [~soar]

Here's the updated plugin with okio (thanks Josh!).
https://repo.jenkins - ci.org/incrementals/org/jenkins Removed - ci/plugins/github-branch-source/2.5.2-rc836.bde357341ecd/

bitwiseman@gmail.com (JIRA)

unread,
May 9, 2019, 8:32:04 PM5/9/19
to jenkinsc...@googlegroups.com

Josh Soref
Okay, so to be clear this is still an experiment/exploration. The point of this exploration is to see if switching to using okhttp3 will address the FileNotFound issues. We're going to need more reports before we can release it.

Ebrahim Moshaya, Amir Barkal, David Sanftenberg, Aleksey Smyrnov (and anyone else)
Please give this version of the plug a try: https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/github-branch-source/2.5.3-rc841.52a0b90bff37/

amirbarkal@sparkbeyond.com (JIRA)

unread,
May 10, 2019, 1:29:03 AM5/10/19
to jenkinsc...@googlegroups.com

Liam Newman
Not really sure how to reproduce this - can you post instructions?
We’re using Multibranch pipeline repository with GitHub branch source configured to build PRs, branches and tags.

jsoref+jenkins@gmail.com (JIRA)

unread,
May 10, 2019, 4:18:03 PM5/10/19
to jenkinsc...@googlegroups.com

So, we aren't currently hitting the

‘Jenkinsfile’ not found

problem, but we are seeing that the periodic scans don't seem to be running periodically, and a branch whose name has been recycled (but for whom we'd expect github to send a notification) isn't being noticed automatically.

We are able to use "Scan Repository Now" to pick up those branches, which feels like progress.

bitwiseman@gmail.com (JIRA)

unread,
May 10, 2019, 10:12:03 PM5/10/19
to jenkinsc...@googlegroups.com

Josh Soref
Let's talk about an issues you see with okhttp3 version as a separate issue:
https://issues.jenkins-ci.org/browse/JENKINS-57411

We sort of hijacked this issue as something that might be fixed by the okhttp3 upgrade. If you see this issue again, it should go here, if you see other issues that should go there. Sound good?

Reply all
Reply to author
Forward
0 new messages