Yes, I resolved it by upgrade the script security plugin. You need to
upgrade this plugin separately in the first place before you upgrade other
plugins. Don't upgrade it with others.
Seems like upgrading Script Security to 1.21 or newer should fix most of
these. It's sort of a flattened tree and
HI, Daniel:
I have another issue. I would like to know if you can help?
I have branches set up in bitbucket. Some of branches are deleted from
bitbucket. But they still show up when I click build with parameters. Have
you ever met this issue?
thanks.
jason
On Wednesday, February 22, 2017 at
Hi Jason,
Did the depency error got solved ?? if solved so , can you please share it
with me .
thanks
On Wednesday, February 22, 2017 at 4:13:57 PM UTC-5, Jason Yu wrote:
>
> Dear jenkins users:
>
> I have upgraded our jenkins from 1.646 to 2.46. After upgrade, I was able
> to log in correctly
It's a gorgeous answer. I resolved the issue by upgrading script security
plugin.
On Wednesday, February 22, 2017 at 1:16:40 PM UTC-8, Daniel Beck wrote:
>
>
> > On 22.02.2017, at 22:13, Jason Yu >
> wrote:
> >
> > Please kindly give me some clue on how to trouble shoot this.
> >
>
> Seems
> On 22.02.2017, at 22:13, Jason Yu wrote:
>
> Please kindly give me some clue on how to trouble shoot this.
>
Seems like upgrading Script Security to 1.21 or newer should fix most of these.
It's sort of a flattened tree and Pipeline Supporting APIs not being able to be
loaded breaks a bunc