Re: Spring Security upgrade from 5.x to 6.x

[Ivan Fernandez Calvo]

Please do it, I am waiting for this change to update the SAML plugin to the 
latest PAC4J version

On Saturday, May 11, 2024 at 8:48:51 AM UTC+2 timja...@gmail.com wrote:

> Sounds good to me
>
> On Sat, 11 May 2024 at 04:08, Mark Waite  wrote:
>
>>
>>
>> On Friday, May 10, 2024 at 12:51:46 PM UTC-6 Basil wrote:
>>
>> Based on my prototyping in JENKINS-73120, there is quite a bit of work 
>> to support Jetty 12 (even just EE 8 with javax imports), blocked on 
>> the requirement of Java 17. From my perspective the sooner we require 
>> Java 17, the better. Perhaps we can require Java 17 in weeklies two 
>> weeks earlier than planned, acknowledging that this creates two fewer 
>> choices for LTS selection. Thoughts? 
>>
>>
>> I like the idea.  It would mean that the LTS baseline selected for the
>> last Jenkins LTS to support Java 11 would need to be two weeks earlier,
>> but we've chosen LTS baselines that were not the most recent weekly
>> before.
>>
>> 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-de...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/450e7eff-2c7b-4aba-a10a-979aa7dba9a2n%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/1576c72f-d501-4930-b545-9361826d1516n%40googlegroups.com.

Re: Banned dependencies error compiling SAML plugin PR

[Ivan Fernandez Calvo]

I missed the actual error message between too much text

ERROR] Rule 3:
org.codehaus.mojo.extraenforcer.dependencies.EnforceBytecodeVersion

I will bump it to the latest 5.X and wait for Java 17 bytecode



On Tuesday, December 12, 2023 at 10:09:24 PM UTC+1 m...@basilcrow.com wrote:

> As of v6.x, pac4j requires Java 17 or newer. The Jenkins plugin
> development toolchain will not accept Java 17 bytecode as long as
> Jenkins core still supports Java 11. You will need to stay on v5.x of
> pac4j until around fall of next year when Jenkins requires Java 17 or
> newer.
>

-- 
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/9319a3df-2940-4848-bf66-0271a08d867dn%40googlegroups.com.

Re: Help upgrading acegi-security to spring-security

[Ivan Fernandez Calvo]

I have made recently the migration of the SAML plugin to Spring-security, 
it was not too hard, change imports and some Jenkins classes now change to 
whatever2, I did not have to change functionality

https://github.com/jenkinsci/saml-plugin/pull/261

El sábado, 22 de octubre de 2022 a las 17:23:21 UTC+2, steve.b...@gmail.com 
escribió:

> Hi everyone,
>
> Does anyone with acegi-/spring-security experience fancy helping out with 
> the https://github.com/jenkinsci/reverse-proxy-auth-plugin?
>
> As part of the modernisation we need to upgrade acegi security to spring 
> security and I have had an initial look at it but I think I'll need some 
> help.
>
> Any tips or suggestions are more than welcome.
>
> Steve
>

-- 
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/d3000692-f054-420b-bb24-d97ce1f38eecn%40googlegroups.com.

Re: Parent pom 4.43.1 message from validate?

[Ivan Fernandez Calvo]

I updated SAML, SSH build Agents, and trilead-api to that Jenkins of the 
parent pom without issues, these plugins are in BOM version 
1478.v81d3dc4f9a_43 I have noticed those plugins use 1500.ve4d05cd32975 
that is the latest
, maybe is related.


https://github.com/jenkinsci/saml-plugin/blob/main/pom.xml#L28
https://github.com/jenkinsci/ssh-slaves-plugin/blob/main/pom.xml#L8
https://github.com/jenkinsci/trilead-api-plugin/blob/main/pom.xml#L8
El martes, 19 de julio de 2022 a las 19:32:59 UTC+2, m...@basilcrow.com 
escribió:

> I do not have any mirrors defined in my ~/.m2/settings.xml file but I see 
> the problem in Text Finder (Maven 3.8.6, Java 17) with 
> mojohaus/extra-enforcer-rules#220 
>  and I do not 
> see the problem with that commit reverted.
>

-- 
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/a458afb9-872c-48fc-a191-78b7e7cb7c36n%40googlegroups.com.

Re: Need review of PR for jenkinsci/trilead-ssh2

[Ivan Fernandez Calvo]

Thank you for the PR, I am reviewing it, there is a couple of tests to 
check why they fail after the change, and you should add a unit test for 
the new feature.

El lunes, 27 de junio de 2022 a las 13:50:36 UTC+2, mike escribió:

> Hi,
> Not sure how to reach out to people involved in this repo.
>
> I have added support for below digests in jenkinsci 
> /*trilead-ssh2 
> * 
>
> add support for hmac-sha...@openssh.com hmac-sha2-256-etm@open… by mpet · 
> Pull Request #93 · jenkinsci/trilead-ssh2 (github.com)
>
>
> 
> Friendly reminder, anyone managing this repo Please review.
> @Matt Sicker do you still have access to repo?
>
> br,
>
> //mike
>
>

-- 
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/93122689-d18e-47f2-b44c-0f1ad4e82266n%40googlegroups.com.

Re: Something is killing my launcher after 90-100 seconds

[Ivan Fernandez Calvo]

finally, I found my ghost, it is not related to the launcher nor the 
remoting, there is a timeout of 180 seconds in the JenkinsRule, when this 
timeout happens usually see a message in logs informing that you reached 
that timeout, in my case the stop of Jenkins causes an IO exception in 
remoting and that message is not shown, it can be a good idea to inform 
about that timeout when the JenkinsRule starts.

It is possible to remove this timeout if you set the property 
*jenkins.test.timeout*


  
  
maven-surefire-plugin
  

  -1

  

  



El viernes, 10 de diciembre de 2021 a las 18:03:41 UTC+1, Ivan Fernandez 
Calvo escribió:

> the link to the test that fails is wrong, this is the test that fails 
> after 90-100 seconds
>
>
> https://github.com/kuisathaverat/ssh-slaves-plugin/blob/apache_mina/src/test/java/io/jenkins/plugins/sshbuildagents/ssh/agents/AgentRSA512ConnectionTest.java#L48
>
> El viernes, 10 de diciembre de 2021 a las 17:46:38 UTC+1, Ivan Fernandez 
> Calvo escribió:
>
>> Hi,
>>
>> I am implementing a new launcher based on the Apache Mina SSHD library, I 
>> can connect the Agent, I can launch jobs, and the agent is stable in jobs 
>> that run for hours. so far so good, but not, if the agent does not have IO 
>> something is killing the agent. In the beginning I thought that was 
>> something in the SSH connection implementation, but to discard that I have 
>> made some unit test that can be connected for more than 5 min without 
>> issues. then I though that was related to the pingThread because there were 
>> traces of it on the logs but finally I have discarded it too. So I can 
>> stabilise a SSH connection and open a channel but after 90-100 seconds of 
>> inactivity the channel is closed with and EOF error, the test always fail 
>> more or less at the same time.
>>
>> This is the test of the classes outside Jenkins 
>> https://github.com/kuisathaverat/ssh-slaves-plugin/blob/apache_mina/src/test/java/io/jenkins/plugins/sshbuildagents/ssh/agents/ClientRSA512ConnectionTest.java#L121
>>
>> This is the long connection test on Jenkins that fails after 90-100 
>> seconds 
>> https://github.com/kuisathaverat/ssh-slaves-plugin/blob/apache_mina/src/test/java/io/jenkins/plugins/sshbuildagents/ssh/agents/ClientRSA512ConnectionTest.java#L121
>>
>> this is the branch with the new launcher 
>> https://github.com/kuisathaverat/ssh-slaves-plugin/tree/apache_mina
>>
>> I am using Jenkins core 2.303
>>
>> These are the latest lines of the long in FINE level Jenkins logs, on the 
>> Agent there is no errors (it is also on FINE level).
>>
>>  Dec 10, 2021 5:16:38 PM 
>> org.apache.sshd.common.session.helpers.AbstractSession request
>> FINE: request(ClientSessionImpl[jenkins@localhost/127.0.0.1:55135]) 
>> request=keepal...@jenkins.io, timeout=59995ms, requestSeqNo=19333, 
>> result received=true
>> Dec 10, 2021 5:16:57 PM org.apache.sshd.common.util.logging.LoggingUtils 
>> error
>> SEVERE: pumpInputStream(ChannelExec[id=0, recipient=0
>> ]-ClientSessionImpl[jenkins@localhost/127.0.0.1:55135]) Caught 
>> IOException : Pipe broken
>> java.io.IOException: Pipe broken
>> at java.base/java.io.PipedInputStream.read(PipedInputStream.java:321)
>> at java.base/java.io.PipedInputStream.read(PipedInputStream.java:377)
>> at 
>> org.apache.sshd.client.channel.ChannelSession.securedRead(ChannelSession.java:203)
>> at 
>> org.apache.sshd.client.channel.ChannelSession.pumpInputStream(ChannelSession.java:171)
>> at 
>> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
>> at 
>> java.base/java.util.concurrent.FutureTask.run$$$capture(FutureTask.java:264)
>> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java)
>> at 
>> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
>> at 
>> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
>> at java.base/java.lang.Thread.run(Thread.java:829)
>>
>> Dec 10, 2021 5:16:57 PM 
>> org.apache.sshd.common.util.closeable.AbstractCloseable close
>> FINE: close(ChannelExec[id=0, recipient=0
>> ]-ClientSessionImpl[jenkins@localhost/127.0.0.1:55135]) Closing 
>> gracefully
>> Dec 10, 2021 5:16:57 PM org.apache.sshd.common.channel.AbstractChannel 
>> preClose
>> FINE: close(ChannelExec[id=0, recipient=0
>> ]-ClientSessionImpl[jenkins@localhost/127.0.0.1:55135]) no EOF sent
>> Dec 10, 2021 5:16:57 PM org.apache.sshd.common.channel.Window close
>> FINE: Closing Window[client/local](ChannelExec[id=0

Re: Something is killing my launcher after 90-100 seconds

[Ivan Fernandez Calvo]

the link to the test that fails is wrong, this is the test that fails after 
90-100 seconds

https://github.com/kuisathaverat/ssh-slaves-plugin/blob/apache_mina/src/test/java/io/jenkins/plugins/sshbuildagents/ssh/agents/AgentRSA512ConnectionTest.java#L48

El viernes, 10 de diciembre de 2021 a las 17:46:38 UTC+1, Ivan Fernandez 
Calvo escribió:

> Hi,
>
> I am implementing a new launcher based on the Apache Mina SSHD library, I 
> can connect the Agent, I can launch jobs, and the agent is stable in jobs 
> that run for hours. so far so good, but not, if the agent does not have IO 
> something is killing the agent. In the beginning I thought that was 
> something in the SSH connection implementation, but to discard that I have 
> made some unit test that can be connected for more than 5 min without 
> issues. then I though that was related to the pingThread because there were 
> traces of it on the logs but finally I have discarded it too. So I can 
> stabilise a SSH connection and open a channel but after 90-100 seconds of 
> inactivity the channel is closed with and EOF error, the test always fail 
> more or less at the same time.
>
> This is the test of the classes outside Jenkins 
> https://github.com/kuisathaverat/ssh-slaves-plugin/blob/apache_mina/src/test/java/io/jenkins/plugins/sshbuildagents/ssh/agents/ClientRSA512ConnectionTest.java#L121
>
> This is the long connection test on Jenkins that fails after 90-100 
> seconds 
> https://github.com/kuisathaverat/ssh-slaves-plugin/blob/apache_mina/src/test/java/io/jenkins/plugins/sshbuildagents/ssh/agents/ClientRSA512ConnectionTest.java#L121
>
> this is the branch with the new launcher 
> https://github.com/kuisathaverat/ssh-slaves-plugin/tree/apache_mina
>
> I am using Jenkins core 2.303
>
> These are the latest lines of the long in FINE level Jenkins logs, on the 
> Agent there is no errors (it is also on FINE level).
>
>  Dec 10, 2021 5:16:38 PM 
> org.apache.sshd.common.session.helpers.AbstractSession request
> FINE: request(ClientSessionImpl[jenkins@localhost/127.0.0.1:55135]) 
> request=keepal...@jenkins.io, timeout=59995ms, requestSeqNo=19333, result 
> received=true
> Dec 10, 2021 5:16:57 PM org.apache.sshd.common.util.logging.LoggingUtils 
> error
> SEVERE: pumpInputStream(ChannelExec[id=0, recipient=0
> ]-ClientSessionImpl[jenkins@localhost/127.0.0.1:55135]) Caught 
> IOException : Pipe broken
> java.io.IOException: Pipe broken
> at java.base/java.io.PipedInputStream.read(PipedInputStream.java:321)
> at java.base/java.io.PipedInputStream.read(PipedInputStream.java:377)
> at 
> org.apache.sshd.client.channel.ChannelSession.securedRead(ChannelSession.java:203)
> at 
> org.apache.sshd.client.channel.ChannelSession.pumpInputStream(ChannelSession.java:171)
> at 
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at 
> java.base/java.util.concurrent.FutureTask.run$$$capture(FutureTask.java:264)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java)
> at 
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at 
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:829)
>
> Dec 10, 2021 5:16:57 PM 
> org.apache.sshd.common.util.closeable.AbstractCloseable close
> FINE: close(ChannelExec[id=0, recipient=0
> ]-ClientSessionImpl[jenkins@localhost/127.0.0.1:55135]) Closing gracefully
> Dec 10, 2021 5:16:57 PM org.apache.sshd.common.channel.AbstractChannel 
> preClose
> FINE: close(ChannelExec[id=0, recipient=0
> ]-ClientSessionImpl[jenkins@localhost/127.0.0.1:55135]) no EOF sent
> Dec 10, 2021 5:16:57 PM org.apache.sshd.common.channel.Window close
> FINE: Closing Window[client/local](ChannelExec[id=0, recipient=0
> ]-ClientSessionImpl[jenkins@localhost/127.0.0.1:55135])
> Dec 10, 2021 5:16:57 PM org.apache.sshd.common.channel.Window close
> FINE: Closing Window[client/remote](ChannelExec[id=0, recipient=0
> ]-ClientSessionImpl[jenkins@localhost/127.0.0.1:55135])
> Dec 10, 2021 5:16:57 PM org.apache.sshd.common.channel.AbstractChannel 
> sendEof
> FINE: sendEof(ChannelExec[id=0, recipient=0
> ]-ClientSessionImpl[jenkins@localhost/127.0.0.1:55135]) 
> SSH_MSG_CHANNEL_EOF (state=Graceful)
> Dec 10, 2021 5:16:57 PM 
> org.apache.sshd.common.session.helpers.AbstractSession encode
> FINE: encode(ClientSessionImpl[jenkins@localhost/127.0.0.1:55135]) packet 
> #19334 sending command=96[SSH_MSG_CHANNEL_EOF] len=5
> Dec 10, 2021 5:16:57 PM org.apache.sshd.common.io.nio2.Nio2Session 
> writeBuffer
> FINE: writeBuffer(Nio2Session[local=/127.0.0.1:65447, remote=localhost/127
> .0.0.1:55135]) writing 68 bytes
> Dec 10, 202

Something is killing my launcher after 90-100 seconds

[Ivan Fernandez Calvo]

Hi,

I am implementing a new launcher based on the Apache Mina SSHD library, I 
can connect the Agent, I can launch jobs, and the agent is stable in jobs 
that run for hours. so far so good, but not, if the agent does not have IO 
something is killing the agent. In the beginning I thought that was 
something in the SSH connection implementation, but to discard that I have 
made some unit test that can be connected for more than 5 min without 
issues. then I though that was related to the pingThread because there were 
traces of it on the logs but finally I have discarded it too. So I can 
stabilise a SSH connection and open a channel but after 90-100 seconds of 
inactivity the channel is closed with and EOF error, the test always fail 
more or less at the same time.

This is the test of the classes outside 
Jenkins 
https://github.com/kuisathaverat/ssh-slaves-plugin/blob/apache_mina/src/test/java/io/jenkins/plugins/sshbuildagents/ssh/agents/ClientRSA512ConnectionTest.java#L121

This is the long connection test on Jenkins that fails after 90-100 seconds 
https://github.com/kuisathaverat/ssh-slaves-plugin/blob/apache_mina/src/test/java/io/jenkins/plugins/sshbuildagents/ssh/agents/ClientRSA512ConnectionTest.java#L121

this is the branch with the new 
launcher https://github.com/kuisathaverat/ssh-slaves-plugin/tree/apache_mina

I am using Jenkins core 2.303

These are the latest lines of the long in FINE level Jenkins logs, on the 
Agent there is no errors (it is also on FINE level).

 Dec 10, 2021 5:16:38 PM 
org.apache.sshd.common.session.helpers.AbstractSession request
FINE: request(ClientSessionImpl[jenkins@localhost/127.0.0.1:55135]) 
request=keepal...@jenkins.io, timeout=59995ms, requestSeqNo=19333, result 
received=true
Dec 10, 2021 5:16:57 PM org.apache.sshd.common.util.logging.LoggingUtils 
error
SEVERE: pumpInputStream(ChannelExec[id=0, recipient=0
]-ClientSessionImpl[jenkins@localhost/127.0.0.1:55135]) Caught IOException 
: Pipe broken
java.io.IOException: Pipe broken
at java.base/java.io.PipedInputStream.read(PipedInputStream.java:321)
at java.base/java.io.PipedInputStream.read(PipedInputStream.java:377)
at 
org.apache.sshd.client.channel.ChannelSession.securedRead(ChannelSession.java:203)
at 
org.apache.sshd.client.channel.ChannelSession.pumpInputStream(ChannelSession.java:171)
at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at 
java.base/java.util.concurrent.FutureTask.run$$$capture(FutureTask.java:264)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java)
at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)

Dec 10, 2021 5:16:57 PM 
org.apache.sshd.common.util.closeable.AbstractCloseable close
FINE: close(ChannelExec[id=0, recipient=0
]-ClientSessionImpl[jenkins@localhost/127.0.0.1:55135]) Closing gracefully
Dec 10, 2021 5:16:57 PM org.apache.sshd.common.channel.AbstractChannel 
preClose
FINE: close(ChannelExec[id=0, recipient=0
]-ClientSessionImpl[jenkins@localhost/127.0.0.1:55135]) no EOF sent
Dec 10, 2021 5:16:57 PM org.apache.sshd.common.channel.Window close
FINE: Closing Window[client/local](ChannelExec[id=0, recipient=0
]-ClientSessionImpl[jenkins@localhost/127.0.0.1:55135])
Dec 10, 2021 5:16:57 PM org.apache.sshd.common.channel.Window close
FINE: Closing Window[client/remote](ChannelExec[id=0, recipient=0
]-ClientSessionImpl[jenkins@localhost/127.0.0.1:55135])
Dec 10, 2021 5:16:57 PM org.apache.sshd.common.channel.AbstractChannel 
sendEof
FINE: sendEof(ChannelExec[id=0, recipient=0
]-ClientSessionImpl[jenkins@localhost/127.0.0.1:55135]) SSH_MSG_CHANNEL_EOF 
(state=Graceful)
Dec 10, 2021 5:16:57 PM 
org.apache.sshd.common.session.helpers.AbstractSession encode
FINE: encode(ClientSessionImpl[jenkins@localhost/127.0.0.1:55135]) packet #
19334 sending command=96[SSH_MSG_CHANNEL_EOF] len=5
Dec 10, 2021 5:16:57 PM org.apache.sshd.common.io.nio2.Nio2Session 
writeBuffer
FINE: writeBuffer(Nio2Session[local=/127.0.0.1:65447, remote=localhost/127.0
.0.1:55135]) writing 68 bytes
Dec 10, 2021 5:16:57 PM 
hudson.remoting.SynchronousCommandTransport$ReaderThread 
run
INFO: I/O error in channel ssh-agent-rsa512
java.io.IOException: Unexpected termination of the channel
at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:75)
Caused by: java.io.EOFException
at 
java.base/java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2872)
at 
java.base/java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3367)
at 
java.base/java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:936)
at java.base/java.io.ObjectInputStream.(ObjectInputStream.java:379)
at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49)
at hudson.remoting.Command.readFrom(Command.java:142)
at 

Re: ASM in core

[Ivan Fernandez Calvo]

Hi,

I would like to add an issue related to not bump the ASM library, I 
recently hit an issue with stapler (see 
https://groups.google.com/g/jenkinsci-dev/c/JppfFwqIrCU) and it is related 
to compile the plugin for JDK 11 only,
new plugins use new libraries and more and more libraries use JDK 11 
nowadays for obvious reasons. 
So bump the ASM version is something completely necessary. Break thing is 
fine and more when those things are 10 years old stuff, in general, the 
Jenkins Core has a few forked libraries that are a pain to maintain 
updated, most of them are 10 yo pains. Thus, I think it is a matter of 
making a damage control of the plugins affected by the change and fix those 
that are still maintained or in use, Do we know which plugins are affected 
by the change on ASM?

BTW the ASM/JNR/JNA update is part of the JEP-211 

 and JENKINS-40689  so 
stuff longtime ago exposed
El jueves, 10 de junio de 2021 a las 21:58:38 UTC+2, m...@basilcrow.com 
escribió:

> On Thu, Jun 10, 2021 at 11:28 AM Tim Jacomb  wrote:
> >
> > It would be good to see a more recent report given we’re on version 9 in 
> core to see if anything has changed in recent versions
>
> Great point, Tim. Core 2.273 shipped with ASM 5.0.3, prior to the
> upgrade of JNR (and therefore the accidental upgrade of ASM) in 2.274.
> Here are the differences between ASM 5.0.3 and ASM 9.1:
>
>
> https://diff.revapi.org/?groupId=org.ow2.asm=asm=5.0.3=9.1
>
> https://diff.revapi.org/?groupId=org.ow2.asm=asm-analysis=5.0.3=9.1
>
> https://diff.revapi.org/?groupId=org.ow2.asm=asm-commons=5.0.3=9.1
>
> https://diff.revapi.org/?groupId=org.ow2.asm=asm-tree=5.0.3=9.1
>
> https://diff.revapi.org/?groupId=org.ow2.asm=asm-util=5.0.3=9.1
>
> The library seems quite stable between 5.0.3 and 9.1. Apart from new
> classes and the addition of generics, nothing seems to have been
> removed or renamed. (Similarly, recent versions of Guava are more
> stable than older versions.)
>
> In any case, I doubt we would roll back the JNR changes made in 2.274
> at this point. For better or for worse, ASM 9.1 is here to stay as
> part of the core API, so we might as well own it in the short term.
> (In the long term, removing or hiding Guice/JNR and therefore
> Guava/ASM would be nice, of course.)
>

-- 
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/acdeb1a2-a126-45f8-bc4d-9e387fc05750n%40googlegroups.com.

Re: HELP NEEDED - Jenkins contributor summit on Jun 25

[Ivan Fernandez Calvo]

Hi,

I could help with some stuff before, during, and after the event, simply 
let me know what to do.

Thanks
El viernes, 4 de junio de 2021 a las 23:22:43 UTC+2, Oleg Nenashev escribió:

> Dear all,
>
> As you know, we will be organizing the Jenkins contributor summit on June 
> 25th (landing page ). 
> I would like to make it a quite big contributor event where we agree on 
> some key Jenkins topics, e.g. security or API/plugin deprecation/EoL 
> policy. There is also interest in contributing onboarding events and to 
> have joint sessions focused on interoperability and on end user 
> experiences.Full 
> coordination document 
> 
> .
>
> The event is in 3 weeks. The preparation was delayed by some professional 
> and personal events, and also the increased GSoC workload. There are a few 
> contributors who planned to dedicate time to help with hosting the event, 
> but unfortunately they will not be able to dedicate enough time. If we want 
> to organize a decent event, more organizers are needed! Beow you can find 
> several activities where help is needed, 
>
> Before the summit:
>
>- Finalizing the agenda
>- Coordinating the schedule with presenters
>- Finalizing the end users presentation agenda
>- Getting the event promoted in the community channels
>- Working with@Alyssa Tong and the CDF to deliver swag to key summit 
>contributors
>- Facilitating conversations
>- Coordinating hosting of the newcomer track. IIUC Mark will be no 
>longer able to drive that as we discussed with him initially
>
> During the event:
>
>- Hosting / Moderating the event
>- Moderating the breakout rooms
>- Speaking about projects, SIGs and their statuses
>
> After the event:
>
>- Processing and publishing recordings 
>- Writing a summary blogpost
>- Swag logistics
>- Capturing follow-ups on the Jenkins roadmap, creating follow-up tasks
>
> Please respond to this thread if you would be willing to dedicate some 
> time and to contribute to the event.Please feel free to comment and suggest 
> changes in the.coordination document 
> 
> .
>
> Thanks for your time,
> Oleg Nenashev
> Acting Jenkins Events Officer
>
>

-- 
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/0cf4a5dc-b8e9-4c0a-8d51-6239f36713f8n%40googlegroups.com.

Issues creating a ManagementLink on JDK 11

[Ivan Fernandez Calvo]

Hi,

I am moving some configuration I have (that is working) to a new section in 
the Manage Jenkins. I've adapted the code in the AWS Global configuration 
to my needs, but it did not work completely, I can see the configuration 
options but none of the checks URL works all launch the following exception 
when the page is loaded. after a while I track the issue to the JDK 11, if 
I use JDK 8 everything works but with JDK 11 it fails. Do you have any idea 
how to resolve it?

2021-05-29 11:57:27.759+ [id=28]WARNING 
h.ExpressionFactory2$JexlExpression#evaluate: Caught exception evaluating: 
h.calcCheckUrl(pattrs,  pattrs.checkUrl,descriptor,pattrs.field) in 
/jenkins/elasticStack/. Reason: java.lang.IllegalArgumentException
java.lang.IllegalArgumentException
at org.kohsuke.asm5.ClassReader.(ClassReader.java:170)
at org.kohsuke.asm5.ClassReader.(ClassReader.java:153)
at org.kohsuke.asm5.ClassReader.(ClassReader.java:424)
at 
org.kohsuke.stapler.ClassDescriptor$ASM.loadParametersFromAsm(ClassDescriptor.java:312)
at 
org.kohsuke.stapler.ClassDescriptor$ASM.access$000(ClassDescriptor.java:300)
at 
org.kohsuke.stapler.ClassDescriptor.loadParameterNames(ClassDescriptor.java:196)
at 
hudson.util.ReflectionUtils$MethodInfo.names(ReflectionUtils.java:122)
at 
hudson.util.ReflectionUtils$Parameter.name(ReflectionUtils.java:180)
at 
hudson.util.FormValidation$CheckMethod.findParameters(FormValidation.java:601)
at 
hudson.util.FormValidation$CheckMethod.(FormValidation.java:587)
at hudson.model.Descriptor.getCheckMethod(Descriptor.java:401)
at hudson.Functions.calcCheckUrl(Functions.java:1917)
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.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258)
at 
org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104)
at 
org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
at 
org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
at 
org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)
at 
org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)
at 
hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74)
at 
org.apache.commons.jelly.expression.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61)
at 
org.apache.commons.jelly.expression.ExpressionSupport.evaluateAsString(ExpressionSupport.java:46)
at org.apache.commons.jelly.tags.core.ExprTag.doTag(ExprTag.java:42)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at 
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at 
org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
at 
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at 
org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
at 
org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
at 
org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at 
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:100)
at 
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at 
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at 
org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at 
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:100)
at 
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at 
org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
at 

Re: External logs storage for Pipeline/FreeStyle jobs

[Ivan Fernandez Calvo]

I will continue working on my implementation of JEP-210 for pipelines the 
API is simple to implement and extend 
https://github.com/kuisathaverat/pipeline-filebeat-logs so far it works 
fine on a production-grade instance, there are a few details I want to 
change. For the JEP-207 I think I will not try to use something similar it 
seems too complex to simply send the logs to external storage, I will 
simply redirect the logs and that's it, we do not have too many FreeStyle 
jobs and we can convert them to pipelines.

El miércoles, 19 de mayo de 2021 a las 19:12:46 UTC+2, Oleg Nenashev 
escribió:

> >  The logstash plugin can forward logs to for both pipeline and freestyle 
> to elastic search and others. But it doesn't support to read the logs from 
> there to display in Jenkins, what it forwards is rather heavy weight and 
> for pipeline jobs not the complete output is transferred (all the output 
> from the pipeline core not coming from a step itself is missing, like the 
> first lines with what caused the build and the final line with the result)
>
> I had a PoC for pluggable log storage and the Logstash plugin in 2016... 
> We started this project but then I had to stop working on that due to the 
> reasons outside my control. FTR 
> https://speakerdeck.com/onenashev/jw2016-hackathon-external-build-logging-prototype-demo
>
> FWIW it is much easier to implement a push-only pluggable log storage than 
> one with visualization. In JEP-207 / JEP-210 Jesse and me designed a 
> seamless integration with runtime visualization support. It ended up being 
> a massive time overhead compared to be a push-only solution.
>
>
> On Saturday, May 15, 2021 at 2:12:42 PM UTC+2 Markus Winter wrote:
>
>> The logstash plugin can forward logs to for both pipeline and freestyle 
>> to elastic search and others.
>> But it doesn't support to read the logs from there to display in Jenkins, 
>> what it forwards is rather heavy weight and for pipeline jobs not the 
>> complete output is transferred (all the output from the pipeline core not 
>> coming from a step itself is missing, like the first lines with what caused 
>> the build and the final line with the result)
>>
>> There is an implementation for what you want to do at 
>> https://github.com/SAP/elasticsearch-logs-plugin (inspired by the 
>> cloudwatch logs plugin)
>>
>> This plugin was mainly implemented to forward the logs of a 
>> JenkinsFileRunner from inside a short living Kubernetes pod so it is 
>> available outside. It is partially generic as it has an extension point 
>> (similar to logstash plugin) and we implemented also forwarding to fluentd 
>> (that will then forward to Elastic Search, this has proven to be more 
>> robust in our scenario).
>> It can also read from ES, but performance is rather bad here. Also some 
>> plugins still rely on the log being available in the file system, so we 
>> decided to have both though this meant to copy code from the pipeline 
>> plugins.
>> It can also forward logs of Freestyle jobs.
>>
>> The plugin also provides eventing for pipeline steps and transfers much 
>> less data than the logstash plugin.
>>
>>
>>
>> Am 10.05.2021 um 18:43 schrieb Oleg Nenashev:
>>
>> Yes, JEP-207 was abandoned after, ehm some reorg at my company. Great to 
>> see my former teammates commenting in this thread :D
>>
>> JEP-207 was indeed abandoned, but there were pull requests submitted to 
>> the Jenkins core and reference implementations (see the JEP for links). We 
>> had some disagreements with Jesse on APIs, especially w.r.t splitting the 
>> Log Storage and the Log Browser extensions (I needed it for Logstash/ELK 
>> where there might be multiple browsing implementations). But overall the 
>> API work was ready for merge with @Beta annotations IMHO. Same goes to 
>> External Log Storage API plugin. Note that JEP-207 was designed not only 
>> for AbstractProject-alike jobs, but it also added foundations for external 
>> Task Logs which is also a good use-case for centralized log systems.
>>
>> The work could be definitely finished. As Jesse said, the most 
>> complicated part would be ensuring JEP-207 and JEP-210 interoperability 
>> without performance loss. Also there would be a major merge conflict if we 
>> recover the old PR I'd guess.
>>
>> If somebody is interested, I am interested to participate as much as my 
>> time allows. Spoiler alert: not so much
>>
>>
>>
>>
>>
>> On Monday, May 10, 2021 at 5:36:34 PM UTC+2 Jesse Glick wrote:
>>
>>> On Mon, May 10, 2021 at 11:11 AM kuisathaverat  
>>> wrote:
>>>
 it [is] only for pipelines so I have taken a look at JEP-207: External 
 Build Logging support in the Jenkins Core 
  
 but it seems abandoned

>>>
>>> Yes. Something like that could be resurrected if there is a need, with 
>>> https://javadoc.jenkins.io/plugin/workflow-api/org/jenkinsci/plugins/workflow/log/package-summary.html
>>>  
>>> reworked 

Re: JenkinsRule doesn't persist the data file, any hints?

[Ivan Fernandez Calvo]

we hit a similar issue testing JobDSL definitions, the workaround is to use 
a custom TestPluginManager that ignores the detached plugins from the war 
see 
https://issues.jenkins.io/browse/JENKINS-60295?focusedCommentId=400912=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-400912

El viernes, 27 de septiembre de 2019 a las 19:42:54 UTC+2, 
victormar...@gmail.com escribió:

> Thanks,
>
> That particular step doesn't fail in production but when using the 
> JenkinsRule. After debugging just a bit I think it was some kind of missing 
> plugin dependency. Although the stactrace makes the debug really hard though
>
> On Friday, 27 September 2019 15:44:26 UTC+1, Jesse Glick wrote:
>>
>> On Fri, Sep 27, 2019 at 6:28 AM Victor Martinez 
>>  wrote: 
>> > an exception which occurred: 
>> > in field 
>> org.jenkinsci.plugins.pipeline.modeldefinition.withscript.WithScriptScript.script
>>  
>>
>> > in object 
>> org.jenkinsci.plugins.pipeline.modeldefinition.agent.impl.LabelScript@37db0aae
>>  
>>
>> > in … 
>> > Caused: java.io.NotSerializableException: log 
>>
>> Sounds like you have some variable or field named `log` which is the 
>> problem. 
>>
>

-- 
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/134b4b90-c9df-4148-b6ed-ff0d21841302n%40googlegroups.com.

Re: java.lang.VerifyError: (class: com/thoughtworks/xstream/core/util/SerializationMembers ...

[Ivan Fernandez Calvo]

yep, I found the culprit, one dependency that I do not need

+--- org.jenkins-ci.plugins:job-dsl-core:1.77
|+--- org.codehaus.groovy:groovy-all:2.4.12 -> 2.5.14 (*)
|+--- xmlunit:xmlunit:1.4
|\--- org.jvnet.hudson:xstream:1.4.7-jenkins-1



El miércoles, 10 de febrero de 2021 a las 21:07:33 UTC+1, Jesse Glick 
escribió:

> On Wed, Feb 10, 2021 at 1:26 PM kuisathaverat  wrote:
>
>> I know it is because of the change of the XStream
>> but I dunno what I have to change. Any idea?
>>
>
> Maybe you have the old forked XStream in your test classpath somewhere?
>

-- 
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/c428b499-9dae-45f4-be6e-097bdcc04bf3n%40googlegroups.com.

Re: Jenkins 3.x

[Ivan Fernandez Calvo]

+1000 to considered those changes as a major change

El miércoles, 25 de noviembre de 2020 a las 17:37:21 UTC+1, James Nord 
escribió:

> Hi all,
>
> with the recent weeklies we have a couple of changes (Acegi 
> upgrade/table-to-div) that break compatibility in plugins.
>
> Whilst many open source plugins have been updated and made compatible with 
> the old and new version by the people making the changes (and compatability 
> layers have been added as far as possible), there can be closed source ones 
> that we have no sight of that can be broken.
>
> Given this is an API compatibility breakage, I am wondering why don't we 
> bump the version number to Jenkins 3.x  to signify the breaking API?
>
> Regards
>
> /James
>

-- 
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/3929b9b0-d36b-4eb7-bc46-81fc01e7c21en%40googlegroups.com.

Re: NTLM Authentication

[Ivan Fernandez Calvo]

I guess that it is because nobody has an interest in developing a plugin 
for NTLM authentication because there are better ways to authenticate 
against windows, for example, Active directory that has support for 
authentication and authorization, also NTLM is pretty old and insecure. If 
after all that you continue thinking to use it you can use an Apache HTTP 
server in front of Jenkins and configure there the NTLM authentication.

https://en.wikipedia.org/wiki/NT_LAN_Manage
https://docs.moodle.org/310/en/NTLM_authentication#APACHE_Configuration

https://plugins.jenkins.io/active-directory/

El lunes, 16 de noviembre de 2020 a las 16:55:36 UTC+1, chrisb...@gmail.com 
escribió:

>
> Hello everyone,
>
> I'd like to know why Jenkins does not consider NTLM authentication on 
> Windows.
>
> Many thanks.
>

-- 
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/d6fde3a9-ca08-48f1-ae77-2fbdc31b10e6n%40googlegroups.com.

Re: Base64 a string with pipeline?

[Ivan Fernandez Calvo]

We put an encode and decode steps on our shared pipeline library, so we do 
not need to whitelist anything

https://github.com/elastic/apm-pipeline-library/blob/master/vars/base64decode.groovy
https://github.com/elastic/apm-pipeline-library/blob/master/vars/base64encode.groovy
El viernes, 16 de octubre de 2020 a las 17:51:38 UTC+2, 
mikeyca...@gmail.com escribió:

> I've got a bunch of developers all looking to have me approve, what feels 
> like 20 different ways to base64 encode a string.
>
> Is there a common method already approved or a prefered way of doing it in 
> pipeline scripts?   
>
> Was thinking of writing a small plugin command just so everyone is on the 
> same page... but thought I'd ask before coding something like that up.
>

-- 
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/056a7ff0-1cce-4bb8-a3ca-16a4d11329f7n%40googlegroups.com.

Re: ANN: Agent Docker images renaming on April 12-13

[Ivan Fernandez Calvo]

sshd-agent sounds fine to me

-- 
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/a1b08b59-5072-4cbb-b5dd-2586c87f5c4e%40googlegroups.com.

Re: Proposal: Moving the plugin adoption labels from Wiki to GitHub topics

[Ivan Fernandez Calvo]

Sure, the badge is something additional,
 something that users can see when they go to the documentation, then they can 
decide 
if they want to use a plugin in adoption.

-- 
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/7e802140-b00c-4ccc-adcf-c84be95ab610%40googlegroups.com.

Re: PROPOSAL: Remove network discovery services

[Ivan Fernandez Calvo]

Swarm plugin has about 7000 installations, this is the potential Jenkins 
instances affected, I am agree to remove it from the core but I think that 
should be provided as a plugin, maybe the needed staff can be moved to the 
swarm plugin.

-- 
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/f02c1bff-41ef-4bce-bd9d-27b230d9fd68%40googlegroups.com.

Re: Proposal: Official Docker Image maintenance team (Jenkins and Agents)

[Ivan Fernandez Calvo]

I'd like to be involved also at least on the testing part

El martes, 10 de diciembre de 2019, 12:34:05 (UTC+1), Oleg Nenashev 
escribió:
>
> BTW, I suggest the following list of maintainers based on the recent 
> activity:
>
>- Mark Waite
>- Alex Earl
>- Carlos Sanchez
>- Oleg Nenashev
>- Baptiste Mathus
>- Olivier Vernin
>
> Alternative is to just keep all members of 
> https://github.com/orgs/jenkinsci/teams/docker/members though some 
> contributors are not active at the moment
>
> BR, Oleg
>
> On Tuesday, December 10, 2019 at 11:42:49 AM UTC+1, Mark Waite wrote:
>>
>> I would like that very much
>>
>> On Tue, Dec 10, 2019, 11:19 AM Oleg Nenashev  wrote:
>>
>>> Hi all,
>>>
>>> Right now we have a number of official packages for Docker:
>>>
>>>- https://github.com/jenkinsci/docker  
>>>- https://github.com/jenkinsci/docker-slave  
>>>- https://github.com/jenkinsci/docker-ssh-slave 
>>>- https://github.com/jenkinsci/docker-jnlp-slave 
>>>- https://github.com/jenkinsci/jnlp-agents  
>>>
>>> All these repositories have different teams which define permissions/. 
>>> In addition to that we have jenkinsci/docker and 
>>> jenkinsci/docker-packaging-team team which also grant permissions. It is 
>>> quite difficult to manage the repositories in the current state, and it is 
>>> difficult to request reviews.
>>>
>>> I suggest to keep things simple and just proceed with a single team for 
>>> the official packaging:
>>>
>>>- Introduce an official "docker-packaging-team" under umbrella of 
>>>Platform Special Interest group which currently manages Docker packaging
>>>- Cleanup existing teams, leave just one for all official Jenkins 
>>>master and agent mages. Plugin Docker packaging (e.g. Remoting over 
>>> Apache 
>>>Kafka, Swarm plugin) will not be affected
>>>- Update GitHub and DockerHub teams to reflect the changes (mostly 
>>>jenkins4eval which grants write permissions)  
>>>- Add new team to CODEOWNERS in all repos
>>>
>>> WDYT?
>>>
>>> Thanks in advance,
>>> Oleg
>>>
>>> -- 
>>> 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 jenkin...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCPBvAvsqC4nqpr2e%2BqBOo2BdMqa%3DY5%3Dx%2BhVO735YzX_w%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/a2eb969d-f874-47a0-9fcc-51ed874f2128%40googlegroups.com.

Re: Accessing PR head commit sha from a pipeline using branch source plugin

[Ivan Fernandez Calvo]

we faced the same problem a few months ago, we've resolved it by adding a 
calculated environment variable for more details see 
https://groups.google.com/forum/#!topic/jenkinsci-dev/Dus0VX6y04g 

-- 
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/ee8163ba-5f14-48f8-b888-0983d67e22f4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Working with distributed builds

[Ivan Fernandez Calvo]

There is a plugin that copies files in the workspace, that it is what you 
want see https://plugins.jenkins.io/config-file-provider

El domingo, 9 de junio de 2019, 22:04:50 (UTC+2), Rajeev Ranjan escribió:
>
> Hi team,
> I am stuck at end which currently I don't have clue how to proceed.
> I have a plugin which is having some powershell files as resources in the 
> jar (generated at build time). 
> During runtime 
>
>1. it extracts the plugin jar from $JENKINS_HOME to get powershell 
>files 
>2. execute it to perform business logic of the plugin on the project
>3. generates the output file in the provided path. 
>
> It works perfectly fine if it is only master.The problem here with this is 
> it fails in distributed architecture as it won't have . 
>
> What solution I can think of is to 
>
>1. copy the plugin to slave, 
>2. extract the files and execute the powershell files in slave 
>instance, 
>3. and copy back the output to master/slave as per input?
>
> I am not sure how to copy the files between master/slave, any reference 
> would be appreciated.
> Also I am not sure even if this would work, is this the correct way for 
> the whole procedure (extracting the powershell files from jar, copying 
> between slave/master and executing it in slave).
> Plugin: UiPath plugin 
> 
>
> Regards,
> Rajeev Ranjan
>

-- 
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/9356cfd1-ec1b-411f-aebe-b7a20d34a083%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multibranch pipeline overwrite GIT_COMMIT when merges the master branch

[Ivan Fernandez Calvo]

I have opened an improvement issue 
https://issues.jenkins-ci.org/browse/JENKINS-56341

-- 
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/0368b6e4-a391-4105-a9d5-3a90ca22e9c3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multibranch pipeline overwrite GIT_COMMIT when merges the master branch

[Ivan Fernandez Calvo]

It is a little odd but this function makes the trick, so now I can use a 
new environment variable GIT_BASE_COMMIT to reference the real commit 

```
def getBaseCommit(){
  def baseCommit = ''
  def latestCommit = sh(label: 'Get previous commit', script: "git 
rev-parse HEAD", returnStdout: true)?.trim()
  def previousCommit = sh(label: 'Get previous commit', script: "git 
rev-parse HEAD^", returnStdout: true)?.trim()
  if(env?.CHANGE_ID == null){
baseCommit = env.GIT_COMMIT
  } else if("${env.GIT_COMMIT}".equals("${latestCommit}")){
baseCommit = env.GIT_COMMIT
  } else {
baseCommit = previousCommit
  }
  env.GIT_BASE_COMMIT = baseCommit
  return baseCommit
}
```

-- 
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/ca060a72-eeb8-46d6-b148-e7258fb310d7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Multibranch pipeline overwrite GIT_COMMIT when merges the master branch

[Ivan Fernandez Calvo]

Hi,

We use multibranch pipelines for our project, it works pretty well and it 
is nice to have PRs tested merged with the master branch, we also use 
Blueocean for our UI, and here we have to use a workaround to make our UI 
user-friendly.
Our jobs spin 100-150 test in parallel, BO is not really user-friendly with 
that amount of parallel stages so we make groups and launch a downstream 
job for each group, at this point all OK, the problem starts when you try 
to pass the GIT_COMMIT
to the downstream job if the master branch has changed when the checkout 
make the merge, the resulting commit (GIT_COMMIT env variable) is not in 
the repo,so the downstream job cannot checkout the GIT_COMMIT and it fails. 
I can pass the GIT_BRANCH but I'd prefer to pass the commit sha1. I start 
to play with `git rev-list HEAD -4` and `git reflog -6` to see if always 
have the same pattern and try to grab the correct commit sha1, but I start 
thinking that should be a better way. 
Also, I can disable the merge and make it on the downstream job but I don't 
like it either. WDYT?

GIT_PREVIOUS_COMMIT also point to an existing commit so I cannot use it.

In this example, the PR head commit is 
`08da92d31512c4a0c24948bc80f911f83c075070`, but GIT_COMMIT points 
to'7c36975a772dbab59e20169a0ac01e60fb6db739' and GIT_PREVIOUS_COMMIT to 
'6cd1da59add5d188cad41b9cbdcd33f4a7241c63' none of those in the repo

```
using credential token
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/org/repo.git # timeout=10
Fetching without tags
Fetching upstream changes from https://github.com/org/repo.git
 > git --version # timeout=10
using GIT_ASKPASS to set credentials GitHub user @elasticmachine User + 
Personal Access Token
 > git fetch --no-tags --progress https://github.com/org/arepo.git 
+refs/pull/352/head:refs/remotes/origin/PR-352 
+refs/heads/master:refs/remotes/origin/master
Merging remotes/origin/master commit 
e067dce0923be39f9b48e721240cf26ee083ab9e into PR head commit 
08da92d31512c4a0c24948bc80f911f83c075070
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 08da92d31512c4a0c24948bc80f911f83c075070
 > git merge e067dce0923be39f9b48e721240cf26ee083ab9e # timeout=10
 > git rev-parse HEAD^{commit} # timeout=10
Merge succeeded, producing a620f8fbd54f038733b1b238d90c59ccf18f3fc1
Checking out Revision a620f8fbd54f038733b1b238d90c59ccf18f3fc1 (PR-352)
Commit message: "Merge commit 'e067dce0923be39f9b48e721240cf26ee083ab9e' 
into HEAD"
First time build. Skipping changelog.
> git checkout -f 08da92d31512c4a0c24948bc80f911f83c075070
> git merge e067dce0923be39f9b48e721240cf26ee083ab9e # timeout=10
> git rev-parse HEAD^{commit} # timeout=10
> git config core.sparsecheckout # timeout=10
> git checkout -f a620f8fbd54f038733b1b238d90c59ccf18f3fc1
> git rev-list --no-walk 6cd1da59add5d188cad41b9cbdcd33f4a7241c63 # 
timeout=10
```

```
[2019-02-28T19:36:16.610Z] export GIT_BRANCH='PR-352'
[2019-02-28T19:36:16.838Z] export 
GIT_COMMIT='7c36975a772dbab59e20169a0ac01e60fb6db739'
[2019-02-28T19:36:16.838Z] export 
GIT_PREVIOUS_COMMIT='6cd1da59add5d188cad41b9cbdcd33f4a7241c63'
```

I can grab `git HEAD -1` but I am not sure always would be correct because 
if there aren't changes on the master branch GIT_COMMIT is correct.

```
[2019-02-28T19:36:16.838Z] + git reflog -6
[2019-02-28T19:36:16.838Z] a620f8f HEAD@{0}: merge 
e067dce0923be39f9b48e721240cf26ee083ab9e: Merge made by the 'recursive' 
strategy.
[2019-02-28T19:36:16.838Z] 08da92d HEAD@{1}: checkout: moving from master 
to 08da92d31512c4a0c24948bc80f911f83c075070
```

```
[2019-02-28T19:36:16.838Z] + git rev-list HEAD -4
[2019-02-28T19:36:16.838Z] a620f8fbd54f038733b1b238d90c59ccf18f3fc1
[2019-02-28T19:36:16.838Z] 08da92d31512c4a0c24948bc80f911f83c075070
[2019-02-28T19:36:16.838Z] 6646f0310ea4e6e176faa178a6a2ecf3be11168b
[2019-02-28T19:36:16.838Z] 6ff5224c0892801c2632be855d91a38426677ba5
```

-- 
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/dfc013df-ae4c-4b2b-afeb-b9069a30fe2e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Listen executor/node events

[Ivan Fernandez Calvo]

Hi,

We have a custom implementation to provision Jenkins agents, it works 
pretty well and allow us to provision more than 400 and downscale when they 
finish. we have a known bug that happens when we spin more than 100 agents 
at the same time, the bug is that pipelines try to reuse an agent because 
the way we manage to put the agent offline and destroy (about 1-2% of 
times). In order to improve this, we are thinking about to listen to the 
executor events or the node/computer events but I did not find something 
that does not implies to modify some existing, the nodes are swarm nodes. 
other solution could be to make in some way those swarm agents some kind of 
one-shot agents. Have anyone any idea how we can approach this? 

-- 
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/08d86af8-ec92-41eb-adc9-b54f851f16fc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ssh-slaves plugin now uses trilead-api plugin instead trilead-ssh2 module

[Ivan Fernandez Calvo]

I will revert the change today

-- 
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/cfd35c0d-ea26-41f4-a1d0-76afbc12616d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

ssh-slaves plugin now uses trilead-api plugin instead trilead-ssh2 module

[Ivan Fernandez Calvo]

Hi,

I released ssh-slaves plugin two days ago and I break backward 
compatibility with plugins that use ssh-slaves as a dependency, this is 
because I start to use trilead-api plugin instead the trilead-ssh2 module 
from the core (similar to bouncycastle plugin), this change is motivated to 
be able to use different version of trilead than the core. Now is warned on 
the changelog and there is a section on the troubleshooting guide, in the 
next days I will manage to make PRs to every plugin that depends on 
ssh-slaves plugin to add the  trilead-api plugin dependency


  org.jenkins-ci.plugins
  trilead-api
  1.0.1






  
  

  org.jenkins-ci.tools
  maven-hpi-plugin
  
com.trilead.ssh2
  

  



https://github.com/jenkinsci/ssh-slaves-plugin/blob/master/CHANGELOG.md#1290-nov-18-2018
https://github.com/jenkinsci/ssh-slaves-plugin/blob/master/doc/TROUBLESHOOTING.md#1290-breaks-compatibility-with-cloud-plugins-that-do-not-use-trilead-api-plugin-as-dependency

-- 
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/bc244631-6971-4d55-ac38-65ee04629ffb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Add trilead-ssh2 component to the CI

[Ivan Fernandez Calvo]

Hi,

A few months ago the CI on DEV@Cloud was deactivated, so right now the 
trilead-ssh2 component does not have CI, and PR are not compiled and 
tested. I have tried to put it in the CI by creating a Jenkinsfile like we 
do with plugins but the component does not appear in the list of plugins in 
the CI. I have made the same with Trilead API plugin and it works thus I 
suppose that for component I have to make something different, Could 
anybody help me with this?

Regards 
Ivan

-- 
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/bcf9c987-35e6-49ee-9f8a-0fdbe3e91e78%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Amazon ECR plugin does to adoption

[Ivan Fernandez Calvo]

Hi all,

I am not interested to maintain this plugin anymore, so I put it on 
adoption.

-- 
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/cef68f16-9b01-44f4-a1b0-3aad83095258%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Subversion plugin goes to adoption

[Ivan Fernandez Calvo]

Hi all,

I am not interested to maintain this plugin anymore, so I put it on 
adoption.

-- 
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/a2a7b8dc-13ed-452a-ab88-7a9132b43547%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: trilead-ssh2 maintainer

[Ivan Fernandez Calvo]

Hi Oleg,

Yes, I still interested on it.

   - GitHub id: kuisathaverat
   - Jenkins infrastructure account id: ifernandezcalvo


El martes, 28 de agosto de 2018, 10:59:54 (UTC+2), Oleg Nenashev escribió:
>
> Ivan, after many pings I was unable to get the requested actions from the 
> maintainer (e.g. releasing pending PRs).
> Are you still interested in taking ownership?
> If yes, I am ready to transfer it.
>
> BR, Oleg
>
> On Tuesday, April 17, 2018 at 4:10:06 PM UTC+2, Oleg Nenashev wrote:
>>
>> Hi Ivan,
>>
>> Actually I have reached out to the current maintainer (Michael Clarke) in 
>> the private message.
>> And he said he is still planning to maintain this particular lib. So we 
>> cannot grant ownership right now.
>>
>> I will ping him
>>
>> BR, Oleg
>>
>>
>>
>> On Tue, Apr 17, 2018 at 3:52 PM, Ivan Fernandez Calvo <
>> kuisat...@gmail.com > wrote:
>>
>>> Hi,
>>>
>>> There is no new from current maintainers either in the pull requests nor 
>>> here, Can we move forward?
>>>
>>> -- 
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "Jenkins Developers" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/jenkinsci-dev/z-uIydVxqMM/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> jenkinsci-de...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/8a8389a8-d43f-412c-ad63-e211e6bae509%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/8a8389a8-d43f-412c-ad63-e211e6bae509%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>

-- 
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/65ed3d7b-03a0-4a01-bf00-bce3db133390%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ATH 1.60 release

[Ivan Fernandez Calvo]

thx a lot

El miércoles, 9 de mayo de 2018, 11:53:45 (UTC+2), ogondza escribió:
>
> On 2018-05-08 10:57, Ivan Fernandez Calvo wrote: 
> > I cannot make it by myself, I saw that used to be Oliver Gondza who make 
> > the release of the ATH, Oliver please, Could you release it? thanks in 
> > advance 
>
> Hey, 1.60 released a minute ago. 
>
> -- 
> oliver 
>

-- 
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/509a33a6-1ee2-488c-9daa-248b9c72aec3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ATH 1.60 release

[Ivan Fernandez Calvo]

I cannot make it by myself, I saw that used to be Oliver Gondza who make 
the release of the ATH, Oliver please, Could you release it? thanks in 
advance 

El lunes, 7 de mayo de 2018, 17:35:19 (UTC+2), Jesse Glick escribió:
>
> On Mon, May 7, 2018 at 10:23 AM, Ivan Fernandez Calvo 
> <kuisat...@gmail.com > wrote: 
> > Since a few months, there is not a new release of the ATH, Could be 
> possible 
> > to release the 1.60 version? 
>
> I think you can just go ahead and do it. Releases only matter for 
> third parties with custom test suites anyway; there is no effect on 
> the Jenkins project’s own test runs. 
>

-- 
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/5f8fdad5-a6f8-4866-b087-0fb8f9f2dce9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

ATH 1.60 release

[Ivan Fernandez Calvo]

Hi,

Since a few months, there is not a new release of the ATH, Could be 
possible to release the 1.60 version?

https://github.com/jenkinsci/acceptance-test-harness

Regards

Ivan Fernandez

-- 
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/54870c93-abfa-4b8f-b92d-0e76bd124c37%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: trilead-ssh2 maintainer

[Ivan Fernandez Calvo]

Hi,

There is no new from current maintainers either in the pull requests nor 
here, Can we move forward?

-- 
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/8a8389a8-d43f-412c-ad63-e211e6bae509%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Request access to join the Jenkins CERT team

[Ivan Fernandez Calvo]

Hi,

I would like to request access to join the Jenkins CERT team.


   - GitHub 2-factor auth enabled: yes
   - Signed CLA: https://github.com/jenkinsci/infra-cla/pull/58 
   - GitHub Username: kuisathaverat
   - IRC Nickname: kuisathaverat
   - Jenkins community username: ifernandezcalvo

-- 
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/3c486332-ebfe-40ed-b322-c0b9176c2dae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

trilead-ssh2 maintainer

[Ivan Fernandez Calvo]

Hi,

I recently take the maintainer of the SSH Agent Plugin, taking a look at 
the trilead-ssh2 PRs queue I saw that there is some PR pending of merge and 
I wonder if there is maintainer for this component and if could make sense 
to take the maintainer. if it is not maintainer I can take it.

-- 
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/48eeef34-4cb6-4b60-9154-d71389ed5022%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problem accessing com.cloudbees.jenkins.plugins.amazonecr.AmazonECSRegistryCredential from groovy

[Ivan Fernandez Calvo]

in that case why you do not use something like

node {
stage ('test'){
withCredentials([usernamePassword(credentialsId: 
'ecr:ap-northeast-1:a0312a7b-972e-44e2-b2a4-7edfc78b62be', passwordVariable: 
'PASSWORD', usernameVariable: 'USER')]) {
sh 'curl -u $USER:$PASSWORD http://whateverUrl'   
}
}
}


https://jenkins.io/doc/book/pipeline/getting-started/#snippet-generator

https://jenkins.io/doc/book/pipeline/getting-started/



El jueves, 20 de abril de 2017, 2:07:12 (UTC+2), Denis Boulas escribió:
>
> I want to do some API calls to registry in the pipeline with curl or 
> something else.
>
> 2017-04-20 1:51 GMT+03:00 Ivan Fernandez Calvo <kuisat...@gmail.com 
> >:
>
>> You are trying to get the password into a Pipeline, Why do you not use 
>> withCredentials step?
>> https://jenkins.io/doc/pipeline/steps/credentials-binding/
>>
>> --
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Jenkins Developers" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/jenkinsci-dev/3OCPmx6_R5w/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> jenkinsci-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/8d75287d-db7d-49f5-9cfd-3a15faaccae1%40googlegroups.com
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Best regards,
> Denis Boulas
>

-- 
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/c40c2636-25ff-42b2-bffe-161bc09fc19f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problem accessing com.cloudbees.jenkins.plugins.amazonecr.AmazonECSRegistryCredential from groovy

[Ivan Fernandez Calvo]

You are trying to get the password into a Pipeline, Why do you not use 
withCredentials step?
https://jenkins.io/doc/pipeline/steps/credentials-binding/

-- 
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/8d75287d-db7d-49f5-9cfd-3a15faaccae1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

zephyr-for-jira-test-management-plugin Compatibility with Pipeline

[Ivan Fernandez Calvo]

Hi,

I made a PR few months ago to make zephyr-for-jira-test-management-plugin 
compatible with Pipeline Plugin and it is still waiting for merge/close, Is 
this Plugin maintained? Are there any way to merge it an release? 

https://github.com/jenkinsci/zephyr-for-jira-test-management-plugin/pull/2

-- 
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/a2624bdb-2727-4b34-9554-e69a4c76667b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Adoption of Amazon ECR Plugin

[Ivan Fernandez Calvo]

Daniel,

Still I don't have the permissions to manage PR on SAML Plugin, Do I have 
to do something else?

El jueves, 27 de octubre de 2016, 16:53:41 (UTC+2), Daniel Beck escribió:
>
>
> > On 27.10.2016, at 16:51, Ben McCann  
> wrote: 
> > 
> > Thanks for taking over Daniel! 
>
> Forwarding the thanks to Ivan who's going to do the actual work -- I just 
> grant permissions ;-) 
>
>

-- 
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/9f6efa08-e77c-47d2-8a1b-5e3802050837%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Adoption of Amazon ECR Plugin

[Ivan Fernandez Calvo]

Daniel,

So now I am the maintainer of Amazon ECR Plugin and SAML Plugin , isn't it?

El jueves, 27 de octubre de 2016, 11:26:59 (UTC+2), Daniel Beck escribió:
>
>
> > On 13.10.2016, at 23:06, Ivan Fernandez Calvo <kuisat...@gmail.com 
> > wrote: 
> > 
> > Hi guys, 
> > 
> > I recently made a PR to Amazon ECR Plugin and I saw that it is in 
> adoption, Could be posible to adopt it? currently I do not maintain any 
> plugin but I made some contributions for few jenkinsci repositories 
> > 
> > GitHub id: kuisathaverat 
> > Jenkins infrastructure account id: ifernandezcalvo 
>
> Request looks good. I added you as committer and made you default 
> assignee. Please make sure to update wiki page etc., and (maybe?) batch 
> change assignee of all the plugin's issues from Nicolas to you. 
>
> Thanks for taking over! 
>
>

-- 
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/0b182d67-f7f4-4dd0-909a-aa77ed1021ee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Adoption of Amazon ECR Plugin

[Ivan Fernandez Calvo]

Also I would like to adopt SAML Plugin 
<https://wiki.jenkins-ci.org/display/JENKINS/SAML+Plugin>

El jueves, 13 de octubre de 2016, 23:06:24 (UTC+2), Ivan Fernandez Calvo 
escribió:
>
> Hi guys,
>
> I recently made a PR to Amazon ECR 
> <https://wiki.jenkins-ci.org/display/JENKINS/Amazon+ECR> Plugin and I saw 
> that it is in adoption, Could be posible to adopt it? currently I do not 
> maintain any plugin but I made some contributions for few jenkinsci 
> repositories
>
> GitHub id: kuisathaverat 
> <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fkuisathaverat=D=1=AFQjCNGIB8csOH5QvH33XqqSo3p0GTCSyg>
>  
> Jenkins infrastructure account id: ifernandezcalvo
>

-- 
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/b888fbdb-3d89-46c4-843c-407b4f6daf34%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Adoption of Amazon ECR Plugin

[Ivan Fernandez Calvo]

Hi guys,

I recently made a PR to Amazon ECR 
 Plugin and I saw 
that it is in adoption, Could be posible to adopt it? currently I do not 
maintain any plugin but I made some contributions for few jenkinsci 
repositories

GitHub id: kuisathaverat  
Jenkins infrastructure account id: ifernandezcalvo

-- 
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/f0f0f146-4979-44fe-a2c8-25e3da33ed18%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.