[JIRA] (JENKINS-59918) labels and step script content shown inconsistently in blue ocean steps
Title: Message Title David Dumas commented on JENKINS-59918 Re: labels and step script content shown inconsistently in blue ocean steps This issue is frustrating, I can't find a workaround to have a clean step name all the time in BlueOcean UI. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202717.1571916022000.2721.1581007080253%40Atlassian.JIRA.
[JIRA] (JENKINS-58970) Backwards compatibility broken with version 2.3.0 for KV1
Title: Message Title David Dumas commented on JENKINS-58970 Re: Backwards compatibility broken with version 2.3.0 for KV1 Yes, maybe I should create a new issue, my intent was to discuss that setting a default engine version does not prevent issues or show explicit errors when trying to use engine v2 on v1 (or v1 on v2) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201317.1565984294000.6412.1566328260245%40Atlassian.JIRA.
[JIRA] (JENKINS-58970) Backwards compatibility broken with version 2.3.0 for KV1
Title: Message Title David Dumas edited a comment on JENKINS-58970 Re: Backwards compatibility broken with version 2.3.0 for KV1 1) Updated Hashicorp Vault from 0.9.6 to 1.0+2) Updated plugin from 2.1.1 to 2.3.1 (bumps Java vault driver 2.0.0 to 4.0.0)Result: nothing was working anymore without an explicit error message and engine v2 was set by default globally (Jenkins configured with CasC 1.27)Possible fixes I used: * explicitly set engine v1 usage in CasC* upgrade existing version 1 kv store to version 2 kv store with CLI command vault kv enable-versioning secret/ I don't know if there is a way to have an explicit error when trying to use API v2 on a K/V engine v1, but it might save users from troubles Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201317.1565984294000.6401.1566326760321%40Atlassian.JIRA.
[JIRA] (JENKINS-58970) Backwards compatibility broken with version 2.3.0 for KV1
Title: Message Title David Dumas commented on JENKINS-58970 Re: Backwards compatibility broken with version 2.3.0 for KV1 1) Updated Hashicorp Vault from 0.9.6 to 1.0+ 2) Updated plugin from 2.1.1 to 2.3.1 (bumps Java vault driver 2.0.0 to 4.0.0) Result: nothing was working anymore without an explicit error message and engine v2 was set by default globally (Jenkins configured with CasC 1.27) Possible fixes I used: explicitly set engine v1 usage in CasC upgrade existing version 1 kv store to version 2 kv store with CLI command vault kv enable-versioning secret/ I don't know if there is a way to have an explicit error when trying to use API v2 on a K/V engine v1, but it might save users from troubles Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201317.1565984294000.6397.1566326640169%40Atlassian.JIRA.
[JIRA] (JENKINS-58970) Backwards compatibility broken with version 2.3.0 for KV1
Title: Message Title
David Dumas edited a comment on JENKINS-58970
Re: Backwards compatibility broken with version 2.3.0 for KV1
I am quite concerned that when enabling v2 in configuration (at any level), if K/V engine v2 is not enabled in Vault after upgrading from v1, not a single explicit error shows up in both Jenkins & Vault logs, secret is retrieved with no data and envVars are not set: ``` {{ No such property: testing for class: groovy.lang.Binding ``` }}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201317.1565984294000.6354.1566325260371%40Atlassian.JIRA.
[JIRA] (JENKINS-58970) Backwards compatibility broken with version 2.3.0 for KV1
Title: Message Title David Dumas commented on JENKINS-58970 Re: Backwards compatibility broken with version 2.3.0 for KV1 I am quite concerned that when enabling v2 in configuration (at any level), if K/V engine v2 is not enabled in Vault after upgrading from v1, not a single explicit error shows up in both Jenkins & Vault logs, secret is retrieved with no data and envVars are not set: ```No such property: testing for class: groovy.lang.Binding``` Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201317.1565984294000.6351.1566325200507%40Atlassian.JIRA.
