[JIRA] (JENKINS-44032) embeddable build status should bust cache
Title: Message Title Kevin Carrasco commented on JENKINS-44032 Re: embeddable build status should bust cache Thomas Döring I'm using 2.0 and this is not an issue for me anymore. It actually wasnt the plugin's fault but a misconfiguration of the nginx proxy ssl certs. I put an nginx proxy infront of Jenkins to handle the ssl stuff. When adding the cert you must concatenate the server certificate and the CA certificate together. For example: cat servercert.crt ca_cert.crt > nginxcert.crt If you dont do this and only use servercert.crt, everything will look fine if you use a browser to go to Jenkins but when you use a tool like curl, the cert will not be trusted. I've seen other system tools behave this way and have also seen this when using SSL libraries for some programming/scripting languages which is probably why GitHub's markdown renderer didnt want to load the badge. After configuring this properly, the badge loaded with no problems. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44032) embeddable build status should bust cache
Title: Message Title Kevin Carrasco commented on JENKINS-44032 Re: embeddable build status should bust cache I'm having this issue as well. Maybe the Cache-Control header needs to be tweaked a bit more? Here are the headers from my build status badge which does not render on GitHub: $ curl -L -I https://jenkins.bardel.ca/buildStatus/icon?job=backend/master HTTP/1.1 200 OK Server: nginx/1.13.12 Date: Fri, 17 Aug 2018 21:15:31 GMT Content-Type: image/svg+xml;charset=utf-8 Content-Length: 802 Connection: keep-alive X-Content-Type-Options: nosniff ETag: "/static/0e86a960/build-passing-brightgreen-flat.svg" Expires: Fri, 01 Jan 1984 00:00:00 GMT Cache-Control: no-cache, private X-SSH-Endpoint: jenkins.bardel.ca:50022 and here are the headers of a different badge that does render correctly on GitHub: $ curl -L -I https://ruby-gem-downloads-badge.herokuapp.com/rails HTTP/1.1 200 OK Server: Cowboy Connection: keep-alive Date: Fri, 17 Aug 2018 21:08:23 GMT Content-Type: image/svg+xml;Content-Encoding: gzip; charset=utf-8 Pragma: no-cache Etag: "0415ad7e8ce0c3161a010b8f55ff01cb" Last-Modified: Fri, 17 Aug 2018 21:07:23 GMT Cache-Control: private, no-cache, no-store, must-revalidate, max-age=-86400 Expires: Thu, 16 Aug 2018 21:08:23 GMT Via: 1.1 vegur Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups
[JIRA] (JENKINS-51255) Kubernetes plugin declarative pipeline can't use readFile to read yaml file
Title: Message Title Kevin Carrasco edited a comment on JENKINS-51255 Re: Kubernetes plugin declarative pipeline can't use readFile to read yaml file [~oleg_nenashev] I expect to read k8s-podspec.yaml from the repository. We would like the yaml file to be part of the source code on a separate file. For now we're including the yaml contents in the Jenkinsfile. 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-51255) Kubernetes plugin declarative pipeline can't use readFile to read yaml file
Title: Message Title Kevin Carrasco commented on JENKINS-51255 Re: Kubernetes plugin declarative pipeline can't use readFile to read yaml file Oleg Nenashev I expect to read k8s-podspec.yaml from the repository. 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-51255) Kubernetes plugin declarative pipeline can't use readFile to read yaml file
Title: Message Title
Kevin Carrasco created an issue
Jenkins / JENKINS-51255
Kubernetes plugin declarative pipeline can't use readFile to read yaml file
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2018-05-10 22:02
Priority:
Minor
Reporter:
Kevin Carrasco
Using the following settings declarative pipeline:
pipeline {
agent {
kubernetes {
cloud 'OpenShift'
label 'jenkins-agent-pod'
yaml readFile('k8s-podspec.yaml')
}
}
...
Results in the following error from Jenkins:
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] readFile
Required context class hudson.FilePath is missing
Perhaps you forgot to surround the code with a step that provides this, such as: node
[Pipeline] End of Pipeline
