[JIRA] (JENKINS-51196) Display caches statistics in servers global configuration
Title: Message Title Joseph Petersen resolved as Fixed Jenkins / JENKINS-51196 Display caches statistics in servers global configuration Change By: Joseph Petersen Status: Open Resolved Resolution: Fixed Released As: 2.2.13 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52134) Build status is not sent to Mercurial repo on BitBucket
Title: Message Title Joseph Petersen resolved as Fixed Jenkins / JENKINS-52134 Build status is not sent to Mercurial repo on BitBucket Change By: Joseph Petersen Status: Open Resolved Assignee: Joseph Petersen Resolution: Fixed Released As: 2.2.13 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47283) Allow for different HTTP & SSH endpoint URIs
Title: Message Title Joseph Petersen updated JENKINS-47283 Jenkins / JENKINS-47283 Allow for different HTTP & SSH endpoint URIs Change By: Joseph Petersen Status: In Review Resolved Resolution: Fixed Released As: 2.2.13 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54331) Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13
Title: Message Title Joseph Petersen assigned an issue to Nikolas Falco Jenkins / JENKINS-54331 Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13 Change By: Joseph Petersen Assignee: Joseph Petersen Nikolas Falco 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52138) Change the BitBucket status message for "In progress" builds
Title: Message Title Joseph Petersen resolved as Fixed Jenkins / JENKINS-52138 Change the BitBucket status message for "In progress" builds Change By: Joseph Petersen Status: Open Resolved Resolution: Fixed Released As: 2.2.13 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47617) CHANGE_BRANCH no longer reporting branch name, but instead PR
Title: Message Title Joseph Petersen resolved as Fixed Jenkins / JENKINS-47617 CHANGE_BRANCH no longer reporting branch name, but instead PR Change By: Joseph Petersen Status: Open Resolved Assignee: Joseph Petersen Resolution: Fixed Released As: 2.2.13 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51063) Multibranch pipeline does not handle correctly webhook of kind tag created
Title: Message Title Joseph Petersen updated JENKINS-51063 Jenkins / JENKINS-51063 Multibranch pipeline does not handle correctly webhook of kind tag created Change By: Joseph Petersen Status: Fixed but Unreleased Resolved Released As: 2.2.13 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47978) Lightweight checkout not working for branches that contain forward slash '/'
Title: Message Title Joseph Petersen resolved as Fixed Recently tested it with 2.2.13 at least it seems fixed. Jenkins / JENKINS-47978 Lightweight checkout not working for branches that contain forward slash '/' Change By: Joseph Petersen Status: Reopened Resolved Assignee: Vivek Pandey Joseph Petersen Resolution: Fixed 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54297) Failing to report build status to BitBucket server
Title: Message Title Joseph Petersen updated an issue Jenkins / JENKINS-54297 Failing to report build status to BitBucket server Change By: Joseph Petersen Issue Type: Bug Improvement 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54297) Failing to report build status to BitBucket server
Title: Message Title Joseph Petersen edited a comment on JENKINS-54297 Re: Failing to report build status to BitBucket server Definitely not a bug, this is the intended error message you should handle as Jenkins admins.Go fix your Jenkins URL. it should be a full FQDN as according to bitbucket server requirements .Perhaps the error message could be improved? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54297) Failing to report build status to BitBucket server
Title: Message Title Joseph Petersen updated an issue Jenkins / JENKINS-54297 Failing to report build status to BitBucket server Change By: Joseph Petersen Priority: Major Trivial 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54297) Failing to report build status to BitBucket server
Title: Message Title Joseph Petersen commented on JENKINS-54297 Re: Failing to report build status to BitBucket server Definitely not a bug, this is the intended error message you should handle as Jenkins admins. Go fix your Jenkins URL. it should be a full FQDN as according to bitbucket server. Perhaps the error message could be improved? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54297) Failing to report build status to BitBucket server
Title: Message Title Joseph Petersen commented on JENKINS-54297 Re: Failing to report build status to BitBucket server Depends on the version of Bitbucket server your using New version limits the build status API to FQDN hostnames. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53959) Pipeline Git LFS avoid pull on master
Title: Message Title Joseph Petersen created an issue Jenkins / JENKINS-53959 Pipeline Git LFS avoid pull on master Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2018-10-09 12:39 Priority: Blocker Reporter: Joseph Petersen When using declarative pipeline and adding the additional behavior to "Git LFS pull after checkout" This is actually done on master too. Which for very LARGE files seems over kill. First off we don't have LFS installed on master. Secondly we don't have that much storage allocated cause we never considered the master would be trying to pull from our LFS storage that is a job for our agents... Unless I am mistaken I don't think this is the intended behavior. Of course I could try an extension plugin that says avoids LFS checkout on master. I would be happy to look into a solution for the git plugin if this is indeed not the intended behavior. Add Comment
[JIRA] (JENKINS-53959) Pipeline Git LFS avoid pull on Jenkins Master
Title: Message Title Joseph Petersen updated an issue Jenkins / JENKINS-53959 Pipeline Git LFS avoid pull on Jenkins Master Change By: Joseph Petersen Summary: Pipeline Git LFS avoid pull on master Jenkins Master 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53959) Pipeline Git LFS avoid pull on Jenkins Master
Title: Message Title Joseph Petersen updated an issue Jenkins / JENKINS-53959 Pipeline Git LFS avoid pull on Jenkins Master Change By: Joseph Petersen Priority: Blocker Trivial 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53933) set file permission on ssh key when on windows to enable OpenSSH client
Title: Message Title Joseph Petersen created an issue Jenkins / JENKINS-53933 set file permission on ssh key when on windows to enable OpenSSH client Issue Type: Task Assignee: Mark Waite Components: git-client-plugin Created: 2018-10-07 16:57 Priority: Major Reporter: Joseph Petersen We would like to enable Windows agents/master to set file permissions correctly for the ssh key when they are using OpenSSH made by Microsoft. Using java.nio.file to set permissons is possible This to avoid the dreaded error message from OpenSSH: @@@ @ WARNING: UNPROTECTED PRIVATE KEY FILE! @ @@@ Permissions for 'ssh_host_dsa_key' are too open. Incoming PR Add Comment
[JIRA] (JENKINS-53732) Git plugin unit test is leaking into user's git config
Title: Message Title Joseph Petersen created an issue Jenkins / JENKINS-53732 Git plugin unit test is leaking into user's git config Issue Type: Task Assignee: Mark Waite Components: git-plugin Created: 2018-09-22 12:21 Priority: Blocker Reporter: Joseph Petersen I have had several times where I noticed my user.email and user.name was changed in my git config. [include] path = .gitconfig.local [user] name = Name From Git-Plugin-Test email = email.from.git.plugin.t...@example.com Because I use a include of local git global config. Finally figured out it was git-plugin unit tests messing with my config. Is there are way we can ban the test or fix this for all versions since this test was included. Add Comment
[JIRA] (JENKINS-53732) Git plugin unit test is leaking into user's git config
Title: Message Title
Joseph Petersen updated an issue
Jenkins / JENKINS-53732
Git plugin unit test is leaking into user's git config
Change By:
Joseph Petersen
I have had several times where I noticed my user.email and user.name was changed in my git config. This is the culprit: https://github.com/jenkinsci/git-plugin/blob/70634f15702157af3a5b7f49e953882c45e438df/src/test/java/jenkins/plugins/git/CliGitCommand.java#L137-L149 {code:java}[include] path = .gitconfig.local[user] name = Name From Git-Plugin-Test email = email.from.git.plugin.t...@example.com{code} Because I use a include of local git global config.Finally figured out it was git-plugin unit tests messing with my config. Is there are way we can ban the test or fix this for all versions since this test was included. Happens for instance when you run unit test for Bitbucket branch source plugin...
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53732) Git plugin unit test is leaking into user's git config
Title: Message Title
Joseph Petersen updated an issue
Jenkins / JENKINS-53732
Git plugin unit test is leaking into user's git config
Change By:
Joseph Petersen
I have had several times where I noticed my user.email and user.name was changed in my git config.This is the culprit: [ https://github.com/jenkinsci/git-plugin/blob/70634f15702157af3a5b7f49e953882c45e438df/src/test/java/jenkins/plugins/git/CliGitCommand.java#L137-L149 ] {code:java}[include] path = .gitconfig.local[user] name = Name From Git-Plugin-Test email = email.from.git.plugin.t...@example.com{code} Because I use a include of local git global config.Finally figured out it was git-plugin unit tests messing with my config. Is there are way we can ban the test or fix this for all versions since this test was included. Happens for instance when you run unit test for Bitbucket branch source plugin...
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55220) Multibranch Pipeline jobs get randomly lost
Title: Message Title Joseph Petersen commented on JENKINS-55220 Re: Multibranch Pipeline jobs get randomly lost Jonas Büth I suggest you dedicate time to debug the issue, I am only a maintainer of the plugin, I do not work with Bitbucket directly anymore so it requires more time than I can afford to debug issues. I rely on the community to solve any issues they might experience. If you need guidance on how to get started, please ask away. I suggest you look here: https://wiki.jenkins.io/display/JENKINS/Plugin+tutorial 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55220) Multibranch Pipeline jobs get randomly lost
Title: Message Title Joseph Petersen commented on JENKINS-55220 Re: Multibranch Pipeline jobs get randomly lost potential fix should be available in 2.2.16. Should appear in the update center in a few hours. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51282) Azure VM plugin log is too chatty
Title: Message Title Joseph Petersen commented on JENKINS-51282 Re: Azure VM plugin log is too chatty I would just lower the log level from INFO to FINE. Then it is up to the Jenkins admin to create a logger: https://support.cloudbees.com/hc/en-us/articles/204880580-How-do-I-create-a-logger-in-Jenkins-for-troubleshooting-and-diagnostic-information- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54401) NPE when parsing scm git revision date on PR branches
Title: Message Title Joseph Petersen commented on JENKINS-54401 Re: NPE when parsing scm git revision date on PR branches Seems to have resolved itself: INFRA-1868 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54859) Branch event java.lang.NullPointerException
Title: Message Title Joseph Petersen resolved as Duplicate Jenkins / JENKINS-54859 Branch event java.lang.NullPointerException Change By: Joseph Petersen Status: Open Resolved Resolution: Duplicate 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54401) NPE when parsing scm git revision date on PR branches
Title: Message Title Joseph Petersen commented on JENKINS-54401 Re: NPE when parsing scm git revision date on PR branches Create a ticket for Jenkins infra, it is uploaded to artifactory as posted on GitHub 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54401) NPE when parsing scm git revision date on PR branches
Title: Message Title Joseph Petersen updated JENKINS-54401 Jenkins / JENKINS-54401 NPE when parsing scm git revision date on PR branches Change By: Joseph Petersen Status: In Review Resolved Resolution: Fixed Released As: 2.2.15 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54401) NPE when parsing scm git revision date on PR branches
Title: Message Title Joseph Petersen commented on JENKINS-54401 Re: NPE when parsing scm git revision date on PR branches Released as 2.2.15 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53767) Offer plugin management tooling
Title: Message Title Joseph Petersen edited a comment on JENKINS-53767 Re: Offer plugin management tooling In JCasC we ended up removing the plugin management support was causing issues and startup. See [https://github.com/jenkinsci/configuration-as-code-plugin/pull/769]Thank you [~oleg_nenashev] for the GSoC write up 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53767) Offer plugin management tooling
Title: Message Title Joseph Petersen edited a comment on JENKINS-53767 Re: Offer plugin management tooling In JCasC we ended up removing the plugin management support as it was causing issues and on startup. See [https://github.com/jenkinsci/configuration-as-code-plugin/pull/769]Thank you [~oleg_nenashev] for the GSoC write up 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53767) Offer plugin management tooling
Title: Message Title Joseph Petersen edited a comment on JENKINS-53767 Re: Offer plugin management tooling In JCasC we ended up removing the plugin management support as it was causing issues and startup. See [https://github.com/jenkinsci/configuration-as-code-plugin/pull/769]Thank you [~oleg_nenashev] for the GSoC write up 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53767) Offer plugin management tooling
Title: Message Title Joseph Petersen commented on JENKINS-53767 Re: Offer plugin management tooling In JCasC we ended up removing the plugin management support was causing issues and startup. See https://github.com/jenkinsci/configuration-as-code-plugin/pull/769 Thank you Oleg Nenashev for the GSoC write up 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53767) Offer plugin management tooling
Title: Message Title Joseph Petersen updated an issue Jenkins / JENKINS-53767 Offer plugin management tooling Change By: Joseph Petersen Jenkins does offer a web UI to manage plugin installation from a live master instance, but in many deployments administrator would like to control installed plugins by version and by tooling, before jenkins master starts. * docker official image provides an install-plugins.sh script which evolved far beyond its initial "help script" scope. * configuration-as-code implemented plugin installation hack based on PluginSite.Plugin#deploy. (Removed as of v1.8 of JCasC plugin) * open-source update center does expose plugins-version.json on casc request so one can manage versions for all hosted plugins, not just latest * custom war packager does support plugin installation on his own * jenkins evergreen does manage plugin installation based on updates from metadata server, using his own logic implemented by nodejs evergreen client. * jenkinsfile-runner does manage plugin installation implemented in Go * coreOS provides a [groovy script|https://github.com/coreos/jenkins-os/blob/master/init.groovy] to handle required plugins * cloudbees DEV@Cloud uses a set of Chef Ruby recipes for the same purpose * etc Everybody is re-inventing the wheel, partially implementing the "details" of plugin management (signed metadata, artifacts checksums, plugins detached from core, ...). It becomes obvious Jenkins should provide adequate tooling for plugin installation _outside_ jenkins live instance. Add Comment
[JIRA] (JENKINS-56553) Make ProxyConfiguration compatible with JCasC
Title: Message Title Joseph Petersen updated an issue Jenkins / JENKINS-56553 Make ProxyConfiguration compatible with JCasC Change By: Joseph Petersen Labels: jcasc-compatibility testing-second-label 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56553) Make ProxyConfiguration compatible with JCasC
Title: Message Title Joseph Petersen updated an issue Jenkins / JENKINS-56553 Make ProxyConfiguration compatible with JCasC Change By: Joseph Petersen Labels: jcasc-compatibility testing-second-label 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52906) jira-plugin: FAILED TO EXPORT hudson.plugins.jira.JiraProjectProperty
Title: Message Title Joseph Petersen commented on JENKINS-52906 Re: jira-plugin: FAILED TO EXPORT hudson.plugins.jira.JiraProjectProperty Reworking the PR after being stale for a while 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53767) Offer plugin management tooling
Title: Message Title Joseph Petersen edited a comment on JENKINS-53767 Re: Offer plugin management tooling From JCasC point of view:Should be possible to add an optional JCasC configurator to Jenkins core that would at least take care of reading the configurations at startup and invoke the installation of plugins before ever starting to configure plugins. That would at least take care of plugin installation where JCasC is concerned. Though it would still require more plugin installation tooling. Regarding plugin installation toolingI still strongly believe that tooling should either stay within Java or a mix of Java and Go.If it was pure Java I could foresee the tool becoming overly large and burden by dependency hell.A mix of Go and Java could work.Go would be the main source library and has a better native HTTP client.Java jar would just be a wrapper for calling go functions: [https://medium.com/learning-the-go-programming-language/calling-go-functions-from-other-languages-4c7d8bcc69bf] 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53767) Offer plugin management tooling
Title: Message Title Joseph Petersen edited a comment on JENKINS-53767 Re: Offer plugin management tooling From JCasC point of view:Should be possible to add an optional JCasC configurator to Jenkins core that would at least take care of Plugin reading the configurations at startup and invoke the installation but of plugins before ever starting to configure plugins. That would at least take care of plugin installation where JCasC is concerned. Though it would still require more plugin installation tooling. Regarding plugin installation toolingI still strongly believe that tooling should either stay within Java or a mix of Java and Go.If it was pure Java I could foresee the tool becoming overly large and burden by dependency hell.A mix of Go and Java could work.Go would be the main source library and has a better native HTTP client.Java jar would just be a wrapper for calling go functions: [https://medium.com/learning-the-go-programming-language/calling-go-functions-from-other-languages-4c7d8bcc69bf] 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53767) Offer plugin management tooling
Title: Message Title Joseph Petersen edited a comment on JENKINS-53767 Re: Offer plugin management tooling From JCasC point of view:Should be possible to add an optional JCasC configurator to Jenkins core that .That would at least take care of reading the configurations at startup and invoke the installation of plugins before ever starting to configure plugins.That would at least take care of plugin installation where JCasC is concerned.Though it would still require more plugin installation tooling. Regarding plugin installation toolingI still strongly believe that tooling should either stay within Java or a mix of Java and Go.If it was pure Java I could foresee the tool becoming overly large and burden by dependency hell.A mix of Go and Java could work.Go would be the main source library and has a better native HTTP client.Java jar would just be a wrapper for calling go functions: [https://medium.com/learning-the-go-programming-language/calling-go-functions-from-other-languages-4c7d8bcc69bf] 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53767) Offer plugin management tooling
Title: Message Title Joseph Petersen commented on JENKINS-53767 Re: Offer plugin management tooling From JCasC point of view: Should be possible to add an optional JCasC configurator to Jenkins core that would take care of Plugin installation but it would still require more plugin installation tooling. Regarding plugin installation tooling I still strongly believe that tooling should either stay within Java or a mix of Java and Go. If it was pure Java I could foresee the tool becoming overly large and burden by dependency hell. A mix of Go and Java could work. Go would be the main source library and has a better native HTTP client. Java jar would just be a wrapper for calling go functions: https://medium.com/learning-the-go-programming-language/calling-go-functions-from-other-languages-4c7d8bcc69bf 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53767) Offer plugin management tooling
Title: Message Title Joseph Petersen edited a comment on JENKINS-53767 Re: Offer plugin management tooling From JCasC point of view:Should be possible to add an optional JCasC configurator to Jenkins core. That would at least take care of reading Reading the configurations at startup and invoke the installation of plugins before ever starting to configure plugins.That would at least take care of plugin installation where JCasC is concerned.Though it would still require more plugin installation tooling. Regarding plugin installation toolingI still strongly believe that tooling should either stay within Java or a mix of Java and Go.If it was pure Java I could foresee the tool becoming overly large and burden by dependency hell.A mix of Go and Java could work.Go would be the main source library and has a better native HTTP client.Java jar would just be a wrapper for calling go functions: [https://medium.com/learning-the-go-programming-language/calling-go-functions-from-other-languages-4c7d8bcc69bf] 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52906) jira-plugin: FAILED TO EXPORT hudson.plugins.jira.JiraProjectProperty
Title: Message Title Joseph Petersen assigned an issue to Olivier Lamy Jenkins / JENKINS-52906 jira-plugin: FAILED TO EXPORT hudson.plugins.jira.JiraProjectProperty Change By: Joseph Petersen Assignee: Joseph Petersen Olivier Lamy 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52906) jira-plugin: FAILED TO EXPORT hudson.plugins.jira.JiraProjectProperty
Title: Message Title Joseph Petersen updated JENKINS-52906 Jenkins / JENKINS-52906 jira-plugin: FAILED TO EXPORT hudson.plugins.jira.JiraProjectProperty Change By: Joseph Petersen Status: In Progress Review 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52906) jira-plugin: FAILED TO EXPORT hudson.plugins.jira.JiraProjectProperty
Title: Message Title Joseph Petersen commented on JENKINS-52906 Re: jira-plugin: FAILED TO EXPORT hudson.plugins.jira.JiraProjectProperty Currently awaiting review/merge 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56926) Jenkinsfile not found in a subfolder
Title: Message Title Joseph Petersen commented on JENKINS-56926 Re: Jenkinsfile not found in a subfolder the update should be available shortly in the update center 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49082) mstest is not visible in pipeline syntax
Title: Message Title Joseph Petersen assigned an issue to Joseph Petersen Jenkins / JENKINS-49082 mstest is not visible in pipeline syntax Change By: Joseph Petersen Assignee: Ivo Bellin Salarin Joseph Petersen 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49082) mstest is not visible in pipeline syntax
Title: Message Title Joseph Petersen resolved as Fixed Released in v1.0.0 Jenkins / JENKINS-49082 mstest is not visible in pipeline syntax Change By: Joseph Petersen Status: Open Resolved Resolution: Fixed Released As: v1.0.0 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53144) Whenever Jenkins is restarted, any updates\additions to the VSTEST global settings are lost.
Title: Message Title Joseph Petersen updated JENKINS-53144 Should be fixed in the upcoming release Jenkins / JENKINS-53144 Whenever Jenkins is restarted, any updates\additions to the VSTEST global settings are lost. Change By: Joseph Petersen Status: Open Fixed but Unreleased Resolution: Fixed 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53144) Whenever Jenkins is restarted, any updates\additions to the VSTEST global settings are lost.
Title: Message Title Joseph Petersen assigned an issue to Joseph Petersen Jenkins / JENKINS-53144 Whenever Jenkins is restarted, any updates\additions to the VSTEST global settings are lost. Change By: Joseph Petersen Assignee: Joseph Petersen 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53144) Whenever Jenkins is restarted, any updates\additions to the VSTEST global settings are lost.
Title: Message Title Joseph Petersen updated JENKINS-53144 1.0.8 should appear in the update center in the near future Jenkins / JENKINS-53144 Whenever Jenkins is restarted, any updates\additions to the VSTEST global settings are lost. Change By: Joseph Petersen Status: Fixed but Unreleased Resolved Released As: 1.0.8 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56142) quality gates are not generated in snippet generator
Title: Message Title Joseph Petersen created an issue Jenkins / JENKINS-56142 quality gates are not generated in snippet generator Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-02-14 15:14 Environment: warnings-ng: 3.0.0 Priority: Minor Reporter: Joseph Petersen This is what the snippet generator produces: recordIssues qualityGates: [], tools: [msBuild()] Add Comment
[JIRA] (JENKINS-56142) quality gates are not generated in snippet generator
Title: Message Title Joseph Petersen commented on JENKINS-56142 Re: quality gates are not generated in snippet generator Ulli Hafner both QualityGateStatus and QualityGateType are not describable so I assume that snippet generator is gonna fail hard to generate these 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55927) Jenkins multibranch pipeline scan is triggered in case of remote pull request merge
Title: Message Title Joseph Petersen commented on JENKINS-55927 Re: Jenkins multibranch pipeline scan is triggered in case of remote pull request merge Antonio Muñiz or Stephen Connolly perhaps either of you can speak to the reason for reindexing? Doing a quick look at gitea and github plugins none of them forces the reindex Should we perhaps remove it? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55927) Jenkins multibranch pipeline scan is triggered in case of remote pull request merge
Title: Message Title Joseph Petersen commented on JENKINS-55927 Re: Jenkins multibranch pipeline scan is triggered in case of remote pull request merge Not sure what your issue is, can you please provide a more detailed description 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51924) Supporting converters for non-Java languages
Title: Message Title Joseph Petersen commented on JENKINS-51924 Re: Supporting converters for non-Java languages Hi Share Cheng We would be very interested in adding support for dotcover code coverage. Dotcover's reports only supports line coverage, I haven't looked too closely to the implementation. Though would you consider it possible to have support for dotcover? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56322) URL validation breaks when inside private LAN
Title: Message Title Joseph Petersen resolved as Fixed Jenkins / JENKINS-56322 URL validation breaks when inside private LAN Change By: Joseph Petersen Status: Open Resolved Resolution: Fixed Released As: v2.4.3 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56322) URL validation breaks when inside private LAN
Title: Message Title Joseph Petersen commented on JENKINS-56322 Re: URL validation breaks when inside private LAN Hi hugo fonseca feel free to test out v2.4.3 should cover your use case 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48737) Provide lightweight checkouts for Bitbucket Pull Requests
Title: Message Title Joseph Petersen resolved as Fixed Jenkins / JENKINS-48737 Provide lightweight checkouts for Bitbucket Pull Requests Change By: Joseph Petersen Status: Open Resolved Resolution: Fixed Released As: v2.4.3 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48737) Provide lightweight checkouts for Bitbucket Pull Requests
Title: Message Title Joseph Petersen commented on JENKINS-48737 Re: Provide lightweight checkouts for Bitbucket Pull Requests Merged #174 which adds support for lightweight checkout though only for bitbucket server. Bitbucket cloud is only partially covered by PR head revisions on the same owner & repository. See https://bitbucket.org/site/master/issues/5814/refify-pull-requests-by-making-them-a-ref 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55071) Slow branch scan when using Bitbucket source
Title: Message Title Joseph Petersen commented on JENKINS-55071 Re: Slow branch scan when using Bitbucket source if you go into Jenkins global settings, you can enable cache for bitbucket cloud endpoint. You should increase your periodic scans to 8 hours or more and rely on events from Bitbucket cloud. Łukasz Wojciechowski you can achieve the same effect by adding branch filters in the behavior sections. No need to hardcode it. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57513) Split the large databound constructors into databound setters
Title: Message Title Joseph Petersen edited a comment on JENKINS-57513 Re: Split the large databound constructors into databound setters https://github.com/jenkinsci/configuration-as-code-plugin/issues/885https://github.com/jenkinsci/configuration-as-code-plugin/issues/381 we also had several users on gitter ask for help debugging null pointers and it all leads to those large data bound constructors that assume null does not exist. 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.199415.1558053245000.372.1558053540095%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57513) Split the large databound constructors into databound setters
Title: Message Title Joseph Petersen commented on JENKINS-57513 Re: Split the large databound constructors into databound setters https://github.com/jenkinsci/configuration-as-code-plugin/issues/885 https://github.com/jenkinsci/configuration-as-code-plugin/issues/381 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.199415.1558053245000.370.1558053480139%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57513) Split the large databound constructors into databound setters
Title: Message Title Joseph Petersen commented on JENKINS-57513 Re: Split the large databound constructors into databound setters Matt Sicker Raihaan Shouhell 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.199415.1558053245000.374.1558054200105%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57513) Split the large databound constructors into databound setters
Title: Message Title Joseph Petersen created an issue Jenkins / JENKINS-57513 Split the large databound constructors into databound setters Issue Type: Task Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2019-05-17 00:34 Priority: Minor Reporter: Joseph Petersen Inside EC2 plugin there is a lot of constructors with a large set of databound constructors. Databound constructor should only be used for mandatory/final parameters Where databound setters should be used for optional parameters. https://jenkins.io/doc/developer/plugin-development/pipeline-integration/#constructor-vs-setters Add Comment
[JIRA] (JENKINS-57513) Split the large databound constructors into databound setters
Title: Message Title Joseph Petersen edited a comment on JENKINS-57513 Re: Split the large databound constructors into databound setters [~jvz] I agree with you but for JCasC we only really care about the lovely data binding ;)I would like to point out this lovely PR which could solve all our data binding problem and jelly problems at the same time: https://github.com/stapler/stapler/pull/147 https://github.com/jenkinsci/jenkins/pull/3669 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.199415.1558053245000.4428.1558109460150%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57513) Split the large databound constructors into databound setters
Title: Message Title Joseph Petersen commented on JENKINS-57513 Re: Split the large databound constructors into databound setters Matt Sicker I agree with you but for JCasC we only really care about the lovely data binding I would like to point out this lovely PR which could solve all our data binding problem and jelly problems at the same time: https://github.com/stapler/stapler/pull/147 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.199415.1558053245000.4422.1558109040282%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57505) Cannot quote $ (dolar sign) in yaml
Title: Message Title
Joseph Petersen commented on JENKINS-57505
Re: Cannot quote $ (dolar sign) in yaml
You ought to read our readme on how to handle secrets: https://github.com/jenkinsci/configuration-as-code-plugin#handling-secrets You have to escape secrets with ^${MY_TEXT}
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.199370.1558010334000.13519.1559037480145%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57121) list view jobnames is missing getter and setter for jcasc compliance
Title: Message Title Joseph Petersen assigned an issue to Joseph Petersen Jenkins / JENKINS-57121 list view jobnames is missing getter and setter for jcasc compliance Change By: Joseph Petersen Assignee: Joseph Petersen 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.198871.1555696084000.21224.1559668620576%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57121) list view jobnames is missing getter and setter for jcasc compliance
Title: Message Title Joseph Petersen updated JENKINS-57121 Jenkins / JENKINS-57121 list view jobnames is missing getter and setter for jcasc compliance Change By: Joseph Petersen Status: In Progress Review 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.198871.1555696084000.21229.1559668620666%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57121) list view jobnames is missing getter and setter for jcasc compliance
Title: Message Title Joseph Petersen started work on JENKINS-57121 Change By: Joseph Petersen Status: Open In Progress 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.198871.1555696084000.21228.1559668620648%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57845) provide configurator/databound setter for certificate credential
Title: Message Title Joseph Petersen created an issue Jenkins / JENKINS-57845 provide configurator/databound setter for certificate credential Issue Type: Bug Assignee: Unassigned Components: credentials-plugin Created: 2019-06-04 16:27 Labels: jcasc-compatibility Priority: Minor Reporter: Joseph Petersen JCasC cannot easily configure UploadedKeyStoreSource as the expected input is a bytes array. Users would like to configure the certificate via the same "upload" function that is provided by stapler when configured via JCasC https://github.com/jenkinsci/credentials-plugin/blob/bddcf41ba3388cb54126e3f626b3deb7d65e3b53/src/main/java/com/cloudbees/plugins/credentials/impl/CertificateCredentialsImpl.java#L677 Add Comment
[JIRA] (JENKINS-57121) list view jobnames is missing getter and setter for jcasc compliance
Title: Message Title Joseph Petersen commented on JENKINS-57121 Re: list view jobnames is missing getter and setter for jcasc compliance Please see the down stream PR: https://github.com/jenkinsci/configuration-as-code-plugin/pull/850/files#diff-d4180fbd418102ca8a2290ab285cb17c 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.198871.1555696084000.5586.1558374180125%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57567) View's description has no setter which is needed for JCasC
Title: Message Title Joseph Petersen created an issue Jenkins / JENKINS-57567 View's description has no setter which is needed for JCasC Issue Type: Bug Assignee: Joseph Petersen Components: core Created: 2019-05-20 17:49 Labels: jcasc-compatibility Priority: Minor Reporter: Joseph Petersen The description in view is missing a databound setter, this affects items ListView too Add Comment
[JIRA] (JENKINS-57567) View's description has no setter which is needed for JCasC
Title: Message Title Joseph Petersen commented on JENKINS-57567 Re: View's description has no setter which is needed for JCasC Is related to JENKINS-57121 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.199481.1558374598000.5595.1558374660046%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57567) View's description has no setter which is needed for JCasC
Title: Message Title Joseph Petersen started work on JENKINS-57567 Change By: Joseph Petersen Status: Open In Progress 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.199481.1558374598000.5596.1558374720058%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57121) list view jobnames is missing getter and setter for jcasc compliance
Title: Message Title Joseph Petersen commented on JENKINS-57121 Re: list view jobnames is missing getter and setter for jcasc compliance Does not work for jobNames Vi Pl your config uses includeRegex. 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.198871.1555696084000..1558373460176%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57567) View's description has no setter which is needed for JCasC
Title: Message Title Joseph Petersen updated JENKINS-57567 Jenkins / JENKINS-57567 View's description has no setter which is needed for JCasC Change By: Joseph Petersen Status: In Progress Review 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.199481.1558374598000.5720.1558387740233%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57121) list view jobnames is missing getter and setter for jcasc compliance
Title: Message Title Joseph Petersen created an issue Jenkins / JENKINS-57121 list view jobnames is missing getter and setter for jcasc compliance Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-04-19 17:48 Labels: jcasc-compatibility Priority: Minor Reporter: Joseph Petersen JCasC users want to configure list views yet sadly jobNames does not have a getter or setter making it improbable for JCasC to configure list views. https://github.com/jenkinsci/jenkins/blob/2767b00146ce2ff2738b7fd7c6db95a26b8f9f39/core/src/main/java/hudson/model/ListView.java#L80 Add Comment
[JIRA] (JENKINS-57122) ToolDescriptor#getDefaultProperties should be marked as Restricted No External Use
Title: Message Title Joseph Petersen updated an issue Jenkins / JENKINS-57122 ToolDescriptor#getDefaultProperties should be marked as Restricted No External Use Change By: Joseph Petersen JCasC will attempt to export which has no setterSince this is used for form binding it is best to mark this as restricted signaling no one should override it. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57122) ToolDescriptor#getDefaultProperties should be marked as Restricted No External Use
Title: Message Title Joseph Petersen updated an issue Jenkins / JENKINS-57122 ToolDescriptor#getDefaultProperties should be marked as Restricted No External Use Change By: Joseph Petersen JCasC will attempt to export defaultProperties , and if users than tries to roundtrip the configuration , it will say no attribute is available for defaultProperties which has no setter. Since this The method is used for form binding it is , so best to mark this as restricted signaling .Signaling to JCasC export it should not be exported, and no one should override it. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57122) ToolDescriptor#getDefaultProperties should be marked as Restricted No External Use
Title: Message Title Joseph Petersen created an issue Jenkins / JENKINS-57122 ToolDescriptor#getDefaultProperties should be marked as Restricted No External Use Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-04-19 18:19 Labels: jcasc-compatibility Priority: Minor Reporter: Joseph Petersen JCasC will attempt to export which has no setter Since this is used for form binding it is best to mark this as restricted signaling no one should override it. Add Comment
[JIRA] (JENKINS-57122) ToolDescriptor#getDefaultProperties should be marked as Restricted No External Use
Title: Message Title Joseph Petersen updated an issue Jenkins / JENKINS-57122 ToolDescriptor#getDefaultProperties should be marked as Restricted No External Use Change By: Joseph Petersen JCasC will attempt to export defaultProperties and if users than tries to roundtrip the configuration it will say no attribute is available for defaultProperties which has no setter . Since this is used for form binding it is best to mark this as restricted signaling no one should override it. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57218) NPE from SymbolLookup after job-dsl update without configuration-as-code
Title: Message Title Joseph Petersen commented on JENKINS-57218 Re: NPE from SymbolLookup after job-dsl update without configuration-as-code Jesse Glick jobdsl #1175 should hopefully fix it unless you are referring to another issue. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56073) Configuration-as-Code compatibility
Title: Message Title Joseph Petersen commented on JENKINS-56073 Re: Configuration-as-Code compatibility Linked to HAP-1018 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.197499.1549833378000.8104.1562863320253%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56073) Configuration-as-Code compatibility
Title: Message Title Joseph Petersen commented on JENKINS-56073 Re: Configuration-as-Code compatibility WIP: jfrog/jenkins-artifactory-plugin #169 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.197499.1549833378000.8669.1562931720152%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58482) req
Title: Message Title Joseph Petersen updated an issue Jenkins / JENKINS-58482 req Change By: Joseph Petersen Component/s: _unsorted Component/s: accurev-plugin 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.200618.1563011989000.9262.1563020460136%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58482) req
Title: Message Title Joseph Petersen assigned an issue to Unassigned Jenkins / JENKINS-58482 req Change By: Joseph Petersen Assignee: Joseph Petersen 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.200618.1563011989000.9260.1563020400116%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58330) ChangTest
Title: Message Title Joseph Petersen updated an issue Jenkins / JENKINS-58330 ChangTest Change By: Joseph Petersen Component/s: _unsorted Component/s: accurev-plugin 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.200441.1562209278000.1545.1562210100189%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58330) ChangTest
Title: Message Title Joseph Petersen assigned an issue to Unassigned Jenkins / JENKINS-58330 ChangTest Change By: Joseph Petersen Assignee: Joseph Petersen 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.200441.1562209278000.1547.1562210100219%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56926) Jenkinsfile not found in a subfolder
Title: Message Title Joseph Petersen resolved as Fixed Jenkins / JENKINS-56926 Jenkinsfile not found in a subfolder Change By: Joseph Petersen Status: Open Resolved Resolution: Fixed Released As: v2.4.4 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58970) Backwards compatibility broken with version 2.3.0 for KV1
Title: Message Title Joseph Petersen commented on JENKINS-58970 Re: Backwards compatibility broken with version 2.3.0 for KV1 You can already specify the engine version. 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.5697.1566252000206%40Atlassian.JIRA.
[JIRA] (JENKINS-58991) Getting NullPointerException com.bettercloud.vault.api.Logical.read after upgrade to 2.3.0
Title: Message Title Joseph Petersen commented on JENKINS-58991 Re: Getting NullPointerException com.bettercloud.vault.api.Logical.read after upgrade to 2.3.0 Vaclav Adamec if you could share your pipeline step or UI step. What most likely is the case is you have not set `engineVersion` 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.201340.1566206161000.5694.1566251760179%40Atlassian.JIRA.
[JIRA] (JENKINS-57847) NPE when using Vault Plugin with older version of vault
Title: Message Title Joseph Petersen commented on JENKINS-57847 Re: NPE when using Vault Plugin with older version of vault Using v2.3.0 of hashicorp vault plugin you have specify engine version 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.199805.1559668368000.5701.1566252120217%40Atlassian.JIRA.
[JIRA] (JENKINS-58970) Backwards compatibility broken with version 2.3.0 for KV1
Title: Message Title Joseph Petersen commented on JENKINS-58970 Re: Backwards compatibility broken with version 2.3.0 for KV1 I'd disagree with changing the default, let me come up with a different solution 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.5709.1566252540427%40Atlassian.JIRA.
[JIRA] (JENKINS-58970) Backwards compatibility broken with version 2.3.0 for KV1
Title: Message Title Joseph Petersen resolved as Fixed Jenkins / JENKINS-58970 Backwards compatibility broken with version 2.3.0 for KV1 Change By: Joseph Petersen Status: In Progress Resolved Assignee: Peter Tierno Joseph Petersen Resolution: Fixed Released As: https://github.com/jenkinsci/hashicorp-vault-plugin/releases/tag/hashicorp-vault-plugin-2.3.1 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.5841.1566276000492%40Atlassian.JIRA.
[JIRA] (JENKINS-58970) Backwards compatibility broken with version 2.3.0 for KV1
Title: Message Title Joseph Petersen commented on JENKINS-58970 Re: Backwards compatibility broken with version 2.3.0 for KV1 v2.3.1 should be in the update center shortly 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.5838.1566275940185%40Atlassian.JIRA.
[JIRA] (JENKINS-58947) Vault credentials not found secret/
Title: Message Title Joseph Petersen commented on JENKINS-58947 Re: Vault credentials not found secret/ Upgrading to v2.3.1 allows you to set your vault engine on the Vault Configuration. It will default to version 2 so if it still fails you will most likely have to set it to version 1. If you want to know more about engine version read here: https://www.vaultproject.io/docs/secrets/kv/index.html 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.201293.1565870178000.5854.1566276300535%40Atlassian.JIRA.
[JIRA] (JENKINS-58947) Vault credentials not found secret/
Title: Message Title Joseph Petersen resolved as Fixed Jenkins / JENKINS-58947 Vault credentials not found secret/ Change By: Joseph Petersen Status: Open Resolved Assignee: Peter Tierno Joseph Petersen Resolution: Fixed Released As: https://github.com/jenkinsci/hashicorp-vault-plugin/releases/tag/hashicorp-vault-plugin-2.3.1 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.201293.1565870178000.5851.1566276300496%40Atlassian.JIRA.
[JIRA] (JENKINS-58991) Getting NullPointerException com.bettercloud.vault.api.Logical.read after upgrade to 2.3.0
Title: Message Title Joseph Petersen commented on JENKINS-58991 Re: Getting NullPointerException com.bettercloud.vault.api.Logical.read after upgrade to 2.3.0 Upgrading to v2.3.1 allows you to set your vault engine on the Vault Configuration. It will default to version 2 so if it still fails you will most likely have to set it to version 1. If you want to know more about engine version read here: https://www.vaultproject.io/docs/secrets/kv/index.html 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.201340.1566206161000.5845.1566276240347%40Atlassian.JIRA.
[JIRA] (JENKINS-58970) Backwards compatibility broken with version 2.3.0 for KV1
Title: Message Title Joseph Petersen started work on JENKINS-58970 Change By: Joseph Petersen Status: Open In Progress 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.5833.1566274860345%40Atlassian.JIRA.
