[JIRA] (JENKINS-61340) Cannot launch windows pods
Title: Message Title Olivier Vernin moved an issue Jenkins / JENKINS-61340 Cannot launch windows pods Change By: Olivier Vernin Project: Infrastructure Jenkins Key: INFRA JENKINS - 2504 61340 Workflow: classic default workflow JNJira + In-Review Component/s: kubernetes-plugin Component/s: kubernetes Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because yo
[JIRA] (JENKINS-61340) Cannot launch windows pods
Title: Message Title Olivier Vernin commented on JENKINS-61340 Re: Cannot launch windows pods I moved this ticket to the right project with the right component 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.204921.1583349755000.6250.1583395980114%40Atlassian.JIRA.
[JIRA] (JENKINS-61325) Empty history in details view of warnings
Title: Message Title Ulli Hafner commented on JENKINS-61325 Re: Empty history in details view of warnings But you can see results in the details page of every job? Which browser are you using? Do you have a reverse proxy installed? Can you open the developer perspective in your browser and have a look if there are any errors popping up? 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.204914.158332883.6252.1583396100214%40Atlassian.JIRA.
[JIRA] (JENKINS-61289) Obat Penggugur Kandungan Cytotec dan Gastrul
Title: Message Title Olivier Vernin deleted an issue Jenkins / JENKINS-61289 Obat Penggugur Kandungan Cytotec dan Gastrul 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.204865.1583130406000.6258.1583396280709%40Atlassian.JIRA.
[JIRA] (JENKINS-61340) Cannot launch windows pods
Title: Message Title
Kalle Niemitalo updated an issue
Jenkins / JENKINS-61340
Cannot launch windows pods
Formatting didn't come out great
I improved the formatting but can't help with the problem itself. The issue should perhaps be moved from INFRA to JENKINS though, if the problem occurs on your own Jenkins instance rather than on one maintained by the Jenkins project.
Change By:
Kalle Niemitalo
Hi, Hi, I'm trying to get windows pods working on GKE but for both the _jnlp_ and _shell_ container I get the following errors: ``` {quote} Error: failed to start container "jnlp": Error response from daemon: CreateComputeSystem jnlp: The system cannot find the file specified. ``` ``` {quote}{quote} Error: failed to start container "shell": Error response from daemon: CreateComputeSystem shell: The system cannot find the file specified. ``` {quote} This is using the sample pipeline: ``` {code:groovy} /* * Runs a build on a Windows pod. * Tested in EKS: https://docs.aws.amazon.com/eks/latest/userguide/windows-support.html */ podTemplate(yaml: ''' apiVersion: v1kind v1kind : Podspec Podspec : containers: - name: jnlp image: jenkins/jnlp-agent:latest-windows - name: shell image: mcr.microsoft.com/powershell:preview-windowsservercore-1809 command: - powershell args: - Start-Sleep - 99 nodeSelector: beta.kubernetes.io/os: windows ''') \ { node(POD_LABEL) { container('shell') { powershell 'Get-ChildItem Env: | Sort Name' } } } ``` {code} Here's an outline the commands I used to setup the cluster: ``` {code:sh} gcloud beta container clusters create jenkins-cd \ --num-nodes 2 \ --machine-type n1-standard-2 \ --scopes "https://www.googleapis.com/auth/source.read_write,cloud-platform" \ --enable-ip-alias \ --release-channel=rapid gcloud container clusters get-credentials jenkins-cd gcloud beta container node-pools create windows-pool \ --cluster=jenkins-cd \ --image-type=WINDOWS_SAC \ --no-enable-autoupgrade \ --machine-type=n1-standard-2 ``` ``` {code}{code:sh} wget https://get.helm.sh/helm-v2.16.1-linux-amd64.tar.gz tar zxfv helm-v2.16.1-linux-amd64.tar. gzcp gzcp linux-amd64/helm . kubectl create clusterrolebinding cluster-admin-binding --clusterrole=cluster-admin --user=$(gcloud config get-value account) kubectl create serviceacco
[JIRA] (JENKINS-60409) Form Submission Length Cap
Title: Message Title Oleg Nenashev reopened an issue Jenkins / JENKINS-60409 Form Submission Length Cap Change By: Oleg Nenashev Resolution: Fixed Status: Resolved Reopened 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.203466.1575915955000.6301.1583396342903%40Atlassian.JIRA.
[JIRA] (JENKINS-60199) jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login
Title: Message Title Oleg Nenashev reopened an issue Jenkins / JENKINS-60199 jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login Change By: Oleg Nenashev Resolution: Fixed Status: Resolved Reopened 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.203169.1574080196000.6313.1583396343138%40Atlassian.JIRA.
[JIRA] (JENKINS-60409) Form Submission Length Cap
Title: Message Title Oleg Nenashev commented on JENKINS-60409 Re: Form Submission Length Cap Winstone 5.9 with fixes was released: https://github.com/jenkinsci/winstone/releases/tag/winstone-5.9 Jenkins Core update pull request: https://github.com/jenkinsci/jenkins/pull/4542 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.203466.1575915955000.6286.1583396342714%40Atlassian.JIRA.
[JIRA] (JENKINS-60199) jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login
Title: Message Title Oleg Nenashev commented on JENKINS-60199 Re: jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login Winstone 5.9 with fixes was released: https://github.com/jenkinsci/winstone/releases/tag/winstone-5.9 Jenkins Core update pull request: https://github.com/jenkinsci/jenkins/pull/4542 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.203169.1574080196000.6271.1583396342453%40Atlassian.JIRA.
[JIRA] (JENKINS-61325) Empty history in details view of warnings
Title: Message Title Why Name updated an issue Jenkins / JENKINS-61325 Empty history in details view of warnings Change By: Why Name Attachment: empty_his.JPG 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.204914.158332883.6460.1583396406977%40Atlassian.JIRA.
[JIRA] (JENKINS-28335) Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Title: Message Title Kari Niemi commented on JENKINS-28335 Re: Step to run Git commands w/ credentials & tool (was: GitPublisher support) Official coudbees provided instructions for the workaround: https://support.cloudbees.com/hc/en-us/articles/360027646491-Pipeline-Equivalent-to-Git-Publisher ...but they have bugs in the examples: withCredentials is used to publish variable GIT_USERNAME ... and then that variable is referenced with GIT_AUTH_USR in shell step. The same mistake for password variables. 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.162769.1431338323000.6457.1583396406800%40Atlassian.JIRA.
[JIRA] (JENKINS-60536) Jenkins job hangs in Jira call after git rev-list command
Title: Message Title David France commented on JENKINS-60536 Re: Jenkins job hangs in Jira call after git rev-list command The merged version has been fine for the last week - can't see any stuck threads, To be fair though, we haven't gone back and checked if the freezing behaviour would come back without this. The merge was pushed up to https://github.com/xft-devs/jira-plugin . If you haven't already, it may be worth trying pulling or cloning that again. 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.203639.1576745651000.6469.1583396580374%40Atlassian.JIRA.
[JIRA] (JENKINS-61341) FileNotFoundException if withCredentials([sshUserPrivateKey]) is called twice
Title: Message Title
Timo Heck created an issue
Jenkins / JENKINS-61341
FileNotFoundException if withCredentials([sshUserPrivateKey]) is called twice
Issue Type:
Bug
Assignee:
Unassigned
Components:
credentials-binding-plugin
Created:
2020-03-05 08:22
Environment:
OS: centos Jenkins: 2.223 OpenJDK 1.8.0_242 credentials-binding: 1.21 ssh-steps: 2.0.0
Priority:
Minor
Reporter:
Timo Heck
Hi. I am currently working on a Jenkins pipeline and trying to move all credential handling in the domain of the jenkins instance. To be able to execute an ssh command on another machine we use private key authentication. I tried to accomplish this by combining credentials-binding and ssh-steps but ran into a problem I couldn't find a solution to. I basicly do this:
node {
def remote = [:]
remote.name = "integration_server"
remote.host = integration_server
remote.allowAnyHosts = true
withCredentials([sshUserPrivateKey(credentialsId: 'myCredentialId', keyFileVariable: 'identity', passphraseVariable: '', usernameVariable: 'userName')]) {
remote.user = userName
remote.identityFile = identity
sshCommand remote: remote, command: "do stuff"
}
...
withCredentials([sshUserPrivateKey(credentialsId: 'myCredentialId', keyFileVariable: 'identity', passphraseVariable: '', usernameVariable: 'userName')]) {
remote.user = userName
remote.identityFile = identity
sshCommand remote: remote, command: "do some other stuff"
}
}
[JIRA] (JENKINS-61325) Empty history in details view of warnings
Title: Message Title Why Name updated an issue Jenkins / JENKINS-61325 Empty history in details view of warnings Change By: Why Name Attachment: js_error.JPG 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.204914.158332883.6477.1583396640151%40Atlassian.JIRA.
[JIRA] (JENKINS-61325) Empty history in details view of warnings
Title: Message Title Why Name commented on JENKINS-61325 Re: Empty history in details view of warnings Yes, see attached I am using Chrome, see errors 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.204914.158332883.6479.1583396700180%40Atlassian.JIRA.
[JIRA] (JENKINS-61321) Pipeline Job configuration appears read-only for users with project-level permissions after update to Jenkins 2.223
Title: Message Title Daniel Beck commented on JENKINS-61321 Re: Pipeline Job configuration appears read-only for users with project-level permissions after update to Jenkins 2.223 Only an LTS candidate so this doesn't get missed if we decide to include JENKINS-61202. 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.204910.1583317053000.6488.1583396820213%40Atlassian.JIRA.
[JIRA] (TEST-201) moj task
Title: Message Title Andjela Milic created an issue test / TEST-201 moj task Issue Type: Task Assignee: Andjela Milic Components: foo13 Created: 2020-03-05 08:40 Environment: sasaasas Priority: Minor Reporter: Andjela Milic asasasa Add Comment This message was sent by Atlassian Jira (v7.13.
[JIRA] (JENKINS-60199) jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-60199 jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login Change By: Oleg Nenashev Environment: Jenkins: 2.205, Jenkins LTS 2.204.3 , and 2.204.4 Winstone 5.5 to 5.8 Apache 2.4.41 as reverse proxy 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.203169.1574080196000.6518.1583397781154%40Atlassian.JIRA.
[JIRA] (JENKINS-60409) Form Submission Length Cap
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-60409 Form Submission Length Cap Change By: Oleg Nenashev Environment: Jenkins 2.205+, Jenkins LTS 2.204.3 and 2.204.4Winstone 5.5 to 5.8 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.203466.1575915955000.6503.1583397780890%40Atlassian.JIRA.
[JIRA] (JENKINS-61325) Empty history in details view of warnings
Title: Message Title Ulli Hafner commented on JENKINS-61325 Re: Empty history in details view of warnings Do you see the elements in the Issues tab, they are also loaded using AJAX? How is your Jenkins instance protected? Are you using a reverse proxy? When there is a 500 error, then Jenkins should also report something in the log file, can you please check? 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.204914.158332883.6530.1583397840236%40Atlassian.JIRA.
[JIRA] (JENKINS-60409) Form Submission Length Cap
Title: Message Title
Oleg Nenashev updated an issue
Jenkins / JENKINS-60409
Form Submission Length Cap
Change By:
Oleg Nenashev
**Jenkins LTS Notice**: Jenkins LTS 2.204.3 and 2.204.4 are also affected due to the Winstone upgrade which was backported as a part of the JENKINS-57888 fix backporting. Please see [https://groups.google.com/forum/#!topic/jenkinsci-dev/M_RtDuDXtbU] for the discussion and retrospective In Jenkins Version 2.205, PR #4339 moved the cloud configuration from Configure System into is own configuration form on the Manage Nodes page. There is a cap to the length of this form (20) and prevents me from adding additional docker clouds into the settings.{code:java}java.lang.IllegalStateException: Form is larger than max length 20 at org.eclipse.jetty.server.Request.extractFormParameters(Request.java:562) at org.eclipse.jetty.server.Request.extractContentParameters(Request.java:519) at org.eclipse.jetty.server.Request.getParameters(Request.java:430)Caused: org.eclipse.jetty.http.BadMessageException: 400: Unable to parse form content at org.eclipse.jetty.server.Request.getParameters(Request.java:434) at org.eclipse.jetty.server.Request.getParameterNames(Request.java:1077) at hudson.security.csrf.CrumbFilter.extractCrumbFromRequest(CrumbFilter.java:112) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:118) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:90) at hudson.security.HudsonFilter.doFilter(HudsonFilter.j
[JIRA] (JENKINS-60199) jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-60199 jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login Change By: Oleg Nenashev After the upgrade from 2.204 to 2.205 jenkins redirects to http(s)://127.0.0.1/ after login. **Jenkins LTS Notice**: Jenkins LTS 2.204.3 and 2.204.4 are also affected due to the Winstone upgrade which was backported as a part of the JENKINS-57888 fix backporting. Please see [https://groups.google.com/forum/#!topic/jenkinsci-dev/M_RtDuDXtbU] for the discussion and retrospective 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.203169.1574080196000.6545.1583398021299%40Atlassian.JIRA.
[JIRA] (JENKINS-60409) Form Submission Length Cap
Title: Message Title
Oleg Nenashev updated an issue
Jenkins / JENKINS-60409
Form Submission Length Cap
Change By:
Oleg Nenashev
**Jenkins LTS Notice**: Jenkins LTS 2.204.3 and 2.204.4 are also affected due to the Winstone upgrade which was backported introduced as a part of the JENKINS-57888 fix backporting. Please see [https://groups.google.com/forum/#!topic/jenkinsci-dev/M_RtDuDXtbU] for the discussion and retrospectiveIn Jenkins Version 2.205, PR #4339 moved the cloud configuration from Configure System into is own configuration form on the Manage Nodes page. There is a cap to the length of this form (20) and prevents me from adding additional docker clouds into the settings.{code:java}java.lang.IllegalStateException: Form is larger than max length 20 at org.eclipse.jetty.server.Request.extractFormParameters(Request.java:562) at org.eclipse.jetty.server.Request.extractContentParameters(Request.java:519) at org.eclipse.jetty.server.Request.getParameters(Request.java:430)Caused: org.eclipse.jetty.http.BadMessageException: 400: Unable to parse form content at org.eclipse.jetty.server.Request.getParameters(Request.java:434) at org.eclipse.jetty.server.Request.getParameterNames(Request.java:1077) at hudson.security.csrf.CrumbFilter.extractCrumbFromRequest(CrumbFilter.java:112) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:118) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:90) at hudson.security.HudsonFilter.doFilter(H
[JIRA] (JENKINS-60199) jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-60199 jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login Change By: Oleg Nenashev After the upgrade from 2.204 to 2.205 jenkins redirects to http(s)://127.0.0.1/ after login. **Jenkins LTS Notice**: Jenkins LTS 2.204.3 and 2.204.4 are also affected due to the Winstone upgrade which was backported introduced as a part of the JENKINS-57888 fix backporting. Please see [https://groups.google.com/forum/#!topic/jenkinsci-dev/M_RtDuDXtbU] for the discussion and retrospective 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.203169.1574080196000.6573.1583398201338%40Atlassian
[JIRA] (JENKINS-60199) jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-60199 jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login Change By: Oleg Nenashev After the upgrade from 2.204 to 2.205 jenkins redirects to http(s)://127.0.0.1/ after login. *Workaround*: For Apache: set "ProxyPreserveHost On" as documented in [https://wiki.jenkins.io/display/JENKINS/Running+Jenkins+behind+Apache] **Jenkins LTS Notice**: Jenkins LTS 2.204.3 and 2.204.4 are also affected due to the Winstone upgrade which was introduced as a part of the JENKINS-57888 fix backporting. Please see [https://groups.google.com/forum/#!topic/jenkinsci-dev/M_RtDuDXtbU] for the discussion and retrospective 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 discus
[JIRA] (JENKINS-61196) Define tool-specific quality gates
Title: Message Title R. F. commented on JENKINS-61196 Re: Define tool-specific quality gates I have configured my pipeline in the way that it uses scanForIssues step for each tool independently (e.g. java(), javaDoc(), taskScanner()). At the end there is a pipeline stage which always posts the results (depending on the results of the previously Gradle task and if a scan has been done) like this: publishIssues issues: [java, javaDoc, ...] Here I can configure qualityGates which will affect all tools. I could configure recordIssues or scanForIssues plus publishIssues for each tool scan, but then on the main status page of a Jenkins job, Jenkins shows multiple trend charts for each tool separately. For the publishIssues step there is no option like this: publishIssues trendChartType: 'AGGREGATION_ONLY' This option would allow me using multipe publishIssues steps. Only for recordIssues I can do that: recordIssues aggregatingResults: true But using recordIssues I cannot suppress showing all other trend charts of each tool scan. In the end this is the only option I have found that the status page shows the aggregation trend chart only! I also notice this has a bad side effect when it comes to dashbords. Using this solution ends up in the fact that I can display only the aggregated values, not separated by tools. Add Comment
[JIRA] (JENKINS-61196) Define tool-specific quality gates
Title: Message Title
R. F. edited a comment on JENKINS-61196
Re: Define tool-specific quality gates
I have configured my pipeline in the way that it uses {{scanForIssues}} step for each tool independently (e.g. java(), javaDoc(), taskScanner()).At the end there is a pipeline stage which always posts the results (depending on the results of the previously Gradle task and if a scan has been done) like this:{code:java}publishIssues issues: [java, javaDoc, ...]{code}Here I can configure *qualityGates which will affect all tools*.I could configure {{recordIssues}} or {{scanForIssues}} plus {{publishIssues}} for each tool scan, but then on the main status page of a Jenkins job, *Jenkins shows multiple trend charts for each tool separately*. For the {{publishIssues}} step there is no option like this:{code:java}publishIssues trendChartType: 'AGGREGATION_ONLY'{code}This option would allow me using multipe {{publishIssues}} steps.Only for {{recordIssues}} I can do that:{code:java}recordIssues aggregatingResults: true{code}But using {{recordIssues}} I cannot suppress showing all other trend charts of each tool scan.In the end this is the only option I have found that the status page shows the aggregation trend chart only!I also notice noticed this has a bad side effect when it comes to dashbords. Using this solution ends up in the fact that I can display only the aggregated values, not separated by tools.
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,
[JIRA] (JENKINS-61196) Define tool-specific quality gates
Title: Message Title Ulli Hafner commented on JENKINS-61196 Re: Define tool-specific quality gates I see. Then please rework the issue description and title so it is clear what actually should be done. Adding the trendChartType property to publishIssues should not be hard... 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.204744.1582539544000.6631.1583402520138%40Atlassian.JIRA.
[JIRA] (JENKINS-61196) Define tool-specific quality gates
Title: Message Title
Ulli Hafner edited a comment on JENKINS-61196
Re: Define tool-specific quality gates
I see. Then please rework the issue description and title so it is clear what actually should be done. Adding the {{trendChartType}} property to {{ publishIssues }} should not be hard...
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.204744.1582539544000.6633.1583402580251%40Atlassian.JIRA.
[JIRA] (JENKINS-59973) rtUpload / rtDownload fail with HTTP 401 / 403
Title: Message Title Eyal Ben Moshe edited a comment on JENKINS-59973 Re: rtUpload / rtDownload fail with HTTP 401 / 403 Could this be a bug in the "authorize-project plugin " plugin ? See [https://github.com/jfrog/jenkins-artifactory-plugin/issues/247] 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.202777.157235158.6640.1583403180357%40Atlassian.JIRA.
[JIRA] (JENKINS-59973) rtUpload / rtDownload fail with HTTP 401 / 403
Title: Message Title Eyal Ben Moshe commented on JENKINS-59973 Re: rtUpload / rtDownload fail with HTTP 401 / 403 Could this be a bug in the "authorize-project plugin"? See https://github.com/jfrog/jenkins-artifactory-plugin/issues/247 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.202777.157235158.6638.1583403180312%40Atlassian.JIRA.
[JIRA] (JENKINS-59670) Support retrieval of secrets from multiple AWS accounts
Title: Message Title Chris Kilding updated JENKINS-59670 Jenkins / JENKINS-59670 Support retrieval of secrets from multiple AWS accounts Change By: Chris Kilding Status: In Progress Review 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.202362.1570220885000.6648.1583403360603%40Atlassian.JIRA.
[JIRA] (JENKINS-60908) AWS Secrets Manager Plugin Breaking Change
Title: Message Title Chris Kilding updated JENKINS-60908 Jenkins / JENKINS-60908 AWS Secrets Manager Plugin Breaking Change Change By: Chris Kilding Status: In Progress Review 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.204299.1580318008000.6650.1583403360625%40Atlassian.JIRA.
[JIRA] (JENKINS-61291) Allow CasC to retrieve secrets from Secrets Manager
Title: Message Title Chris Kilding updated JENKINS-61291 Jenkins / JENKINS-61291 Allow CasC to retrieve secrets from Secrets Manager Change By: Chris Kilding Status: In Progress Review 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.204868.1583151125000.6651.1583403420091%40Atlassian.JIRA.
[JIRA] (JENKINS-60921) Revisit typography
Title: Message Title Félix Queiruga Balado started work on JENKINS-60921 Change By: Félix Queiruga Balado Status: Open In Progress 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.204318.1580393661000.6653.1583403720349%40Atlassian.JIRA.
[JIRA] (JENKINS-60921) Revisit typography
Title: Message Title Félix Queiruga Balado assigned an issue to Félix Queiruga Balado Jenkins / JENKINS-60921 Revisit typography Change By: Félix Queiruga Balado Assignee: Félix Queiruga Balado 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.204318.1580393661000.6654.1583403720367%40Atlassian.JIRA.
[JIRA] (JENKINS-60972) Rename the root breadcrumb
Title: Message Title Félix Queiruga Balado updated an issue Jenkins / JENKINS-60972 Rename the root breadcrumb Change By: Félix Queiruga Balado Labels: newbie-friendly 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.204437.1580894909000.6657.1583404140382%40Atlassian.JIRA.
[JIRA] (JENKINS-61224) "Monitors" terminology should not be used in GUI
Title: Message Title Félix Queiruga Balado updated an issue Jenkins / JENKINS-61224 "Monitors" terminology should not be used in GUI Change By: Félix Queiruga Balado Labels: lts-candidate newbie-friendly 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.204778.158264254.6659.1583404140410%40Atlassian.JIRA.
[JIRA] (JENKINS-60924) Add the PostCSS pre-processor
Title: Message Title Félix Queiruga Balado updated an issue Jenkins / JENKINS-60924 Add the PostCSS pre-processor Change By: Félix Queiruga Balado Labels: newbie-friendly 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.204321.158039935..1583404200173%40Atlassian.JIRA.
[JIRA] (JENKINS-60972) Rename the root breadcrumb
Title: Message Title Félix Queiruga Balado updated an issue Jenkins / JENKINS-60972 Rename the root breadcrumb Change By: Félix Queiruga Balado One of the items discussed on the UX SIG meetings ([https://jenkins.io/sigs/ux/]) was renaming the root breadcrumb to _"Home"_. The reason for this is that it can be confusing having Jenkins in 2 consecutive lines. An example of how it could look:!rootbreadcrumb.png! The solution probably should take into account i18n capabilities. 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.204437.1580894909000.6673.1583404380163%40Atlassian.JIRA.
[JIRA] (JENKINS-61322) After update to 2.204.4 I get javax.xml.bind.JAXBException immediately after login
Title: Message Title Mark Hagers updated an issue Jenkins / JENKINS-61322 After update to 2.204.4 I get javax.xml.bind.JAXBException immediately after login Change By: Mark Hagers Priority: Blocker Minor 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.204911.1583318535000.6675.1583404440383%40Atlassian.JIRA.
[JIRA] (JENKINS-61322) After update to 2.204.4 I get javax.xml.bind.JAXBException immediately after login
Title: Message Title Mark Hagers commented on JENKINS-61322 Re: After update to 2.204.4 I get javax.xml.bind.JAXBException immediately after login We solved this by restoring from a backup, so this is not very urgent currently. Even though few people may run into this, I still think this is a potentially serious issue: If you install a plugin that affects logging into jenkins (such as the crowd 2 plugin) and the plugin runs into a problem you may be unable to log in. There is no good recovery path from there, since you'll be unable to uninstall the plugin. 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.204911.1583318535000.6677.1583404740114%40Atlassian.JIRA.
[JIRA] (JENKINS-61193) When using proxy also export the no_proxy hosts.
Title: Message Title Gyanesha Prajjwal commented on JENKINS-61193 Re: When using proxy also export the no_proxy hosts. I have added a commit, please verify it. 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.204739.1582532685000.6679.1583404980113%40Atlassian.JIRA.
[JIRA] (JENKINS-61224) "Monitors" terminology should not be used in GUI
Title: Message Title Romen Rodriguez-Gil edited a comment on JENKINS-61224 Re: "Monitors" terminology should not be used in GUI I'd agree with Jesse, we don't need to have text at all, just the bell and the number, as is common pattern in many other cases, such as GitHub.[~fqueiruga], are you OK if I assign this to myself as discussed in the UX SIG? I'll be happy to work on that so that I get more familiar with the Jenkins UI and can keep contributing to it. Edit: Just chatted with Félix and he is OK, so I'm assigning it to me 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.204778.158264254.6682.1583405100444%40Atlassian.JIRA.
[JIRA] (JENKINS-61224) "Monitors" terminology should not be used in GUI
Title: Message Title Romen Rodriguez-Gil assigned an issue to Romen Rodriguez-Gil Jenkins / JENKINS-61224 "Monitors" terminology should not be used in GUI Change By: Romen Rodriguez-Gil Assignee: Félix Queiruga Balado Romen Rodriguez-Gil 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.204778.158264254.6689.1583405100644%40Atlassian.JIRA.
[JIRA] (JENKINS-60924) Add the PostCSS pre-processor
Title: Message Title Félix Queiruga Balado updated an issue Jenkins / JENKINS-60924 Add the PostCSS pre-processor Change By: Félix Queiruga Balado Add the PostCSS pre-processor ([https://postcss.org/]) to improve the generated CSS bundles with features like .h3.Plugins needed:- Autoprefixer (https://github.com/postcss/ autoprefixer or REM fallbacks )h4 . Possible candidatesSome research is needed to determine if the following plugins are useful:- Flexbugs fixes(https://github.com/luisrudge/postcss-flexbugs-fixes)The most straightforward way to go is to apply it the `webpack.config.js` file located under the `war` module 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/jenkin
[JIRA] (JENKINS-60924) Add the PostCSS pre-processor
Title: Message Title Félix Queiruga Balado updated an issue Jenkins / JENKINS-60924 Add the PostCSS pre-processor Change By: Félix Queiruga Balado Add the PostCSS pre-processor ([https://postcss.org/]) to improve the generated CSS bundles. The most straightforward way to go is to apply it the `webpack.config.js` file located under the `war` module h4.Plugins needed:- Autoprefixer (https://github.com/postcss/autoprefixer)h4.Possible candidatesSome research is needed to determine if the following plugins are useful:- Flexbugs fixes(https://github.com/luisrudge/postcss-flexbugs-fixes) The most straightforward way to go is to apply it the `webpack.config.js` file located under the `war` module 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
[JIRA] (JENKINS-60924) Add the PostCSS pre-processor
Title: Message Title Félix Queiruga Balado updated an issue Jenkins / JENKINS-60924 Add the PostCSS pre-processor Change By: Félix Queiruga Balado Add the PostCSS pre-processor ([https://postcss.org/]) to improve the generated CSS bundles. h3 h4 .Plugins needed:- Autoprefixer (https://github.com/postcss/autoprefixer)h4.Possible candidatesSome research is needed to determine if the following plugins are useful:- Flexbugs fixes(https://github.com/luisrudge/postcss-flexbugs-fixes)The most straightforward way to go is to apply it the `webpack.config.js` file located under the `war` module 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.204321.158039935.66
[JIRA] (JENKINS-61342) httprequest plugin: Systemproperties do not work
Title: Message Title leon gregori created an issue Jenkins / JENKINS-61342 httprequest plugin: Systemproperties do not work Issue Type: Bug Assignee: Janario Oliveira Components: http-request-plugin Created: 2020-03-05 10:50 Environment: http request plugin: 1.8.24 Jenkins: 2.204.2 Priority: Major Reporter: leon gregori Dear Jenkins Community, im using httprequest plugin with systemproperties. unfortunately, when using proxy from systemproperties, the request does not work. When giving the proxy dedicated into httprequest dsl method, it works: Works: httpRequest httpProxy: 'http://192.105.124.55:8081', authentication: 'GitHubID', url: "https://raw.github.blabla.net/bl-abla/some/master/project/project.properties" Does not work: httpRequest authentication: 'GitHubID', responseHandle: 'NONE', url: "https://raw.github.blabla.net/bl-abla/some/master/project/project.properties" , useSystemProperties: true The system properties are as follows and should fit to what is required: http.proxyHost http://192.105.124.55:8081 http.proxyPort 8081 https.proxyHost http://192.105.124.55:8081 https.proxyPort 8081 However, with systemproperties it does not work:
[JIRA] (JENKINS-61224) "Monitors" terminology should not be used in GUI
Title: Message Title Baptiste Mathus commented on JENKINS-61224 Re: "Monitors" terminology should not be used in GUI Woot <3! Gracias Romen! Go go go ! \o/ 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.204778.158264254.6708.1583406600367%40Atlassian.JIRA.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski updated an issue Jenkins / JENKINS-57795 Orphaned EC2 instances after Jenkins restart Change By: Jakub Bochenski Environment: Jenkins ver. 2.176.1 , 2.204.2 ec2 plugin 1.43, 1.44, 1.45, 1.49.1 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.199745.1559315049000.6723.1583407080729%40Atlassian.JIRA.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski updated an issue Jenkins / JENKINS-57795 Orphaned EC2 instances after Jenkins restart Change By: Jakub Bochenski Environment: Jenkins ver. 2.176.1ec2 plugin 1.43, 1.44, 1.45 , 1.49.1 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.199745.1559315049000.6721.1583407080708%40Atlassian.JIRA.
[JIRA] (JENKINS-60764) Allow configuration per folder rather than globally
Title: Message Title Chris Kilding commented on JENKINS-60764 Re: Allow configuration per folder rather than globally How secret names are treated is still up for discussion, at the moment the draft implementation rejects them, but we could potentially support a namespacing feature for this. Eg your Jenkins job would ask for credential ID "/" and it would be fetched from the relevant account. This would allow the secret names in each AWS account to be identical. But it leaks an implementation detail - the AWS account ID - into the Jenkins job definition, which is not ideal for credential portability. When I say Jenkins running in a shared tools account, basically this is a pattern where you have a number of environment-specific accounts (staging, prod) and you want a single Jenkins to manage them. It's not appropriate for that Jenkins to run in any of the environment-specific accounts, because by definition it exists outside those environments to manage them. As a result it is often put in an environment-independent account (sometimes called 'tools') with any other shared infrastructure (e.g. Artifactory), and given cross-account access to manage the relevant AWS resources in each environment. Even if a particular job only gets secrets from, say, the production account, under the hood Jenkins would make cross-account requests to get them. When you said you want to have a single Jenkins managing all three environments, I assumed you had a setup like this in mind. 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.
[JIRA] (JENKINS-61343) EC2 alive slaves monitor thread died unexpectedly
Title: Message Title Jakub Bochenski created an issue Jenkins / JENKINS-61343 EC2 alive slaves monitor thread died unexpectedly Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2020-03-05 11:20 Environment: Jenkins ver. 2.204.2 ec2 plugin 1.49.1 Priority: Major Reporter: Jakub Bochenski I'm seeing this in the logs every 10 minutes. The monitor thread starts and then dies. 10 minutes later it repeats. Mar 05, 2020 10:54:35 AM INFO hudson.model.AsyncPeriodicWork lambda$doRun$0 Started EC2 alive slaves monitor Mar 05, 2020 10:54:35 AM SEVERE hudson.init.impl.InstallUncaughtExceptionHandler$DefaultUncaughtExceptionHandler uncaughtException A thread (EC2 alive slaves monitor thread/10354) died unexpectedly due to an uncaught exception, this may leave your Jenkins in a bad way and is usually indicative of a bug in the code. java.lang.NullPointerException at hudson.plugins.ec2.util.MinimumInstanceChecker.lambda$countQueueItemsForAgentTemplate$8(MinimumInstanceChecker.java:67) at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:174) at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472) at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708) at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.util.stream.LongPipeline.reduce(LongPipe
[JIRA] (JENKINS-59901) UFT Tests from ALM. Run on Planned Host.
Title: Message Title Juan Pablo Ruiz-Moyano Gomez commented on JENKINS-59901 Re: UFT Tests from ALM. Run on Planned Host. No news on this issue? There is a new version [6.0] but we think a fix haven't been implemented. Is there any version planned? Thank you. 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.202650.1571836527000.6731.1583407680230%40Atlassian.JIRA.
[JIRA] (JENKINS-60764) Allow configuration per folder rather than globally
Title: Message Title Chris Kilding commented on JENKINS-60764 Re: Allow configuration per folder rather than globally Regarding the question of access control... a new approach has just come up, which might be more appropriate for your use case. This approach would involve defining credentials for the folders plugin in JCasC YAML - basically what you have already done with the folders plugin, but codified in YAML. You would interpolate the actual values of those credentials using JCasC interpolation key syntax. The upcoming SecretSource support in the AWS secrets manager credentials provider (JENKINS-61291) would then resolve the values from Secrets Manager, and save them into the on-disk copy of those credentials. JCasC would then fetch the values from Secrets Manager each time it runs, to keep them up to date. As far as your jobs are concerned, the credentials will still come from the folders plugin like they do today. So the folders plugin would still be responsible for access control. 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.204025.1579015116000.6743.1583407980164%40Atlassian.JIRA.
[JIRA] (JENKINS-60764) Allow configuration per folder rather than globally
Title: Message Title Chris Kilding edited a comment on JENKINS-60764 Re: Allow configuration per folder rather than globally Regarding the question of access control... a new approach has just come up, which might be more appropriate for your use case.This approach would involve defining credentials for the folders plugin in JCasC YAML - basically what you have already done with the folders plugin, but codified in YAML. You would interpolate the actual values of those credentials using JCasC interpolation key syntax. The upcoming SecretSource support in the AWS secrets manager credentials provider (JENKINS-61291) would then resolve the values from Secrets Manager, and hand them back to JCasC, which would save them into the on-disk copy of those credentials. JCasC would then fetch the values from Secrets Manager each time it runs, to keep them up to date.As far as your jobs are concerned, the credentials will still come from the folders plugin like they do today. So the folders plugin would still be responsible for access control. 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.204025.1579015116000.6746.1583408040201%40Atlassian.JIRA.
[JIRA] (JENKINS-60764) Allow configuration per folder rather than globally
Title: Message Title Chris Kilding edited a comment on JENKINS-60764 Re: Allow configuration per folder rather than globally Regarding the question of access control... a new approach has just come up, which might be more appropriate for your use case.This approach would involve defining credentials for the folders plugin in JCasC YAML - basically what you have already done with the folders plugin, but codified in YAML. You would interpolate the actual values of those credentials using JCasC interpolation key syntax. The upcoming SecretSource support in the AWS secrets manager credentials provider (JENKINS-61291) would then resolve the values from Secrets Manager, and hand them back to JCasC, which would save them into the on-disk copy of those credentials.JCasC would then fetch the values from Secrets Manager consults its interpolation sources each time it runs, to keep them which should ensure that your credentials stay up to date on a frequency of however often you run JCasC .As far as your jobs are concerned, the credentials will still come from the folders plugin like they do today. So the folders plugin would still be responsible for access control. 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.204025.1579015116000.6749.1583408160155%40Atlassian.JIRA.
[JIRA] (JENKINS-61344) Api call with a token lead to a 403 but the user has "overall read" via "authenticated user" group
Title: Message Title greg oire created an issue Jenkins / JENKINS-61344 Api call with a token lead to a 403 but the user has "overall read" via "authenticated user" group Issue Type: Bug Assignee: Daniel Beck Components: matrix-auth-plugin Created: 2020-03-05 11:43 Environment: Jenkins 2.204.2 JDK Oracle 8 (202) Labels: jenkins api matrix-auth Priority: Minor Reporter: greg oire I use "Project-based Matrix Authorization Strategy ". I set the group "Authenticated Users" with permission overall read, job read, credential view, view read. If a user try to call an api with a token like: `curl -u myuser:123456 -v -H 'Accept: application/json' https://jenkins/api/json` then the response is 403 with a HTML body in which I have "myuser is missing the Overall/Read permission" If I add a "overall read" permission on the "myuser" itself, then the api is working (200 + data) Does this mean that authenticating via a token do not add the 'authenticated' group ? Is this wanted? if so why not a "tokens" group ?
[JIRA] (JENKINS-61344) Api call with a token lead to a 403 but the user has "overall read" via "authenticated user" group
Title: Message Title Daniel Beck closed an issue as Not A Defect Overall/Read grants basic access to Jenkins. Nothing more. Users without that basically cannot do anything, except in very limited circumstances. Users have a group or don't, the method of authentication doesn't change what they're authorized to do. Jenkins / JENKINS-61344 Api call with a token lead to a 403 but the user has "overall read" via "authenticated user" group Change By: Daniel Beck Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this m
[JIRA] (JENKINS-61345) DescriptorList#newInstanceFromRadioList() and ExtensionDescriptorList#newInstanceFromRadioList() may throw undocumented runtime JSONException
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-61345 DescriptorList#newInstanceFromRadioList() and ExtensionDescriptorList#newInstanceFromRadioList() may throw undocumented runtime JSONException Change By: Oleg Nenashev Assignee: Oleg Nenashev 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.204937.1583410086000.6757.1583410140275%40Atlassian.JIRA.
[JIRA] (JENKINS-61345) DescriptorList#newInstanceFromRadioList() and ExtensionDescriptorList#newInstanceFromRadioList() may throw undocumented runtime JSONException
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-61345 DescriptorList#newInstanceFromRadioList() and ExtensionDescriptorList#newInstanceFromRadioList() may throw undocumented runtime JSONException Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-03-05 12:08 Priority: Minor Reporter: Oleg Nenashev It was discovered during the analysis of https://github.com/jenkinsci/jenkins/pull/3969/ parent.getJSONObject(name) may throw a JSONException "if the key is not found or if the value is not a JSONObject". http://javadox.com/org.json/json/20151123/org/json/JSONObject.html#getJSONObject-java.lang.String- . In such case Jenkins will still throw a proper Error in the most of configuration form submissions, but it might become an issue for other API usages like Groovy plugin. So it is better to fix it Add Comment
[JIRA] (JENKINS-61345) DescriptorList#newInstanceFromRadioList() and ExtensionDescriptorList#newInstanceFromRadioList() may throw undocumented runtime JSONException
Title: Message Title Oleg Nenashev started work on JENKINS-61345 Change By: Oleg Nenashev Status: Open In Progress 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.204937.1583410086000.6758.1583410140289%40Atlassian.JIRA.
[JIRA] (JENKINS-61344) Api call with a token lead to a 403 but the user has "overall read" via "authenticated user" group
Title: Message Title greg oire commented on JENKINS-61344 Re: Api call with a token lead to a 403 but the user has "overall read" via "authenticated user" group From your answer, Jenkins do have a bug. If I set Overall/Read to "authenticated" user, then I expect even with a token, such policy is executed hence a user without other permission would be able to call jenkins api. It is not the case. 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.204936.1583408586000.6760.1583411940147%40Atlassian.JIRA.
[JIRA] (JENKINS-61059) Allow the deletion/modification of EC2 clouds through groovy
Title: Message Title
John Doe commented on JENKINS-61059
Re: Allow the deletion/modification of EC2 clouds through groovy
This is apparently already possible. I was able to delete all existing clouds using the following snippet:
Jenkins jenkins = Jenkins.getInstance()
jenkins.clouds.each {
jenkins.clouds.remove(it)
}
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.204539.1581434861000.6762.1583412180163%40Atlassian.JIRA.
[JIRA] (JENKINS-61059) Allow the deletion/modification of EC2 clouds through groovy
Title: Message Title
John Doe edited a comment on JENKINS-61059
Re: Allow the deletion/modification of EC2 clouds through groovy
This is apparently already possible. I was able to delete all existing clouds using the following snippet: {code:java}Jenkins jenkins = Jenkins.getInstance()jenkins.clouds.each { jenkins.clouds.remove(it)}{code}
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.204539.1581434861000.6764.1583412180195%40Atlassian.JIRA.
[JIRA] (JENKINS-61059) Allow the deletion/modification of EC2 clouds through groovy
Title: Message Title John Doe closed an issue as Not A Defect Jenkins / JENKINS-61059 Allow the deletion/modification of EC2 clouds through groovy Change By: John Doe Status: Open Closed Resolution: Not A Defect 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.204539.1581434861000.6766.1583412240379%40Atlassian.JIRA.
[JIRA] (JENKINS-61344) Api call with a token lead to a 403 but the user has "overall read" via "authenticated user" group
Title: Message Title Daniel Beck commented on JENKINS-61344 Re: Api call with a token lead to a 403 but the user has "overall read" via "authenticated user" group greg oire Adding the authenticated pseudo-group is the responsibility of the plugin providing authentication (i.e. security realm). So there seems to be a bug here, I agree, but not in matrix-auth. 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.204936.1583408586000.6769.1583412300142%40Atlassian.JIRA.
[JIRA] (JENKINS-61344) Api call with a token lead to a 403 but the user has "overall read" via "authenticated user" group
Title: Message Title greg oire commented on JENKINS-61344 Re: Api call with a token lead to a 403 but the user has "overall read" via "authenticated user" group Is there a generic specific handler for token somewhere or each authentication handler duplicate the token authentication management ? 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.204936.1583408586000.6771.1583412540119%40Atlassian.JIRA.
[JIRA] (JENKINS-61344) Api call with a token lead to a 403 but the user has "overall read" via "authenticated user" group
Title: Message Title greg oire commented on JENKINS-61344 Re: Api call with a token lead to a 403 but the user has "overall read" via "authenticated user" group OK, I found the code, but will need to debug as at first sight it seems correct... Thank you. 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.204936.1583408586000.6773.1583413380157%40Atlassian.JIRA.
[JIRA] (JENKINS-57402) Let diagrams interact with Details table
Title: Message Title Why Name commented on JENKINS-57402 Re: Let diagrams interact with Details table For the mean time another simpler to implement option is to add the new / outstanding / solved attribute in the issues table so it can be sorted or filtered 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.199186.1557486983000.6779.1583415660190%40Atlassian.JIRA.
[JIRA] (JENKINS-61325) Empty history in details view of warnings
Title: Message Title Why Name commented on JENKINS-61325 Re: Empty history in details view of warnings You are correct. The problem was related to the server and not to the plugin and it was solved. Closing the ticket. 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.204914.158332883.6782.1583415780116%40Atlassian.JIRA.
[JIRA] (JENKINS-61325) Empty history in details view of warnings
Title: Message Title Why Name closed an issue as Not A Defect Jenkins / JENKINS-61325 Empty history in details view of warnings Change By: Why Name Status: Open Closed Resolution: Not A Defect 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.204914.158332883.6784.1583415840214%40Atlassian.JIRA.
[JIRA] (JENKINS-61346) environmentVariables doesn't escape multiline content
Title: Message Title
Jakub Bochenski created an issue
Jenkins / JENKINS-61346
environmentVariables doesn't escape multiline content
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2020-03-05 14:25
Priority:
Major
Reporter:
Jakub Bochenski
This keeps tripping me. This will result in invalid properties file format:
environmentVariables {
env 'config', '''multiline
content
'''
You have to add sth like string.replaceAll('\n','n' ) to escape it manually
Add Comment
[JIRA] (JENKINS-61346) environmentVariables doesn't escape multiline content
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-61346
environmentVariables doesn't escape multiline content
Change By:
Jakub Bochenski
This keeps tripping me. This will result in invalid properties file format:{code}environmentVariables {env 'config', '''multilinecontent } ''' } {code}You have to add sth like {{string.replaceAll('\n','n' )}} to escape it manually
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.204938.1583418355000.6790.1583418420377%40Atlassian.JIRA.
[JIRA] (JENKINS-61346) environmentVariables doesn't escape multiline content
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-61346
environmentVariables doesn't escape multiline content
Change By:
Jakub Bochenski
This keeps tripping me. This will result in invalid properties file format:{code}environmentVariables {env 'config', '''multilinecontent } '''{code}You have to add sth like {{string.replaceAll('\n','n' )}} to escape it manually
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.204938.1583418355000.6788.1583418420345%40Atlassian.JIRA.
[JIRA] (JENKINS-61346) environmentVariables doesn't escape multiline content
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-61346
environmentVariables doesn't escape multiline content
Change By:
Jakub Bochenski
This keeps tripping me. This will result in invalid properties file format:{code}environmentVariables {env 'config', '''multilinecontent'''}{code}You have to add sth like {{string.replaceAll('\n','\\\ \ n' )}} to escape it manually
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.204938.1583418355000.6792.1583418480262%40Atlassian.JIRA.
[JIRA] (JENKINS-61340) Cannot launch windows pods
Title: Message Title Alexander Perry commented on JENKINS-61340 Re: Cannot launch windows pods It looks like a symlink related to a log file is causing issues, does any know a work around for this? kubectl logs -f pods/windows-test-9-mdt6s-t2kj3-2qv1t jnlp failed to try resolving symlinks in path "\\var\\log\\pods\\default_windows-test-9-mdt6s-t2kj3-2qv1t_318ba281-c8ec-4a56-8515-c65316427b01\\jnlp\\0.log": CreateFile \var\log\pods\default_windows-test-9-mdt6s-t2kj3-2qv1t_318ba281-c8ec-4a56-8515-c65316427b01\jnlp\0.log: The system cannot find the file specified. 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.204921.1583349755000.6811.1583419560170%40Atlassian.JIRA.
[JIRA] (JENKINS-61346) environmentVariables doesn't escape multiline content
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-61346
environmentVariables doesn't escape multiline content
Change By:
Jakub Bochenski
This keeps tripping me. This will result in invalid properties file format:{code}environmentVariables {env 'config', '''multilinecontent'''}{code}You have to add sth like {{string.replaceAll('\n','\n\\' )}} to escape it manuallyEDIT: above should work but doesn't because of some bug in the envijector, but {{string.replace('\n','\\\ \ n')}} works
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.204938.1583418355000.6817.1583419680370%40Atlassian.JIRA.
[JIRA] (JENKINS-61346) environmentVariables doesn't escape multiline content
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-61346
environmentVariables doesn't escape multiline content
Change By:
Jakub Bochenski
This keeps tripping me. This will result in invalid properties file format:{code}environmentVariables {env 'config', '''multilinecontent'''}{code}You have to add sth like {{string.replaceAll('\n','\ n \\ n ' )}} to escape it manually EDIT: above should work but doesn't because of some bug in the envijector, but {{string.replace('\n','\\n')}} works
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.204938.1583418355000.6813.1583419680289%40Atlassian.JIRA.
[JIRA] (JENKINS-61346) environmentVariables doesn't escape multiline content
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-61346
environmentVariables doesn't escape multiline content
Change By:
Jakub Bochenski
This keeps tripping me. This will result in invalid properties file format:{code}environmentVariables {env 'config', '''multilinecontent'''}{code}You have to add sth like {{string.replaceAll('\n','\n\\' )}} to escape it manuallyEDIT: above should work but doesn't because of some bug in the envijector, but {{string.replace('\n','\\ \\ n')}} works
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.204938.1583418355000.6815.1583419680331%40Atlassian.JIRA.
[JIRA] (JENKINS-61346) environmentVariables doesn't escape multiline content
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-61346
environmentVariables doesn't escape multiline content
Change By:
Jakub Bochenski
This keeps tripping me. This will result in invalid properties file format:{code}environmentVariables {env 'config', '''multilinecontent'''}{code}You have to add sth like {{string.replaceAll('\n','\n\\' )}} to escape it manuallyEDIT: above should work but doesn't because of some bug in the envijector, but {{string.replace('\n','\\ \ n')}} works
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.204938.1583418355000.6819.1583419740284%40Atlassian.JIRA.
[JIRA] (JENKINS-61346) environmentVariables doesn't escape multiline content
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-61346
environmentVariables doesn't escape multiline content
Change By:
Jakub Bochenski
This keeps tripping me. This will result in invalid properties file format:{code}environmentVariables {env 'config', '''multilinecontent'''}{code}You have to add sth like {{string.replaceAll('\n','\n\\' )}} to escape it manuallyEDIT: above should work but doesn't because of some bug in the envijector, but {{string.replace('\n','\\ \ n')}} works
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.204938.1583418355000.6821.1583419740312%40Atlassian.JIRA.
[JIRA] (JENKINS-61346) environmentVariables doesn't escape multiline content
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-61346
environmentVariables doesn't escape multiline content
Change By:
Jakub Bochenski
This keeps tripping me. This will result in invalid properties file format:{code}environmentVariables {env 'config', '''multilinecontent'''}{code}You have to add sth like {{string.replaceAll('\n','\n\\' )}} to escape it manuallyEDIT: above should work but doesn't because of some bug in the envijector, but {{string.replace('\n','\\ \ n')}} works
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.204938.1583418355000.6823.1583419740338%40Atlassian.JIRA.
[JIRA] (JENKINS-61346) environmentVariables doesn't escape multiline content
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-61346
environmentVariables doesn't escape multiline content
Change By:
Jakub Bochenski
This keeps tripping me. This will result in invalid properties file format:{code}environmentVariables {env 'config', '''multilinecontent'''}{code}You have to add sth like { { code} string.replaceAll('\n','\n\\' ) {code } } to escape it manuallyEDIT: above should work but doesn't because of some bug in the envijector, but {code}string.replace('\n','\\n'){code} works
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.204938.1583418355000.6827.1583419800288%40Atlassian.JIRA.
[JIRA] (JENKINS-61346) environmentVariables doesn't escape multiline content
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-61346
environmentVariables doesn't escape multiline content
Change By:
Jakub Bochenski
This keeps tripping me. This will result in invalid properties file format:{code}environmentVariables {env 'config', '''multilinecontent'''}{code}You have to add sth like {{string.replaceAll('\n','\n\\' )}} to escape it manuallyEDIT: above should work but doesn't because of some bug in the envijector, but { { code} string.replace('\n','\\n') {code } } works
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.204938.1583418355000.6825.1583419800228%40Atlassian.JIRA.
[JIRA] (JENKINS-60199) jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login
Title: Message Title Mark Waite commented on JENKINS-60199 Re: jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login Do we also need a message applied to the 2.204.3 changelog and the 2.204.4 changelog to alert users that they may be affected by it? 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.203169.1574080196000.6842.1583421900368%40Atlassian.JIRA.
[JIRA] (JENKINS-60039) durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
Title: Message Title
Tim Black commented on JENKINS-60039
Re: durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
We're having same problem, but it's not yet clear what change caused the behavior. We are on durable task plugin v1.33, however we have not updated this recently to my knowledge (and I haven't been able to find plugin update history anywhere - any advice?) The signature of the build failures is that the `withDockerContainer` step completes successfully, and the pipeline begins to run the sh command (the first step in the `withDockerContainer` clause) and there's no apparent activity (other than the seemingly normal output in the durable task plugin loggers) for 5 minutes, then the failure message as the OP here. Here is what the durable task loggers output during those 5 minutes: ``` Mar 05, 2020 7:03:57 AM FINER org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep seems to be online so using /var/lib/jenkins/workspace/TesiraFirmwareNG_develop Mar 05, 2020 7:03:57 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep still running in /var/lib/jenkins/workspace/TesiraFirmwareNG_develop on ``` After 5 minutes, I then see: ``` Mar 05, 2020 7:05:12 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep calling close with nl=true Mar 05, 2020 7:05:14 AM FINEST org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep JENKINS-34021: DurableTaskStep.Execution.listener present in CpsStepContext[101:sh]:OwnerTesiraFirmwareNG/develop/42:TesiraFirmwareNG/develop #42 Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep launching task against hudson.remoting.LocalChannel@41a7fb38 using hudson.Launcher$LocalLauncher@722b273b Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.durabletask.BourneShellScript launching [nohup, sh, c, ({ while [ -d '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859' -a ! -f '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-result.txt' ]; do touch '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-log.txt'; sleep 3; done } & jsc=durable-97017349f4d4de030acf9aecc2fb49fa; JENKINS_SERVER_COOKIE=$$jsc 'sh' -xe '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/script.sh' > '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-log.txt' 2>&1; echo $$? > '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-result.txt.tmp'; mv '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-result.txt.tmp' '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-result.txt'; wait) >& 2>&- &] Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep launched task Mar 05, 2020 7:05:14 AM FINEST org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep JENKINS-34021: DurableTaskStep.Execution.listener present in CpsStepContext[102:sh]:OwnerTesiraFirmwareNG/develop/42:TesiraFirmwareNG/develop #42 Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep launching task against hudson.remoting.LocalChannel@41a7fb38 using hudson.Launcher$LocalLauncher@460edded Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.durabletask.BourneShellScript launching [nohup, sh, c, ({ while [ -d '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a359e9b0' -a ! -f '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a359e9b0/jenkins-result.txt' ]; do touch '/var/lib/jenkins/workspace/TesiraF
[JIRA] (JENKINS-60039) durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
Title: Message Title
Tim Black edited a comment on JENKINS-60039
Re: durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
We're having same problem, but it's not yet clear what change caused the behavior. We are on durable task plugin v1.33, and [Jenkins ver. 2.190.3|https://jenkins.io/], however we have not updated this recently to my knowledge (and I haven't been able to find plugin update history anywhere - any advice?) . The signature of the build failures is that the `withDockerContainer` step completes successfully, and the pipeline begins to run the sh command (the first step in the `withDockerContainer` clause) and there's no apparent activity (other than the seemingly normal output in the durable task plugin loggers) for 5 minutes, then the failure message as the OP here. Here is what the durable task loggers output during those 5 minutes: ``` {code:java} Mar 05, 2020 7:03:57 AM FINER org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep seems to be online so using /var/lib/jenkins/workspace/TesiraFirmwareNG_develop Mar 05, 2020 7:03:57 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep still running in /var/lib/jenkins/workspace/TesiraFirmwareNG_develop on {code} ``` After 5 minutes, I then see: ``` {code:java} Mar 05, 2020 7:05:12 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepcalling close with nl=trueMar 05, 2020 7:05:14 AM FINEST org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepJENKINS-34021: DurableTaskStep.Execution.listener present in CpsStepContext[101:sh]: Owner[TesiraFirmwareNG OwnerTesiraFirmwareNG /develop/42:TesiraFirmwareNG/develop #42 ] Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskSteplaunching task against hudson.remoting.LocalChannel@41a7fb38 using hudson.Launcher$LocalLauncher@722b273bMar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.durabletask.BourneShellScriptlaunching [nohup, sh, - c, ( \ { while [ -d '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859' -a \ ! -f '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-result.txt' ]; do touch '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-log.txt'; sleep 3; done } & jsc=durable-97017349f4d4de030acf9aecc2fb49fa; JENKINS_SERVER_COOKIE=$$jsc 'sh' -xe '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/script.sh' > '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-log.txt' 2>&1; echo $$? > '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-result.txt.tmp'; mv '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-result.txt.tmp' '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-result.txt'; wait) >& - 2>&- &]Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskSteplaunched taskMar 05, 2020 7:05:14 AM FINEST org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepJENKINS-34021: DurableTaskStep.Execution.listener present in CpsStepContext[102:sh]: Owner[TesiraFirmwareNG OwnerTesiraFirmwareNG /develop/42:TesiraFirmwareNG/develop #42 ] Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskSteplaunching task against hudson.remoting.LocalChannel@41a7fb38 using hudson.Launcher$LocalLauncher@460eddedMar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.durabletask.BourneShellScriptlaunching [nohup, sh, - c, ( \ { while [ -d '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a
[JIRA] (JENKINS-61347) Checkout problem on a branch
Title: Message Title
Omega Bionic created an issue
Jenkins / JENKINS-61347
Checkout problem on a branch
Issue Type:
New Feature
Assignee:
Omega Bionic
Components:
jenkinsfile-runner
Created:
2020-03-05 15:36
Environment:
Linux
Priority:
Minor
Reporter:
Omega Bionic
Hi ! I can't checkout on a branch, I'm always detached and I can't find any documentation on how to do it, so I'm wondering if it's possible ^^'
steps {
checkout scm
And I would like full tag like: v5.2.1-66-ga026dc4 and not like: a026dc4 So I end up with an incomplete tag. Would you have a solution? Thank you
Add Comment
[JIRA] (JENKINS-60409) Form Submission Length Cap
Title: Message Title Jesse Glick started work on JENKINS-60409 Change By: Jesse Glick Status: Open In Progress 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.203466.1575915955000.6897.1583422682786%40Atlassian.JIRA.
[JIRA] (JENKINS-60409) Form Submission Length Cap
Title: Message Title Jesse Glick updated JENKINS-60409 Jenkins / JENKINS-60409 Form Submission Length Cap Change By: Jesse Glick Status: In Progress Review 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.203466.1575915955000.6899.1583422682815%40Atlassian.JIRA.
[JIRA] (JENKINS-60409) Form Submission Length Cap
Title: Message Title Jesse Glick updated JENKINS-60409 Jenkins / JENKINS-60409 Form Submission Length Cap Change By: Jesse Glick Status: Reopened Open 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.203466.1575915955000.6881.1583422682583%40Atlassian.JIRA.
[JIRA] (JENKINS-60223) Pipeline implementing readObject/writeObject fails with ProxyException CpsCallableInvocation
Title: Message Title Roland Stengel commented on JENKINS-60223 Re: Pipeline implementing readObject/writeObject fails with ProxyException CpsCallableInvocation Sergei, many thanks, it's simple and it works. Interestingly, Jenkins does not serialize a multi branch pipeline, so i can't use read/writeObject to resume from stage, but this another story 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.203198.1574244805000.6915.1583423280388%40Atlassian.JIRA.
[JIRA] (JENKINS-60199) jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login
Title: Message Title Oleg Nenashev commented on JENKINS-60199 Re: jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login Mark Waite it would be nice, I have not got to it yet due to LTS backports 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.203169.1574080196000.6917.1583423280421%40Atlassian.JIRA.
[JIRA] (JENKINS-61262) Error on configure Jenkins save
Title: Message Title Heidi Rechek commented on JENKINS-61262 Re: Error on configure Jenkins save removing plugin removed error. Why would a plugin cause that kind of error? 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.204833.1582835438000.6929.1583423342350%40Atlassian.JIRA.
[JIRA] (JENKINS-60039) durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
Title: Message Title
Tim Black commented on JENKINS-60039
Re: durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
REverting DT plugin to v1.29, restarting Jenkins, and re building a test job that uses withDockerContainer { sh }, results in this:
Running in Durability level: PERFORMANCE_OPTIMIZED
[Pipeline] Start of Pipeline
[Pipeline] End of Pipeline
java.lang.NoSuchMethodError: No such DSL method 'pipeline' found among steps [ansiblePlaybook, ansibleVault, build, checkout, emailext, emailextrecipients, findFiles, git, input, jiraComment, jiraIssueSelector, jiraSearch, junit, library, libraryResource, load, lock, milestone, nodesByLabel, office365ConnectorSend, parallel, properties, publishHTML, readCSV, readJSON, readManifest, readMavenPom, readProperties, readTrusted, readYaml, resolveScm, sha1, slackSend, slackUploadFile, stage, svn, tee, timestamps, tm, touch, unzip, withCredentials, writeCSV, writeJSON, writeMavenPom, writeYaml, xunit, zip] or symbols [AUnit, BoostTest, CTest, CUnit, Check, CppTest, CppUnit, Custom, FPCUnit, GoogleTest, JUnit, MSTest, MbUnit, NUnit2, NUnit3, PHPUnit, QtTest, UnitTest, Valgrind, all, always, ant, antFromApache, antOutcome, antTarget, apiToken, architecture, archiveArtifacts, artifactManager, authorizationMatrix, batchFile, bitbucket, booleanParam, brokenBuildSuspects, brokenTestsSuspects, buildAllBranches, buildAnyBranches, buildButton, buildChangeRequests, buildDiscarder, buildNamedBranches, buildNoneBranches, buildParameter, buildRegularBranches, buildSelector, buildTags, caseInsensitive, caseSensitive, certificate, choice, choiceParam, clock, cloud, command, configFile, configFileProvider, copyArtifactPermission, copyArtifacts, credentials, cron, crumb, culprits, defaultView, demand, developers, disableConcurrentBuilds, disableResume, dockerCert, downloadSettings, downstream, dumb, durabilityHint, embUnit, envInject, envVars, exact, extendedChoice, failed, file, fileParam, filePath, fingerprint, frameOptions, freeStyle, freeStyleJob, fromScm, fromSource, git, gitBranchDiscovery, gitHubBranchDiscovery, gitHubBranchHeadAuthority, gitHubForkDiscovery, gitHubSshCheckout, gitHubTagDiscovery, gitHubTrustContributors, gitHubTrustEveryone, gitHubTrustNobody, gitHubTrustPermissions, gitParameter, gitTagDiscovery, github, githubPush, globalConfigFiles, gtester, headRegexFilter, headWildcardFilter, hyperlink, hyperlinkToModels, inheriting, inheritingGlobal, installSource, jdk, jdkInstaller, jgit, jgitapache, jnlp, jobName, lastCompleted, lastDuration, lastFailure, lastGrantedAuthorities, lastStable, lastSuccess, lastSuccessful, lastWithArtifacts, latestSavedBuild, legacy, legacySCM, list, local, location, logRotator, loggedInUsersCanDoAnything, masterBuild, maven, maven3Mojos, mavenErrors, mavenMojos, mavenWarnings, modernSCM, myView, nodeProperties, nonInheriting, none, office365ConnectorSend, office365ConnectorWebhooks, overrideIndexTriggers, paneStatus, parameters, passed, password, pattern, permalink, permanent, pipelineTriggers, plainText, plugin, pollSCM, projectNamingStrategy, proxy, queueItemAuthenticator, quietPeriod, rateLimitBuilds, recipients, regex, requestor, run, runParam, sSHLauncher, schedule, scmRetryCount, scriptApproval, scriptApprovalLink, search, security, shell, skipped, slackNotifier, slave, sourceRegexFilter, sourceWildcardFilter, specific, ssh, sshUserPrivateKey, stackTrace, standard, status, string, stringParam, swapSpace, text, textParam, tmpSpace, toolLoc
[JIRA] (JENKINS-60039) durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
Title: Message Title
Tim Black edited a comment on JENKINS-60039
Re: durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
REverting DT plugin to v1.29, restarting Jenkins, and re building a test job that uses withDockerContainer \{ sh }, results in the below error. Note that we are using PERFORMANCE_OPTIMIZED durability level for this : job. That seems relevant, but I don't know enough to connect the dots. Also what seems relevant is that this behavior started after a reboot of the Jenkins master _while a job downstream of this test job was running on a_ slave. From what I've read about Durable Task plugin, its purpose is to enable nodes to manage/monitor processes running on other nodes. This smells rotten. Please enlighten me if you can connect any of these dots. __ {code:java}Running in Durability level: PERFORMANCE_OPTIMIZED[Pipeline] Start of Pipeline[Pipeline] End of Pipelinejava.lang.NoSuchMethodError: No such DSL method 'pipeline' found among steps [ansiblePlaybook, ansibleVault, build, checkout, emailext, emailextrecipients, findFiles, git, input, jiraComment, jiraIssueSelector, jiraSearch, junit, library, libraryResource, load, lock, milestone, nodesByLabel, office365ConnectorSend, parallel, properties, publishHTML, readCSV, readJSON, readManifest, readMavenPom, readProperties, readTrusted, readYaml, resolveScm, sha1, slackSend, slackUploadFile, stage, svn, tee, timestamps, tm, touch, unzip, withCredentials, writeCSV, writeJSON, writeMavenPom, writeYaml, xunit, zip] or symbols [AUnit, BoostTest, CTest, CUnit, Check, CppTest, CppUnit, Custom, FPCUnit, GoogleTest, JUnit, MSTest, MbUnit, NUnit2, NUnit3, PHPUnit, QtTest, UnitTest, Valgrind, all, always, ant, antFromApache, antOutcome, antTarget, apiToken, architecture, archiveArtifacts, artifactManager, authorizationMatrix, batchFile, bitbucket, booleanParam, brokenBuildSuspects, brokenTestsSuspects, buildAllBranches, buildAnyBranches, buildButton, buildChangeRequests, buildDiscarder, buildNamedBranches, buildNoneBranches, buildParameter, buildRegularBranches, buildSelector, buildTags, caseInsensitive, caseSensitive, certificate, choice, choiceParam, clock, cloud, command, configFile, configFileProvider, copyArtifactPermission, copyArtifacts, credentials, cron, crumb, culprits, defaultView, demand, developers, disableConcurrentBuilds, disableResume, dockerCert, downloadSettings, downstream, dumb, durabilityHint, embUnit, envInject, envVars, exact, extendedChoice, failed, file, fileParam, filePath, fingerprint, frameOptions, freeStyle, freeStyleJob, fromScm, fromSource, git, gitBranchDiscovery, gitHubBranchDiscovery, gitHubBranchHeadAuthority, gitHubForkDiscovery, gitHubSshCheckout, gitHubTagDiscovery, gitHubTrustContributors, gitHubTrustEveryone, gitHubTrustNobody, gitHubTrustPermissions, gitParameter, gitTagDiscovery, github, githubPush, globalConfigFiles, gtester, headRegexFilter, headWildcardFilter, hyperlink, hyperlinkToModels, inheriting, inheritingGlobal, installSource, jdk, jdkInstaller, jgit, jgitapache, jnlp, jobName, lastCompleted, lastDuration, lastFailure, lastGrantedAuthorities, lastStable, lastSuccess, lastSuccessful, lastWithArtifacts, latestSavedBuild, legacy, legacySCM, list, local, location, logRotator, loggedInUsersCanDoAnything, masterBuild, maven, maven3Mojos, mavenErrors, mavenMojos, mavenWarnings, modernSCM, myView, nodeProperties, nonInheriting, none, office365ConnectorSend, office365ConnectorWebhooks, overrideIndexTriggers, paneStatus, parameters, passed, password, pattern, permalink, permanent, pipelineTriggers, plainText, plugin, pollSCM, projectNamingStrategy, proxy, queueItemAuthenticator, quietPeriod, rate
[JIRA] (JENKINS-44466) Allow plugins to override aspects of the Blue Ocean theme
Title: Message Title Brandon Fryslie edited a comment on JENKINS-44466 Re: Allow plugins to override aspects of the Blue Ocean theme What's the Is there any known timeline on when this might be implemented ? This is pretty inconvenient We would appreciate this feature a lot . :) We use different color schemes to signal to users which environment Jenkins is running in. e.g., a Jenkins running in 'dev' has different colors to that running in 'prod'. This helps prevent issues where a user thinks they are running a job on their local 'dev' Jenkins instance but instead they are running it on the actual production instance.Implementing a field in the global configuration that lets us define our own CSS file to load from the 'userContent' directory of Jenkins would be straightforward and allow us to change things as needed. This doesn't need to be complicated, we just need some way to inject some minor CSS into the page. 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.182294.1495611527000.6944.1583424420265%40Atlassian.JIRA.
[JIRA] (JENKINS-61340) Cannot launch windows pods
Title: Message Title Alexander Perry commented on JENKINS-61340 Re: Cannot launch windows pods It seems to me that the log is not being created and this causes the image to fail. The directory in question on the host is empty: C:\var\log\pods\default_windows-test-9-mdt6s-t2kj3-2qv1t_318ba281-c8ec-4a56-8515-c65316427b01\jnlp>dir Volume in drive C has no label. Volume Serial Number is C62F-FA38 Directory of C:\var\log\pods\default_windows-test-9-mdt6s-t2kj3-2qv1t_318ba281-c8ec-4a56-8515-c65316427b01\jnlp 03/04/2020 05:07 PM . 03/04/2020 05:07 PM .. 0 File(s) 0 bytes 2 Dir(s) 75,565,420,544 bytes free Is there an option I can put into the template to prevent logging through the symlink? Or just disable logging entirely? 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.204921.1583349755000.6951.1583424660207%40Atlassian.JIRA.
