I meet the same situation. I'd like to contribute this feature, but no
guarantees of the time.
On Thu, Jun 6, 2019 at 3:29 AM Torsten Walter wrote:
> As far as I can tell from the documentation the plugin tries to read
> secrets from the kubernetes namespace where Jenkins is running. Is there
>
As far as I can tell from the documentation the plugin tries to read
secrets from the kubernetes namespace where Jenkins is running. Is there a
way to tell the plugin to sync secrets from a different namespace?
--
You received this message because you are subscribed to the Google Groups
"Jenkins
Hello guys,
do you have a simple example of an ignore error in a stage (pipeline) ?
--
This email is intended solely for the person or entity to which it is
addressed and may contain confidential and/or privileged information. If
you are not the intended recipient and have received this em
Also, can you post the exact error message you are getting?
> On Jun 5, 2019, at 09:59, Devin Nusbaum wrote:
>
> I’m not aware of any intentional changes like this. What versions of Pipeline
> Groovy and Pipeline Nodes and Processes are you currently running?
>
>> On Jun 5, 2019, at 06:51, Dam
I’m not aware of any intentional changes like this. What versions of Pipeline
Groovy and Pipeline Nodes and Processes are you currently running?
> On Jun 5, 2019, at 06:51, Damien Coraboeuf wrote:
>
> Hi,
>
> We're using Jenkins LTS 2.164.3 and Pipeline Basic Steps 2.16, and the
> behaviour o
Is anyone using Vault successfully with Jenkins? I'm an admin for Jenkins
which external teams use, and I can't come up with a good workflow.
Currently we're using Jenkins Credential Store (JCS) + folders
Good: secrets are not shared across folders (teams)
Bad: 1. Customers can't add sec
Hi,
We're using Jenkins LTS 2.164.3 and Pipeline Basic Steps 2.16, and the
behaviour of the `dir` step has started to change, impacting most of our
pipelines.
I could reproduce this on a small pipeline:
node {
stage("Test") {
sh '''
mkdir -p parent/child
ech
