[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title Pascal Widdershoven commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria Thanks for fixing this Liam Newman! It's been a long time frustration. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.723.1580801402732%40Atlassian.JIRA.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title Liam Newman updated JENKINS-54126 Github-branch-source-plugin v2.6.0 Jenkins / JENKINS-54126 Jenkinsfile not found in PR on GitHub -- Does not meet criteria Change By: Liam Newman Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.398.1580767625909%40Atlassian.JIRA.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title Raihaan Shouhell commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria Liam Newman AFAICT with just github-api-plugin 1.106 the problem should go away? Of course it might do something less optimal Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.9169.1580442962061%40Atlassian.JIRA.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title Liam Newman updated JENKINS-54126 The fix for this issue has been merged and will be released in the next day or two in github-branch-source v2.6.0. If you want to try it out now: install github-api-plugin 1.6.0 and then install the hpi from: https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/github-branch-source/2.5.9-rc1028.3059575bf1cc/ Jenkins / JENKINS-54126 Jenkinsfile not found in PR on GitHub -- Does not meet criteria Change By: Liam Newman Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title Liam Newman commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria Jesse GlickYes, I've reported it to github via a support ticket. I have not heard back from them beyond an automated response. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.2096.1579385162131%40Atlassian.JIRA.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title Jesse Glick commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria So has this been reported to GitHub? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.1981.1579353544627%40Atlassian.JIRA.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title Liam Newman commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria We have determined that issue is being caused by a bug in the GitHub API. The problem is described in https://github.com/github-api/github-api/pull/669 . The linked PR (https://github.com/github-api/github-api/pull/665) now shows a workaround that should work for all scenarios. The workaround will only execute when actually needed and will occur without caller of the github-api library knowing about it. I'll do the work to upgrade this dependency (already in progress) and this problem will go away. This is my top priority for the coming week. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.1755.1579310703610%40Atlassian.JIRA.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title
Jim Klimov edited a comment on JENKINS-54126
Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria
+1 for the issue that was annoying for so long now, although most often seen on real branches (masters and releases of our project that are really providing a Jenkinsfile)Yes we do use GitHub caching, advocated for it to appear, and hope it stays :) with the poor internet uplink we have, and with github REST API quotas for uncached requests abound, and no possibility to get hooks thus requiring polling, - our farm couldn't really work without it.So I set out digging in the data, and found that cached HTTP-404s in \*.0 files correlate with very short \*.1 files (the compact error message from Github REST API), so selecting those to look deeper:{code}:; find . -name '*.1' -size 1 | sed -e 's,^./,,' -e s',.1$,,' | while read F ; do egrep 'HTTP.*404' "$F.0" >&2 && echo "=== $F" && head -1 "$F.0" && ls -la "$F"* ; done{code}Due to reasons unknown however, the cached response for some of the URLs is HTTP/404 even with a valid JSON in the (gzipped) `hashstring.1` file:{code}{"message":"No commit found for the ref refs/heads/4.2.0-FTY","documentation_url":"https://developer.github.com/v3/repos/contents/"}{code}and the corresponding `hashstring.0` file looks like:{code}:; cat fbe7227813e6f1a6bbb2f1e5202a84a2.0https://api.github.com/repos/42ity/libzmq/contents/?ref=refs%2Fheads%2F4.2.0-FTYGET1Authorization: Basic NDJpdHktY2k6NjA5MDk2YTVmNzNhNTc1YzE1OWYxZjI3NDJlZmI1YjhiMTQzZmIzMw==HTTP/1.1 404 Not Found31X-OAuth-Scopes: admin:repo_hook, public_repo, repo:status, repo_deploymentX-Accepted-OAuth-Scopes:X-GitHub-Media-Type: github.v3; format=jsonContent-Encoding: gzipTransfer-Encoding: chunkedConnection: keep-aliveContent-Type: application/octet-streamX-Cache: MISS from thunderbolt.localdomainX-Cache-Lookup: MISS from thunderbolt.localdomain:8080Via: 1.1 thunderbolt.localdomain (squid/3.4.4)Server: GitHub.comDate: Thu, 28 Nov 2019 00:41:22 GMTStatus: 304 Not ModifiedX-RateLimit-Limit: 5000X-RateLimit-Remaining: 5000X-RateLimit-Reset: 1574905280Cache-Control: private, max-age=60, s-maxage=60Vary: Accept, Authorization, Cookie, X-GitHub-OTPETag: "2513f4bbc2abb8b63adbec8336a82810a4fb5dc5"Last-Modified: Wed, 05 Dec 2018 10:54:24 GMTAccess-Control-Expose-Headers: ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-TypeAccess-Control-Allow-Origin: *Strict-Transport-Security: max-age=31536000; includeSubdomains; preloadX-Frame-Options: denyX-Content-Type-Options: nosniffX-XSS-Protection: 1; mode=blockReferrer-Policy: origin-when-cross-origin, strict-origin-when-cross-originContent-Security-Policy: default-src 'none'X-GitHub-Request-Id: F066:2FC4:FE494:24E933:5DDF17B1OkHttp-Sent-Millis: 1574901681913OkHttp-Received-Millis:
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title
Jim Klimov edited a comment on JENKINS-54126
Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria
+1 for the issue that was annoying for so long now , although most often seen on real branches (masters and releases of our project that are really providing a Jenkinsfile) Yes we do use GitHub caching, advocated for it to appear, and hope it stays :) with the poor internet uplink we have, and with github REST API quotas for uncached requests abound, and no possibility to get hooks thus requiring polling, - our farm couldn't really work without it.So I set out digging in the data, and found that cached HTTP-404s in \*.0 files correlate with very short \*.1 files (the compact error message from Github REST API), so selecting those to look deeper:{code}:; find . -name '*.1' -size 1 | sed -e 's,^./,,' -e s',.1$,,' | while read F ; do egrep 'HTTP.*404' "$F.0" >&2 && echo "=== $F" && head -1 "$F.0" && ls -la "$F"* ; done{code}Due to reasons unknown however, the cached response for some of the URLs is HTTP/404 even with a valid JSON in the (gzipped) `hashstring.1` file:{code}{"message":"No commit found for the ref refs/heads/4.2.0-FTY","documentation_url":"https://developer.github.com/v3/repos/contents/"}{code}and the corresponding `hashstring.0` file looks like:{code}:; cat fbe7227813e6f1a6bbb2f1e5202a84a2.0https://api.github.com/repos/42ity/libzmq/contents/?ref=refs%2Fheads%2F4.2.0-FTYGET1Authorization: Basic NDJpdHktY2k6NjA5MDk2YTVmNzNhNTc1YzE1OWYxZjI3NDJlZmI1YjhiMTQzZmIzMw==HTTP/1.1 404 Not Found31X-OAuth-Scopes: admin:repo_hook, public_repo, repo:status, repo_deploymentX-Accepted-OAuth-Scopes:X-GitHub-Media-Type: github.v3; format=jsonContent-Encoding: gzipTransfer-Encoding: chunkedConnection: keep-aliveContent-Type: application/octet-streamX-Cache: MISS from thunderbolt.localdomainX-Cache-Lookup: MISS from thunderbolt.localdomain:8080Via: 1.1 thunderbolt.localdomain (squid/3.4.4)Server: GitHub.comDate: Thu, 28 Nov 2019 00:41:22 GMTStatus: 304 Not ModifiedX-RateLimit-Limit: 5000X-RateLimit-Remaining: 5000X-RateLimit-Reset: 1574905280Cache-Control: private, max-age=60, s-maxage=60Vary: Accept, Authorization, Cookie, X-GitHub-OTPETag: "2513f4bbc2abb8b63adbec8336a82810a4fb5dc5"Last-Modified: Wed, 05 Dec 2018 10:54:24 GMTAccess-Control-Expose-Headers: ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-TypeAccess-Control-Allow-Origin: *Strict-Transport-Security: max-age=31536000; includeSubdomains; preloadX-Frame-Options: denyX-Content-Type-Options: nosniffX-XSS-Protection: 1; mode=blockReferrer-Policy: origin-when-cross-origin, strict-origin-when-cross-originContent-Security-Policy: default-src 'none'X-GitHub-Request-Id: F066:2FC4:FE494:24E933:5DDF17B1OkHttp-Sent-Millis: 1574901681913OkHttp-Received-Millis:
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title
Jim Klimov edited a comment on JENKINS-54126
Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria
+1 for the issue that was annoying for so long nowYes we do use GitHub caching, advocated for it to appear, and hope it stays :) with the poor internet uplink we have, and with github REST API quotas for uncached requests abound, and no possibility to get hooks thus requiring polling, - our farm couldn't really work without it. So I set out digging in the data, and found that cached HTTP-404s in \*.0 files correlate with very short \*.1 files (the compact error message from Github REST API), so selecting those to look deeper: {code} :; find . -name '*.1' -size 1 | sed -e 's,^./,,' -e s',.1$,,' | while read F ; do egrep 'HTTP.*404' "$F.0" >&2 && echo "=== $F" && head -1 "$F.0" && ls -la "$F"* ; done {code} Due to reasons unknown however, the cached response for some of the URLs is HTTP/404 even with a valid JSON in the (gzipped) `hashstring.1` file: {code} {"message":"No commit found for the ref refs/heads/4.2.0-FTY","documentation_url":"https://developer.github.com/v3/repos/contents/"} {code} and the corresponding `hashstring.0` file looks like: {code} :; cat fbe7227813e6f1a6bbb2f1e5202a84a2.0https://api.github.com/repos/42ity/libzmq/contents/?ref=refs%2Fheads%2F4.2.0-FTYGET1Authorization: Basic NDJpdHktY2k6NjA5MDk2YTVmNzNhNTc1YzE1OWYxZjI3NDJlZmI1YjhiMTQzZmIzMw==HTTP/1.1 404 Not Found31X-OAuth-Scopes: admin:repo_hook, public_repo, repo:status, repo_deploymentX-Accepted-OAuth-Scopes:X-GitHub-Media-Type: github.v3; format=jsonContent-Encoding: gzipTransfer-Encoding: chunkedConnection: keep-aliveContent-Type: application/octet-streamX-Cache: MISS from thunderbolt.localdomainX-Cache-Lookup: MISS from thunderbolt.localdomain:8080Via: 1.1 thunderbolt.localdomain (squid/3.4.4)Server: GitHub.comDate: Thu, 28 Nov 2019 00:41:22 GMTStatus: 304 Not ModifiedX-RateLimit-Limit: 5000X-RateLimit-Remaining: 5000X-RateLimit-Reset: 1574905280Cache-Control: private, max-age=60, s-maxage=60Vary: Accept, Authorization, Cookie, X-GitHub-OTPETag: "2513f4bbc2abb8b63adbec8336a82810a4fb5dc5"Last-Modified: Wed, 05 Dec 2018 10:54:24 GMTAccess-Control-Expose-Headers: ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-TypeAccess-Control-Allow-Origin: *Strict-Transport-Security: max-age=31536000; includeSubdomains; preloadX-Frame-Options: denyX-Content-Type-Options: nosniffX-XSS-Protection: 1; mode=blockReferrer-Policy: origin-when-cross-origin, strict-origin-when-cross-originContent-Security-Policy: default-src 'none'X-GitHub-Request-Id: F066:2FC4:FE494:24E933:5DDF17B1OkHttp-Sent-Millis: 1574901681913OkHttp-Received-Millis:
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title
Jim Klimov commented on JENKINS-54126
Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria
+1 for the issue that was annoying for so long now Yes we do use GitHub caching, advocated for it to appear, and hope it stays So I set out digging in the data, and found that cached HTTP-404s in *.0 files correlate with very short *.1 files (the compact error message from Github REST API), so selecting those to look deeper: :; find . -name '.1' -size 1 | sed -e 's,^./,,' -e s',.1$,,' | while read F ; do egrep 'HTTP.*404' "$F.0" >&2 && echo "=== $F" && head -1 "$F.0" && ls -la "$F" ; done Due to reasons unknown however, the cached response for some of the URLs is HTTP/404 even with a valid JSON in the (gzipped) `hashstring.1` file: {"message":"No commit found for the ref refs/heads/4.2.0-FTY","documentation_url":"https://developer.github.com/v3/repos/contents/"} and the corresponding `hashstring.0` file looks like: :; cat fbe7227813e6f1a6bbb2f1e5202a84a2.0 https://api.github.com/repos/42ity/libzmq/contents/?ref=refs%2Fheads%2F4.2.0-FTY GET 1 Authorization: Basic NDJpdHktY2k6NjA5MDk2YTVmNzNhNTc1YzE1OWYxZjI3NDJlZmI1YjhiMTQzZmIzMw== HTTP/1.1 404 Not Found 31 X-OAuth-Scopes: admin:repo_hook, public_repo, repo:status, repo_deployment X-Accepted-OAuth-Scopes: X-GitHub-Media-Type: github.v3; format=json Content-Encoding: gzip Transfer-Encoding: chunked Connection: keep-alive Content-Type: application/octet-stream X-Cache: MISS from thunderbolt.localdomain X-Cache-Lookup: MISS from thunderbolt.localdomain:8080 Via: 1.1 thunderbolt.localdomain (squid/3.4.4) Server: GitHub.com Date: Thu, 28 Nov 2019 00:41:22 GMT Status: 304 Not Modified X-RateLimit-Limit: 5000 X-RateLimit-Remaining: 5000 X-RateLimit-Reset: 1574905280 Cache-Control: private, max-age=60, s-maxage=60 Vary: Accept, Authorization, Cookie, X-GitHub-OTP ETag: "2513f4bbc2abb8b63adbec8336a82810a4fb5dc5" Last-Modified: Wed, 05 Dec 2018 10:54:24 GMT Access-Control-Expose-Headers: ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type Access-Control-Allow-Origin: * Strict-Transport-Security: max-age=31536000; includeSubdomains; preload X-Frame-Options: deny X-Content-Type-Options: nosniff X-XSS-Protection: 1; mode=block Referrer-Policy: origin-when-cross-origin, strict-origin-when-cross-origin Content-Security-Policy: default-src 'none' X-GitHub-Request-Id: F066:2FC4:FE494:24E933:5DDF17B1 OkHttp-Sent-Millis: 1574901681913 OkHttp-Received-Millis: 1574901682110 TLS_RSA_WITH_AES_128_GCM_SHA256 2
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title Aðalsteinn Rúnarsson edited a comment on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria Hey, [~bitwiseman]This is happening very rarely for us, but it is annoying when it happens :PI can see about running that OkHttp3 update, it seems to be a patch version behind though? Are there any drawbacks from installing the OkHttp3 version? As a side note, It might be related, sometimes when we add a github repo and the credentials provided in Jenkins don't have access we seem to run into a cache-ing issue as well.So we add the Jenkins user to the Github repo with Admin access, but rescanning the pipeline still fails with invalid credentials error. Also the "Validate" function in the Job configuration will output `Error: Credentials Ok`This can be worked around by changing the case of any letter in the repo url in the Job configuration. (for example change `https://github.com/user/repo` to `https://github.com/User/repo`)I haven't tried deleting the Github Branch Source cache but I'm guessing that would also solve the issue, I will try that next time instead of the above mentioned workaround. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.5469.1570787821855%40Atlassian.JIRA.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title Aðalsteinn Rúnarsson commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria Hey, Liam Newman This is happening very rarely for us, but it is annoying when it happens I can see about running that OkHttp3 update, it seems to be a patch version behind though? Are there any drawbacks from installing the OkHttp3 version? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.5377.1570787402220%40Atlassian.JIRA.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title Liam Newman commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria Jordan Jennings - That is a completely separate issue. Jay Ache Jon Cormier Aðalsteinn Rúnarsson Would you be willing to try the OkHttp3 update in JENKINS-57411 ? It will not fix the issue while it is happening, but we are hoping it may prevent or reduce the occurrences, but we need more people that have actually seen the issue to try the fix. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.3018.1570502881844%40Atlassian.JIRA.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title Aðalsteinn Rúnarsson commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria Seeing this happen still, Jenkins 2.190.1 Github Branch Source Plugin. 2.5.8 Pipeline: Multibranch: 2.21 This has been happening from time to time for us and now again today. I did notice in a related/linked issue, https://issues.jenkins-ci.org/browse/JENKINS-57206, that this might be related to the webhook from github setting: "mergeable_state": "unknown", And I can confirm that it is what was sent in our case. And to recover we had to delete the cache at `$JENKINS_HOME/org.jenkinsci.plugins.github_branch_source.GitHubSCMProbe.cache/*` as it would not recover by re-scanning nor retriggering the webhook. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.2678.1570470061798%40Atlassian.JIRA.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title Jordan Jennings commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria We're seeing this all the time on PRs that use the draft PR feature in GitHub. I found a related issue reported for it already: https://issues.jenkins-ci.org/browse/JENKINS-57206 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.8321.1567787281773%40Atlassian.JIRA.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title
Jay Ache edited a comment on JENKINS-54126
Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Steps to reproduce:1. Create a branch {{testbranch}} that is one commit behind the tip of {{master}} (or some branch that is to be merged into)2. Make a commit to {{testbranch}} that will cause a conflict with the latest on {{master}}.3. In GitHub, create a pull-request for {{testbranch}} to be merged into {{master}}. (It will warn you that it can't be automatically merged, but "don't worry, you can still create the pull-request". (Jenkins Multibranch pipeline will refuse to create a build for both the branch and the PR).4. Rebase {{testbranch}} off the latest on {{master}}, resolve the conflicts, and {{git push origin testbranch --force}}.5. Jenkins Multibranch pipeline will catch that the branch changed, and build the branch, however, it still doesn't sense the pull-request, and refuses to create a build for it.Closing and re-opening the pull-request doesn't help.Closing the pull-request and opening a new one (for the same, conflict-free branch) does work (but is obviously not ideal).{{rm -rf $JENKINS_HOME/org.jenkinsci.plugins.github_branch_source.GitHubSCMProbe.cache/*}} does work.I'd also like to state that there indeed was a Jenkinsfile on {{testbranch}}, and that the trigger of this bug is when there's a merge conflict _at the time the pull-request is created_. Jenkins 2.176.2GitHub Source Plugin 2.5.6Pipeline: Multibranch 2.21
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.1406.1566959701783%40Atlassian.JIRA.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title Jay Ache commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria Steps to reproduce: 1. Create a branch testbranch that is one commit behind the tip of master (or some branch that is to be merged into) 2. Make a commit to testbranch that will cause a conflict with the latest on master. 3. In GitHub, create a pull-request for testbranch to be merged into master. (It will warn you that it can't be automatically merged, but "don't worry, you can still create the pull-request". (Jenkins Multibranch pipeline will refuse to create a build for both the branch and the PR). 4. Rebase testbranch off the latest on master, resolve the conflicts, and git push origin testbranch --force. 5. Jenkins Multibranch pipeline will catch that the branch changed, and build the branch, however, it still doesn't sense the pull-request, and refuses to create a build for it. Closing and re-opening the pull-request doesn't help. Closing the pull-request and opening a new one (for the same, conflict-free branch) does work (but is obviously not ideal). rm -rf $JENKINS_HOME/org.jenkinsci.plugins.github_branch_source.GitHubSCMProbe.cache/* does work. I'd also like to state that there indeed was a Jenkinsfile on testbranch, and that the trigger of this bug is when there's a merge conflict at the time the pull-request is created. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.1318.1566959461892%40Atlassian.JIRA.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title Jon Cormier commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria We encountered this problem today, we have: Jenkins v2.176.2 Branch API Plugin v2.5.4 GitHub Branch Source v2.5.5 Multijob plugin v 1.32 Pipeline: Multibranch 2.21 deleting the files under $JENKINS_HOME/org.jenkinsci.plugins.github_branch_source.GitHubSCMProbe.cache resolved the problem. This isn't a viable longterm solution though. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.6030.1566306241980%40Atlassian.JIRA.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title Sudheer Gundanna commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria This issue occurred on one our branch today. On login to Jenkins server I noticed entire branch was missing under jobs folder. We use Multipipeline project and 2.164.2, this is so annoying as we lost entire history of PR(s) that went to this branch. We map build number to PR to do feature testing and now we don't have that details. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.18199.1563825121722%40Atlassian.JIRA.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title Liam Newman commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria Thomas Liddle It is good to know the workaround still works. Thanks! 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.12382.1563292081537%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title Thomas Liddle commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria Hello All - I had this same issue with the Jenkinsfile was being discovered during the scan. After deleting the cache file specified and re-scanning it worked perfectly. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.11034.1563196262009%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title
Nick Carpenter edited a comment on JENKINS-54126
Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Workaround that worked for me:Groovy config - for a container {code:java} //See BUG - https://issues.jenkins-ci. org /browse/JENKINS-54126 org .jenkinsci.plugins.github_branch_source.GitHubSCMSource.cacheSize=0{code}And{code:java}GitHubServerConfig server = new GitHubServerConfig("my_github_credential_API"); server.setApiUrl(githubAPIurl)server.setClientCacheSize(0) //<--See https://issues.jenkins-ci.org/browse/JENKINS-54126. Had to disable this one too to get this to stop happening{code}Once both of those are configured, delete the directory:$jenkins_home/org.jenkinsci.plugins.github_branch_source.GitHubSCMProbe.cache Now that directory is not getting re-populated. Not sure why 2nd code block was required, but for what its worth, to the next person.
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.6492.1561146841742%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title
Nick Carpenter commented on JENKINS-54126
Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Workaround that worked for me: Groovy config - for a container
//See BUG - https://issues.jenkins-ci.org/browse/JENKINS-54126 org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.cacheSize=0
And
GitHubServerConfig server = new GitHubServerConfig("my_github_credential_API");
server.setApiUrl(githubAPIurl)
server.setClientCacheSize(0) //<--See https://issues.jenkins-ci.org/browse/JENKINS-54126. Had to disable this one too to get this to stop happening
Once both of those are configured, delete the directory: $jenkins_home/org.jenkinsci.plugins.github_branch_source.GitHubSCMProbe.cache Now that directory is not getting re-populated. Not sure why 2nd code block was required, but for what its worth, to the next person.
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.6415.1561146121596%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title Adam Beswick edited a comment on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria I tried 2.5.4-rc849.b58a1bae7fce, it did not fix the issue for me.I had been running builds on the branch (without a PR up) with no problem. Then as soon as I made a PR for the branch, Jenkins lost track of the branch and PR because it could no longer see the Jenkinsfile on scan. I had made the PR after merging master, and resolving conflicts in the Jenkinsfile. Deleting the cache (as above), also fixed this for me. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.20869.1559653622156%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title Adam Beswick edited a comment on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria I tried 2.5.4-rc849.b58a1bae7fce, it did not fix the issue for me. I had been running builds on the branch (without a PR up) with no problem. Then as soon as I made a PR for the branch, Jenkins lost track of the branch and PR because it could no longer see the Jenkinsfile on scan. I had made the PR after merging master, and resolving conflicts in the Jenkinsfile. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.20794.1559653501755%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title Adam Beswick commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria I tried 2.5.4-rc849.b58a1bae7fce, it did not fix the issue for me. I had been running builds on the branch (without a PR up) with no problem. Then as soon as I made a PR for the branch, Jenkins lost track of the branch and PR because it could no longer see the Jenkinsfile on scan. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.20713.1559653323248%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title Liam Newman commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria Aleksey Smyrnov, Jesse Scott, Joseph Collard, Josh Soref, David Sanftenberg, Alun Edwards, Ebrahim Moshaya, Nelson Wolf We're are trying to test whether this underlying issue could be fixed or improved by moving to okhttp3. If you are willing to help, please try the patched version of the plugin shown in the description of https://issues.jenkins-ci.org/browse/JENKINS-57411 . Thanks. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.15553.1559150880994%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title Liam Newman assigned an issue to Liam Newman Jenkins / JENKINS-54126 Jenkinsfile not found in PR on GitHub -- Does not meet criteria Change By: Liam Newman Assignee: rsandell Liam Newman 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.15481.1559150521426%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-54126 Jenkinsfile not found in PR on GitHub -- Does not meet criteria Change By: Josh Soref Summary: Jenkinsfile not found in PR on GitHub -- Does not meet criteria 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.11778.1558730521845%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
