Or just install the now-released 1.1.6. Everything does have to build to
get fixed, but you can bypass that by running the script at
https://issues.jenkins-ci.org/browse/JENKINS-44809?focusedCommentId=302837=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-302837
in the
here is the list to downgrade
pipeline model definition
pipeline declarative extention point
pipeline model api
pipeline stage tags metadata
1.1.5 back to 1.1.4
On Sunday, June 11, 2017 at 9:46:31 PM UTC-7, Dan Tran wrote:
>
> looking forward for a fix. The issue comes back to our Jenkins
>
>
looking forward for a fix. The issue comes back to our Jenkins
@Andrew, you have a list of plugins we can use the downgrade back?
-Dan
On Sunday, June 11, 2017 at 7:12:05 AM UTC-7, Andrew Bayer wrote:
>
> So this ended up being an actual bug in Declarative. Sigh. Working on it.
>
> A.
>
> On
So this ended up being an actual bug in Declarative. Sigh. Working on it.
A.
On Sun, Jun 11, 2017 at 8:12 AM ST wrote:
> FYI: Downgrading didn't help, not sure what you mean by "dashboard or
> monitor". The only similar plugin names I've installed are
>
>-
FYI: Downgrading didn't help, not sure what you mean by "dashboard or
monitor". The only similar plugin names I've installed are
- "Dashboard for Blue Ocean" plugin 1.0.1
- "External Monitor Job Type Plugin" 1.7
And downgrading them to previous version didnt help.
I've created
Yes I upgraded some plugins and restarted jenkins a few hours before this
happened. But after that several builds of this job went fine, so I'm
thinking it must be something else that has triggered the SOE.
Changing the agent declaration in the pipeline script I did using the
"Replay" function,
I'm getting StackOverflowException when trying to open the folder of my
multibranch pipeline job, see below for first part of the stacktrace.
The pipeline is defined in declarative job dsl and has worked fine so far.
This SOE occurred now after I've changed in my pipeline from
pipeline {
agent