[JIRA] (JENKINS-52966) Two sequential stages in a parallel stage in a declarative pipeline making use of the same agent can cause a StackOverflowError
Title: Message Title Bastian Brodbeck commented on JENKINS-52966 Re: Two sequential stages in a parallel stage in a declarative pipeline making use of the same agent can cause a StackOverflowError I also have this problem with our declarative pipeline, but we do not use parallel steps. We run Jenkins Jenkins 2.176.1 but I had it with 2.150.1 as well. I think it happened from one day to another a few days back. Cannot remember having done any change to Jenkins or the pipeline that caused this to happen. I though updating Jenkins and all installed Plugins might fix the issue, but it did not. The things I noticed: it happens 9 out of 10 builds when it happens then consistent at the same step when chaining the pipeline to mediate the issue it happens at another step (and stays there) – i initially thought it might be related to credentials (withCredentials, withAWS) When i reduce the size of the pipeline it does not happen. But then of course we can not use the result. so far it only happened on my Windows machine, never during a mac build System Log: Unexpected exception in CPS VM thread: CpsFlowExecution java.lang.IllegalStateException: JENKINS-50407: no loaded shell in CpsFlowExecution Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-47617) CHANGE_BRANCH no longer reporting branch name, but instead PR
Title: Message Title Bastian Brodbeck commented on JENKINS-47617 Re: CHANGE_BRANCH no longer reporting branch name, but instead PR Any update on this one? I just ran in this issue. No idea how to solve it as I am new to Jenkins. 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-48897) Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline
Title: Message Title Bastian Brodbeck commented on JENKINS-48897 Re: Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline Hi, I have the same issue. While the initial setup with username/password through blue ocean works for detecting branches it does not work when actually running a build. I am not able to add proper credentials with ssh key as described above. And builds won't even start with username/password credentials on my private BitBucket Cloud repositories. using GIT_ASKPASS to set credentials > /usr/bin/git fetch --no-tags --progress https://bitbucket.org/me/my-fancy-fake-repo.git +refs/heads/master:refs/remotes/origin/master ERROR: Timeout after 10 minutes ERROR: Error fetching remote repo 'origin' if i set it up a generic git then i can add an ssh key and the build runs fine. But i won't be able to "discover Pull Requests from origin". 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.
