[JIRA] (JENKINS-62196) Add changelog for 1.44
Title: Message Title Richard Bywater commented on JENKINS-62196 Re: Add changelog for 1.44 Also related, https://www.jenkins.io/security/advisory/2020-05-06/#SECURITY-988 points people at the plugin documentation for information about the new Production Mode but can't find any mention in README or CHANGELOG. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206128.1588834098000.23953.1588993860265%40Atlassian.JIRA.
[JIRA] (JENKINS-61937) hpi:run fails on Java 8 when the plugin depends on 2.230+
Title: Message Title Daniel Beck commented on JENKINS-61937 Re: hpi:run fails on Java 8 when the plugin depends on 2.230+ https://github.com/jenkinsci/maven-hpi-plugin/pull/181 proposed the change from above. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205817.1587074062000.23941.1588986480132%40Atlassian.JIRA.
[JIRA] (JENKINS-61937) hpi:run fails on Java 8 when the plugin depends on 2.230+
Title: Message Title Daniel Beck commented on JENKINS-61937 Re: hpi:run fails on Java 8 when the plugin depends on 2.230+ It seems like it (hpi:run starts with 3.15-SNAPSHOT in the plugin pom.xml despite 2.230), but no idea how to even write a test for it without keeping https://repo.jenkins-ci.org/JENKINS-61937 around indefinitely. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205817.1587074062000.23938.1588986180143%40Atlassian.JIRA.
[JIRA] (JENKINS-61937) hpi:run fails on Java 8 when the plugin depends on 2.230+
Title: Message Title Jesse Glick commented on JENKINS-61937 Re: hpi:run fails on Java 8 when the plugin depends on 2.230+ Sure. Does it work? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205817.1587074062000.23930.1588982160144%40Atlassian.JIRA.
[JIRA] (JENKINS-61818) AUTH: IllegalStateException: Singleton is called recursively returning different results
Title: Message Title Ankur commented on JENKINS-61818 Re: AUTH: IllegalStateException: Singleton is called recursively returning different results I got it on 2.222.1 LTS Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205668.1586157546000.23926.1588977120181%40Atlassian.JIRA.
[JIRA] (JENKINS-61818) AUTH: IllegalStateException: Singleton is called recursively returning different results
Title: Message Title Kirill Merkushev commented on JENKINS-61818 Re: AUTH: IllegalStateException: Singleton is called recursively returning different results Got that in 2.222.3 Downgrading to 2.222.1 helped. Until that, jobs were enable to start Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205668.1586157546000.23922.1588976340177%40Atlassian.JIRA.
[JIRA] (JENKINS-62214) Problem with Jenkins 2.222.x and BFA 1.25.1 (or 1.24.2)
Title: Message Title
Eloy Lafuente edited a comment on JENKINS-62214
Re: Problem with Jenkins 2.222.x and BFA 1.25.1 (or 1.24.2)
Reproduced installing Jenkins 2.222.1 from scratch:- Install Jenkins.- Only install BFA 1.25.1 plugin - Go to Management -> Configure System, add mongodb connection detail.- Test connection OK.- Save / apply changes.- Configuration is not saved.- Go to logs and got the very same error:{code}Could not start new knowledge base, reverting java.lang.NoSuchMethodError: com.fasterxml.jackson.databind.introspect.Annotated.getGenericType()Ljava/lang/reflect/Type; at org.mongojack.internal.MongoAnnotationIntrospector.getTypeForAnnotated(MongoAnnotationIntrospector.java:81) at org.mongojack.internal.MongoAnnotationIntrospector.findDeserializer(MongoAnnotationIntrospector.java:97) at com.fasterxml.jackson.databind.introspect.AnnotationIntrospectorPair.findDeserializer(AnnotationIntrospectorPair.java:665) at com.fasterxml.jackson.databind.deser.BasicDeserializerFactory.findDeserializerFromAnnotation(BasicDeserializerFactory.java:2092) at com.fasterxml.jackson.databind.deser.BasicDeserializerFactory.constructCreatorProperty(BasicDeserializerFactory.java:1019) at com.fasterxml.jackson.databind.deser.BasicDeserializerFactory._addExplicitPropertyCreator(BasicDeserializerFactory.java:634) at com.fasterxml.jackson.databind.deser.BasicDeserializerFactory._addExplicitAnyCreator(BasicDeserializerFactory.java:661) at com.fasterxml.jackson.databind.deser.BasicDeserializerFactory._addDeserializerConstructors(BasicDeserializerFactory.java:411) at com.fasterxml.jackson.databind.deser.BasicDeserializerFactory._constructDefaultValueInstantiator(BasicDeserializerFactory.java:283) at com.fasterxml.jackson.databind.deser.BasicDeserializerFactory.findValueInstantiator(BasicDeserializerFactory.java:224) at com.fasterxml.jackson.databind.deser.BeanDeserializerFactory.buildBeanDeserializer(BeanDeserializerFactory.java:220) at com.fasterxml.jackson.databind.deser.BeanDeserializerFactory.createBeanDeserializer(BeanDeserializerFactory.java:143) at com.fasterxml.jackson.databind.deser.DeserializerCache._createDeserializer2(DeserializerCache.java:414) at com.fasterxml.jackson.databind.deser.DeserializerCache._createDeserializer(DeserializerCache.java:349) at com.fasterxml.jackson.databind.deser.DeserializerCache._createAndCache2(DeserializerCache.java:264) at com.fasterxml.jackson.databind.deser.DeserializerCache._createAndCacheValueDeserializer(DeserializerCache.java:244) at com.fasterxml.jackson.databind.deser.DeserializerCache.findValueDeserializer(DeserializerCache.java:142) at com.fasterxml.jackson.databind.DeserializationContext.findRootValueDeserializer(DeserializationContext.java:491) at com.fasterxml.jackson.databind.ObjectMapper._findRootDeserializer(ObjectMapper.java:4669)Caused: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.mongojack.internal.util.JacksonAccessor.invoke(JacksonAccessor.java:149)Caused: java.lang.RuntimeException at org.mongojack.internal.util.JacksonAccessor.invoke(JacksonAccessor.java:153) at org.mongojack.internal.util.JacksonAccessor.findDeserializer(JacksonAccessor.java:44) at org.mongojack.internal.util.IdHandlerFactory.getIdHandlerForProperty(IdHandlerFactory.java:40) at org.mongojack.JacksonDBCollection.(JacksonDBCollection.java:138) at org.mongojack.JacksonDBCollection.wrap(JacksonDBCollection.java:236) at
[JIRA] (JENKINS-62214) Problem with Jenkins 2.222.x and BFA 1.25.1 (or 1.24.2)
Title: Message Title Eloy Lafuente updated an issue Jenkins / JENKINS-62214 Problem with Jenkins 2.222.x and BFA 1.25.1 (or 1.24.2) Change By: Eloy Lafuente Summary: Problem with Jenkins 2.222. 3 x and BFA 1.25.1 ( and or 1.24.2) Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206148.158571000.23917.1588973880382%40Atlassian.JIRA.
[JIRA] (JENKINS-62214) Problem with Jenkins 2.222.3 and BFA 1.25.1 (and 1.24.2)
Title: Message Title Eloy Lafuente commented on JENKINS-62214 Re: Problem with Jenkins 2.222.3 and BFA 1.25.1 (and 1.24.2) Reproduced installing Jenkins 2.222.1 from scratch: Install Jenkins. Only install BFA 1.25.1 Go to Management -> Configure System, add mongodb connection detail. Test connection OK. Save / apply changes. Go to logs and got the very same error: Could not start new knowledge base, reverting java.lang.NoSuchMethodError: com.fasterxml.jackson.databind.introspect.Annotated.getGenericType()Ljava/lang/reflect/Type; at org.mongojack.internal.MongoAnnotationIntrospector.getTypeForAnnotated(MongoAnnotationIntrospector.java:81) at org.mongojack.internal.MongoAnnotationIntrospector.findDeserializer(MongoAnnotationIntrospector.java:97) at com.fasterxml.jackson.databind.introspect.AnnotationIntrospectorPair.findDeserializer(AnnotationIntrospectorPair.java:665) at com.fasterxml.jackson.databind.deser.BasicDeserializerFactory.findDeserializerFromAnnotation(BasicDeserializerFactory.java:2092) at com.fasterxml.jackson.databind.deser.BasicDeserializerFactory.constructCreatorProperty(BasicDeserializerFactory.java:1019) at com.fasterxml.jackson.databind.deser.BasicDeserializerFactory._addExplicitPropertyCreator(BasicDeserializerFactory.java:634) at com.fasterxml.jackson.databind.deser.BasicDeserializerFactory._addExplicitAnyCreator(BasicDeserializerFactory.java:661) at com.fasterxml.jackson.databind.deser.BasicDeserializerFactory._addDeserializerConstructors(BasicDeserializerFactory.java:411) at com.fasterxml.jackson.databind.deser.BasicDeserializerFactory._constructDefaultValueInstantiator(BasicDeserializerFactory.java:283) at com.fasterxml.jackson.databind.deser.BasicDeserializerFactory.findValueInstantiator(BasicDeserializerFactory.java:224) at com.fasterxml.jackson.databind.deser.BeanDeserializerFactory.buildBeanDeserializer(BeanDeserializerFactory.java:220) at com.fasterxml.jackson.databind.deser.BeanDeserializerFactory.createBeanDeserializer(BeanDeserializerFactory.java:143) at com.fasterxml.jackson.databind.deser.DeserializerCache._createDeserializer2(DeserializerCache.java:414) at com.fasterxml.jackson.databind.deser.DeserializerCache._createDeserializer(DeserializerCache.java:349) at com.fasterxml.jackson.databind.deser.DeserializerCache._createAndCache2(DeserializerCache.java:264) at com.fasterxml.jackson.databind.deser.DeserializerCache._createAndCacheValueDeserializer(DeserializerCache.java:244) at com.fasterxml.jackson.databind.deser.DeserializerCache.findValueDeserializer(DeserializerCache.java:142) at com.fasterxml.jackson.databind.DeserializationContext.findRootValueDeserializer(DeserializationContext.java:491) at com.fasterxml.jackson.databind.ObjectMapper._findRootDeserializer(ObjectMapper.java:4669) Caused: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at
[JIRA] (JENKINS-61818) AUTH: IllegalStateException: Singleton is called recursively returning different results
Title: Message Title Ankur updated an issue Jenkins / JENKINS-61818 AUTH: IllegalStateException: Singleton is called recursively returning different results Change By: Ankur Attachment: Jenkins error.log Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205668.1586157546000.23908.1588972380331%40Atlassian.JIRA.
[JIRA] (JENKINS-61818) AUTH: IllegalStateException: Singleton is called recursively returning different results
Title: Message Title Ankur commented on JENKINS-61818 Re: AUTH: IllegalStateException: Singleton is called recursively returning different results I am seeing same errors in log. Attaching full log.Jenkins error.log Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205668.1586157546000.23910.1588972380374%40Atlassian.JIRA.
[JIRA] (JENKINS-62211) Justin Harringa asked me to open this: pipeline triggers not working using https://github.com/jenkinsci/config-driven-pipeline-plugin
Title: Message Title
Justin Harringa edited a comment on JENKINS-62211
Re: Justin Harringa asked me to open this: pipeline triggers not working using https://github.com/jenkinsci/config-driven-pipeline-plugin
[~funeeldy] ah! Actually, I believe what is going on here is that the template may not actually be in the actual job workspace since we attempt to do a lightweight checkout (so {{getWorkSpace()}} will likely return {{null}} or something unexpected - I think that's your declared method if I understand correctly). Would you be able to utilize {{env.BRANCH_NAME}} instead of {{getWorkSpace()}} or perhaps [one of the other envs|https://docs.cloudbees.com/docs/admin-resources/latest/automating-with-jenkinsfile/working-with-the-env] ({{JOB_NAME}} may be another candidate depending on whether this is a MultiBranch setup or another root job type) ?
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206145.151564000.23905.1588971240153%40Atlassian.JIRA.
[JIRA] (JENKINS-62211) Justin Harringa asked me to open this: pipeline triggers not working using https://github.com/jenkinsci/config-driven-pipeline-plugin
Title: Message Title
Justin Harringa commented on JENKINS-62211
Re: Justin Harringa asked me to open this: pipeline triggers not working using https://github.com/jenkinsci/config-driven-pipeline-plugin
marlene cote ah! Actually, I believe what is going on here is that the template may not actually be in the actual job workspace since we attempt to do a lightweight checkout (so getWorkSpace() will likely return null or something unexpected - I think that's your declared method if I understand correctly). Would you be able to utilize env.BRANCH_NAME instead of getWorkSpace() or perhaps one of the other envs{{}}?
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206145.151564000.23901.1588971120206%40Atlassian.JIRA.
[JIRA] (JENKINS-62211) Justin Harringa asked me to open this: pipeline triggers not working using https://github.com/jenkinsci/config-driven-pipeline-plugin
Title: Message Title
Justin Harringa edited a comment on JENKINS-62211
Re: Justin Harringa asked me to open this: pipeline triggers not working using https://github.com/jenkinsci/config-driven-pipeline-plugin
[~funeeldy] ah! Actually, I believe what is going on here is that the template may not actually be in the actual job workspace since we attempt to do a lightweight checkout (so {{getWorkSpace()}} will likely return {{null}} or something unexpected - I think that's your declared method if I understand correctly). Would you be able to utilize {{env.BRANCH_NAME}} instead of {{getWorkSpace()}} or perhaps [one of the other envs|https://docs.cloudbees.com/docs/admin-resources/latest/automating-with-jenkinsfile/working-with-the-env] {{}} ?
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206145.151564000.23903.1588971120435%40Atlassian.JIRA.
[JIRA] (JENKINS-61937) hpi:run fails on Java 8 when the plugin depends on 2.230+
Title: Message Title
Daniel Beck commented on JENKINS-61937
Re: hpi:run fails on Java 8 when the plugin depends on 2.230+
Tentative fix idea, WDYT?
$ git diff
diff --git a/src/main/java/org/jenkinsci/maven/plugins/hpi/MavenArtifact.java b/src/main/java/org/jenkinsci/maven/plugins/hpi/MavenArtifact.java
index e5b4c0c..bffa23e 100644
--- a/src/main/java/org/jenkinsci/maven/plugins/hpi/MavenArtifact.java
+++ b/src/main/java/org/jenkinsci/maven/plugins/hpi/MavenArtifact.java
@@ -55,6 +55,9 @@ public class MavenArtifact implements Comparable {
* Is this a Jenkins plugin?
*/
public boolean isPlugin() throws IOException {
+if ("system".equals(getScope())) {
+return false;
+}
String type = getResolvedType();
return type.equals("hpi") || type.equals("jpi");
}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205817.1587074062000.23890.1588968480185%40Atlassian.JIRA.
[JIRA] (JENKINS-62209) classMethod FAILED
Title: Message Title T I commented on JENKINS-62209 Re: classMethod FAILED Liam Newman Jenkins 2.234 Pipeline Model Definition 1.6.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206143.150587000.23885.1588968300179%40Atlassian.JIRA.
[JIRA] (JENKINS-62209) classMethod FAILED
Title: Message Title Liam Newman commented on JENKINS-62209 Re: classMethod FAILED T I What versions of Jenkins and Pipeline Model Definition are you using? What pipeline are you running? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206143.150587000.23874.1588967100600%40Atlassian.JIRA.
[JIRA] (JENKINS-62063) BlueOcean UI is broken due to ClassCastException
Title: Message Title Liam Newman commented on JENKINS-62063 Re: BlueOcean UI is broken due to ClassCastException Trying simple work around: https://github.com/jenkinsci/blueocean-plugin/pull/2076/ . Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205962.1588001733000.23871.1588966980181%40Atlassian.JIRA.
[JIRA] (JENKINS-53954) Cannot connect to slave/agent Linux anymore
Title: Message Title Matt Sicker commented on JENKINS-53954 Re: Cannot connect to slave/agent Linux anymore Were you using the "uploaded file on Jenkins master" for storing your key? That option was removed a while ago due to security issues. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194557.1539073377000.23864.1588964880248%40Atlassian.JIRA.
[JIRA] (JENKINS-44772) User Scoped credentials are not used by the "withCredentials" pipeline step
Title: Message Title Matt Sicker commented on JENKINS-44772 Re: User Scoped credentials are not used by the "withCredentials" pipeline step Sounds like this feature may be implemented by JENKINS-58170? It works for withCredentials at least, though I've found other plugins that don't work properly with this new feature. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182827.1496920844000.23842.1588963200540%40Atlassian.JIRA.
[JIRA] (JENKINS-58967) Credentials not available after upgrade to LTS 2.176.2
Title: Message Title Matt Sicker resolved as Not A Defect Sounds like this wasn't a regression then? Jenkins / JENKINS-58967 Credentials not available after upgrade to LTS 2.176.2 Change By: Matt Sicker Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-61430) Credentials 2.31 dramatically slows lookups
Title: Message Title Matt Sicker commented on JENKINS-61430 Re: Credentials 2.31 dramatically slows lookups I don't see any relevant changes in the credentials plugin. Perhaps this is a regression in the kubernetes credentials plugin? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205108.1583932048000.23834.1588962900130%40Atlassian.JIRA.
[JIRA] (JENKINS-61937) hpi:run fails on Java 8 when the plugin depends on 2.230+
Title: Message Title Jesse Glick commented on JENKINS-61937 Re: hpi:run fails on Java 8 when the plugin depends on 2.230+ This clearly looks like a case of maven-hpi-plugin being insufficiently robust. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205817.1587074062000.23832.1588962540198%40Atlassian.JIRA.
[JIRA] (JENKINS-61937) hpi:run fails on Java 8 when the plugin depends on 2.230+
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-61937 hpi:run fails on Java 8 when the plugin depends on 2.230+ Change By: Jesse Glick Labels: lts-candidate regression Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205817.1587074062000.23830.1588962480160%40Atlassian.JIRA.
[JIRA] (JENKINS-61937) hpi:run fails on Java 8 when the plugin depends on 2.230+
Title: Message Title Daniel Beck reopened an issue Jenkins / JENKINS-61937 hpi:run fails on Java 8 when the plugin depends on 2.230+ Change By: Daniel Beck Resolution: Not A Defect Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205817.1587074062000.23823.1588961881217%40Atlassian.JIRA.
[JIRA] (JENKINS-61937) hpi:run fails on Java 8 when the plugin depends on 2.230+
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-61937 hpi:run fails on Java 8 when the plugin depends on 2.230+ Change By: Daniel Beck Component/s: core Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205817.1587074062000.23817.1588961881009%40Atlassian.JIRA.
[JIRA] (JENKINS-61937) hpi:run fails on Java 8 when the plugin depends on 2.230+
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-61937 hpi:run fails on Java 8 when the plugin depends on 2.230+ Change By: Daniel Beck Priority: Blocker Minor Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205817.1587074062000.23820.1588961881127%40Atlassian.JIRA.
[JIRA] (JENKINS-61937) hpi:run fails on Java 8 when the plugin depends on 2.230+
Title: Message Title Daniel Beck assigned an issue to Unassigned Jenkins / JENKINS-61937 hpi:run fails on Java 8 when the plugin depends on 2.230+ Change By: Daniel Beck Assignee: Daniel Beck Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205817.1587074062000.23814.1588961880946%40Atlassian.JIRA.
[JIRA] (JENKINS-61937) hpi:run fails on Java 8 when the plugin depends on 2.230+
Title: Message Title Daniel Beck updated JENKINS-61937 Jenkins / JENKINS-61937 hpi:run fails on Java 8 when the plugin depends on 2.230+ Change By: Daniel Beck Status: Reopened Open Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205817.1587074062000.23825.1588961881250%40Atlassian.JIRA.
[JIRA] (JENKINS-61937) hpi:run fails on Java 8 when the plugin depends on 2.230+
Title: Message Title
Daniel Beck updated an issue
Jenkins / JENKINS-61937
hpi:run fails on Java 8 when the plugin depends on 2.230+
Change By:
Daniel Beck
[https://github.com/jenkinsci/jenkins/pull/3947/files#r408456990] Steps to reproduce:Use the following {{~/.m2/settings.xml}}:{noformat} xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd"> cert-snapshots trueJENKINS-61937 https://repo.jenkins-ci.org/JENKINS-61937/ true true {noformat}The specified repository is configured to always return 401 or 403 for all resolutions due to referencing a repository no non-admin user has access to.Result when building current matrix-auth-plugin with a patched 2.230 core dependency:{noformat}[INFO] --- maven-hpi-plugin:3.12:run (default-cli) @ matrix-auth ---[INFO] Logging initialized @7418ms to org.eclipse.jetty.util.log.Slf4jLog[INFO] Generating /Users/danielbeck/Repositories/github.com/daniel-beck/matrix-auth-plugin/work/plugins/matrix-auth.hplDownloading from JENKINS-61937: https://repo.jenkins-ci.org/JENKINS-61937/com/sun/tools/1.8.0/tools-1.8.0.pom[WARNING] Error resolving project artifact: Could not transfer artifact com.sun:tools:pom:1.8.0 from/to JENKINS-61937 (https://repo.jenkins-ci.org/JENKINS-61937/): Not authorized for project com.sun:tools:jar:1.8.0[INFO] Copying dependency Jenkins plugin /Users/danielbeck/.m2/repository/org/jenkins-ci/plugins/structs/1.19/structs-1.19.hpi[INFO] Copying dependency Jenkins plugin /Users/danielbeck/.m2/repository/org/jenkins-ci/plugins/workflow/workflow-multibranch/2.10/workflow-multibranch-2.10.hpi[INFO] Copying dependency Jenkins plugin /Users/danielbeck/.m2/repository/org/jenkins-ci/plugins/workflow/workflow-job/2.7/workflow-job-2.7.hpi[INFO] Copying dependency Jenkins plugin /Users/danielbeck/.m2/repository/org/jenkins-ci/plugins/job-dsl/1.76/job-dsl-1.76.hpi[INFO] Copying dependency Jenkins plugin /Users/danielbeck/.m2/repository/org/jenkins-ci/plugins/branch-api/2.0.0/branch-api-2.0.0.hpi[INFO] [INFO] BUILD FAILURE[INFO] [INFO] Total time: 7.945 s[INFO] Finished at: 2020-05-08T20:07:00+02:00[INFO] [ERROR] Failed to execute goal org.jenkins-ci.tools:maven-hpi-plugin:3.12:run (default-cli) on project matrix-auth: Unable to copy dependency plugin: Failed to open artifact com.sun:tools:jar:1.8.0:system at /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre/../lib/tools.jar: org.apache.maven.project.ProjectBuildingException: Error resolving project artifact: Failure to transfer com.sun:tools:pom:1.8.0 from https://repo.jenkins-ci.org/JENKINS-61937/ was cached in the local repository, resolution will not be reattempted until the update interval of JENKINS-61937 has elapsed or updates are forced. Original
[JIRA] (JENKINS-62211) Justin Harringa asked me to open this: pipeline triggers not working using https://github.com/jenkinsci/config-driven-pipeline-plugin
Title: Message Title Justin Harringa commented on JENKINS-62211 Re: Justin Harringa asked me to open this: pipeline triggers not working using https://github.com/jenkinsci/config-driven-pipeline-plugin Thanks marlene cote! If I recall correctly, some triggers require an initial pipeline run to save (even for a raw pipeline without this plugin) but that may have been fixed. I'm also curious if this may have something to do with `getWorkSpace()`. Will take a look. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206145.151564000.23808.1588959480200%40Atlassian.JIRA.
[JIRA] (JENKINS-62223) Many field descriptions of git plugin pipeline docs are empty
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-62223 Many field descriptions of git plugin pipeline docs are empty Change By: Mark Waite Labels: documentation newbie-friendly Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206157.1588958601000.23806.1588958700057%40Atlassian.JIRA.
[JIRA] (JENKINS-62223) Many field descriptions of git plugin pipeline docs are empty
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-62223 Many field descriptions of git plugin pipeline docs are empty Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206157.1588958601000.23805.1588958640214%40Atlassian.JIRA.
[JIRA] (JENKINS-62223) Many field descriptions of git plugin pipeline docs are empty
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-62223 Many field descriptions of git plugin pipeline docs are empty Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2020-05-08 17:23 Environment: Git plugin 4.2.2 Labels: newbie-friendly Priority: Minor Reporter: Mark Waite The online reference documentation for the Jenkins Pipeline checkout step is automatically extracted from released plugin online help pages. Several of the fields in the GitSCM online documentation include no description. The following fields are examples of fields that should be described so that readers know how to use them: UserRemoteConfig.credentialsId CGit.repoUrl GogsGit.repoUrl GitSCM.gitTool GitSCM.extensions.GitLFSPull GitSCM.extensions.SparseCheckoutPaths.sparseCheckPaths.path Add help for those fields by following the same naming convention and file placement elsewhere in the plugin. The help files are html files placed in the src/resources directory. See the references option as an example.
[JIRA] (JENKINS-39742) Active Choice Plugin should honor ParameterDefinition serializability (was: Active Choice Plugin in Pipelines throw NotSerializableException)
Title: Message Title Ben Courliss commented on JENKINS-39742 Re: Active Choice Plugin should honor ParameterDefinition serializability (was: Active Choice Plugin in Pipelines throw NotSerializableException) Would be nice to see if this could be fixed. Would love to use ActiveChoices in my declarative pipelines. Ran into this issue today so I'm falling back to a freestyle job. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176327.1479212513000.23796.1588956780257%40Atlassian.JIRA.
[JIRA] (JENKINS-62222) log file spammed with a warning message
Title: Message Title Sam Darwin updated an issue Jenkins / JENKINS-6 log file spammed with a warning message Change By: Sam Darwin Hi,Jenkins Freestyle Project.Running a post-build step to upload files to S3 with the s3-plugin version 0.11.5. Specify S3 source, destination, profile. Standard usage of the plugin.About 6000 files are uploaded. In the jenkins log /var/log/jenkins/jenkins.log are about 6000 warning messages:2020-05-07 21:04:54.461+ [id=801] WARNING hudson.util.Secret#toString: Use of toString() on hudson.util.Secret from java.lang.String.valueOf(String.java:2994). Prefer getPlainText() or getEncryptedValue() depending your needs. see [https://jenkins.io/redirect/hudson.util.Secret/]The text of that warning is apparently found in jenkins/core/src/main/java/hudson/util/Secret.javaAs far as I am aware, the s3-plugin is being used in the standard way. Nothing has been customized. Just uploading files to S3 after the build finishes. Glad to provide more information if that's helpful. This problem has been reproduced on two different Jenkins servers, so it seems consistent. You may try. To The goal would be to solve the error, or at least not spam the log file with thousands of warnings.Thanks. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-62222) log file spammed with a warning message
Title: Message Title Sam Darwin created an issue Jenkins / JENKINS-6 log file spammed with a warning message Issue Type: Bug Assignee: Alexander A Components: s3-plugin Created: 2020-05-08 16:26 Environment: Jenkins version 2.233, operating system Ubuntu 18.04. Plugins installed: s3-plugin 0.11.5, AWS Credentials Plugin, Github Pull Request Builder. Priority: Minor Reporter: Sam Darwin Hi, Jenkins Freestyle Project. Running a post-build step to upload files to S3 with the s3-plugin version 0.11.5. Specify S3 source, destination, profile. Standard usage of the plugin. About 6000 files are uploaded. In the jenkins log /var/log/jenkins/jenkins.log are about 6000 warning messages: 2020-05-07 21:04:54.461+ [id=801] WARNING hudson.util.Secret#toString: Use of toString() on hudson.util.Secret from java.lang.String.valueOf(String.java:2994). Prefer getPlainText() or getEncryptedValue() depending your needs. see https://jenkins.io/redirect/hudson.util.Secret/ The text of that warning is apparently found in jenkins/core/src/main/java/hudson/util/Secret.java As far as I am aware, the s3-plugin is being used in the standard way. Nothing has been customized. Just uploading files to S3 after the build finishes. Glad to provide more information if that's helpful. This problem has been reproduced on two different Jenkins servers, so it seems consistent. You may try. To goal would be to solve the error, or at least not spam the log file with thousands of warnings. Thanks.
[JIRA] (JENKINS-62063) BlueOcean UI is broken due to ClassCastException
Title: Message Title Liam Newman commented on JENKINS-62063 Re: BlueOcean UI is broken due to ClassCastException Caused by https://github.com/jenkinsci/blueocean-plugin/pull/2049/ Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205962.1588001733000.23782.1588954800162%40Atlassian.JIRA.
[JIRA] (JENKINS-62199) Google always assign Public IP
Title: Message Title Fritz Elfert stopped work on JENKINS-62199 Change By: Fritz Elfert Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206131.1588840839000.23779.1588954260179%40Atlassian.JIRA.
[JIRA] (JENKINS-62202) Users without Overall/Administer can no longer configure permissions of jobs etc.
Title: Message Title Daniel Beck updated JENKINS-62202 Fixed in 2.6.1 which should be available shortly. Jenkins / JENKINS-62202 Users without Overall/Administer can no longer configure permissions of jobs etc. Change By: Daniel Beck Status: In Review Closed Resolution: Fixed Released As: matrix-auth-2.6.1 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You
[JIRA] (JENKINS-62199) Google always assign Public IP
Title: Message Title Fritz Elfert commented on JENKINS-62199 Re: Google always assign Public IP There is a generic mailing-list for users of jenkins. See: https://www.jenkins.io/mailing-lists/ Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206131.1588840839000.23774.1588953960225%40Atlassian.JIRA.
[JIRA] (JENKINS-62190) Add UI test for Freestyle Configuration
Title: Message Title Johannes Hintermaier assigned an issue to Johannes Hintermaier Jenkins / JENKINS-62190 Add UI test for Freestyle Configuration Change By: Johannes Hintermaier Assignee: Johannes Hintermaier Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206122.158880313.23772.1588952100326%40Atlassian.JIRA.
[JIRA] (JENKINS-62190) Add UI test for Freestyle Configuration
Title: Message Title Johannes Hintermaier started work on JENKINS-62190 Change By: Johannes Hintermaier Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206122.158880313.23770.1588952100301%40Atlassian.JIRA.
[JIRA] (JENKINS-62221) EC2 plugin perpetually loops unable to verify key for host
Title: Message Title
Edward Hartwell Goose updated an issue
Jenkins / JENKINS-62221
EC2 plugin perpetually loops unable to verify key for host
Change By:
Edward Hartwell Goose
I've just upgraded our EC2 plugin to the latest (1.50.2) and have found our nodes are not spinning up.They perpetually loop with the following logs:{{May 08, 2020 4:12:23 PM hudson.plugins.ec2.EC2Cloud INFO: The line with the key doesn't have the required format. Found: "ssh-ed25519 C3Nzarestofkeygoeshere ". Expected a line with this text: "ALGORITHM THEHOSTKEY", example: "ssh-ed25519 C3NzaC1lZDI1NTE5IJbvbEIoY3tqKwkeRW/L1FnbCLLp8a1TwSOyZHKJqFFR "}} {{}} Based on this:[https://github.com/jenkinsci/ec2-plugin/blob/master/src/main/java/hudson/plugins/ec2/ssh/verifiers/SshHostKeyVerificationStrategy.java#L139-L146], which says:String[] parts = line.split(" ");if (parts.length > 2) { The example will never work:{{ssh-ed25519 C3NzaC1lZDI1NTE5IJbvbEIoY3tqKwkeRW/L1FnbCLLp8a1TwSOyZHKJqFFR }}will never split into > 2 pieces as the code says. E.g.: https://repl.it/repls/FoolishCrookedWebsiteEither I'm misunderstanding how this is meant to work, or the error message is unclear.I've not done anything to change our configuration other than upgrading the plugin - so quite frustrated that it has completely stopped working for us.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-62221) EC2 plugin perpetually loops unable to verify key for host
Title: Message Title
Edward Hartwell Goose updated an issue
Jenkins / JENKINS-62221
EC2 plugin perpetually loops unable to verify key for host
Change By:
Edward Hartwell Goose
I've just upgraded our EC2 plugin to the latest (1.50.2) and have found our nodes are not spinning up.They perpetually loop with the following logs:{{May 08, 2020 4:12:23 PM hudson.plugins.ec2.EC2Cloud INFO: The line with the key doesn't have the required format. Found: "ssh-ed25519 C3Nzarestofkeygoeshere ". Expected a line with this text: "ALGORITHM THEHOSTKEY", example: "ssh-ed25519 C3NzaC1lZDI1NTE5IJbvbEIoY3tqKwkeRW/L1FnbCLLp8a1TwSOyZHKJqFFR "}} Based on this:[https://github.com/jenkinsci/ec2-plugin/blob/master/src/main/java/hudson/plugins/ec2/ssh/verifiers/SshHostKeyVerificationStrategy.java#L139-L146], which says:String[] parts = line.split(" ");if (parts.length > 2) { The example will never work:{{ssh-ed25519 C3NzaC1lZDI1NTE5IJbvbEIoY3tqKwkeRW/L1FnbCLLp8a1TwSOyZHKJqFFR }}will never split into > 2 pieces as the code says. E.g.: https://repl.it/repls/FoolishCrookedWebsiteEither I'm misunderstanding how this is meant to work, or the error message is unclear.I've not done anything to change our configuration other than upgrading the plugin - so quite frustrated that it has completely stopped working for us .
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-62199) Google always assign Public IP
Title: Message Title Jonathan E commented on JENKINS-62199 Re: Google always assign Public IP We are going to use widely this plugin with the cloud feature. Is there a forum or any place I discuss it with others? limitation, bugs, etc. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206131.1588840839000.23762.1588951620317%40Atlassian.JIRA.
[JIRA] (JENKINS-62221) EC2 plugin perpetually loops unable to verify key for host
Title: Message Title
Edward Hartwell Goose created an issue
Jenkins / JENKINS-62221
EC2 plugin perpetually loops unable to verify key for host
Issue Type:
Bug
Assignee:
FABRIZIO MANFREDI
Components:
ec2-plugin
Created:
2020-05-08 15:26
Labels:
ec2-plugin
Priority:
Minor
Reporter:
Edward Hartwell Goose
I've just upgraded our EC2 plugin to the latest (1.50.2) and have found our nodes are not spinning up. They perpetually loop with the following logs: May 08, 2020 4:12:23 PM hudson.plugins.ec2.EC2Cloud INFO: The line with the key doesn't have the required format. Found: "ssh-ed25519 C3Nzarestofkeygoeshere ". Expected a line with this text: "ALGORITHM THEHOSTKEY", example: "ssh-ed25519 C3NzaC1lZDI1NTE5IJbvbEIoY3tqKwkeRW/L1FnbCLLp8a1TwSOyZHKJqFFR "{{}} Based on this: https://github.com/jenkinsci/ec2-plugin/blob/master/src/main/java/hudson/plugins/ec2/ssh/verifiers/SshHostKeyVerificationStrategy.java#L139-L146, which says: String[] parts = line.split(" "); if (parts.length > 2) { The example will never work: {{ssh-ed25519 C3NzaC1lZDI1NTE5IJbvbEIoY3tqKwkeRW/L1FnbCLLp8a1TwSOyZHKJqFFR }} will never split into > 2 pieces as the code says. E.g.: https://repl.it/repls/FoolishCrookedWebsite Either I'm misunderstanding how this is meant to work, or the error message is unclear. I've not done anything to change our configuration other than upgrading the plugin - so quite frustrated that it has completely stopped working for us.
[JIRA] (JENKINS-62199) Google always assign Public IP
Title: Message Title Jonathan E commented on JENKINS-62199 Re: Google always assign Public IP Thanks, Works great. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206131.1588840839000.23760.1588951140152%40Atlassian.JIRA.
[JIRA] (JENKINS-62195) ec2-1.50.2 doesn't work with SSH <7.5
Title: Message Title Ramon Leon updated JENKINS-62195 Jenkins / JENKINS-62195 ec2-1.50.2 doesn't work with SSH <7.5 Change By: Ramon Leon Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206127.1588831961000.23750.1588950186136%40Atlassian.JIRA.
[JIRA] (JENKINS-62195) ec2-1.50.2 doesn't work with SSH <7.5
Title: Message Title Ramon Leon started work on JENKINS-62195 Change By: Ramon Leon Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206127.1588831961000.23748.1588950185861%40Atlassian.JIRA.
[JIRA] (JENKINS-62195) ec2-1.50.2 doesn't work with SSH <7.5
Title: Message Title Ramon Leon commented on JENKINS-62195 Re: ec2-1.50.2 doesn't work with SSH <7.5 A PR to use the no option instead of off which still these days is a synonym, although it was advertised they may differ in the future (from 2017): https://github.com/jenkinsci/ec2-plugin/pull/460 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206127.1588831961000.23738.1588950182535%40Atlassian.JIRA.
[JIRA] (JENKINS-60077) Cppcheck plugin failure on report analysis
Title: Message Title Jonathan Cormier commented on JENKINS-60077 Re: Cppcheck plugin failure on report analysis My Jenkins version is 2.176.3, Cppcheck plugin version is 1.25, OpenJDK version is openjdk 11.0.7 Slaves log is the following: May 08, 2020 9:36:54 AM hudson.remoting.UserRequest perform WARNING: LinkageError while performing UserRequest:org.jenkinsci.plugins.cppcheck.CppcheckParserResult@197b3cdc java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException at org.jenkinsci.plugins.cppcheck.CppcheckParserResult.invoke(CppcheckParserResult.java:69) at org.jenkinsci.plugins.cppcheck.CppcheckParserResult.invoke(CppcheckParserResult.java:24) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3069) at hudson.remoting.UserRequest.perform(UserRequest.java:211) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834) Caused by: java.lang.ClassNotFoundException: Bootstrap pseudo-classloader disabled: javax.xml.bind.JAXBException via null at hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch4(RemoteClassLoader.java:858) at hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch3(RemoteClassLoader.java:893) at sun.reflect.GeneratedMethodAccessor32.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:931) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at org.jenkinsci.remoting.CallableDecorator.call(CallableDecorator.java:18) at hudson.remoting.CallableDecoratorList$1.call(CallableDecoratorList.java:21) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to channel at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1788) at hudson.remoting.Request.call(Request.java:202) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:288) at com.sun.proxy.$Proxy6.fetch3(Unknown Source) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:211) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:589) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522) at org.jenkinsci.plugins.cppcheck.CppcheckParserResult.invoke(CppcheckParserResult.java:69) at org.jenkinsci.plugins.cppcheck.CppcheckParserResult.invoke(CppcheckParserResult.java:24) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3069) at hudson.remoting.UserRequest.perform(UserRequest.java:211) at
[JIRA] (JENKINS-62195) ec2-1.50.2 doesn't work with SSH <7.5
Title: Message Title Ramon Leon commented on JENKINS-62195 Re: ec2-1.50.2 doesn't work with SSH <7.5 Another workaround is to set the strategy to Check New Hard which will set the option to yes which is supported by all versions. This strategy requires the key is added to the known_hosts file Another workaround is to use avoid using the ssh command and the plugin will use a pure-java ssh command to do that. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206127.1588831961000.23703.1588948500864%40Atlassian.JIRA.
[JIRA] (JENKINS-62195) ec2-1.50.2 doesn't work with SSH <7.5
Title: Message Title Ramon Leon edited a comment on JENKINS-62195 Re: ec2-1.50.2 doesn't work with SSH <7.5 Another workaround is to set the strategy to Check New Hard which will set the option to yes which is supported by all versions. This strategy requires the key is added to the known_hosts fileAnother workaround is to avoid using the ssh command and the plugin will use a pure-java ssh command client to do that the connection . Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206127.1588831961000.23715.1588948501117%40Atlassian.JIRA.
[JIRA] (JENKINS-62195) ec2-1.50.2 doesn't work with SSH <7.5
Title: Message Title Ramon Leon edited a comment on JENKINS-62195 Re: ec2-1.50.2 doesn't work with SSH <7.5 Another workaround is to set the strategy to Check New Hard which will set the option to yes which is supported by all versions. This strategy requires the key is added to the known_hosts fileAnother workaround is to use avoid using the ssh command and the plugin will use a pure-java ssh command to do that. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206127.1588831961000.23713.1588948501082%40Atlassian.JIRA.
[JIRA] (JENKINS-62195) ec2-1.50.2 doesn't work with SSH <7.5
Title: Message Title
Mark Waite edited a comment on JENKINS-62195
Re: ec2-1.50.2 doesn't work with SSH <7.5
Yes, Debian Stretch is the current Debian "[oldstable|https://wiki.debian.org/DebianOldStable]" release and is delivering OpenSSH 7.4p1. It is a distribution which the Debian project continues to patch and will continue to patch until the release of [Debian next-stable|https://wiki.debian.org/DebianReleases] ("Bullseye"). No release date has been set for Bullseye. After Bullseye releases, Debian Stretch will stop receiving patches. [~danielbeck] is correct that we'll need to update the Docker base images. That seems like a good topic for the Platform SIG and a good place to reach consensus on labeling patterns and practices. Red Hat 7 and CentOS 7 are also still actively being patched by their maintainers and are delivering OpenSSH 7.4p1. Red Hat Enterprise Linux 7 is slated to be [supported through 2024|https://en.wikipedia.org/wiki/Red_Hat_Enterprise_Linux#Product_life_cycle].
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206127.1588831961000.23686.1588947720482%40Atlassian.JIRA.
[JIRA] (JENKINS-62220) GitHub App to support credentials with multiple organizations
Title: Message Title Naresh Rayapati created an issue Jenkins / JENKINS-62220 GitHub App to support credentials with multiple organizations Issue Type: Improvement Assignee: Unassigned Components: github-branch-source-plugin Created: 2020-05-08 14:19 Priority: Major Reporter: Naresh Rayapati We are trying to use same app on Jobs across orgs and is not working as we need to maintain duplicate credentials for multiple organization. Maintaining same credentials for multiple orgs seems duplicate to me, is there any chance we can avoid this? Our use case is, since it is internal (GitHub Enterprise) bot, it is pretty open and we don't even know who would invite this bot to their organization, and this bot does takes care of creating Jenkins job through DSL scripts, which is using the standard credentials. So it is very hard to keep creating credentials on the fly for every org that this bot is being invited to. Thanks a bunch for all the help on maintaining this awesome plugin. Let me know your thoughts I can log a follow up JIRA. Related discussion on PR: https://github.com/jenkinsci/github-branch-source-plugin/pull/290#discussion_r415168275 Add Comment
[JIRA] (JENKINS-55973) Update Jenkins POM and Core to SpotBugs
Title: Message Title Jesse Glick started work on JENKINS-55973 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197384.1549366215000.23676.1588946949761%40Atlassian.JIRA.
[JIRA] (JENKINS-55973) Update Jenkins POM and Core to SpotBugs
Title: Message Title Jesse Glick commented on JENKINS-55973 Re: Update Jenkins POM and Core to SpotBugs What is the overall status here? Core is patched; do we need something done in plugin POMs? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197384.1549366215000.23679.1588946949923%40Atlassian.JIRA.
[JIRA] (JENKINS-62195) ec2-1.50.2 doesn't work with SSH <7.5
Title: Message Title
Mark Waite commented on JENKINS-62195
Re: ec2-1.50.2 doesn't work with SSH <7.5
Yes, Debian Stretch is the current Debian "oldstable" release and is delivering OpenSSH 7.4p1. It is a distribution which the Debian project continues to patch and will continue to patch until the release of Debian next-stable ("Bullseye"). No release date has been set for Bullseye. After Bullseye releases, Debian Stretch will stop receiving patches. Red Hat 7 and CentOS 7 are also still actively being patched by their maintainers and are delivering OpenSSH 7.4p1. Red Hat Enterprise Linux 7 is slated to be supported through 2024.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206127.1588831961000.23666.1588946520323%40Atlassian.JIRA.
[JIRA] (JENKINS-62208) sshGet (scp mode) is showing the entire contents of the file in console output log
Title: Message Title Naresh Rayapati updated an issue Jenkins / JENKINS-62208 sshGet (scp mode) is showing the entire contents of the file in console output log Change By: Naresh Rayapati Labels: ssh-steps-plugin-2.0.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206142.1588875761000.23663.1588945740217%40Atlassian.JIRA.
[JIRA] (JENKINS-62208) sshGet (scp mode) is showing the entire contents of the file in console output log
Title: Message Title Naresh Rayapati updated an issue Jenkins / JENKINS-62208 sshGet (scp mode) is showing the entire contents of the file in console output log Change By: Naresh Rayapati Summary: sshget sshGet (scp mode) is showing the entire contents of the file in console output log Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206142.1588875761000.23660.1588945680315%40Atlassian.JIRA.
[JIRA] (JENKINS-62208) sshget (scp mode) is showing the entire contents of the file in console output log
Title: Message Title Naresh Rayapati updated an issue Jenkins / JENKINS-62208 sshget (scp mode) is showing the entire contents of the file in console output log Change By: Naresh Rayapati Summary: sshget (scp mode) is showing the entire contents of the file in console output log Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206142.1588875761000.23657.1588945680262%40Atlassian.JIRA.
[JIRA] (JENKINS-62208) sshget is showing the entire contents of the file in console output log
Title: Message Title Naresh Rayapati commented on JENKINS-62208 Re: sshget is showing the entire contents of the file in console output log I found a bug in the code, going to fix it soon to not to print the file in scp mode. But in cases like where you wanted to print the file contents explicitly, there are couple of other steps around reading file contents and printing those to console. https://www.jenkins.io/doc/pipeline/steps/workflow-basic-steps/#readfile-read-file-from-workspace def data = "" FileName) println(data) Few advanced steps to read specific files like yaml,csv or json here: https://www.jenkins.io/doc/pipeline/steps/pipeline-utility-steps/ Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206142.1588875761000.23654.1588945620157%40Atlassian.JIRA.
[JIRA] (JENKINS-62195) ec2-1.50.2 doesn't work with SSH <7.5
Title: Message Title Daniel Beck commented on JENKINS-62195 Re: ec2-1.50.2 doesn't work with SSH <7.5 Oleg Nenashev As this problem seems to occur because of very outdated base images, it's reasonable to inform the SIG about the consequences of that. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206127.1588831961000.23644.1588945140348%40Atlassian.JIRA.
[JIRA] (JENKINS-62211) Justin Harringa asked me to open this: pipeline triggers not working using https://github.com/jenkinsci/config-driven-pipeline-plugin
Title: Message Title marlene cote commented on JENKINS-62211 Re: Justin Harringa asked me to open this: pipeline triggers not working using https://github.com/jenkinsci/config-driven-pipeline-plugin I noticed a typo in the line for the cp nightly build and corrected it. Here is the new line: getWorkSpace() == 'Nightly/CP-NightlyBuilds/branches/int/int_cp' ? 'H 20 * * 4-6' : but it still failed to trigger last night. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206145.151564000.23641.1588945080110%40Atlassian.JIRA.
[JIRA] (JENKINS-62195) ec2-1.50.2 doesn't work with SSH <7.5
Title: Message Title Ryan Campbell commented on JENKINS-62195 Re: ec2-1.50.2 doesn't work with SSH <7.5 Noting in case it isn't clear, that a valid workaround is to update the ssh client to a more recent version which supports these more secure options. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206127.1588831961000.23633.1588944960262%40Atlassian.JIRA.
[JIRA] (JENKINS-62195) ec2-1.50.2 doesn't work with SSH <7.5
Title: Message Title Ramon Leon assigned an issue to Ramon Leon Jenkins / JENKINS-62195 ec2-1.50.2 doesn't work with SSH <7.5 Change By: Ramon Leon Assignee: Ramon Leon Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206127.1588831961000.23622.1588944600316%40Atlassian.JIRA.
[JIRA] (JENKINS-62208) sshget is showing the entire contents of the file in console output log
Title: Message Title Craig Webster commented on JENKINS-62208 Re: sshget is showing the entire contents of the file in console output log Thank you, i removed that line and it fixed my issue. scp vs sftp still confuses me; when i want to copy a file between linux servers the command I use is scp so probably that's why I had that in there. Curious though, why does the plugin echo the file contents to console output when using scp as transfer mode? Honestly in some ways it is handy because there are times when i actually do want the file echoed to the console. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206142.1588875761000.23618.1588944360301%40Atlassian.JIRA.
[JIRA] (JENKINS-62206) Triggering Pipeline job from a multibranch pipeline fails
Title: Message Title nazia mahimi commented on JENKINS-62206 Re: Triggering Pipeline job from a multibranch pipeline fails corrected the job name , do i have to specifiy the branch too? if so how? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206140.1588868944000.23615.1588944180129%40Atlassian.JIRA.
[JIRA] (JENKINS-62206) Triggering Pipeline job from a multibranch pipeline fails
Title: Message Title
nazia mahimi updated an issue
Jenkins / JENKINS-62206
Triggering Pipeline job from a multibranch pipeline fails
Change By:
nazia mahimi
triggering a pipeline job from the multibranch pipeline doesnt work , it fails with the following errorSucessfully[Pipeline] build[Pipeline] }[Pipeline] // scriptError when executing success post condition:hudson.AbortException: No item named UKAPI- Data- Manager- Deploy-Dev found at org.jenkinsci.plugins.workflow.support.steps.build.BuildTriggerStepExecution.start(BuildTriggerStepExecution.java:75) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:286) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:179) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at sun.reflect.GeneratedMethodAccessor1473.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42)here is the code in the Multibranch pipelinepost { always { { echo 'Test run completed' } success { script { if (env.BRANCH_NAME == 'master') { echo 'Sucessfully' build job: 'Data-Deploy-Dev', parameters: [ string(name: 'DOCKER_APP_IMAGE_TAG', value: "${env.DOCKER_APP_IMAGE_TAG}"), string(name: 'DOCKER_WEB_IMAGE_TAG', value: "${env.DOCKER_WEB_IMAGE_TAG}") ], wait: false }else { { echo 'Sucessfully!' } } } failure { { echo 'Failed!' } unstable { { echo 'This will run only if the run was marked as unstable' } changed { { echo 'This will run only if the state of the Pipeline has changed' echo 'For example, if the Pipeline was previously failing but is now successful' } } the pipeline job Data-Deploy-Dev is present, but still it errors as not found
Add Comment
[JIRA] (JENKINS-62195) ec2-1.50.2 doesn't work with SSH <7.5
Title: Message Title Oleg Nenashev commented on JENKINS-62195 Re: ec2-1.50.2 doesn't work with SSH <7.5 We also hit the issues after upgrading the plugin on ci.jenkins.io which currently uses the plugin to provision agents in AWS. https://groups.google.com/forum/#!topic/jenkinsci-dev/2_WmJWSjtuc for a general discussion about agents stability, CC Mark Waite. Daniel Beck FYI this plugin is not really within the scope of the platform SIG. I am working to get the issue reviewed by the maintainers, but it is unlikely to happen immediately due to bank holidays, etc. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206127.1588831961000.23611.1588943400395%40Atlassian.JIRA.
[JIRA] (JENKINS-62195) ec2-1.50.2 doesn't work with SSH <7.5
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-62195 ec2-1.50.2 doesn't work with SSH <7.5 Change By: Oleg Nenashev Assignee: FABRIZIO MANFREDI Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206127.1588831961000.23592.1588943160516%40Atlassian.JIRA.
[JIRA] (JENKINS-62195) ec2-1.50.2 doesn't work with SSH <7.5
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-62195 ec2-1.50.2 doesn't work with SSH <7.5 Change By: Oleg Nenashev Labels: regression Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206127.1588831961000.23599.1588943160641%40Atlassian.JIRA.
[JIRA] (JENKINS-62063) BlueOcean UI is broken due to ClassCastException
Title: Message Title Steve Todorov commented on JENKINS-62063 Re: BlueOcean UI is broken due to ClassCastException Liam Newman Yes - we do have multibranch-defaults-plugin installed (as marked in the issue description) and we are specifically using the part of loading `Jenkinsfile`s using `Managed Files` on some of our jobs. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205962.1588001733000.23585.1588942560323%40Atlassian.JIRA.
[JIRA] (JENKINS-62063) BlueOcean UI is broken due to ClassCastException
Title: Message Title Steve Todorov edited a comment on JENKINS-62063 Re: BlueOcean UI is broken due to ClassCastException [~bitwiseman] Yes - we do have multibranch-defaults-plugin installed (as marked in the issue description) and we are specifically using the part of loading `Jenkinsfile`s using `Managed Files` on some of our jobs. I've actually tried removing the plugin just now and confirm it's part of the problem. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205962.1588001733000.23587.1588942560377%40Atlassian.JIRA.
[JIRA] (JENKINS-62180) Exception on reading the Jenkins settings for Bitbucket Cloud
Title: Message Title Roberto Devesa commented on JENKINS-62180 Re: Exception on reading the Jenkins settings for Bitbucket Cloud Same here. The credentials dropdown also doesn't work for existing Bitbucket branch sources but it does work when adding a fresh Bitbucket source. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206112.1588787398000.23579.1588938660287%40Atlassian.JIRA.
[JIRA] (JENKINS-62180) Exception on reading the Jenkins settings for Bitbucket Cloud
Title: Message Title Roberto Devesa edited a comment on JENKINS-62180 Re: Exception on reading the Jenkins settings for Bitbucket Cloud Same here. The credentials dropdown also doesn't work for existing Bitbucket branch sources but it does work when adding a fresh Bitbucket source on a project . Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206112.1588787398000.23581.1588938660320%40Atlassian.JIRA.
[JIRA] (JENKINS-62213) Synchronize LoadRunner Enterprise With Git changed build result to FAILURE
Title: Message Title Paul-Adrian Tofan assigned an issue to Daniel Danan Jenkins / JENKINS-62213 Synchronize LoadRunner Enterprise With Git changed build result to FAILURE Change By: Paul-Adrian Tofan Assignee: Maria Narcisa Galan Daniel Danan Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206147.156583000.23577.1588934100294%40Atlassian.JIRA.
[JIRA] (JENKINS-49141) P4 plugin removed BOM from utf8 files
Title: Message Title ram Shukla commented on JENKINS-49141 Re: P4 plugin removed BOM from utf8 files am facing the the same issue on P4Plugin version 1.10.4 and jenkins version 2.190.3 error CNDL0104 : Not a valid source file; detail: Data at the root level is invalid. Line 1, position 1. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187977.1516811255000.23558.1588933440436%40Atlassian.JIRA.
[JIRA] (JENKINS-49141) P4 plugin removed BOM from utf8 files
Title: Message Title ram Shukla edited a comment on JENKINS-49141 Re: P4 plugin removed BOM from utf8 files am facing the the same issue on P4Plugin version 1.10. 4 6 and jenkins version 2.190.3error CNDL0104 : Not a valid source file; detail: Data at the root level is invalid. Line 1, position 1. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187977.1516811255000.23567.1588933440564%40Atlassian.JIRA.
[JIRA] (JENKINS-62219) Role-based Authorization Strategy can't be effect immediately when assigned a none admin role to a new User
Title: Message Title jianfeng ru updated an issue Jenkins / JENKINS-62219 Role-based Authorization Strategy can't be effect immediately when assigned a none admin role to a new User Change By: jianfeng ru Hi guys,I've use offical docker image to run a jenkins containerWhen I create a new user and assign it to a none-admin role ( only have read all and read jobs permmsions and regular _expression_ to filter jobs), !image-2020-05-08-17-40-35-934.png!that account can't see any jobs at that time.!image-2020-05-08-17- 43 42 -49- 887 028 .png |thumbnail !The jobs will not show up until 20 minutes later or much longer or restart jenkins Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-62219) Role-based Authorization Strategy can't be effect immediately when assigned a none admin role to a new User
Title: Message Title jianfeng ru updated an issue Jenkins / JENKINS-62219 Role-based Authorization Strategy can't be effect immediately when assigned a none admin role to a new User Change By: jianfeng ru Attachment: image-2020-05-08-17-43-49-887.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206153.1588931066000.23553.1588931160182%40Atlassian.JIRA.
[JIRA] (JENKINS-62219) Role-based Authorization Strategy can't be effect immediately when assigned a none admin role to a new User
Title: Message Title jianfeng ru created an issue Jenkins / JENKINS-62219 Role-based Authorization Strategy can't be effect immediately when assigned a none admin role to a new User Issue Type: Bug Assignee: Oleg Nenashev Attachments: image-2020-05-08-17-40-35-934.png, image-2020-05-08-17-42-49-028.png, image-2020-05-08-17-43-49-887.png Components: role-strategy-plugin Created: 2020-05-08 09:44 Environment: Jenkins 2.204.5 official docker image Jenkins-blueocean AWS Linux base centos Role-based Authorization Strategy 2.16 Priority: Minor Reporter: jianfeng ru Hi guys, I've use offical docker image to run a jenkins container When I create a new user and assign it to a none-admin role ( only have read all and read jobs permmsions and regular _expression_ to filter jobs), that account can't see any jobs at that time. The jobs will not show up until 20 minutes later or much longer or restart jenkins
[JIRA] (JENKINS-61779) Regression: Job stuck in queue waiting forever after upgrade
Title: Message Title Daniel Beck commented on JENKINS-61779 Re: Regression: Job stuck in queue waiting forever after upgrade Alain Campeau Thanks for these steps, I'll try to reproduce them when I have some time. About Configure this job's "Restrict where this project can run" setting so its "Label _expression_" value is the one specified for master, so DISPATCH What happens when you don't check that box, or specify "master" here? Would that be a viable workaround for this problem, and if not, why not? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205618.158582599.23545.1588928940171%40Atlassian.JIRA.
[JIRA] (JENKINS-62218) Read-only job configuration for folders
Title: Message Title
Tim Jacomb created an issue
Jenkins / JENKINS-62218
Read-only job configuration for folders
Issue Type:
Task
Assignee:
Francisco Fernández
Components:
cloudbees-folder-plugin
Created:
2020-05-08 09:07
Priority:
Minor
Reporter:
Tim Jacomb
https://www.jenkins.io/doc/developer/views/read-only/ Something like:
var="readOnlyMode" value="${!app.hasPermission(it.CONFIGURE)}" />
Needs adding to the views provided by cloudbees-folder
Add Comment
[JIRA] (JENKINS-62090) Network interfaces and an instance-level security groups may not be specified on the same request
Title: Message Title CloudBees Foundation Security assigned an issue to Raihaan Shouhell Jenkins / JENKINS-62090 Network interfaces and an instance-level security groups may not be specified on the same request Change By: CloudBees Foundation Security Assignee: Raihaan Shouhell Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205998.158815227.23536.1588927320314%40Atlassian.JIRA.
[JIRA] (JENKINS-58093) Label properties cannot be exported or configured by JCasC
Title: Message Title Evaristo Gutierrez updated JENKINS-58093 Jenkins / JENKINS-58093 Label properties cannot be exported or configured by JCasC Change By: Evaristo Gutierrez Status: In Review Resolved Resolution: Fixed Released As: configuration-as-code-1.40 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200134.1560944232000.23532.1588924740290%40Atlassian.JIRA.
[JIRA] (JENKINS-62215) antisamy-markup-formatter-plugin v2.0 filters input fields from uno-choice plugin
Title: Message Title Bruno P. Kinoshita commented on JENKINS-62215 Re: antisamy-markup-formatter-plugin v2.0 filters input fields from uno-choice plugin Thanks for the report and for the taking your time to provide detailed description and screenshots. We were preparing a release for the next days (waiting till pending pull request gets reviewed/tested by other maintainers). I will try to include some time to take a look and try to reproduce/fix this one. Bruno Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206149.159205000.23530.1588917840195%40Atlassian.JIRA.
[JIRA] (JENKINS-62145) Getting error when clicking on testlink results 'sidepanel.jelly' for class hudson.plugins.testlink.TestLinkResult
Title: Message Title Bruno P. Kinoshita commented on JENKINS-62145 Re: Getting error when clicking on testlink results 'sidepanel.jelly' for class hudson.plugins.testlink.TestLinkResult Hi Empower Solutions No updates from me, sorry. The project is maintained by volunteers. I haven't had time to look into the issue yet. If it's urgent for you, you can reach out to CloudBees. They provide paid support. If you have a pull request, I can review and prepare a release quite quickly. Otherwise I will prioritize it in the next development cycle (busy with $work, GSoC, Apache, and family for the next weeks) Bruno Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206064.1588413622000.23528.1588917720218%40Atlassian.JIRA.
