Re: Issue with BluePageDecorator extension

['Gavin Mogan' via Jenkins Developers]

Blueocean as been pretty abandoned so the amount of people who know
how to work with it is pretty low. Also if I remember correctly the
extension system was never really setup so lots of stuff is hard
coded, not sure its extendable.

That being said, looking at your first screenshot, I think blueocean
is a react app that binds itself to #root, with absolute positioning.
You might be able to get it on top with z-index and absolute
positioning.

Gavin

On Wed, May 25, 2022 at 8:37 PM Anil Kumar  wrote:
>
> Hey everyone,
>
> I am using the BluePageDecorator extension point to add a custom header to 
> all the blue ocean pages in my Jenkins instance. I have included my custom 
> content in the header.jelly file as per the documentation.
>
> But the content is not being displayed or hidden on the build details page. I 
> can see the div appended to html but for some reason, it is not displayed. It 
> is being rendered correctly on the home page and job list page.
>
> I am attaching the screenshots and code snippets below.
>
> Can someone guide and suggest to me if I am doing anything incorrectly?
>
> Thanks in advance,
> Anil Kumar
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/e187d832-9acb-4dda-b308-65daa37a6910n%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_Dut%2BEjCjcuRi-vLpuuhUz%2BdAk1_rG_W5rXK%2BZ4pvDV0WHQ%40mail.gmail.com.

Re: Building an hpi file?

['Gavin Mogan' via Jenkins Developers]

>From the last time I looked into this, the recommendation is to use
https://github.com/uhafner/warnings-ng-plugin-devenv (which is linked
from one or more of the readmes)

On Wed, May 25, 2022 at 1:17 PM Simon Matthews
 wrote:
>
> I am trying to add another parser. The intent is that the warnings-ng plugin 
> will show (and use) my new additional parser and I believe that they way to 
> achieve that is through adding the parser to analysis-model.
>
> Simon
>
> On Wednesday, May 25, 2022 at 12:33:46 PM UTC-7 bma...@gmail.com wrote:
>>
>> analysis-model is a jar, not a plugin. So it will create a jar as expected.
>> It is used by other plugins I think (cannot check just now).
>>
>> What are you trying to achieve?
>>
>> Le mer. 25 mai 2022 à 21:18, Simon Matthews  a écrit :
>>>
>>> I am attempting to build a modified version of the analysis-model plugin.I 
>>> think that I need to create an hpi file which I can then install in my 
>>> jenkins installation, but if this is not correct, please tell me.
>>>
>>> It's not clear to me how to do this from the command line: I think it has 
>>> changed over time, so there are plenty of old pages that are now incorrect.
>>>
>>> I think that I need to use maven to build the "hpi:hpi" target, but this 
>>> may be wrong. In any case, attempts to do this result in an error: I have 
>>> tried other targets, such as "package" and "install". They appear to 
>>> complete the build successfully, but don't create an hpi file.
>>>
>>> Running:
>>> ~/bin/apache-maven-3.8.5/bin/mvn hpi:hpi
>>> results in:
>>> [ERROR] Failed to execute goal 
>>> org.jenkins-ci.tools:maven-hpi-plugin:3.29-rc1263.227a_29289ce3:hpi 
>>> (default-cli) on project analysis-model: Failed to determine Jenkins 
>>> version this plugin depends on. -> [Help 1]
>>> I have tried adding the following to my pom.xml file:
>>> 2.332.3
>>> but it doesn't help.
>>>
>>> What am I doing wrong?
>>>
>>> Simon
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups 
>>> "Jenkins Developers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to jenkinsci-de...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/549954d3-3d28-46dd-a3b8-2d450474c87an%40googlegroups.com.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/1a70187a-1ead-4607-bce9-acdcf2348819n%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DutiQnW8_X1w1F0qTR7VtWM%2BohjqU%2B_YCtp8tT7j06jXwQ%40mail.gmail.com.

Re: Building an hpi file?

[Simon Matthews]

I am trying to add another parser. The intent is that the warnings-ng 
plugin will show (and use) my new additional parser and I believe that they 
way to achieve that is through adding the parser to analysis-model. 

Simon

On Wednesday, May 25, 2022 at 12:33:46 PM UTC-7 bma...@gmail.com wrote:

> analysis-model is a jar, not a plugin. So it will create a jar as expected.
> It is used by other plugins I think (cannot check just now).
>
> What are you trying to achieve?
>
> Le mer. 25 mai 2022 à 21:18, Simon Matthews  a 
> écrit :
>
>> I am attempting to build a modified version of the analysis-model 
>> plugin.I think that I need to create an hpi file which I can then install 
>> in my jenkins installation, but if this is not correct, please tell me. 
>>
>> It's not clear to me how to do this from the command line: I think it has 
>> changed over time, so there are plenty of old pages that are now incorrect. 
>>
>> I think that I need to use maven to build the "hpi:hpi" target, but this 
>> may be wrong. In any case, attempts to do this result in an error: I have 
>> tried other targets, such as "package" and "install". They appear to 
>> complete the build successfully, but don't create an hpi file. 
>>
>> Running: 
>> ~/bin/apache-maven-3.8.5/bin/mvn hpi:hpi
>> results in:
>> [ERROR] Failed to execute goal 
>> org.jenkins-ci.tools:maven-hpi-plugin:3.29-rc1263.227a_29289ce3:hpi 
>> (default-cli) on project analysis-model: Failed to determine Jenkins 
>> version this plugin depends on. -> [Help 1]
>> I have tried adding the following to my pom.xml file:
>> 2.332.3
>> but it doesn't help. 
>>
>> What am I doing wrong? 
>>
>> Simon
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-de...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/549954d3-3d28-46dd-a3b8-2d450474c87an%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1a70187a-1ead-4607-bce9-acdcf2348819n%40googlegroups.com.

Re: Building an hpi file?

[Baptiste Mathus]

analysis-model is a jar, not a plugin. So it will create a jar as expected.
It is used by other plugins I think (cannot check just now).

What are you trying to achieve?

Le mer. 25 mai 2022 à 21:18, Simon Matthews  a
écrit :

> I am attempting to build a modified version of the analysis-model plugin.I
> think that I need to create an hpi file which I can then install in my
> jenkins installation, but if this is not correct, please tell me.
>
> It's not clear to me how to do this from the command line: I think it has
> changed over time, so there are plenty of old pages that are now incorrect.
>
> I think that I need to use maven to build the "hpi:hpi" target, but this
> may be wrong. In any case, attempts to do this result in an error: I have
> tried other targets, such as "package" and "install". They appear to
> complete the build successfully, but don't create an hpi file.
>
> Running:
> ~/bin/apache-maven-3.8.5/bin/mvn hpi:hpi
> results in:
> [ERROR] Failed to execute goal
> org.jenkins-ci.tools:maven-hpi-plugin:3.29-rc1263.227a_29289ce3:hpi
> (default-cli) on project analysis-model: Failed to determine Jenkins
> version this plugin depends on. -> [Help 1]
> I have tried adding the following to my pom.xml file:
> 2.332.3
> but it doesn't help.
>
> What am I doing wrong?
>
> Simon
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/549954d3-3d28-46dd-a3b8-2d450474c87an%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS5E-XJLxeTps6OgLZhpjh2cL0j1ZZtLTBZX%3DydYzAJMAg%40mail.gmail.com.

Re: Plugin Updates

['Jesse Glick' via Jenkins Developers]

On Wed, May 25, 2022 at 1:37 PM priya jagyasi 
wrote:

> Can anyone please let me know how much time it takes to have the plugin
> under 'Updates' in the Jenkins update center for any instance after the
> GitHub workflow release is completed successfully? Is it immediate or any
> approximate time?
>

Generally it should appear within the hour.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2UPhGZXFZ6xuoOkadv%2BkAVa_sH3V5w55aSbg%3D2Av0h4w%40mail.gmail.com.

Building an hpi file?

[Simon Matthews]

I am attempting to build a modified version of the analysis-model plugin.I 
think that I need to create an hpi file which I can then install in my 
jenkins installation, but if this is not correct, please tell me. 

It's not clear to me how to do this from the command line: I think it has 
changed over time, so there are plenty of old pages that are now incorrect. 

I think that I need to use maven to build the "hpi:hpi" target, but this 
may be wrong. In any case, attempts to do this result in an error: I have 
tried other targets, such as "package" and "install". They appear to 
complete the build successfully, but don't create an hpi file. 

Running: 
~/bin/apache-maven-3.8.5/bin/mvn hpi:hpi
results in:
[ERROR] Failed to execute goal 
org.jenkins-ci.tools:maven-hpi-plugin:3.29-rc1263.227a_29289ce3:hpi 
(default-cli) on project analysis-model: Failed to determine Jenkins 
version this plugin depends on. -> [Help 1]
I have tried adding the following to my pom.xml file:
2.332.3
but it doesn't help. 

What am I doing wrong? 

Simon

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/549954d3-3d28-46dd-a3b8-2d450474c87an%40googlegroups.com.

Re: 409 errr on plugin release

[priya jagyasi]

Thanks for the information.

On Wednesday, May 25, 2022 at 11:45:37 PM UTC+5:30 ga...@gavinmogan.com 
wrote:

> Be patient man. Not only do things take time to run but people have other 
> responsibilities than just Jenkins. Within 3 hours of a release things 
> should be fully updated.
>
> As for releasing, I don't think you can have ci releasing and manual 
> version numbers. Its one or the other
>
>
> On Wed., May 25, 2022, 11:12 a.m. priya jagyasi,  
> wrote:
>
>> I see that Github action released 1.038 version of plugin ~40 minutes ago 
>> here 
>> https://github.com/jenkinsci/lightstep-incident-response-plugin/releases/tag/1.038.va_c2181133b_79
>> .
>> However, on the plugins site, I still see 1.036 version 
>> https://plugins.jenkins.io/lightstep-incident-response/#documentation. 
>> Am I missing something? I believe if it is released from Github action, the 
>> plugin should have an updated version?
>>
>> On Wednesday, May 25, 2022 at 11:17:00 PM UTC+5:30 priya jagyasi wrote:
>>
>>> This 
>>> https://github.com/jenkinsci/lightstep-incident-response-plugin/pull/6 is 
>>> for fully automated versioning. In our plugin, we do not want fully 
>>> automated versioning. Would the pom file still need any correction to make 
>>> plugin CD enabled? 
>>>
>>> On Wednesday, May 25, 2022 at 1:22:35 AM UTC+5:30 Jesse Glick wrote:
>>>
 https://github.com/jenkinsci/lightstep-incident-response-plugin/pull/6

>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-de...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/4fa7eeff-1610-44cb-b98d-27b14d533345n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/daf0d9d7-bde9-4587-9147-98758790fa5an%40googlegroups.com.

Re: 409 errr on plugin release

['Gavin Mogan' via Jenkins Developers]

Be patient man. Not only do things take time to run but people have other
responsibilities than just Jenkins. Within 3 hours of a release things
should be fully updated.

As for releasing, I don't think you can have ci releasing and manual
version numbers. Its one or the other


On Wed., May 25, 2022, 11:12 a.m. priya jagyasi, 
wrote:

> I see that Github action released 1.038 version of plugin ~40 minutes ago
> here
> https://github.com/jenkinsci/lightstep-incident-response-plugin/releases/tag/1.038.va_c2181133b_79
> .
> However, on the plugins site, I still see 1.036 version
> https://plugins.jenkins.io/lightstep-incident-response/#documentation. Am
> I missing something? I believe if it is released from Github action, the
> plugin should have an updated version?
>
> On Wednesday, May 25, 2022 at 11:17:00 PM UTC+5:30 priya jagyasi wrote:
>
>> This
>> https://github.com/jenkinsci/lightstep-incident-response-plugin/pull/6 is
>> for fully automated versioning. In our plugin, we do not want fully
>> automated versioning. Would the pom file still need any correction to make
>> plugin CD enabled?
>>
>> On Wednesday, May 25, 2022 at 1:22:35 AM UTC+5:30 Jesse Glick wrote:
>>
>>> https://github.com/jenkinsci/lightstep-incident-response-plugin/pull/6
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/4fa7eeff-1610-44cb-b98d-27b14d533345n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_Duvi-HBLR_UZjy44ehor3NN2igbRgGaZpJAzMEku4nkCRQ%40mail.gmail.com.

Re: 409 errr on plugin release

[priya jagyasi]

I see that Github action released 1.038 version of plugin ~40 minutes ago 
here 
https://github.com/jenkinsci/lightstep-incident-response-plugin/releases/tag/1.038.va_c2181133b_79.
However, on the plugins site, I still see 1.036 version 
https://plugins.jenkins.io/lightstep-incident-response/#documentation. Am I 
missing something? I believe if it is released from Github action, the 
plugin should have an updated version?

On Wednesday, May 25, 2022 at 11:17:00 PM UTC+5:30 priya jagyasi wrote:

> This 
> https://github.com/jenkinsci/lightstep-incident-response-plugin/pull/6 is 
> for fully automated versioning. In our plugin, we do not want fully 
> automated versioning. Would the pom file still need any correction to make 
> plugin CD enabled? 
>
> On Wednesday, May 25, 2022 at 1:22:35 AM UTC+5:30 Jesse Glick wrote:
>
>> https://github.com/jenkinsci/lightstep-incident-response-plugin/pull/6
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/4fa7eeff-1610-44cb-b98d-27b14d533345n%40googlegroups.com.

Re: 409 errr on plugin release

[priya jagyasi]

This https://github.com/jenkinsci/lightstep-incident-response-plugin/pull/6 is 
for fully automated versioning. In our plugin, we do not want fully 
automated versioning. Would the pom file still need any correction to make 
plugin CD enabled? 

On Wednesday, May 25, 2022 at 1:22:35 AM UTC+5:30 Jesse Glick wrote:

> https://github.com/jenkinsci/lightstep-incident-response-plugin/pull/6
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/92409bf2-fb43-4831-86cb-07f5d8be0c6fn%40googlegroups.com.

Plugin Updates

[priya jagyasi]

Hi,

Can anyone please let me know how much time it takes to have the plugin 
under 'Updates' in the Jenkins update center for any instance after the 
GitHub workflow release is completed successfully? Is it immediate or any 
approximate time?

Thank you!

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/cf7d8327-df31-4ae9-b973-7ae26282bbbfn%40googlegroups.com.

Re: [Jenkins Docker Images] Request for maintainer access

[Basil Crow]

In case it needed to be said, +1 from me as well!

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjpDjGsqj4h0dM7JH0f4Q5kx6KOtu569TY2Wuqg%3Dv6bxOg%40mail.gmail.com.

Question about credential snapshots

[James Robson]

Hello, 

I need some help in understanding how the CredentialsSnapshotTaker works to 
pass a credential to an agent. I’m trying to update the 
hashicorp-vault-plugin  
to use credential snapshots to prevent access from agents but doing scm 
checkouts aren't working correctly and I can't tell why. You can look at my 
pr  to see 
the change being made.

Most of the credentials work successfully, but attempting to use the 
implementation of the ‘SSH username with private key’ or 'Username and 
Password' with the SCM checkout and git checkout steps will fail (see below 
for examples and the stack trace). However you can use the ssh key with the 
sshagent step and you can use the username+password in withCredentials. 
Looking at the error message and the log messages the scm and git steps are 
trying to access the credential from the agent without using a snapshot. 
Further after adding in some log messages it doesn't look like the 
CredentialsSnapshotTaker classes are ever being invoked. I have looked at 
other plugins using Credential snapshots including a similar change to the 
azure-keyvault plugin 
, which I 
assume works as intended, and I don't see what would make my changes 
different.


Can anyone provide information on how the CredentialsSnapshotTaker system 
is supposed to be used or what is different about the checkout steps 
compared to withCredentials?



This is being run with everything at the latest version:

   - jenkins 2.332.3
   - Pipeline: SCM step 400.v6b_89a_1317c9a_
   - SSH Agent 295.v9ca_a_1c7cc3a_a_
   - Git client 3.11.0
   - Git 4.11.3



The following pipeline will perform a checkout without issue:


sshagent(['my-ssh-key']) {

 sh 'git clone git@my-repo'

}



However the following step will cause a stacktrace:


git branch: 'master', credentialsId: 'my-ssh-key', url: 'git@my-repo'


java.lang.IllegalStateException: Jenkins.instance is missing. Read the 
documentation of Jenkins.getInstanceOrNull to see what you are doing wrong.

   at jenkins.model.Jenkins.get(Jenkins.java:808)

   at 
com.datapipe.jenkins.vault.credentials.common.VaultHelper.getVaultSecret(VaultHelper.java:36)

   at 
com.datapipe.jenkins.vault.credentials.common.VaultHelper.getVaultSecretKey(VaultHelper.java:97)

Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to agent

   at 
hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1784)

   at 
hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356)

   at hudson.remoting.Channel.call(Channel.java:1000)

   at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:143)

   at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native 
Method)

   at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

   at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

   at java.base/java.lang.reflect.Method.invoke(Method.java:566)

   at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:129)

   at com.sun.proxy.$Proxy85.execute(Unknown Source)

   at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:991)

   at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1234)

   at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1294)

   at 
org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:129)

   at 
org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:97)

   at 
org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:84)

   at 
org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)

   at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)

   at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)

   at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)

   at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)

Caused: java.lang.IllegalStateException

   at 
com.datapipe.jenkins.vault.credentials.common.VaultHelper.getVaultSecretKey(VaultHelper.java:108)

   at 
com.datapipe.jenkins.vault.credentials.common.AbstractVaultBaseStandardCredentials.getVaultSecretKeyValue(AbstractVaultBaseStandardCredentials.java:77)

   at 
com.datapipe.jenkins.vault.credentials.common.VaultSSHUserPrivateKeyImpl.getPrivateKey(VaultSSHUserPrivateKeyImpl.java:112)

   at 
com.datapipe.jenkins.vault.credentials.common.VaultSSHUserPrivateKeyImpl.getPrivateKeys(VaultSSHUserPrivateKeyImpl.java:121)

   at 

Re: [Jenkins Docker Images] Request for maintainer access

[Tim Jacomb]

+1

I've granted access, welcome aboard

On Wed, 25 May 2022 at 11:35, Mark Waite  wrote:

>
> On Wed, May 25, 2022 at 4:08 AM Damien Duportal wrote:
>
>> Hello dear contributors, maintainers, readers.
>>
>>
>> I'm writing this email to request a maintainer access (GitHub handle
>> "dduportal") to the following repositories:
>>
>> - https://github.com/jenkinsci/docker
>> - https://github.com/jenkinsci/docker-agent
>> - https://github.com/jenkinsci/docker-ssh-agent
>> - https://github.com/jenkinsci/docker-inbound-agent
>>
>>
>> The reason for this request are the following:
>>
>> - With the persona  of Jenkins Infrastructure officer and team member,
>> the ability to operate these repositories to ensure fast CI/CD process on
>> the infra are key (reality check: we always had maintainers whom did the
>> review work so we never were slowed down, but it would be a "plus")
>> - With the persona of contribuor who want to increase his area of
>> contribution:
>>   * I've already contributed to these repositories in the past years on
>> many topics (from build process to bugfix or features) and I plan to
>> propose more contribution in the upcomings weeks/months
>>   * I'm spending more personal time on helping users on their issues on
>> this area  and I also plan and commit to help more (triaging, writing JEP,
>> and helping more)
>>
>> Of course, this is a question that can be answered by YES or NO: it is
>> for the actual maintainers and Jenkins board and the community to decide
>> (and I would accept whatever answer is given of course without complaining).
>>
>>
> +1 from me to grant maintainer access to Damien for those repositories.
> My answer is YES
>
> Mark Waite
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFEW%3DSUngTF1NZhXn2757s0jeoqbXJYWb2EMJjbnP%3D%2Bvw%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bie-M84UJ18T9bxYue4X3AkWq8jiCttGGcsKPBaeJNA50w%40mail.gmail.com.

Re: [Jenkins Docker Images] Request for maintainer access

[Mark Waite]

On Wed, May 25, 2022 at 4:08 AM Damien Duportal wrote:

> Hello dear contributors, maintainers, readers.
>
>
> I'm writing this email to request a maintainer access (GitHub handle
> "dduportal") to the following repositories:
>
> - https://github.com/jenkinsci/docker
> - https://github.com/jenkinsci/docker-agent
> - https://github.com/jenkinsci/docker-ssh-agent
> - https://github.com/jenkinsci/docker-inbound-agent
>
>
> The reason for this request are the following:
>
> - With the persona  of Jenkins Infrastructure officer and team member, the
> ability to operate these repositories to ensure fast CI/CD process on the
> infra are key (reality check: we always had maintainers whom did the review
> work so we never were slowed down, but it would be a "plus")
> - With the persona of contribuor who want to increase his area of
> contribution:
>   * I've already contributed to these repositories in the past years on
> many topics (from build process to bugfix or features) and I plan to
> propose more contribution in the upcomings weeks/months
>   * I'm spending more personal time on helping users on their issues on
> this area  and I also plan and commit to help more (triaging, writing JEP,
> and helping more)
>
> Of course, this is a question that can be answered by YES or NO: it is for
> the actual maintainers and Jenkins board and the community to decide (and I
> would accept whatever answer is given of course without complaining).
>
>
+1 from me to grant maintainer access to Damien for those repositories.  My
answer is YES

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFEW%3DSUngTF1NZhXn2757s0jeoqbXJYWb2EMJjbnP%3D%2Bvw%40mail.gmail.com.

[Jenkins Docker Images] Request for maintainer access

[Damien Duportal]

Hello dear contributors, maintainers, readers.


I'm writing this email to request a maintainer access (GitHub handle 
"dduportal") to the following repositories:

- https://github.com/jenkinsci/docker
- https://github.com/jenkinsci/docker-agent
- https://github.com/jenkinsci/docker-ssh-agent
- https://github.com/jenkinsci/docker-inbound-agent


The reason for this request are the following:

- With the persona  of Jenkins Infrastructure officer and team member, the 
ability to operate these repositories to ensure fast CI/CD process on the 
infra are key (reality check: we always had maintainers whom did the review 
work so we never were slowed down, but it would be a "plus")
- With the persona of contribuor who want to increase his area of 
contribution:
  * I've already contributed to these repositories in the past years on 
many topics (from build process to bugfix or features) and I plan to 
propose more contribution in the upcomings weeks/months
  * I'm spending more personal time on helping users on their issues on 
this area  and I also plan and commit to help more (triaging, writing JEP, 
and helping more)

Of course, this is a question that can be answered by YES or NO: it is for 
the actual maintainers and Jenkins board and the community to decide (and I 
would accept whatever answer is given of course without complaining).


Cheers,

Damien DUPORTAL

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/43b0ec6d-4255-44d2-a9a0-c117ed97ba60n%40googlegroups.com.