from:"kuisathaverat"

Banned dependencies error compiling SAML plugin PR

2023-12-12 Thread kuisathaverat

Hi,

I am updating the pac4j library in the SAML plugin, the enforcing
plugin tells me that there are some banned dependencies. I have
checked the banned dependencies at
https://github.com/jenkinsci/pom/blob/master/pom.xml#L683C18-L709 and
none of my dependencies is there (see the dependencies tree at the
end). I dunno if it could be related to the Shibboleth libraries that
are not in the maven repo, a long time ago I requested to mirror the
repo to do the same task
https://github.com/jenkins-infra/helpdesk/issues/2375 Do I have to
request it again? Is it a different thing?

[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  01:14 min
[INFO] Finished at: 2023-12-12T21:29:27+01:00
[INFO] 
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-enforcer-plugin:3.4.1:enforce
(display-info) on project saml:
[ERROR] Rule 3:
org.codehaus.mojo.extraenforcer.dependencies.EnforceBytecodeVersion
failed with message:
[ERROR] Found Banned Dependency: org.opensaml:opensaml-messaging-API:jar:5.0.0
[ERROR] Found Banned Dependency: org.pac4j:pac4j-saml:jar:6.0.0
[ERROR] Found Banned Dependency: org.pac4j:pac4j-core:jar:6.0.0
[ERROR] Found Banned Dependency: org.opensaml:opensaml-core-impl:jar:5.0.0
[ERROR] Found Banned Dependency: net.shibboleth:ship-security:jar:9.0.0
[ERROR] Found Banned Dependency: org.opensaml:opensaml-storage-impl:jar:5.0.0
[ERROR] Found Banned Dependency: net.shibboleth:ship-velocity:jar:9.0.0
[ERROR] Found Banned Dependency: org.pac4j:pac4j-javaee:jar:6.0.0
[ERROR] Found Banned Dependency: org.opensaml:opensaml-soap-impl:jar:5.0.0
[ERROR] Found Banned Dependency: org.opensaml:opensaml-saml-api:jar:5.0.0
[ERROR] Found Banned Dependency: org.opensaml:opensaml-soap-api:jar:5.0.0
[ERROR] Found Banned Dependency: org.opensaml:opensaml-profile-API:jar:5.0.0
[ERROR] Found Banned Dependency: org.opensaml:opensaml-security-impl:jar:5.0.0
[ERROR] Found Banned Dependency: net.shibboleth:shib-networking:jar:9.0.0
[ERROR] Found Banned Dependency: org.opensaml:opensaml-saml-impl:jar:5.0.0
[ERROR] Found Banned Dependency: org.opensaml:opensaml-xmlsec-api:jar:5.0.0
[ERROR] Found Banned Dependency: org.opensaml:opensaml-profile-impl:jar:5.0.0
[ERROR] Found Banned Dependency: org.opensaml:opensaml-core-API:jar:5.0.0
[ERROR] Found Banned Dependency: org.opensaml:opensaml-security-API:jar:5.0.0
[ERROR] Found Banned Dependency: org.opensaml:opensaml-storage-api:jar:5.0.0
[ERROR] Found Banned Dependency: net.shibboleth:shib-support:jar:9.0.0
[ERROR] Found Banned Dependency: org.opensaml:opensaml-xmlsec-impl:jar:5.0.0
[ERROR] Found Banned Dependency: org.opensaml:opensaml-messaging-impl:jar:5.0.0
[ERROR] Use 'mvn dependency:tree' to locate the source of the banned
dependencies.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with
the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
Dec 12, 2023 9:29:27 PM io.opentelemetry.sdk.trace.SdkTracerProvider shutdown
WARNING: Calling shutdown() multiple times.


Dependency tree

❯ mvn dependency:tree

[INFO] Scanning for projects...

[INFO]

[INFO] < org.jenkins-ci.plugins:saml >-

[INFO] Building SAML Plugin 4.99-SNAPSHOT

[INFO] [ hpi ]-

[INFO]

[INFO] --- maven-dependency-plugin:3.6.1:tree (default-cli) @ saml ---

[INFO] org.jenkins-ci.plugins:saml:hpi:4.99-SNAPSHOT

[INFO] +- 
io.jenkins.plugins:commons-lang3-api:jar:3.13.0-62.v7d18e55f51e2:compile

[INFO] |  \- org.apache.commons:commons-lang3:jar:3.13.0:compile

[INFO] +- 
io.jenkins.plugins:apache-httpcomponents-client-5-api:jar:5.2.3-1.0:compile

[INFO] |  +- org.apache.httpcomponents.core5:httpcore5:jar:5.2.4:compile

[INFO] |  +- org.apache.httpcomponents.core5:httpcore5-h2:jar:5.2.4:compile

[INFO] |  +- 
org.apache.httpcomponents.core5:httpcore5-reactive:jar:5.2.4:compile

[INFO] |  |  \- org.reactive streams:reactive-streams:jar:1.0.4:compile

[INFO] |  +- org.apache.httpcomponents.client5:httpclient5:jar:5.2.3:compile

[INFO] |  +- 
org.apache.httpcomponents.client5:httpclient5-cache:jar:5.2.3:compile

[INFO] |  \- 
org.apache.httpcomponents.client5:httpclient5-fluent:jar:5.2.3:compile

[INFO] +- io.jenkins.plugins:jaxb:jar:2.3.9-1:compile

[INFO] |  +- com.sun.xml.bind:jaxb-impl:jar:2.3.9:compile

[INFO] |  +- io.jenkins.plugins:javax-activation-api:jar:1.2.0-6:compile

[INFO] |  |  \- com.sun.activation:javax.activation:jar:1.2.0:compile

[INFO] |  \- javax.xml.bind:jaxb-api:jar:2.3.1:compile

[INFO] +-

Re: ASM in core

2021-06-11 Thread kuisathaverat

Robert, Which plugin are you talking about? Which version of the core is
that plugin required as minimum? there is another topic opened a few weeks
ago about deprecated plugins, a plugin should bump it core minimum required
version and update its dependencies often, if not it is not possible to
ensure the interoperability between plugins and with the core, to maintain
10 years of backward compatibility is not a good idea and block the project
to move forward.

El vie, 11 jun 2021 a las 11:19, Robert Sandell ()
escribió:

> Some historical context to know where we "old timers" are coming from :)
> https://kohsuke.org/2012/03/03/potd-package-renamed-asm/
>
> There are several times where I've needed to shade asm in plugins because
> of some transitive dependency. Las time I think it was a dependency on ASM7
> that blew up for me and I had to repackage that dependency to not break
> other plugins that depended on my plugin.
> That's why me and James and others are very very wary of bumping the asm
> dependencies, I think even more wary than for Guava, because there isn't
> enough code coverage due to how the classpath is during unit testing.
> I am not fully read up on the JNI situation so I can't comment on that
> situation, but it sounds like a damned if we do, damned if we don't kind of
> situation?
>
> /B
>
> On Friday, June 11, 2021 at 9:49:51 AM UTC+2 kuisat...@gmail.com wrote:
>
>> 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 a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/NhV_o6zxbzw/unsubscribe.
> To unsubscribe from this group and all its topics, 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/9c2d0cbb-2972-4e88-a51b-c53a5f39f5e4n%40googlegroups.com
> 
> .
>


-- 
Un Saludo
Iván Fernández Calvo
https://www.linkedin.com/in/iv%C3%A1n-fern%C3%A1ndez-calvo-21425033

-- 
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

External logs storage for Pipeline/FreeStyle jobs

2021-05-10 Thread kuisathaverat

Hi,

I've started a plugin to send pipeline logs to an Elasticsearch instance
using the described API in JEP-210: External log storage for Pipeline

It is based on the example implementation pipeline-cloudwatch-logs-plugin

The thing is that it only for pipelines so I have taken a look at JEP-207:
External Build Logging support in the Jenkins Core

but it seems abandoned, or it is what I understand reading the last comment
on jenkins#3575

Is that right? if so what is the best approach to implement a distributed
log system for FreeStyle jobs (and others), a ConsoleLogFilter?

-- 
Un Saludo
Iván Fernández Calvo

-- 
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/CAKo5Qrr8Yi%2BOZiN5aNE305iZJe7MZDDY1fPxj1MUbHnVDeVnbg%40mail.gmail.com.

Update SAMl plugin to use current Spring Security release

2021-02-12 Thread kuisathaverat

Hi,

Due to Upgrade Acegi Security to the latest Spring Security release(
https://issues.jenkins.io/browse/JENKINS-5303),
I updated the SAML plugin to use the new Sprint Security version and pac4j
3.9.0(https://issues.jenkins.io/browse/JENKINS-63350 and
https://github.com/jenkinsci/saml-plugin/pull/90) ,
this requires bumping the shibboleth library. Shibboleth library is not in
the maven central repository
due to security reasons (
https://wiki.shibboleth.net/confluence/display/DEV/Use+of+Maven+Central),
because of that, I have open an issue to mirror/copy the Shibboleth library
repository (https://issues.jenkins.io/browse/INFRA-2809)
The issue here is that I cannot merge and release the SAML plugin with that
change without resolve INFRA-2809
in one way or another, Could we find a solution for this?


-- 
Un Saludo
Iván Fernández Calvo
https://www.linkedin.com/in/iv%C3%A1n-fern%C3%A1ndez-calvo-21425033

-- 
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/CAKo5QroM6ixkFUpPFMeJ0xNyhcrr%3DP4bNN8%2BBSyvk%3DEp%2BS5etg%40mail.gmail.com.

SSHD module to plugin

2021-02-12 Thread kuisathaverat

Hi,

I have a bunch of PRs ready to move forward for a few months, these PRs are
to convert the SSHD Module to a plugin and after that bump the Apache Minda
sshd library.
We are using a really old Apache Minda sshd that is a security risk and
move the SSHD module outside of the core could help to have simpler Jenkins
instances without services you do not need/want.
Thus I would like to make progress and close stuff to start new things
related to that in the SSH Build Agents plugin. How we can manage this?

https://github.com/jenkinsci/sshd-module/pull/38
https://github.com/jenkinsci/jenkins/pull/5049
https://github.com/jenkinsci/sshd-module/pull/40

Update the Apache Minda sshd library
https://github.com/jenkinsci/sshd-module/pull/37

-- 
BR
Iván Fernández Calvo

-- 
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/CAKo5QrqCdukegd5A_FrEmxL3fxHO-7KZfMHsxkzufyB5bzxGiQ%40mail.gmail.com.

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

2021-02-10 Thread kuisathaverat

Hi,

We have a gradle build to test the jobDSL definitions, it works perfectly.
When we going to move the was version used to 2.266 it starts failing with
the following error. I know it is because of the change of the XStream
but I dunno what I have to change. Any idea?

java.lang.VerifyError: (class:
com/thoughtworks/xstream/core/util/SerializationMembers, method:
callReadResolve signature: (Ljava/lang/Object;)Ljava/lang/Object;)
Incompatible object argument for function call
at
hudson.util.RobustReflectionConverter.init(RobustReflectionConverter.java:98)
at hudson.util.XStream2.setupConverters(XStream2.java:218)
at com.thoughtworks.xstream.XStream.init(XStream.java:574)
at com.thoughtworks.xstream.XStream.init(XStream.java:496)
at com.thoughtworks.xstream.XStream.init(XStream.java:465)
at com.thoughtworks.xstream.XStream.init(XStream.java:411)
at com.thoughtworks.xstream.XStream.init(XStream.java:378)
at hudson.util.XStream2.init(XStream2.java:113)
at jenkins.model.Jenkins.clinit(Jenkins.java:5393)
at hudson.PluginManager.clinit(PluginManager.java:2113)
at org.jvnet.hudson.test.JenkinsRule.init(JenkinsRule.java:341)
at JobScriptsSpec.$spock_initializeSharedFields(JobScriptsSpec.groovy:30)

It fails to evaluate the JenkinsRule

import groovy.util.FileNameFinder
import javaposse.jobdsl.dsl.DslScriptLoader
import javaposse.jobdsl.plugin.JenkinsJobManagement
import org.junit.ClassRule
import org.jvnet.hudson.test.JenkinsRule
import spock.lang.Shared
import spock.lang.Specification
import spock.lang.Unroll

class JobScriptsSpec extends Specification {
@Shared
@ClassRule
JenkinsRule jenkinsRule = new JenkinsRule()

@Unroll
def 'test folder script #file.name'(File file) {
given:
def jobManagement = new JenkinsJobManagement(System.out, [:], new
File('.'))
def dslLoader = new DslScriptLoader(jobManagement)

when:
dslLoader.runScript(file.text)

then:
noExceptionThrown()

where:
file << new FileNameFinder().getFileNames('jobs',
'**/folder.groovy')
  .collect { new File(it) }
}
}

This is the exception in Jenkins

[Feb 10, 2021 6:50:59 PM jenkins.model.Jenkins 
SEVERE: Failed to load Jenkins.class
java.lang.VerifyError: (class:
com/thoughtworks/xstream/core/util/SerializationMembers, method:
callReadResolve signature: (Ljava/lang/Object;)Ljava/lang/Object;)
Incompatible object argument for function call
at
hudson.util.RobustReflectionConverter.(RobustReflectionConverter.java:98)
at hudson.util.XStream2.setupConverters(XStream2.java:218)
at com.thoughtworks.xstream.XStream.(XStream.java:574)
at com.thoughtworks.xstream.XStream.(XStream.java:496)
at com.thoughtworks.xstream.XStream.(XStream.java:465)
at com.thoughtworks.xstream.XStream.(XStream.java:411)
at com.thoughtworks.xstream.XStream.(XStream.java:378)
at hudson.util.XStream2.(XStream2.java:113)
at jenkins.model.Jenkins.(Jenkins.java:5393)
at hudson.PluginManager.(PluginManager.java:2113)
at org.jvnet.hudson.test.JenkinsRule.(JenkinsRule.java:341)
at
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:500)
at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:481)
at
org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
at
org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrapNoCoerce.callConstructor(ConstructorSite.java:105)
at
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:59)
at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:238)
at
org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:242)
at JobScriptsSpec.$spock_initializeSharedFields(JobScriptsSpec.groovy:30)
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:567)
at
org.spockframework.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:200)
at org.spockframework.runtime.model.MethodInfo.invoke(MethodInfo.java:113)
at
org.spockframework.runtime.BaseSpecRunner.invokeRaw(BaseSpecRunner.java:484)
at org.spockframework.runtime.BaseSpecRunner.invoke(BaseSpecRunner.java:467)
at
org.spockframework.runtime.BaseSpecRunner.doRunSharedInitializer(BaseSpecRunner.java:145)
at
org.spockframework.runtime.BaseSpecRunner$2.invoke(BaseSpecRunner.java:130)
at

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

2018-11-20 Thread kuisathaverat

Yes, I unmasked the trilead classes on 1.29.1, it resolved the issue.

El mar., 20 nov. 2018 a las 14:52, Mark Waite ()
escribió:

> The ssh-slaves plugin 1.29.1 allows my ssh agents to connect in Java 11
> testing.
>
> Thanks!
>
> On Tue, Nov 20, 2018 at 6:43 AM Mark Waite 
> wrote:
>
>> Thanks.  I thought there was something unique to Java 11 that caused all
>> my agents to be unable to connect to my Java test master when I started
>> with recent plugins yesterday.  I'm relieved it was not specific to Java 11.
>>
>> It looks like ssh-slaves 1.29.1 is the revert.  Is that correct?
>>
>> Thanks!
>> Mark Waite
>>
>> On Tue, Nov 20, 2018 at 3:40 AM Ivan Fernandez Calvo <
>> kuisathave...@gmail.com> wrote:
>>
>>> 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.
>>>
>>
>>
>> --
>> Thanks!
>> Mark Waite
>>
>
>
> --
> Thanks!
> Mark Waite
>
> --
> 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/Ba69w3M-jX0/unsubscribe.
> To unsubscribe from this group and all its topics, 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/CAO49JtF-Y%2B0JyRYD-oRh-ku5wx%2BfnLx-B%2BOxWB0%2BYekQwqiezA%40mail.gmail.com
> 
> .
> 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/CAKo5QroMa81qzbWoB5JyO-PtK0hOFgXNj_e-DYcWSyoQ2nF5JQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Add trilead-ssh2 component to the CI

2018-10-03 Thread kuisathaverat

thx Jesse, I will do

El mar., 2 oct. 2018 a las 17:42, Jesse Glick ()
escribió:

> On Tue, Oct 2, 2018 at 4:08 AM Ivan Fernandez Calvo
>  wrote:
> > 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.
>
> You will need to file an `INFRA` ticket. For context:
>
>
> https://issues.jenkins-ci.org/browse/INFRA-1356?focusedCommentId=320872=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-320872
>
> --
> 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/JAG_0xqQF6g/unsubscribe.
> To unsubscribe from this group and all its topics, 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/CANfRfr3WpvvOZ6%3D%2BQdDSyZXoK1ohGuPB-EMqPQpw%3Dh6ncLuYpA%40mail.gmail.com
> .
> 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/CAKo5QroKUZ53djFOUp-xpWT0kH%2BuVoS7SCVhamEeqZhUhzZbXg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Banned dependencies error compiling SAML plugin PR

Re: ASM in core

External logs storage for Pipeline/FreeStyle jobs

Update SAMl plugin to use current Spring Security release

SSHD module to plugin

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

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

Re: Add trilead-ssh2 component to the CI

8 matches

Site Navigation

Mail list logo

Footer information