Have you tried readJSON from pipeline utility steps plugin?
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To vie
The *.jpi or *.hpi are nothing but plugins which are downloaded when you
install to load your plugin. Ideally present under JENKINS_HOME/plugins
directory.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and s
You can always keep a backup of the config file.
Also I suggest you to do this in your test environment and no production. If
you don't have one, you can easily create it by copying Jenkins_home folder to
a different location.
--
You received this message because you are subscribed to the Goog
1. Try modifying the security tag to false in the config.xml and restart.
2. Validate your config.xml using a xml validator.
3. Try setting Jenkins_home env variable.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this g
Suggest you to add a Jenkins user on the Linux slave and generate a key for
that user and use the same in credentials.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an em
Are you using the private key for user - mdmadmin?
Were the keys generated on jenkins master?
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+un
Can you not restart you Jenkins server with *-Duser.timezone=*
*"Brazil/East"* option if running via jar or setting up environment: -
TZ=Asia/Shanghai , if running a docker.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from
*I have a RELEASE pipeline which triggers a parameterized job: TEST (which
can be triggered standalone too). If the TEST job fails I can rerun it
rather than triggering the complete RELEASE job. Is there a way I can list
the rerun of the TEST job to the upstream release job? So that the
trigger
