[JIRA] (JENKINS-50748) Caught exception evaluating in configureSecurity - NullPointerException
Title: Message Title Oleg Nenashev commented on JENKINS-50748 Re: Caught exception evaluating in configureSecurity - NullPointerException Yes, I confirm your analysis. Thanks! Wadeck Follonier PTAL Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50748) Caught exception evaluating in configureSecurity - NullPointerException
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50748 Caught exception evaluating in configureSecurity - NullPointerException Change By: Oleg Nenashev Labels: lts-candidate regression Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50748) Caught exception evaluating in configureSecurity - NullPointerException
Title: Message Title Oleg Nenashev assigned an issue to Wadeck Follonier Jenkins / JENKINS-50748 Caught exception evaluating in configureSecurity - NullPointerException Change By: Oleg Nenashev Assignee: Wadeck Follonier Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50754) "ERROR: Could not find credentials matching (rolename)" when using AWS role
Title: Message Title Oleg Nenashev commented on JENKINS-50754 Re: "ERROR: Could not find credentials matching (rolename)" when using AWS role Just to clarify, does this ID represent the "AWS Credentials" type? If yes, the plugin won't be able to use them. Only "Docker Registry Token" credentials type is supported by the plugin according to the code, all other credentials will be ignored. https://github.com/jenkinsci/docker-commons-plugin/blob/e00c616a847630fccf637e891000813a7b441ceb/src/main/java/org/jenkinsci/plugins/docker/commons/credentials/DockerRegistryEndpoint.java#L184-L186 The error message could be improved for sure. It could indicate the required type/domain at least Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50502) JEP-200: Refusing to marshal com.blackducksoftware.integration.hub.report.api.ReportData for security reasons
Title: Message Title Oleg Nenashev started work on JENKINS-50502 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50502) JEP-200: Refusing to marshal com.blackducksoftware.integration.hub.report.api.ReportData for security reasons
Title: Message Title Oleg Nenashev commented on JENKINS-50502 Re: JEP-200: Refusing to marshal com.blackducksoftware.integration.hub.report.api.ReportData for security reasons Thanks James Richard. Let us know once it is released, we will update the status documentation Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50566) Google Compute Engine Plugin JEP-200 Class rejected
Title: Message Title Oleg Nenashev commented on JENKINS-50566 Re: Google Compute Engine Plugin JEP-200 Class rejected Evan Brown In order to test it... In the local build with Maven you can use "mvn clean verify -Djenkins.version=2.107.2" to run with particular versions In Jenkinsfile you can use: buildPugin(jenkinsVersions: [null, '2.107.2'])/ It will make the PR builder to run tests with the current and the specified Maven version Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44200) Failed to scout hudson.plugins.cobertura.MavenCoberturaPublisher
Title: Message Title
Florian Kammermann edited a comment on JENKINS-44200
Re: Failed to scout hudson.plugins.cobertura.MavenCoberturaPublisher
Same error here, with different behaviour: * jenkins gui was not accessible anymore * the log showed, that the error was printing in a loop * additionally I had a Guice container error * after restart the loop was gone * the error was shown on startupthe logs{code}Apr 12, 2018 6:26:45 AM hudson.ExtensionFinder$GuiceFinder$SezpozModule configureWARNING: Failed to load hudson.plugins.cobertura.MavenCoberturaPublisherjava.lang.InstantiationException: java.lang.NoClassDefFoundError: hudson/maven/MavenReporter at net.java.sezpoz.IndexItem.element(IndexItem.java:146)Caused by: java.lang.NoClassDefFoundError: hudson/maven/MavenReporter at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:763)Caused by: java.lang.ClassNotFoundException: hudson.maven.MavenReporter at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1374) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1327) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1080)-Apr 12, 2018 6:26:45 AM hudson.ExtensionFinder$GuiceFinder SEVERE: Failed to create Guice container from all the pluginscom.google.common.util.concurrent.ExecutionError: com.google.common.util.concurrent.ExecutionError: java.lang.NoClassDefFoundError: Lorg/jenkinsci/main/modules/instance_identity/InstanceIdentity; at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2232) at com.google.common.cache.LocalCache.get(LocalCache.java:3965) at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3969)--Caused by: com.google.common.util.concurrent.ExecutionError: java.lang.NoClassDefFoundError: Lorg/jenkinsci/main/modules/instance_identity/InstanceIdentity; at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2232) at com.google.common.cache.LocalCache.get(LocalCache.java:3965) at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3969)---Caused by: java.lang.NoClassDefFoundError: Lorg/jenkinsci/main/modules/instance_identity/InstanceIdentity; at java.lang.Class.getDeclaredFields0(Native Method) at java.lang.Class.privateGetDeclaredFields(Class.java:2583) at java.lang.Class.getDeclaredFields(Class.java:1916)---Caused by: java.lang.ClassNotFoundException: org.jenkinsci.main.modules.instance_identity.InstanceIdentity at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357){code} jenkins version: 2.89.4maven integration: 3.1Cobetura: 1.12
Add Comment
[JIRA] (JENKINS-44200) Failed to scout hudson.plugins.cobertura.MavenCoberturaPublisher
Title: Message Title
Florian Kammermann commented on JENKINS-44200
Re: Failed to scout hudson.plugins.cobertura.MavenCoberturaPublisher
Same error here, with different behaviour:
jenkins gui was not accessible anymore
the log showed, that the error was printing in a loop
additionally I had a Guice container error
after restart the loop was gone
the error was shown on startup
the logs {code} Apr 12, 2018 6:26:45 AM hudson.ExtensionFinder$GuiceFinder$SezpozModule configure WARNING: Failed to load hudson.plugins.cobertura.MavenCoberturaPublisher java.lang.InstantiationException: java.lang.NoClassDefFoundError: hudson/maven/MavenReporter at net.java.sezpoz.IndexItem.element(IndexItem.java:146) Caused by: java.lang.NoClassDefFoundError: hudson/maven/MavenReporter at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:763) Caused by: java.lang.ClassNotFoundException: hudson.maven.MavenReporter at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1374) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1327) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1080) - Apr 12, 2018 6:26:45 AM hudson.ExtensionFinder$GuiceFinder SEVERE: Failed to create Guice container from all the plugins com.google.common.util.concurrent.ExecutionError: com.google.common.util.concurrent.ExecutionError: java.lang.NoClassDefFoundError: Lorg/jenkinsci/main/modules/instance_identity/InstanceIdentity; at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2232) at com.google.common.cache.LocalCache.get(LocalCache.java:3965) at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3969) -- Caused by: com.google.common.util.concurrent.ExecutionError: java.lang.NoClassDefFoundError: Lorg/jenkinsci/main/modules/instance_identity/InstanceIdentity; at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2232) at com.google.common.cache.LocalCache.get(LocalCache.java:3965) at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3969) --- Caused by: java.lang.NoClassDefFoundError: Lorg/jenkinsci/main/modules/instance_identity/InstanceIdentity; at java.lang.Class.getDeclaredFields0(Native Method) at java.lang.Class.privateGetDeclaredFields(Class.java:2583) at java.lang.Class.getDeclaredFields(Class.java:1916) --- Caused by: java.lang.ClassNotFoundException: org.jenkinsci.main.modules.instance_identity.InstanceIdentity at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) {code}
[JIRA] (JENKINS-44200) Failed to scout hudson.plugins.cobertura.MavenCoberturaPublisher
Title: Message Title
Florian Kammermann edited a comment on JENKINS-44200
Re: Failed to scout hudson.plugins.cobertura.MavenCoberturaPublisher
Same error here, with different behaviour: * jenkins gui was not accessible anymore * the log showed, that the error was printing in a loop * additionally I had a Guice container error * after restart the loop was gone * the error was shown on startupthe logs \ {code}Apr 12, 2018 6:26:45 AM hudson.ExtensionFinder$GuiceFinder$SezpozModule configureWARNING: Failed to load hudson.plugins.cobertura.MavenCoberturaPublisherjava.lang.InstantiationException: java.lang.NoClassDefFoundError: hudson/maven/MavenReporter at net.java.sezpoz.IndexItem.element(IndexItem.java:146)Caused by: java.lang.NoClassDefFoundError: hudson/maven/MavenReporter at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:763)Caused by: java.lang.ClassNotFoundException: hudson.maven.MavenReporter at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1374) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1327) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1080)-Apr 12, 2018 6:26:45 AM hudson.ExtensionFinder$GuiceFinder SEVERE: Failed to create Guice container from all the pluginscom.google.common.util.concurrent.ExecutionError: com.google.common.util.concurrent.ExecutionError: java.lang.NoClassDefFoundError: Lorg/jenkinsci/main/modules/instance_identity/InstanceIdentity; at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2232) at com.google.common.cache.LocalCache.get(LocalCache.java:3965) at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3969)--Caused by: com.google.common.util.concurrent.ExecutionError: java.lang.NoClassDefFoundError: Lorg/jenkinsci/main/modules/instance_identity/InstanceIdentity; at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2232) at com.google.common.cache.LocalCache.get(LocalCache.java:3965) at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3969)---Caused by: java.lang.NoClassDefFoundError: Lorg/jenkinsci/main/modules/instance_identity/InstanceIdentity; at java.lang.Class.getDeclaredFields0(Native Method) at java.lang.Class.privateGetDeclaredFields(Class.java:2583) at java.lang.Class.getDeclaredFields(Class.java:1916)---Caused by: java.lang.ClassNotFoundException: org.jenkinsci.main.modules.instance_identity.InstanceIdentity at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) \ {code}
Add Comment
[JIRA] (JENKINS-48379) Input/parameters for Stages
Title: Message Title Torsten Kleiber commented on JENKINS-48379 Re: Input/parameters for Stages Don't understand - what do you mean by this? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42079) Allow "local" Shared Library to be loaded from current repo branch
Title: Message Title Jon Sten commented on JENKINS-42079 Re: Allow "local" Shared Library to be loaded from current repo branch Mike Kobit It sure looks like that, that is great news! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50755) multibranch pipeline creates outdated refs when set to run Pull Requests
Title: Message Title
Shiqi Yang updated an issue
Jenkins / JENKINS-50755
multibranch pipeline creates outdated refs when set to run Pull Requests
Change By:
Shiqi Yang
we have a multibranch pipeline job set to build on github Pull Requests with per-merge (Discover pull requests from origin) and (Merging the pull request with the current target branch revision)we have advanced clone behaviors 'Fetch tags' checked'clean after checkout' 'Prune stale remote-tracking branches' and 'wipe out repository & force clone' are all enabledin the job we are also running some reporting and we want to know the head of pull request (before jenkins merge target branch to it) and the way we are doing that is to run a script that runs {code:none}git show -s {BRANCH_NAME}{code}to get the original commit sha. I found that during the run jenkins will create a local ref named `remote/origin/PR-XXX` and jenkins will use that as the rev for running the job. and I believe that is done by command like this:{code:none} ` git fetch --tags --progress GIT_REPO_URL +refs/pull/XXX/head:refs/remotes/origin/PR-XXX +refs/heads/master:refs/remotes/origin/master --prune ` {code} and in this case the $BRANCH_NAME set by jenkins multibranch pipeline will be `PR-XXX` it createsso this worked for me at the beginningbut the problem I am having is that sometimes my git show command doesn't return the head of the pull request but rather an old commit of the same pull request, and I was able to login to one of our builders and investigate, it turns out that `git fetch` command above did not actually create the ref `remotes/origin/PR-XXX` correctly. what's puzzled me even more is that jenkins plugin was able to show the latest commit in its loge.g. the merge right after the git fetch command will show the correct commit shaMerging remotes/origin/master commit into PR head commit the is the right sha that I want. so on the builder you see the following state:at the workspace directory `git show` will show you all the commits correctly (after merge)`git show origin/PR-XXX` will show the old outdated pull request headI ruled out couple of things by poking around:1. the workspace gets completely wiped out before each run, so it won't be that the ref was there from previous runs, and even if was, the fetch command within the current run should have it updated to latest, besides, some of those runs happened on new builders that never run that PR before.2. this should not be github server update delay because sometimes we can repro this again in rerun of the job which happens hours after the head of the PR was updated.and I wasn't able to get a constant repro case on this, only thing I know is that if my PR run fell into that state, I'd have to push another dummy change to fix it, and sometimes I have to push more changes...
[JIRA] (JENKINS-50755) multibranch pipeline creates outdated refs when set to run Pull Requests
Title: Message Title
Shiqi Yang updated an issue
Jenkins / JENKINS-50755
multibranch pipeline creates outdated refs when set to run Pull Requests
Change By:
Shiqi Yang
we have a multibranch pipeline job set to build on github Pull Requests with per-merge (Discover pull requests from origin) and (Merging the pull request with the current target branch revision)we have advanced clone behaviors 'Fetch tags' checked'clean after checkout' 'Prune stale remote-tracking branches' and 'wipe out repository & force clone' are all enabledin the job we are also running some reporting and we want to know the head of pull request (before jenkins merge target branch to it) and the way we are doing that is to run a script that runs {code: shell none }git show -s {BRANCH_NAME}{code}to get the original commit sha. I found that during the run jenkins will create a local ref named `remote/origin/PR-XXX` and jenkins will use that as the rev for running the job. and I believe that is done by command like this: {code:none} `git fetch --tags --progress GIT_REPO_URL +refs/pull/XXX/head:refs/remotes/origin/PR-XXX +refs/heads/master:refs/remotes/origin/master --prune` {code} and in this case the $BRANCH_NAME set by jenkins multibranch pipeline will be `PR-XXX` it createsso this worked for me at the beginningbut the problem I am having is that sometimes my git show command doesn't return the head of the pull request but rather an old commit of the same pull request, and I was able to login to one of our builders and investigate, it turns out that `git fetch` command above did not actually create the ref `remotes/origin/PR-XXX` correctly. what's puzzled me even more is that jenkins plugin was able to show the latest commit in its loge.g. the merge right after the git fetch command will show the correct commit shaMerging remotes/origin/master commit into PR head commit the is the right sha that I want. so on the builder you see the following state:at the workspace directory `git show` will show you all the commits correctly (after merge)`git show origin/PR-XXX` will show the old outdated pull request headI ruled out couple of things by poking around:1. the workspace gets completely wiped out before each run, so it won't be that the ref was there from previous runs, and even if was, the fetch command within the current run should have it updated to latest, besides, some of those runs happened on new builders that never run that PR before.2. this should not be github server update delay because sometimes we can repro this again in rerun of the job which happens hours after the head of the PR was updated.and I wasn't able to get a constant repro case on this, only thing I know is that if my PR run fell into that state, I'd have to push another dummy change to fix it, and sometimes I have to push more changes...
[JIRA] (JENKINS-50755) multibranch pipeline creates outdated refs when set to run Pull Requests
Title: Message Title
Shiqi Yang updated an issue
Jenkins / JENKINS-50755
multibranch pipeline creates outdated refs when set to run Pull Requests
Change By:
Shiqi Yang
we have a multibranch pipeline job set to build on github Pull Requests with per-merge (Discover pull requests from origin) and (Merging the pull request with the current target branch revision)we have advanced clone behaviors 'Fetch tags' checked'clean after checkout' 'Prune stale remote-tracking branches' and 'wipe out repository & force clone' are all enabledin the job we are also running some reporting and we want to know the head of pull request (before jenkins merge target branch to it) and the way we are doing that is to run a script that runs { { code:shell} git show -s {BRANCH_NAME} {code } } to get the original commit sha. I found that during the run jenkins will create a local ref named `remote/origin/PR-XXX` and jenkins will use that as the rev for running the job. and I believe that is done by command like this:`git fetch --tags --progress GIT_REPO_URL +refs/pull/XXX/head:refs/remotes/origin/PR-XXX +refs/heads/master:refs/remotes/origin/master --prune` and in this case the $BRANCH_NAME set by jenkins multibranch pipeline will be `PR-XXX` it createsso this worked for me at the beginningbut the problem I am having is that sometimes my git show command doesn't return the head of the pull request but rather an old commit of the same pull request, and I was able to login to one of our builders and investigate, it turns out that `git fetch` command above did not actually create the ref `remotes/origin/PR-XXX` correctly. what's puzzled me even more is that jenkins plugin was able to show the latest commit in its loge.g. the merge right after the git fetch command will show the correct commit shaMerging remotes/origin/master commit into PR head commit the is the right sha that I want. so on the builder you see the following state:at the workspace directory `git show` will show you all the commits correctly (after merge)`git show origin/PR-XXX` will show the old outdated pull request headI ruled out couple of things by poking around:1. the workspace gets completely wiped out before each run, so it won't be that the ref was there from previous runs, and even if was, the fetch command within the current run should have it updated to latest, besides, some of those runs happened on new builders that never run that PR before.2. this should not be github server update delay because sometimes we can repro this again in rerun of the job which happens hours after the head of the PR was updated.and I wasn't able to get a constant repro case on this, only thing I know is that if my PR run fell into that state, I'd have to push another dummy change to fix it, and sometimes I have to push more changes...
[JIRA] (JENKINS-50755) multibranch pipeline creates outdated refs when set to run Pull Requests
Title: Message Title
Shiqi Yang updated an issue
Jenkins / JENKINS-50755
multibranch pipeline creates outdated refs when set to run Pull Requests
Change By:
Shiqi Yang
we have a multibranch pipeline job set to build on github Pull Requests with per-merge (Discover pull requests from origin) and (Merging the pull request with the current target branch revision)we have advanced clone behaviors 'Fetch tags' checked'clean after checkout' 'Prune stale remote-tracking branches' and 'wipe out repository & force clone' are all enabledin the job we are also running some reporting and we want to know the head of pull request (before jenkins merge target branch to it) and the way we are doing that is to run a script that runs {{git show -s {BRANCH_NAME}}} to get the original commit sha. I found that during the run jenkins will create a local ref named `remote/origin/PR-XXX` and jenkins will use that as the rev for running the job. and I believe that is done by command like this:`git fetch --tags --progress GIT_REPO_URL +refs/pull/XXX/head:refs/remotes/origin/PR-XXX +refs/heads/master:refs/remotes/origin/master --prune` and in this case the $BRANCH_NAME set by jenkins multibranch pipeline will be `PR-XXX` it createsso this worked for me at the beginningbut the problem I am having is that sometimes my git show command doesn't return the head of the pull request but rather an old commit of the same pull request, and I was able to login to one of our builders and investigate, it turns out that `git fetch` command above did not actually create the ref `remotes/origin/PR-XXX` correctly. what's puzzled me even more is that jenkins plugin was able to show the latest commit in its loge.g. the merge right after the git fetch command will show the correct commit shaMerging remotes/origin/master commit into PR head commit the is the right sha that I want. so on the builder you see the following state:at the workspace directory `git show` will show you all the commits correctly (after merge)`git show origin/PR-XXX` will show the old outdated pull request headI ruled out couple of things by poking around:1. the workspace gets completely wiped out before each run, so it won't be that the ref was there from previous runs, and even if was, the fetch command within the current run should have it updated to latest, besides, some of those runs happened on new builders that never run that PR before.2. this should not be github server update delay because sometimes we can repro this again in rerun of the job which happens hours after the head of the PR was updated.and I wasn't able to get a constant repro case on this, only thing I know is that if my PR run fell into that state, I'd have to push another dummy change to fix it, and sometimes I have to push more changes...
[JIRA] (JENKINS-50755) multibranch pipeline creates outdated refs when set to run Pull Requests
Title: Message Title
Shiqi Yang updated an issue
Jenkins / JENKINS-50755
multibranch pipeline creates outdated refs when set to run Pull Requests
Change By:
Shiqi Yang
we have a multibranch pipeline job set to build on github Pull Requests with per-merge (Discover pull requests from origin) and (Merging the pull request with the current target branch revision)we have advanced clone behaviors 'Fetch tags' checked'clean after checkout' 'Prune stale remote-tracking branches' and 'wipe out repository & force clone' are all enabledin the job we are also running some reporting and we want to know the head of pull request (before jenkins merge target branch to it) and the way we are doing that is to run a script that runs ` {{ git show -s {BRANCH_NAME} ` }} to get the original commit sha. I found that during the run jenkins will create a local ref named `remote/origin/PR-XXX` and jenkins will use that as the rev for running the job. and I believe that is done by command like this:`git fetch --tags --progress GIT_REPO_URL +refs/pull/XXX/head:refs/remotes/origin/PR-XXX +refs/heads/master:refs/remotes/origin/master --prune` and in this case the $BRANCH_NAME set by jenkins multibranch pipeline will be `PR-XXX` it createsso this worked for me at the beginningbut the problem I am having is that sometimes my git show command doesn't return the head of the pull request but rather an old commit of the same pull request, and I was able to login to one of our builders and investigate, it turns out that `git fetch` command above did not actually create the ref `remotes/origin/PR-XXX` correctly. what's puzzled me even more is that jenkins plugin was able to show the latest commit in its loge.g. the merge right after the git fetch command will show the correct commit shaMerging remotes/origin/master commit into PR head commit the is the right sha that I want. so on the builder you see the following state:at the workspace directory `git show` will show you all the commits correctly (after merge)`git show origin/PR-XXX` will show the old outdated pull request headI ruled out couple of things by poking around:1. the workspace gets completely wiped out before each run, so it won't be that the ref was there from previous runs, and even if was, the fetch command within the current run should have it updated to latest, besides, some of those runs happened on new builders that never run that PR before.2. this should not be github server update delay because sometimes we can repro this again in rerun of the job which happens hours after the head of the PR was updated.and I wasn't able to get a constant repro case on this, only thing I know is that if my PR run fell into that state, I'd have to push another dummy change to fix it, and sometimes I have to push more changes...
[JIRA] (JENKINS-33056) Please add clean remote option
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33056 Re: Please add clean remote option Code changed in jenkins User: Alex Earl Path: pom.xml src/main/java/jenkins/plugins/publish_over_ssh/BapSshClient.java src/main/resources/jenkins/plugins/publish_over_ssh/Messages.properties src/main/resources/jenkins/plugins/publish_over_ssh/options/SshOverrideTransferDefaults/config.jelly src/test/java/jenkins/plugins/publish_over_ssh/BapSshClientTest.java http://jenkins-ci.org/commit/publish-over-ssh-plugin/5b80db4f084cae85be0b7c510dafe89b18123d7b Log: Fix JENKINS-33056 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33056) Please add clean remote option
Title: Message Title Alex Earl started work on JENKINS-33056 Change By: Alex Earl Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33056) Please add clean remote option
Title: Message Title Alex Earl commented on JENKINS-33056 Re: Please add clean remote option Will add this soon, sorry for the long wait time! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50348) Why does "Pipeline: Groovy" require "Support Core"?
Title: Message Title Christian Höltje commented on JENKINS-50348 Re: Why does "Pipeline: Groovy" require "Support Core"? If it is optional, why can I not uncheck the box next to support-core to disable it? Maybe the bug is that "optional" items cannot be disabled in the plugin manager? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50755) multibranch pipeline creates outdated refs when set to run Pull Requests
Title: Message Title
Shiqi Yang created an issue
Jenkins / JENKINS-50755
multibranch pipeline creates outdated refs when set to run Pull Requests
Issue Type:
Bug
Assignee:
Unassigned
Components:
github-branch-source-plugin
Created:
2018-04-12 01:41
Environment:
jenkins 2.73.3 GitHub Branch Source 2.3.2 Git Plugin 3.7.0 Git Client Plugin 2.7.0
Priority:
Major
Reporter:
Shiqi Yang
we have a multibranch pipeline job set to build on github Pull Requests with per-merge (Discover pull requests from origin) and (Merging the pull request with the current target branch revision) we have advanced clone behaviors 'Fetch tags' checked 'clean after checkout' 'Prune stale remote-tracking branches' and 'wipe out repository & force clone' are all enabled in the job we are also running some reporting and we want to know the head of pull request (before jenkins merge target branch to it) and the way we are doing that is to run a script that runs `git show -s {BRANCH_NAME} ` to get the original commit sha. I found that during the run jenkins will create a local ref named `remote/origin/PR-XXX` and jenkins will use that as the rev for running the job. and I believe that is done by command like this: `git fetch --tags --progress GIT_REPO_URL +refs/pull/XXX/head:refs/remotes/origin/PR-XXX +refs/heads/master:refs/remotes/origin/master --prune` and in this case the $BRANCH_NAME set by jenkins multibranch pipeline will be `PR-XXX` it creates so this worked for me at the beginning but the problem I am having is that sometimes my git show command doesn't return the head of the pull request but rather an old commit of the same pull request, and I was able to login to one of our builders and investigate, it turns out that `git fetch` command above did not actually create the ref
[JIRA] (JENKINS-50663) Deadlock on jenkins startup
Title: Message Title Owen Mehegan commented on JENKINS-50663 Re: Deadlock on jenkins startup henryju please consider submitting a request to remove 2.7.0 from the update center, given that installing it can render Jenkins unable to start at all. See https://jenkins.io/doc/developer/publishing/removing-from-distribution/ Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49928) Add editor ATH coverage for changing agent settings in a Jenkinsfile
Title: Message Title Karl Shultz updated JENKINS-49928 Merged 1716. Jenkins / JENKINS-49928 Add editor ATH coverage for changing agent settings in a Jenkinsfile Change By: Karl Shultz Status: In Review Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49930) Add editor ATH coverage for setting and changing environment variables
Title: Message Title Karl Shultz updated JENKINS-49930 Merged 1716. Jenkins / JENKINS-49930 Add editor ATH coverage for setting and changing environment variables Change By: Karl Shultz Status: In Review Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50747) GitHub Organization Scan only evaluates the first 300 repositories
Title: Message Title Michael Ramirez updated an issue Jenkins / JENKINS-50747 GitHub Organization Scan only evaluates the first 300 repositories Change By: Michael Ramirez Our GitHub organization has over 300 repositories. In the scan log, I only see the first 300 repositories being evaluated resulting in jobs not being created for these repositories repos that come after the first 300 .*Expected Results*: Repositories beyond the first 300 should be evaluated and jobs should be created for them if they match the Repo/Branch/Jenkinsfile criteria*Workaround*: Reduce the number of repositories in the organization to 300 or lower Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50020) CpsFlowExecution unresponsive and Failed to serialize SimpleXStreamFlowNodeStorage
Title: Message Title Sam Van Oort commented on JENKINS-50020 Re: CpsFlowExecution unresponsive and Failed to serialize SimpleXStreamFlowNodeStorage I suspect the pipeline-internal issue is at least partially addressed in the latest workflow-cps and workflow-job releases, and issues with ErrorAction are handled in the latest workflow-api releases. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50670) Pipeline job does not fail when serialization of Pipeline steps arguments fails within NonCPS
Title: Message Title Sam Van Oort commented on JENKINS-50670 Re: Pipeline job does not fail when serialization of Pipeline steps arguments fails within NonCPS Oleg Nenashev the actual argument data is being bulletproofed by JENKINS-50752 implementation now so it CANNOT cause failures elsewhere if it can't be persisted and is instead discarded. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50752) ArgumentsAction Can Fail Serialization Of FlowNodes and Build When Given Unserializable input
Title: Message Title Sam Van Oort commented on JENKINS-50752 Re: ArgumentsAction Can Fail Serialization Of FlowNodes and Build When Given Unserializable input API addition Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50752) ArgumentsAction Can Fail Serialization Of FlowNodes and Build When Given Unserializable input
Title: Message Title Sam Van Oort commented on JENKINS-50752 Re: ArgumentsAction Can Fail Serialization Of FlowNodes and Build When Given Unserializable input Implementation PR Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48379) Input/parameters for Stages
Title: Message Title Michael Neale commented on JENKINS-48379 Re: Input/parameters for Stages nice - Torsten Kleiber should add this to docs! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50752) ArgumentsAction Can Fail Serialization Of FlowNodes and Build When Given Unserializable input
Title: Message Title Sam Van Oort updated JENKINS-50752 Jenkins / JENKINS-50752 ArgumentsAction Can Fail Serialization Of FlowNodes and Build When Given Unserializable input Change By: Sam Van Oort Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50752) ArgumentsAction Should Deal With Unserializable Arguments
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-50752 ArgumentsAction Should Deal With Unserializable Arguments Change By: Sam Van Oort Issue Type: Improvement Bug Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50752) ArgumentsAction Can Fail Serialization Of FlowNodes and Build When Given Unserializable input
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-50752 ArgumentsAction Can Fail Serialization Of FlowNodes and Build When Given Unserializable input Change By: Sam Van Oort Summary: ArgumentsAction Should Deal With Can Fail Serialization Of FlowNodes and Build When Given Unserializable Arguments input Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50706) Non Administrator cannot configure credentials in the Slack Notifier step.
Title: Message Title Allan BURDAJEWICZ updated JENKINS-50706 Jenkins / JENKINS-50706 Non Administrator cannot configure credentials in the Slack Notifier step. Change By: Allan BURDAJEWICZ Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36227) Logstash plugin Global configure error
Title: Message Title Markus Winter resolved as Fixed with v2.0.0 you specify the complete URL for elasticsearch. Jenkins / JENKINS-36227 Logstash plugin Global configure error Change By: Markus Winter Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-50706) Non Administrator cannot configure credentials in the Slack Notifier step.
Title: Message Title Allan BURDAJEWICZ started work on JENKINS-50706 Change By: Allan BURDAJEWICZ Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50706) Non Administrator cannot configure credentials in the Slack Notifier step.
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-50706 Re: Non Administrator cannot configure credentials in the Slack Notifier step. This has a big impact. When a user that is not an administrator save the job configuration, the job loses the credentials configuration falling back to none. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50562) logstash-plugin does not work with elasticsearch 6
Title: Message Title Markus Winter resolved as Not A Defect added a hint in the wiki, that you need to specify index and type Jenkins / JENKINS-50562 logstash-plugin does not work with elasticsearch 6 Change By: Markus Winter Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-28546) logstash doesn't connect to a server and puts no messages out
Title: Message Title Markus Winter resolved as Not A Defect added a hint in the wiki, that you need to specify index and type Jenkins / JENKINS-28546 logstash doesn't connect to a server and puts no messages out Change By: Markus Winter Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more
[JIRA] (JENKINS-33635) Enable globally
Title: Message Title Markus Winter resolved as Fixed v2.0.0 allows to enable it globally for non pipeline jobs Jenkins / JENKINS-33635 Enable globally Change By: Markus Winter Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36318) No Configuration UI
Title: Message Title Markus Winter resolved as Not A Defect With v2.0.0 configuration has been moved to the Configure Jenkins page Jenkins / JENKINS-36318 No Configuration UI Change By: Markus Winter Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-46293) Logstash export to elasticsearch breaks lines on brackes '{'
Title: Message Title
Markus Winter resolved as Not A Defect
updated the wiki that this could happen
Jenkins / JENKINS-46293
Logstash export to elasticsearch breaks lines on brackes '{'
Change By:
Markus Winter
Status:
Open Resolved
Resolution:
Not A Defect
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
[JIRA] (JENKINS-49960) JobProperty instead of BuildWrapper
Title: Message Title Markus Winter resolved as Fixed fixed with v2.0.0 Jenkins / JENKINS-49960 JobProperty instead of BuildWrapper Change By: Markus Winter Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47817) Exception on save job configuration with selecting "send console log to Logstash" option under Build Environments options.
Title: Message Title Markus Winter resolved as Fixed Fixed with v2.0.0 Jenkins / JENKINS-47817 Exception on save job configuration with selecting "send console log to Logstash" option under Build Environments options. Change By: Markus Winter Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more
[JIRA] (JENKINS-39937) logstash-plugin 1.2.0 causes NPE java.lang.NoClassDefFoundError: com/michelin/cio/hudson/plugins/maskpasswords/MaskPasswordsOutputStream
Title: Message Title Markus Winter resolved as Fixed fixed with v2.0.0 Jenkins / JENKINS-39937 logstash-plugin 1.2.0 causes NPE java.lang.NoClassDefFoundError: com/michelin/cio/hudson/plugins/maskpasswords/MaskPasswordsOutputStream Change By: Markus Winter Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-45327) Jenkins resume throwed NPE for org.jenkinsci.plugins.workflow.cps.EnvActionImpl getProperty
Title: Message Title Danrisha Young reopened an issue Jenkins / JENKINS-45327 Jenkins resume throwed NPE for org.jenkinsci.plugins.workflow.cps.EnvActionImpl getProperty Change By: Danrisha Young Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50748) Caught exception evaluating in configureSecurity - NullPointerException
Title: Message Title
Emil Wypych edited a comment on JENKINS-50748
Re: Caught exception evaluating in configureSecurity - NullPointerException
Seems that problem was really introduced with the latest security fix:[https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/lib/form/validateButton.jelly#L51]Commit [07d18cfd|https://github.com/jenkinsci/jenkins/commit/07d18cfd6d336a2b7cc0a78e120d9739a5d4e1d1] In the same file (valdidateButton.jelly) I see that atribute 'with' is not required: {code:java}','-separated list of fields that are sent to the server.{code}but there is an invocation of [THIS|https://github.com/jenkinsci/jenkins/blob/jenkins-2.116/core/src/main/java/hudson/Functions.java#L1381] function with the probably null argument.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45327) Jenkins resume throwed NPE for org.jenkinsci.plugins.workflow.cps.EnvActionImpl getProperty
Title: Message Title Danrisha Young commented on JENKINS-45327 Re: Jenkins resume throwed NPE for org.jenkinsci.plugins.workflow.cps.EnvActionImpl getProperty We are facing a similar issue. What is the fix for this? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50748) Caught exception evaluating in configureSecurity - NullPointerException
Title: Message Title Emil Wypych commented on JENKINS-50748 Re: Caught exception evaluating in configureSecurity - NullPointerException Seems that problem was really introduced with the latest security fix: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/lib/form/validateButton.jelly#L51 Commit 07d18cfd Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50074) Mockito Test for ByIdResultSelector
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50074 Re: Mockito Test for ByIdResultSelector Code changed in jenkins User: Deniz Mardin Path: src/test/java/io/jenkins/plugins/analysis/core/model/ByIdResultSelectorTest.java http://jenkins-ci.org/commit/analysis-core-plugin/d88096c5fc5cca2a0e5a246a00e5eb2a9a3cc6b0 Log: Add JUnit test for ByIdResultSelectorTest for task JENKINS-50074. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50074) Mockito Test for ByIdResultSelector
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50074 Re: Mockito Test for ByIdResultSelector Code changed in jenkins User: Alexander Praegla Path: clean.sh go.sh jenkins.sh skip.sh src/main/java/io/jenkins/plugins/analysis/core/model/AnalysisResult.java src/main/java/io/jenkins/plugins/analysis/core/quality/HealthReportBuilder.java src/main/java/io/jenkins/plugins/analysis/core/views/ResultAction.java src/test/java/io/jenkins/plugins/analysis/core/model/ByIdResultSelectorTest.java src/test/java/io/jenkins/plugins/analysis/core/steps/IssuesRecorderTest.java http://jenkins-ci.org/commit/analysis-core-plugin/2267c099113a76e625a9429df6a02afd3cbd1531 Log: Merge pull request #3 from AlexanderPraegla/JENKINS-50074 JENKINS-50074 Mockito Test for ByIdResultSelector Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50074) Mockito Test for ByIdResultSelector
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50074 Re: Mockito Test for ByIdResultSelector Code changed in jenkins User: Ullrich Hafner Path: src/test/java/io/jenkins/plugins/analysis/core/model/ByIdResultSelectorTest.java http://jenkins-ci.org/commit/analysis-core-plugin/52a55ed811803aa748c92512550de9c03058797e Log: Merge pull request #96 from AlexanderPraegla/hm-edu-testing JENKINS-50074 Added Mockito Test for ByIdResultSelector Compare: https://github.com/jenkinsci/analysis-core-plugin/compare/6d9a427e4bb3...52a55ed81180 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50074) Mockito Test for ByIdResultSelector
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50074 Re: Mockito Test for ByIdResultSelector Code changed in jenkins User: AlexanderPraegla Path: clean.sh go.sh jenkins.sh skip.sh src/main/java/io/jenkins/plugins/analysis/core/model/AnalysisResult.java src/main/java/io/jenkins/plugins/analysis/core/quality/HealthReportBuilder.java src/main/java/io/jenkins/plugins/analysis/core/views/ResultAction.java src/test/java/io/jenkins/plugins/analysis/core/steps/IssuesRecorderTest.java http://jenkins-ci.org/commit/analysis-core-plugin/7cde8e0f5fb4e262c12c68ca842e87123e9c6786 Log: Merge branch 'hm-edu-testing' of https://github.com/jenkinsci/analysis-core-plugin into JENKINS-50074 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50074) Mockito Test for ByIdResultSelector
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50074 Re: Mockito Test for ByIdResultSelector Code changed in jenkins User: Alexander Praegla Path: src/test/java/io/jenkins/plugins/analysis/core/model/ByIdResultSelectorTest.java http://jenkins-ci.org/commit/analysis-core-plugin/e424421420e14c3ac766a50c07386bfdbe76f350 Log: Merge pull request #2 from AlexanderPraegla/JENKINS-50074 JENKINS-50074 Mockito Test for ByIdResultSelector - Created unit test Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50074) Mockito Test for ByIdResultSelector
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50074 Re: Mockito Test for ByIdResultSelector Code changed in jenkins User: AlexanderPraegla Path: src/test/java/io/jenkins/plugins/analysis/core/model/ByIdResultSelectorTest.java http://jenkins-ci.org/commit/analysis-core-plugin/ce0e81d31e97ce793d4df0b52e9465e91a6d205f Log: JENKINS-50074 Mockito Test for ByIdResultSelector - Added javadoc + two additional test cases Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50074) Mockito Test for ByIdResultSelector
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50074 Re: Mockito Test for ByIdResultSelector Code changed in jenkins User: AlexanderPraegla Path: src/test/java/io/jenkins/plugins/analysis/core/model/ByIdResultSelectorTest.java http://jenkins-ci.org/commit/analysis-core-plugin/ff720fc2f90cc9f70605e1eeb21b0be429cb647f Log: JENKINS-50074 Mockito Test for ByIdResultSelector - Created unit test Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50652) Aborting a sh or bat step fires both aborted and failure post conditions
Title: Message Title Andrew Bayer updated JENKINS-50652 Jenkins / JENKINS-50652 Aborting a sh or bat step fires both aborted and failure post conditions Change By: Andrew Bayer Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50652) Aborting a sh or bat step fires both aborted and failure post conditions
Title: Message Title Andrew Bayer commented on JENKINS-50652 Re: Aborting a sh or bat step fires both aborted and failure post conditions And I have a fix (I believe) - https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/262. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50750) Attemp to (de-)serialize anonymous class javaposse.jobdsl.plugin.LookupStrategy$2
Title: Message Title
Emil Wypych updated an issue
Jenkins / JENKINS-50750
Attemp to (de-)serialize anonymous class javaposse.jobdsl.plugin.LookupStrategy$2
Change By:
Emil Wypych
Environment:
Jenkins 2. 106 116 Job DSL Plugin 1.68
After upgrade Jenkins to 2. 106 116 I see in the logs the following error:{noformat}Apr 11, 2018 9:06:15 PM WARNING org.jenkinsci.remoting.util.AnonymousClassWarnings warnAttempt to (de-)serialize anonymous class javaposse.jobdsl.plugin.LookupStrategy$2 in file:/var/lib/jenkins/plugins/job-dsl/WEB-INF/lib/classes.jar; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/{noformat}It is not related to the plugin version - I tried to downgrade to 1.67 - problem still exists in this version. Before Jenkins upgrade (it was a direct upgrade from 2. 104 114 to 2. 106 116 ) I hadn't had such errors.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50748) Caught exception evaluating in configureSecurity - NullPointerException
Title: Message Title
Emil Wypych updated an issue
Jenkins / JENKINS-50748
Caught exception evaluating in configureSecurity - NullPointerException
Change By:
Emil Wypych
Environment:
Jenkins 2. 106 116
After upgrading to the latest version (but it might be 2. 105 115 - the upgrade was made from 2. 104 114 to 2. 106 116 directly) I have the following errors when I try to get to the Configure Security section:{noformat}Apr 11, 2018 8:38:43 PM WARNING hudson.ExpressionFactory2$JexlExpression evaluateCaught exception evaluating: h.jsStringEscape(with) in /configureSecurity/. Reason: java.lang.NullPointerExceptionjava.lang.NullPointerException at hudson.Functions.jsStringEscape(Functions.java:1383) at sun.reflect.GeneratedMethodAccessor198.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateAsString(ExpressionSupport.java:46) at org.apache.commons.jelly._expression_.CompositeExpression.evaluateAsString(CompositeExpression.java:256) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.buildAttributes(ReallyStaticTagLibrary.java:111) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at
[JIRA] (JENKINS-50652) Aborting a sh or bat step fires both aborted and failure post conditions
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-50652 Aborting a sh or bat step fires both aborted and failure post conditions Change By: Andrew Bayer Summary: Post stages are incorrectly handled Aborting a sh or bat step fires both aborted and failure post conditions Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50652) Post stages are incorrectly handled
Title: Message Title Andrew Bayer started work on JENKINS-50652 Change By: Andrew Bayer Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50652) Post stages are incorrectly handled
Title: Message Title Andrew Bayer commented on JENKINS-50652 Re: Post stages are incorrectly handled Ok, reproduced it - the sh 'sleep 15' is the reason none of the existing tests caught this. It seems to only be sh or bat getting aborted that results in both failure and aborted firing. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50697) Evaluate impact on Eclipse workflows
Title: Message Title Jesse Glick resolved as Done Jenkins / JENKINS-50697 Evaluate impact on Eclipse workflows Change By: Jesse Glick Status: In Progress Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50697) Evaluate impact on Eclipse workflows
Title: Message Title
Jesse Glick updated an issue
Jenkins / JENKINS-50697
Evaluate impact on Eclipse workflows
Change By:
Jesse Glick
Started off like JENKINS-50696, and…{code:none}SCM provider is not available for scm:null:https://github.com/jglick/mrp-test{code}Um, what? OK, importing existing Maven projects from disk seems to work better. Went to try to configure Maven 3.5.3, and then the IDE froze up and had to be killed and restarted.Anyway, finally got the downstream project opened also, and {{TwoTest}} to run both against a MRP release and against a snapshot and against an Incrementals release and so on.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50743) ToolLocationNodeProperty
Title: Message Title Oleg Nenashev commented on JENKINS-50743 Re: ToolLocationNodeProperty From what I see you create a new property class in your Groovy script and then add it to Jenkins. If yes, it's not a defect IMHO. Groovy objects should not be serialized to the disk, and there is no reliable way to whitelist them. If you provide your System Groovy script, we could suggest how to solve that. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50733) SEVERE: Failed to save build record (job-dsl JEP-200)
Title: Message Title Oleg Nenashev commented on JENKINS-50733 Re: SEVERE: Failed to save build record (job-dsl JEP-200) Yes, it's likely a duplicate of JENKINS-49175 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50754) "ERROR: Could not find credentials matching (rolename)" when using AWS role
Title: Message Title
Jon B created an issue
Jenkins / JENKINS-50754
"ERROR: Could not find credentials matching (rolename)" when using AWS role
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
docker-commons-plugin
Created:
2018-04-11 21:22
Priority:
Major
Reporter:
Jon B
My pipeline looks like this:
pipeline {
agent {
docker {
image '.dkr.ecr.us-west-2.amazonaws.com//cicd-debian-worker:v0.0.2'
label ''
registryUrl 'https://.dkr.ecr.us-west-2.amazonaws.com/'
registryCredentialsId 'JENKINS_SLAVE_AWS_ROLE'
}
}
...
I have also set an AWS credential for which I set the ARN to the role ARN I'm interested in into the global namespace in the credentials store. When I run my pipeline, it fails with:
ERROR: Could not find credentials matching JENKINS_SLAVE_AWS_ROLE
I'm 100% sure the credential exists with that name.
[JIRA] (JENKINS-34034) Publish Over SSH plugin doesn't work with Windows node
Title: Message Title Alex Earl closed an issue as Cannot Reproduce Jenkins / JENKINS-34034 Publish Over SSH plugin doesn't work with Windows node Change By: Alex Earl Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50652) Post stages are incorrectly handled
Title: Message Title
Steve Todorov updated an issue
Jenkins / JENKINS-50652
Post stages are incorrectly handled
Change By:
Steve Todorov
Consider the following example:{code:java}pipeline { agent { label 'linux' } stages {stage('Successful stage') { steps {script { sh "sleep 15" // intentionally not using sleep 15 step!} }} } post {success { echo "Triggered post-success"}failure { echo "Triggered post-failure"}unstable { echo "Triggered post-unstable"}aborted { echo "Triggered post-aborted"} }}{code}Start the build, let it go into "sleep" and abort the build. The result will be:{code:java}[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] echoTriggered post-aborted[Pipeline] echoTriggered post-failure[Pipeline] }{code} The result is having both `post-aborted` and `post-failure` executed. What should have happened was to receive only `post-aborted` step. I've also seen in the logs `post-unstable` and `post-failure`, but I am not sure how to provide a way to reproduce this. I'm not sure how that happened but I have seen it a few times on some of our builds.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50578) Add support to specify checks on ArachniScanner
Title: Message Title Ingo Rissmann resolved as Fixed Checks are supported with release 0.9.4 Jenkins / JENKINS-50578 Add support to specify checks on ArachniScanner Change By: Ingo Rissmann Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34034) Publish Over SSH plugin doesn't work with Windows node
Title: Message Title Alex Domoradov commented on JENKINS-34034 Re: Publish Over SSH plugin doesn't work with Windows node Unfortunately it was a long long time ago. I don't remember and haven't worked with windows any more Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50752) ArgumentsAction Should Deal With Unserializable Arguments
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-50752 ArgumentsAction Should Deal With Unserializable Arguments Change By: Sam Van Oort Although it *shouldn't* happen, but occasionally you see issues with unserializable content being inserted into the arguments which ends up breaking serialization. This can fail the whole persistence of the flow graph , causing loss of data . Instead we should intercept and filter out unserializable inputs when the action is created. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50748) Caught exception evaluating in configureSecurity - NullPointerException
Title: Message Title Ramon Torres commented on JENKINS-50748 Re: Caught exception evaluating in configureSecurity - NullPointerException This same error is also reproducible on a clean docker container: jenkins/jenkins:lts-alpine (2.107.2). Global Password section is missing from Global Configuration. Jobs that use global passwords as environment variables stopped working - environment variables regarding global password don't get passed to the agent. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44789) docker 17.05 multistage Dockerfile breaks dockerFingerprintFrom
Title: Message Title Andrew Hammond commented on JENKINS-44789 Re: docker 17.05 multistage Dockerfile breaks dockerFingerprintFrom +1 with the following FROM line: FROM quay.io/prometheus/golang-builder:1.9-base Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44789) docker 17.05 multistage Dockerfile breaks dockerFingerprintFrom
Title: Message Title Andrew Hammond commented on JENKINS-44789 Re: docker 17.05 multistage Dockerfile breaks dockerFingerprintFrom At the very least can we please disable this functionality since it doesn't provide value and appears to create issues. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50695) Evaluate impact on IDEA workflows
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-50695 Evaluate impact on IDEA workflows Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50697) Evaluate impact on Eclipse workflows
Title: Message Title Jesse Glick started work on JENKINS-50697 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50695) Evaluate impact on IDEA workflows
Title: Message Title Jesse Glick stopped work on JENKINS-50695 Change By: Jesse Glick Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50695) Evaluate impact on IDEA workflows
Title: Message Title
Jesse Glick updated an issue
Jenkins / JENKINS-50695
Evaluate impact on IDEA workflows
Change By:
Jesse Glick
Using 2018.1.1 on a similar setup to JENKINS-50696 and Maven 3.5.3. Seemed to *Import project from external model* OK, though I had to suppress a notification that {{.flattened-pom.xml}} was unmanaged. Tried to add the downstream repo though I think I did something wrong because it did not seem to process any deps, and tried to import two copies of it. Also in all cases the IDE got confused when importing anything that had a {{target}} directory. Basically I could not get much of anything to work, but this is probably out of bafflement at how IDEA is supposed to be used.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For
[JIRA] (JENKINS-50308) EC2 Plugin - Windows sshd support - use ssh + pubkey option instead of winrm
Title: Message Title Alexander A commented on JENKINS-50308 Re: EC2 Plugin - Windows sshd support - use ssh + pubkey option instead of winrm https://github.com/jenkinsci/ec2-plugin/pull/276 fixes sshd for cygwin. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50753) Always said that sdk license is not accept,but I do all accept the licenses
Title: Message Title cnr ting updated an issue Jenkins / JENKINS-50753 Always said that sdk license is not accept,but I do all accept the licenses Change By: cnr ting 1.try install versions of build tools:[root@dns shadowsocks-android]# sdkmanager --listInstalled packages:=] 100% Computing updates... Path | Version | Description | Location --- | --- | --- | --- build-tools;26.0.2 | 26.0.2 | Android SDK Build-Tools 26.0.2 | build-tools/26.0.2/ build-tools;26.0.3 | 26.0.3 | Android SDK Build-Tools 26.0.3 | build-tools/26.0.3/ build-tools;27.0.3 | 27.0.3 | Android SDK Build-Tools 27.0.3 | build-tools/27.0.3/ emulator | 27.1.12 | Android Emulator | emulator/ ndk-bundle | 16.1.4479499 | NDK | ndk-bundle/ patcher;v4 | 1 | SDK Patch Applier v4 | patcher/v4/ platform-tools | 27.0.1 | Android SDK Platform-Tools | platform-tools/ platforms;android-26 | 2 | Android SDK Platform 26 | platforms/android-26/ platforms;android-27 | 1 | Android SDK Platform 27 | platforms/android-27/ tools | 26.1.1 | Android SDK Tools | tools/ 2.sdkmanager shows all licenses are accepted:[root@dns shadowsocks-android]# sdkmanager --licensesAll SDK package licenses accepted.==] 100% Computing updates... start build with jenkins log:[shadowsocks-android] $ /var/lib/jenkins/tools/hudson.plugins.gradle.GradleInstallation/gradle-4.6/bin/gradleStarting a Gradle Daemon (subsequent builds will be faster)Checking the license for package Android SDK Build-Tools 27.0.3 in /var/android-sdk/licensesWarning: License for package Android SDK Build-Tools 27.0.3 not accepted.Checking the license for package Android SDK Platform 27 in /var/android-sdk/licensesWarning: License for package Android SDK Platform 27 not accepted.FAILURE: Build failed with an exception. * What went wrong:A problem occurred configuring project ':core'.> Failed to install the following Android SDK packages as some licences have not been accepted. platforms;android-27 Android SDK Platform 27 build-tools;27.0.3 Android SDK Build-Tools 27.0.3 To build this project, accept the SDK license agreements and install the missing components using the Android Studio SDK Manager. Alternatively, to transfer the license agreements from one workstation to another, see [http://d.android.com/r/studio-ui/export-licenses.html]Using Android SDK: /var/android-sdk* Try:Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights. just don't know what and where goes wrong ,using ./gradlew build command can successfully build.but fail in jeknins
[JIRA] (JENKINS-50753) Always said that sdk license is not accept,but I do all accept the licenses
Title: Message Title cnr ting created an issue Jenkins / JENKINS-50753 Always said that sdk license is not accept,but I do all accept the licenses Issue Type: Bug Assignee: Stefan Wolf Components: gradle-plugin Created: 2018-04-11 20:02 Environment: CentOS 7 4.15.11-1.el7.elrepo.x86_64 Labels: jenkins Priority: Blocker Reporter: cnr ting 1.try install versions of build tools: [root@dns shadowsocks-android]# sdkmanager --list Installed packages:=] 100% Computing updates... Path | Version | Description | Location --- | --- | --- | --- build-tools;26.0.2 | 26.0.2 | Android SDK Build-Tools 26.0.2 | build-tools/26.0.2/ build-tools;26.0.3 | 26.0.3 | Android SDK Build-Tools 26.0.3 | build-tools/26.0.3/ build-tools;27.0.3 | 27.0.3 | Android SDK Build-Tools 27.0.3 | build-tools/27.0.3/ emulator | 27.1.12 | Android Emulator | emulator/ ndk-bundle | 16.1.4479499 | NDK | ndk-bundle/ patcher;v4 | 1 | SDK Patch Applier v4 | patcher/v4/ platform-tools | 27.0.1 | Android SDK Platform-Tools | platform-tools/ platforms;android-26 | 2 | Android SDK Platform 26 | platforms/android-26/ platforms;android-27 | 1 | Android SDK Platform 27 | platforms/android-27/ tools | 26.1.1 | Android SDK Tools | tools/ 2.sdkmanager shows all licenses are accepted: [root@dns shadowsocks-android]# sdkmanager --licenses All SDK package licenses accepted.==] 100% Computing updates... start build with jenkins log: [shadowsocks-android] $ /var/lib/jenkins/tools/hudson.plugins.gradle.GradleInstallation/gradle-4.6/bin/gradle Starting a Gradle Daemon
[JIRA] (JENKINS-50752) ArgumentsAction Should Deal With Unserializable Arguments
Title: Message Title Sam Van Oort started work on JENKINS-50752 Change By: Sam Van Oort Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50695) Evaluate impact on IDEA workflows
Title: Message Title Jesse Glick started work on JENKINS-50695 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50670) Pipeline job does not fail when serialization of Pipeline steps arguments fails within NonCPS
Title: Message Title Sam Van Oort commented on JENKINS-50670 Re: Pipeline job does not fail when serialization of Pipeline steps arguments fails within NonCPS I created JENKINS-50752 to track the fact that we're not successfully bulletproofing against unserializable Action contents. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50752) ArgumentsAction Should Deal With Unserializable Arguments
Title: Message Title Sam Van Oort commented on JENKINS-50752 Re: ArgumentsAction Should Deal With Unserializable Arguments Similar issue in a related domain Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50752) ArgumentsAction Should Deal With Unserializable Arguments
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-50752 ArgumentsAction Should Deal With Unserializable Arguments Change By: Sam Van Oort Although it *shouldn't* happen, but occasionally you see issues with unserializable content being inserted into the arguments which ends up breaking serialization. This can fail the whole persistence of the flow graph. Instead we should intercept and filter out unserializable inputs when the action is created. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50752) ArgumentsAction Should Deal With Unserializable Arguments
Title: Message Title Sam Van Oort created an issue Jenkins / JENKINS-50752 ArgumentsAction Should Deal With Unserializable Arguments Issue Type: Improvement Assignee: Sam Van Oort Components: workflow-api-plugin, workflow-cps-plugin Created: 2018-04-11 19:39 Labels: robustness serialization Priority: Major Reporter: Sam Van Oort Although it shouldn't happen, but occasionally you see issues with unserializable content being inserted into the arguments which ends up breaking serialization. Add Comment
[JIRA] (JENKINS-50751) Link created by naginator plugin contains comma in job numbers over 999
Title: Message Title Robert Baker created an issue Jenkins / JENKINS-50751 Link created by naginator plugin contains comma in job numbers over 999 Issue Type: Bug Assignee: Nicolas De Loof Components: naginator-plugin Created: 2018-04-11 19:37 Environment: Jenkins 2.89.4 Naginator 1.17.2 Priority: Minor Reporter: Robert Baker The Naginator plugin creates a link on the project's build page like the following: Started by Naginator after the failure of build 2018-04-11-143326 Where "2018-04-11-143326" is the name of a build that failed and is hyperlinked to the build output. The hyperlink is: https://my.jenkins.unisys.com/view/Stealth(aware)/job/NFoS-Sysgen-Branch/1,070/ As you can see, when the build number exceeds 999 a comma is injected into the URL, making it invalid. Add Comment
[JIRA] (JENKINS-50742) Bitbucket branches' config.xml contains url entries which incorrectly point to a PR builder in Bitbucket
Title: Message Title
Karl Shultz updated an issue
Jenkins / JENKINS-50742
Bitbucket branches' config.xml contains url entries which incorrectly point to a PR builder in Bitbucket
Change By:
Karl Shultz
*Summary*As a bitbucket-branch-source bug:For a multibranch project stored in a Bitbucket repo, the URLs in the {{ }} sections of {{ jobs/the-bitbucket-multibranch-job/branches/master/config.xml}} , the URL in the {{}} section points to the wrong link are incorrect . This wrong link incorrect URL takes the user to a PR builder page on their Bitbucket server, instead of just taking them to the page for that branch. As originally written up when I thought this was a Blue Ocean bug:Given a working Pipeline on Bitbucket Server, clicking on a successful run of any Discovered while running bitbucket- branch produces the details page as expected -source 2 . Clicking the button next to the Branch name in the top left corner of the page takes the user to a Bitbucket pull request builder page 2.9 , instead of simply going but it looks to Bitbucket with that branch preselected be present in master too .*Frequency*100%*Steps to recreate* : these are still a valid way of recreating the issue, just keep in mind this no longer looks like a Blue Ocean specific bug to me. 1. Connect to a Bitbucket repo with a functioning Jenkinsfile via Blue Ocean, and run that pipeline if you haven't already.2. Click a successful run of {{master}} (or any branch really, it doesn't matter which) to produce the details view, which looks like this: !image-2018-04-11-11-48-53-829.png|thumbnail! 3. Click the button next to the branch name, up near the top left corner of the page. The tooltip says "Opens branch in a new window:" !image-2018-04-11-11-50-07-421.png|thumbnail! 4. That new window will take you to what I call the pull request builder on your Bitbucket server. The URL that button is pointing to is {{https://bitbucket.beescloud.com/projects/FEB/repos/jenkins-49409/compare/commits?sourceBranch=refs%2Fheads%2Fmaster}}. It'll be pre-populated with settings to create a {{master}} to {{master}} PR, which doesn't make a lot of sense: !image-2018-04-11-11-55-50-314.png|thumbnail! 5. This issue only manifests with Bitbucket repos. With GitHub Enterprise, for example, you'll be taken to {{https://your.github.server/org-or-user/another-blank-repo/tree/master}}. A sample URL might be https://github.yourcompany.com/dev1/another-blank-repo/tree/master: !image-2018-04-11-11-59-29-142.png|thumbnail!
[JIRA] (JENKINS-50750) Attemp to (de-)serialize anonymous class javaposse.jobdsl.plugin.LookupStrategy$2
Title: Message Title Emil Wypych created an issue Jenkins / JENKINS-50750 Attemp to (de-)serialize anonymous class javaposse.jobdsl.plugin.LookupStrategy$2 Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2018-04-11 19:14 Environment: Jenkins 2.106 Job DSL Plugin 1.68 Priority: Minor Reporter: Emil Wypych After upgrade Jenkins to 2.106 I see in the logs the following error: Apr 11, 2018 9:06:15 PM WARNING org.jenkinsci.remoting.util.AnonymousClassWarnings warn Attempt to (de-)serialize anonymous class javaposse.jobdsl.plugin.LookupStrategy$2 in file:/var/lib/jenkins/plugins/job-dsl/WEB-INF/lib/classes.jar; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ It is not related to the plugin version - I tried to downgrade to 1.67 - problem still exists in this version. Before Jenkins upgrade (it was a direct upgrade from 2.104 to 2.106) I hadn't had such errors.
[JIRA] (JENKINS-50742) Bitbucket branches' config.xml contains url entries which incorrectly point to a PR builder in Bitbucket
Title: Message Title
Karl Shultz updated an issue
Jenkins / JENKINS-50742
Bitbucket branches' config.xml contains url entries which incorrectly point to a PR builder in Bitbucket
Change By:
Karl Shultz
*Summary*As a bitbucket-branch-source bug: For a multibranch project stored in a Bitbucket repo, {{jobs/the-bitbucket-multibranch-job/branches/master/config.xml}}, the URL in the {{}} section points to the wrong link. This wrong link takes the user to a PR builder page on their Bitbucket server, instead of just taking them to the page for that branch. As originally written up when I thought this was a Blue Ocean bug:Given a working Pipeline on Bitbucket Server, clicking on a successful run of any branch produces the details page as expected. Clicking the button next to the Branch name in the top left corner of the page takes the user to a Bitbucket pull request builder page, instead of simply going to Bitbucket with that branch preselected.*Frequency*100%*Steps to recreate*1. Connect to a Bitbucket repo with a functioning Jenkinsfile via Blue Ocean, and run that pipeline if you haven't already.2. Click a successful run of {{master}} (or any branch really, it doesn't matter which) to produce the details view, which looks like this: !image-2018-04-11-11-48-53-829.png|thumbnail! 3. Click the button next to the branch name, up near the top left corner of the page. The tooltip says "Opens branch in a new window:" !image-2018-04-11-11-50-07-421.png|thumbnail! 4. That new window will take you to what I call the pull request builder on your Bitbucket server. The URL that button is pointing to is {{https://bitbucket.beescloud.com/projects/FEB/repos/jenkins-49409/compare/commits?sourceBranch=refs%2Fheads%2Fmaster}}. It'll be pre-populated with settings to create a {{master}} to {{master}} PR, which doesn't make a lot of sense: !image-2018-04-11-11-55-50-314.png|thumbnail! 5. This issue only manifests with Bitbucket repos. With GitHub Enterprise, for example, you'll be taken to {{https://your.github.server/org-or-user/another-blank-repo/tree/master}}. A sample URL might be https://github.yourcompany.com/dev1/another-blank-repo/tree/master: !image-2018-04-11-11-59-29-142.png|thumbnail!
Add Comment
[JIRA] (JENKINS-50742) Bitbucket branches' config.xml contains url entries which incorrectly point to a PR builder in Bitbucket
Title: Message Title
Karl Shultz updated an issue
Jenkins / JENKINS-50742
Bitbucket branches' config.xml contains url entries which incorrectly point to a PR builder in Bitbucket
Change By:
Karl Shultz
*Summary* As a bitbucket-branch-source bug:As originally written up when I thought this was a Blue Ocean bug: Given a working Pipeline on Bitbucket Server, clicking on a successful run of any branch produces the details page as expected. Clicking the button next to the Branch name in the top left corner of the page takes the user to a Bitbucket pull request builder page, instead of simply going to Bitbucket with that branch preselected.*Frequency*100%*Steps to recreate*1. Connect to a Bitbucket repo with a functioning Jenkinsfile via Blue Ocean, and run that pipeline if you haven't already.2. Click a successful run of {{master}} (or any branch really, it doesn't matter which) to produce the details view, which looks like this: !image-2018-04-11-11-48-53-829.png|thumbnail! 3. Click the button next to the branch name, up near the top left corner of the page. The tooltip says "Opens branch in a new window:" !image-2018-04-11-11-50-07-421.png|thumbnail! 4. That new window will take you to what I call the pull request builder on your Bitbucket server. The URL that button is pointing to is {{https://bitbucket.beescloud.com/projects/FEB/repos/jenkins-49409/compare/commits?sourceBranch=refs%2Fheads%2Fmaster}}. It'll be pre-populated with settings to create a {{master}} to {{master}} PR, which doesn't make a lot of sense: !image-2018-04-11-11-55-50-314.png|thumbnail! 5. This issue only manifests with Bitbucket repos. With GitHub Enterprise, for example, you'll be taken to {{https://your.github.server/org-or-user/another-blank-repo/tree/master}}. A sample URL might be https://github.yourcompany.com/dev1/another-blank-repo/tree/master: !image-2018-04-11-11-59-29-142.png|thumbnail!
Add Comment
[JIRA] (JENKINS-50742) Bitbucket branches' config.xml contains url entries which incorrectly point to a PR builder in Bitbucket
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-50742 Bitbucket branches' config.xml contains url entries which incorrectly point to a PR builder in Bitbucket Change By: Karl Shultz Summary: Detail view for pipelines on Bitbucket : "Opens branch in a new window" branches' config.xml contains url entries which incorrectly goes point to BB pull request a PR builder in Bitbucket Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50749) SAMLException: No valid subject assertion found in response (Azure)
Title: Message Title Daniel Watrous created an issue Jenkins / JENKINS-50749 SAMLException: No valid subject assertion found in response (Azure) Issue Type: Bug Assignee: Ivan Fernandez Calvo Attachments: saml-logs.txt Components: saml-plugin Created: 2018-04-11 19:05 Environment: Docker image jenkins/jenkins:2.107.1 (similar behavior in previous tagged versions too) deployed on kuberntes. SAML Plugin 1.0.5 Labels: jenkins SAML SAMLException Priority: Minor Reporter: Daniel Watrous I have used the saml-plugin to integrate our login with Azure Active Directory. This works most of the time, but sometimes (a few times a month) I get redirected to /securityRealm/finishLogin and I see the stacktrace shown below. I have attached logs to this ticket for org.pac4j.saml I have followed this ticket, https://issues.jenkins-ci.org/browse/JENKINS-44992. My configuration includes the IdP metadata URL and a Refresh Period of 120. I have extended my Maximum Authentication Lifetime to 1209600, which seems to make this happen less often. Sometimes I can workaround this by
[JIRA] (JENKINS-50742) Detail view for pipelines on Bitbucket: "Opens branch in a new window" incorrectly goes to BB pull request builder
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-50742 Detail view for pipelines on Bitbucket: "Opens branch in a new window" incorrectly goes to BB pull request builder Change By: Karl Shultz Component/s: bitbucket-branch-source-plugin Component/s: blueocean-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50742) Detail view for pipelines on Bitbucket: "Opens branch in a new window" incorrectly goes to BB pull request builder
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-50742 Detail view for pipelines on Bitbucket: "Opens branch in a new window" incorrectly goes to BB pull request builder Change By: Karl Shultz Environment: Jenkins:Running release/1.5 via hpi:run, but this can be recreated otherwise. bitbucket-branch-source 2.2.9 SCM:Bitbucket server only. GitHub is not affected by this.Client:Fedora Workstation 27, Chrome 65.0.3325.181 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50327) Update to 2.10.4 causes NullPointerException in HTTPDigestAuthentication.createDigest
Title: Message Title Richard van der Klooster commented on JENKINS-50327 Re: Update to 2.10.4 causes NullPointerException in HTTPDigestAuthentication.createDigest I am having the same issue. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
