Error installing automatically JDK 8u192

Hi, While updating the JDK automatically to the latest available of Java 8(192 it is showing an error when running a job. Jenkins Version 2.157 Runtime Java: 1.8.0_191-b12 OS: Windows Server 2012 R2 Log: [EnvInject] - Loading node environment variables. Installing JDK jdk-8u192-oth-JPR Download

How to restore Safe HTML for Parameter Separator descriptions?

Back in 1.596, I used Safe HTML for all build parameter descriptions, so that the user prompt/guidance under each parameter really "popped" for my large-ish user base. Safe HTML for parameter descriptions has eroded over time with security-related changes. Under 2.89, the Node and Extended Choi

Re: Incorrect visualisation of pipeline with failed stage

So we have to either migrate to BlueOcean or to another CI platform. BTW, I just started to play with BlueOcean this month and in general it seems good. On Wednesday, January 16, 2019 at 3:24:46 PM UTC+2, Brian J. Murrell wrote: > > On Wed, 2019-01-16 at 01:22 -0800, Vitaly Karasik wrote: > > I'

Re: Incorrect visualisation of pipeline with failed stage

Hi It will remain like that as when it was -- *Regards,* *Daljit Singh* *+91-9888466996* *Email: **daljit...@gmail.com * On Wed, Jan 16, 2019 at 2:52 PM Vitaly Karasik wrote: > I'm using Jenkins 2.151 with declarative pipeline. This pipeline has a few > stages. > If one of stages failed, Je

How can we achieve the same effect as Jenkins 1's "Deploy artifacts to Maven repository" with Jenkins 2's pipelines?

Hello, For releases, I'd like to build and test all Maven modules and after the build, deploy everything at once (otherwise, someone has to waste time to clean up the mess in Nexus). In Jenkins 1, this was simple: Build with "mvn clean install" and add a post-build job "Deploy artifacts to Mav

Re: can i use variable to specify the agent label in my declarative pipeline ?

I create agent as string parameters and put in the jennkinsfile without quote. agent { node { label params.agent } } Pada Rabu, 03 Mei 2017 21.58.09 UTC+7, ishan jain menulis: > > I am using declarative syntax to build my pipeline. I am loading several > variables from a properties file in the

Testng reports is not generating.

I've a pipeline job which is used to hit an API that returns a response in json format. I want to use jenkins testng result plugin to show that json into testng report. So that i've made a file name "testng-results.xml" and put that file into workspace location, when i build the job i got foll

Re: [Matrix-auth & Folders] How to properly restrict a user to get access only to a job in a (sub)folder

Hello any suggestion to move forward on this topic? Thanks in advance On Thursday, 20 December 2018 18:13:18 UTC+1, geoffroy...@gmail.com wrote: > > Hello > > i'm a bit struggling for one use case i have, maybe someone could share > its experience on such scenario. > > *Jobs structure:* > >-

Re: Incorrect visualisation of pipeline with failed stage

On Wed, 2019-01-16 at 01:22 -0800, Vitaly Karasik wrote: > I'm using Jenkins 2.151 with declarative pipeline. This pipeline has > a few > stages. > If one of stages failed, Jenkins classic UI (unlike BlueOcean) shows > all > following steps as failed, even they weren't executed at all - see > at

Determine Failed Stage in Jenkins Declarative Pipeline

I'd like to report failed stage in the email notification (similar to https://stackoverflow.com/questions/43439093/determine-failed-stage-in-jenkins-declarative-pipeline). There is env.STAGE_NAME, but unfortunately, it reports "Declarative: Post Actions", not the last stage in the build itself. I

Incorrect visualisation of pipeline with failed stage

I'm using Jenkins 2.151 with declarative pipeline. This pipeline has a few stages. If one of stages failed, Jenkins classic UI (unlike BlueOcean) shows all following steps as failed, even they weren't executed at all - see attached screenshot. Any ideas how to fix that? TIA, Vitaly -- You r