[JIRA] (JENKINS-60177) StackOverflowError After Pipeline Declarative Upgraded to 1.4.0

0 views
Skip to first unread message

charles.bozarth@dematic.com (JIRA)

unread,
Nov 14, 2019, 1:40:02 PM11/14/19
to jenkinsc...@googlegroups.com
Charles Bozarth created an issue
 
Jenkins / Bug JENKINS-60177
StackOverflowError After Pipeline Declarative Upgraded to 1.4.0
Issue Type: Bug Bug
Assignee: Andrew Bayer
Attachments: Console Output for StackOverflowError.txt, Example Pipeline for StackOverflowError.groovy
Components: pipeline-model-definition-plugin
Created: 2019-11-14 18:39
Environment: Windows Server 2016 10.0.14393 N/A Build 14393
Jenkins v2.190.2
Java runtime version 1.8.0_66-b18
Priority: Minor Minor
Reporter: Charles Bozarth

A multibranch pipeline began failing with a StackOverflowError after updating these plugins to 1.4.0. Rolling back to 1.3.9 resolved the issue.

  • Pipeline: Declarative
  • Pipeline: Declarative Extension Points API
  • Pipeline: Model API
  • Pipeline: Stage Tags Metadata

This particular pipeline uses a when statement to bypass a block of stages. These stages are configured as sequential stages, three stages within a parent stage where the when statement is. If the stages are not skipped then the error does not occur.

The pipeline is running on the master (Windows) system with no slaves defined.

Attached is a simplified pipeline and the console output. I've defined the BRANCH_NAME environment variable manually to simulate a Git branch.

For some reason, this was the simplest pipeline I could create. Taking out a seemingly unrelated stage or environment block would allow it to run without error.

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

bitwiseman@gmail.com (JIRA)

unread,
Dec 2, 2019, 2:47:03 PM12/2/19
to jenkinsc...@googlegroups.com
Liam Newman commented on Bug JENKINS-60177
 
Re: StackOverflowError After Pipeline Declarative Upgraded to 1.4.0

Hm, there's nothing in that stack trace that helps me understand what is going wrong there.
I'll take a look at it in the next release after 1.5.0.

charles.bozarth@dematic.com (JIRA)

unread,
Feb 17, 2020, 9:43:03 AM2/17/20
to jenkinsc...@googlegroups.com

I did some additional testing looking for more information. But nothing conclusive. Here's what I tried.

I looked for another system log. The logs I found only reported the same stack trace.

I installed a new, clean instance of Jenkins v2.204.2 on Windows 10 with the default plugins. This puts Pipeline: Declarative at v1.5.1. The error still occurs.

I haven't yet tried this pipeline on Linux.

Reply all
Reply to author
Forward
0 new messages