[JIRA] (JENKINS-29991) view-job-filters-plugin with SCM Job Configuration not working
Title: Message Title Sverre Moe commented on JENKINS-29991 Re: view-job-filters-plugin with SCM Job Configuration not working We are using Jenkins LTS 2.222.3 and this does not work. The SCM filtering does not work as documented Regular _expression_ Job Filter: * SCM Configuration - this one is perhaps the best bang for the buck - put in something like "./my-office-name/." to automatically include all jobs that are organized under source control already by office. At least it does not work for the URL we are using ssh://g...@git.company.com/namespace/project.git regex: ./namespace/. It does not filter using this configuration. I have also tried with other regex patterns. 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.164570.1439858379000.24032.1589103960297%40Atlassian.JIRA.
[JIRA] (JENKINS-29991) view-job-filters-plugin with SCM Job Configuration not working
Title: Message Title
Sverre Moe edited a comment on JENKINS-29991
Re: view-job-filters-plugin with SCM Job Configuration not working
We are using Jenkins LTS 2.222.3 and this does not work for Multibranch Pipelines .The SCM filtering does not work as documented{noformat}Regular _expression_ Job Filter:* SCM Configuration - this one is perhaps the best bang for the buck - put in something like "./my-office-name/." to automatically include all jobs that are organized under source control already by office.{noformat}At least it does not work for the URL we are using ssh://g...@git.company.com/namespace/project.gitregex: ./namespace/.It does not filter using this configuration. I have also tried with other regex patterns.
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.164570.1439858379000.24037.1589103960437%40Atlassian.JIRA.
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title Ramon Leon started work on JENKINS-62231 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.206170.158974000.24042.1589111220359%40Atlassian.JIRA.
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title Ramon Leon created an issue Jenkins / JENKINS-62231 ec2 downgrade from 1.50 fails removing the configured cloud Issue Type: Bug Assignee: Ramon Leon Attachments: Screenshot from 2020-05-10 12-45-00.png, Screenshot from 2020-05-10 13-17-57.png Components: ec2-plugin Created: 2020-05-10 11:46 Environment: Jenkins 2.235, EC2 1.50 > EC2 1.49 Priority: Critical Reporter: Ramon Leon If you downgrade from a recent version of ec2-plugin with the security fixes: 1.50.2 or 1.49.2 or 1.46.3 to the previous installed version after you disabled the Administrative Monitor which show the message about weak strategies used (clicking on Dismiss these messages): the previous ec2-plugin version doesn't initialize correctly and the cloud configuration is lost. The nodes configurations are still there, but they cannot be used as the plugin didn't start.The log printed out: 2020-05-10 11:12:03.789+ [id=33]INFOjenkins.InitReactorRunner$1#onAttained: Listed all plugins 2020-05-10 11:12:04.301+ [id=30]SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Amazon EC2 plugin v1.49.1 (ec2) java.lang.IllegalStateException: Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0 at hudson.ExtensionList.lookupSingleton(ExtensionList.java:451) at hudson.diagnosis.OldDataMonitor.get(OldDataMonitor.java:91) at hudson.di
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title
Ramon Leon commented on JENKINS-62231
Re: ec2 downgrade from 1.50 fails removing the configured cloud
The error seems to be a kind of race-condition between the initialization of the ec2-plugin and the OldDataMonitor extension point. RobustReflectionConverter has to report a non-existing field, but it fails with an exception when it tries to do:
OldDataMonitor.report((Saveable)result, (ArrayList)context.get("ReadError"));
This call ends up on this other one:
return ExtensionList.lookupSingleton(OldDataMonitor.class);
which triggers:
java.lang.IllegalStateException: Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You recei
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title
Ramon Leon edited a comment on JENKINS-62231
Re: ec2 downgrade from 1.50 fails removing the configured cloud
The error seems to be a kind of race-condition between the initialization of the ec2-plugin and the OldDataMonitor extension point. RobustReflectionConverter has to report a non-existing field, but it fails with an exception when it tries to do:{code:java}OldDataMonitor.report((Saveable)result, (ArrayList)context.get("ReadError"));{code}This call ends up on this other one:{code:java} return ExtensionList.lookupSingleton(OldDataMonitor.class); {code}which triggers:{code:java}java.lang.IllegalStateException: Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0{code} I will try to add an ordinal to the @Extension of the EC2 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.206170.158974000.24044.1589113560049%40Atlassian.JIRA.
[JIRA] (JENKINS-59582) build-failure-analyzer fails to load on startup, exception thrown.
Title: Message Title Ramon Leon commented on JENKINS-59582 Re: build-failure-analyzer fails to load on startup, exception thrown. similar case here: https://issues.jenkins-ci.org/browse/JENKINS-62231 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.20.1569837284000.24047.1589114220203%40Atlassian.JIRA.
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title Ramon Leon commented on JENKINS-62231 Re: ec2 downgrade from 1.50 fails removing the configured cloud It seems to be a similar issue: https://issues.jenkins-ci.org/browse/JENKINS-59582 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.206170.158974000.24050.1589114280046%40Atlassian.JIRA.
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title
Ramon Leon edited a comment on JENKINS-62231
Re: ec2 downgrade from 1.50 fails removing the configured cloud
The error seems to be a kind of race-condition between the initialization of the ec2-plugin and the OldDataMonitor extension point. RobustReflectionConverter has to report a non-existing field, but it fails with an exception when it tries to do:{code:java}OldDataMonitor.report((Saveable)result, (ArrayList)context.get("ReadError"));{code}This call ends up on this other one:{code:java} return ExtensionList.lookupSingleton(OldDataMonitor.class); {code}which triggers:{code:java}java.lang.IllegalStateException: Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0{code} I will try to add an Adding _@Extension( ordinal =-1)_ to the @Extension of the EC2 plugin to try to load this one after the AdministrativeMonitors doesn't solve 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.206170.158974000.24051.1589114340048%40Atlassian.JIRA.
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title Ramon Leon commented on JENKINS-62231 Re: ec2 downgrade from 1.50 fails removing the configured cloud It looks like a bug on Jenkins core more likely than a bug on the EC2 plugin itself. Daniel Beck Oleg Nenashev any idea would be appreciated 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.206170.158974000.24069.1589114580082%40Atlassian.JIRA.
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title Ramon Leon edited a comment on JENKINS-62231 Re: ec2 downgrade from 1.50 fails removing the configured cloud It looks like a bug on Jenkins core more likely than a bug on the EC2 plugin itself. [~danielbeck] , [~oleg_nenashev] any idea would be appreciated 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.206170.158974000.24070.1589114580244%40Atlassian.JIRA.
[JIRA] (JENKINS-62230) Installing plugins seems to be failing for random plugins
Title: Message Title Aaron McDonald commented on JENKINS-62230 Re: Installing plugins seems to be failing for random plugins INFRA-2613(https://issues.jenkins-ci.org/browse/INFRA-2613) appears to have resolved this issue for me 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.206167.158907730.24167.1589117280218%40Atlassian.JIRA.
[JIRA] (JENKINS-62230) Installing plugins seems to be failing for random plugins
Title: Message Title Aaron McDonald edited a comment on JENKINS-62230 Re: Installing plugins seems to be failing for random plugins [ INFRA-2613 ](https://issues.jenkins-ci.org/browse/INFRA-2613) appears to have resolved this issue for me 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.206167.158907730.24169.1589117340135%40Atlassian.JIRA.
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title Daniel Beck commented on JENKINS-62231 Re: ec2 downgrade from 1.50 fails removing the configured cloud How can this be reproduced? Specific, detailed and complete steps to do that please. 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.206170.158974000.24171.1589118420167%40Atlassian.JIRA.
[JIRA] (JENKINS-29991) view-job-filters-plugin with SCM Job Configuration not working
Title: Message Title Sverre Moe commented on JENKINS-29991 Re: view-job-filters-plugin with SCM Job Configuration not working I looked at the source code for the plugin. It does not support Pipeline og Multibranch Pipeline 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.164570.1439858379000.24174.1589118480188%40Atlassian.JIRA.
[JIRA] (JENKINS-62232) Implement Code Coverage in Veracode Open-source Jenkins Plugin
Title: Message Title Shihaaz Buhary created an issue Jenkins / JENKINS-62232 Implement Code Coverage in Veracode Open-source Jenkins Plugin Issue Type: Story Assignee: Shihaaz Buhary Components: veracode-scan-plugin Created: 2020-05-10 14:08 Priority: Minor Reporter: Shihaaz Buhary Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed
[JIRA] (JENKINS-62233) View Job Filter SCM RegEx Support Pipeline projects
Title: Message Title Sverre Moe created an issue Jenkins / JENKINS-62233 View Job Filter SCM RegEx Support Pipeline projects Issue Type: Bug Assignee: Sven Schoenung Components: view-job-filters-plugin Created: 2020-05-10 14:12 Priority: Minor Reporter: Sverre Moe The view-job-filters-plugin does not support Pipeline projects for filtering with Regular _expression_ SCM Configuration. It only supports three types of projects, instances of AbstractProject, SCMTriggerItem, and SCMedItem. https://github.com/jenkinsci/view-job-filters-plugin/blob/master/src/main/java/hudson/views/RegExJobFilter.java Need to support both MultibranchProject and WorkflowJob List MultibranchProject.getSCMSources() Collection WorkflowJob.getSCMs() Add Comment
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title
Ramon Leon commented on JENKINS-62231
Re: ec2 downgrade from 1.50 fails removing the configured cloud
I may try to modify the start() method of PluginImpl on EC2 plugin to something like:
@Override
public void start() {
try {
...
load();
} catch (Throwable t) {
if (t.getCause() instanceof ConversionException && t.getCause().getMessage().contains(OldDataMonitor.class.getName())) {
logger.log(Level.INFO, "There was an error loading the plugin, most likely not critical. See https://issues.jenkins-ci.org/browse/JENKINS-62231", t);
} else {
throw t;
}
}
}
But it will help for future problems, not to the current 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.206170.158974000.24189.1589121360175%40Atlassian.JIRA.
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title Ramon Leon commented on JENKINS-62231 Re: ec2 downgrade from 1.50 fails removing the configured cloud Currently, the only workaround is to remove the ec2.xml file before downgrading to a previous version. 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.206170.158974000.24190.1589121360189%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 John Jeffers regarding the downgrade: https://issues.jenkins-ci.org/browse/JENKINS-62231 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.24193.1589121540254%40Atlassian.JIRA.
[JIRA] (JENKINS-62047) Implement steps with Code Blocks
Title: Message Title Aytunc BEKEN started work on JENKINS-62047 Change By: Aytunc BEKEN 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.205939.1587730178000.24204.1589122380309%40Atlassian.JIRA.
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title Ramon Leon commented on JENKINS-62231 Re: ec2 downgrade from 1.50 fails removing the configured cloud I've filed a PR just to warn users: https://github.com/jenkinsci/ec2-plugin/pull/462 but we should avoid any critical exception because of OldDataMonitor modifying the RobustReflectionConverter IMO. 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.206170.158974000.24206.1589122800232%40Atlassian.JIRA.
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title Ramon Leon commented on JENKINS-62231 Re: ec2 downgrade from 1.50 fails removing the configured cloud Filed a PR on Jenkins Core to avoid the OldDataMonitor triggers a plugin load failure: https://github.com/jenkinsci/jenkins/pull/4718 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.206170.158974000.24208.1589123700351%40Atlassian.JIRA.
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title
Ramon Leon updated an issue
Jenkins / JENKINS-62231
ec2 downgrade from 1.50 fails removing the configured cloud
Change By:
Ramon Leon
If you downgrade from a recent version of ec2-plugin with the security fixes: 1.50.2 or 1.49.2 or 1.46.3 to the previous installed version after you disabled the Administrative Monitor which show the message about weak strategies used (clicking on *_Dismiss these messages_*): !Screenshot from 2020-05-10 12-45-00.png|thumbnail! the previous ec2-plugin version doesn't initialize correctly and the *_cloud configuration is lost_*. The nodes configurations are still there, but they cannot be used as the plugin didn't start. !Screenshot from 2020-05-10 13-17-57.png|thumbnail! The log printed out:{code:java}2020-05-10 11:12:03.789+ [id=33]INFOjenkins.InitReactorRunner$1#onAttained: Listed all plugins2020-05-10 11:12:04.301+ [id=30]SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Amazon EC2 plugin v1.49.1 (ec2)java.lang.IllegalStateException: Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0at hudson.ExtensionList.lookupSingleton(ExtensionList.java:451)at hudson.diagnosis.OldDataMonitor.get(OldDataMonitor.java:91)at hudson.diagnosis.OldDataMonitor.report(OldDataMonitor.java:223)at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:368)at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:267)at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)Caused: com.thoughtworks.xstream.converters.ConversionException: Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0 : Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0 Debugging information message : Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0cause-exception : java.lang.IllegalStateExceptioncause-message : Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0class : hudson.plugins.ec2.PluginImplrequired-type : hudson.plugins.ec2.PluginImplconverter-type : hudson.util.RobustReflectionConverterpath: /hudson.plugins.ec2.PluginImplline number : 4version : not available---at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:79)at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50)at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134)at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32)at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1189
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title
Ramon Leon updated an issue
Jenkins / JENKINS-62231
ec2 downgrade from 1.50 fails removing the configured cloud
Change By:
Ramon Leon
If you downgrade from a recent version of ec2-plugin with the security fixes: 1.50.2 or 1.49.2 or 1.46.3 to the previous installed version after you disabled the Administrative Monitor which show the message about weak strategies used (clicking on *_Dismiss these messages_*): !Screenshot from 2020-05-10 12-45-00.png|thumbnail! the previous ec2-plugin version doesn't initialize correctly and the *_cloud configuration is lost_*. The nodes configurations are still there, but they cannot be used as the plugin didn't start. !Screenshot from 2020-05-10 13-17-57.png|thumbnail! The log printed out:{code:java}2020-05-10 11:12:03.789+ [id=33]INFOjenkins.InitReactorRunner$1#onAttained: Listed all plugins2020-05-10 11:12:04.301+ [id=30]SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Amazon EC2 plugin v1.49.1 (ec2)java.lang.IllegalStateException: Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0at hudson.ExtensionList.lookupSingleton(ExtensionList.java:451)at hudson.diagnosis.OldDataMonitor.get(OldDataMonitor.java:91)at hudson.diagnosis.OldDataMonitor.report(OldDataMonitor.java:223)at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:368)at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:267)at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)Caused: com.thoughtworks.xstream.converters.ConversionException: Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0 : Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0 Debugging information message : Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0cause-exception : java.lang.IllegalStateExceptioncause-message : Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0class : hudson.plugins.ec2.PluginImplrequired-type : hudson.plugins.ec2.PluginImplconverter-type : hudson.util.RobustReflectionConverterpath: /hudson.plugins.ec2.PluginImplline number : 4version : not available---at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:79)at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50)at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134)at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32)at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1189
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title
Ramon Leon updated an issue
Jenkins / JENKINS-62231
ec2 downgrade from 1.50 fails removing the configured cloud
Change By:
Ramon Leon
If you downgrade from a recent version of ec2-plugin with the security fixes: 1.50.2 or 1.49.2 or 1.46.3 to the previous installed version after you disabled the Administrative Monitor which show the message about weak strategies used (clicking on *_Dismiss these messages_*): !Screenshot from 2020-05-10 12-45-00.png|thumbnail! the previous ec2-plugin version doesn't initialize correctly and the *_cloud configuration is lost_*. The nodes configurations are still there, but they cannot be used as the plugin didn't start. !Screenshot from 2020-05-10 13-17-57.png|thumbnail! The log printed out:{code:java}2020-05-10 11:12:03.789+ [id=33]INFOjenkins.InitReactorRunner$1#onAttained: Listed all plugins2020-05-10 11:12:04.301+ [id=30]SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Amazon EC2 plugin v1.49.1 (ec2)java.lang.IllegalStateException: Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0at hudson.ExtensionList.lookupSingleton(ExtensionList.java:451)at hudson.diagnosis.OldDataMonitor.get(OldDataMonitor.java:91)at hudson.diagnosis.OldDataMonitor.report(OldDataMonitor.java:223)at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:368)at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:267)at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)Caused: com.thoughtworks.xstream.converters.ConversionException: Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0 : Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0 Debugging information message : Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0cause-exception : java.lang.IllegalStateExceptioncause-message : Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0class : hudson.plugins.ec2.PluginImplrequired-type : hudson.plugins.ec2.PluginImplconverter-type : hudson.util.RobustReflectionConverterpath: /hudson.plugins.ec2.PluginImplline number : 4version : not available---at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:79)at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50)at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134)at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32)at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1189
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title
Ramon Leon updated an issue
Jenkins / JENKINS-62231
ec2 downgrade from 1.50 fails removing the configured cloud
Change By:
Ramon Leon
If you downgrade from a recent version of ec2-plugin with the security fixes: 1.50.2 or 1.49.2 or 1.46.3 to the previous installed version after you disabled the Administrative Monitor which show the message about weak strategies used (clicking on *_Dismiss these messages_*): !Screenshot from 2020-05-10 12-45-00.png|thumbnail! the previous ec2-plugin version doesn't initialize correctly and the *_cloud configuration is lost_*. The nodes configurations are still there, but they cannot be used as the plugin didn't start. !Screenshot from 2020-05-10 13-17-57.png|thumbnail! The log printed out:{code:java}2020-05-10 11:12:03.789+ [id=33]INFOjenkins.InitReactorRunner$1#onAttained: Listed all plugins2020-05-10 11:12:04.301+ [id=30]SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Amazon EC2 plugin v1.49.1 (ec2)java.lang.IllegalStateException: Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0at hudson.ExtensionList.lookupSingleton(ExtensionList.java:451)at hudson.diagnosis.OldDataMonitor.get(OldDataMonitor.java:91)at hudson.diagnosis.OldDataMonitor.report(OldDataMonitor.java:223)at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:368)at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:267)at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)Caused: com.thoughtworks.xstream.converters.ConversionException: Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0 : Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0 Debugging information message : Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0cause-exception : java.lang.IllegalStateExceptioncause-message : Expected 1 instance of hudson.diagnosis.OldDataMonitor but got 0class : hudson.plugins.ec2.PluginImplrequired-type : hudson.plugins.ec2.PluginImplconverter-type : hudson.util.RobustReflectionConverterpath: /hudson.plugins.ec2.PluginImplline number : 4version : not available---at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:79)at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50)at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134)at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32)at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1189
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title Ramon Leon commented on JENKINS-62231 Re: ec2 downgrade from 1.50 fails removing the configured cloud Daniel Beck Added the specific steps to the description. Thanks! 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.206170.158974000.24218.1589124300250%40Atlassian.JIRA.
[JIRA] (JENKINS-62231) ec2 downgrade from 1.50 fails removing the configured cloud
Title: Message Title Ramon Leon updated JENKINS-62231 Jenkins / JENKINS-62231 ec2 downgrade from 1.50 fails removing the configured cloud 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.206170.158974000.24219.1589124300286%40Atlassian.JIRA.
[JIRA] (JENKINS-62195) ec2-1.50.2 doesn't work with SSH <7.5
Title: Message Title John Jeffers commented on JENKINS-62195 Re: ec2-1.50.2 doesn't work with SSH <7.5 Thank you. I was lucky that I had a backup to recover from. Would have been very bad otherwise. 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.24257.1589126760410%40Atlassian.JIRA.
[JIRA] (JENKINS-62230) Installing plugins seems to be failing for random plugins
Title: Message Title Y K resolved as Duplicate This is resolved, I am now able to download plugins successfully. Jenkins / JENKINS-62230 Installing plugins seems to be failing for random plugins Change By: Y K Status: Open Resolved Resolution: Duplicate 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 ht
[JIRA] (JENKINS-62048) Yaml format validation before running
Title: Message Title Aytunc BEKEN started work on JENKINS-62048 Change By: Aytunc BEKEN 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.205940.158773027.24278.1589131140230%40Atlassian.JIRA.
[JIRA] (JENKINS-62048) Yaml format validation before running
Title: Message Title Aytunc BEKEN closed an issue as Won't Fix Jenkins / JENKINS-62048 Yaml format validation before running Change By: Aytunc BEKEN Status: In Progress Closed Resolution: Won't Fix 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.205940.158773027.24282.1589132280213%40Atlassian.JIRA.
[JIRA] (JENKINS-61949) Configuration of action triggers in an Organization folder
Title: Message Title Aytunc BEKEN commented on JENKINS-61949 Re: Configuration of action triggers in an Organization folder Hi, I fixed the issue with GitHub Organization Folder. Also tested with real repositories in GitHub. This fix is released with 1.8.4 version. I will be glad if you can provide feedback. Thanks. 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.205829.1587131764000.24292.1589133180182%40Atlassian.JIRA.
[JIRA] (JENKINS-62140) Allow use of remote file for non-multibranch pipeline
Title: Message Title Aytunc BEKEN commented on JENKINS-62140 Re: Allow use of remote file for non-multibranch pipeline Let me summarize what I understood. You want to define two repository sources in Pipeline jobs ( not - multibranch pipeline). One of them will be repository for the code, the other one will be for the Jenkins file. Is that right ? If Yes, implementing this with Remote FIle plugin will not be possible as It is implemented for MultiBranch Projects. May this can be a new 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.206059.1588359835000.24295.1589134200201%40Atlassian.JIRA.
[JIRA] (JENKINS-18622) Broken description tool-tip display in Job Name w/ Options
Title: Message Title Tobias Gruetzmacher updated JENKINS-18622 Jenkins / JENKINS-18622 Broken description tool-tip display in Job Name w/ Options Change By: Tobias Gruetzmacher Status: Open Fixed but Unreleased Assignee: Jacob Robertson Tobias Gruetzmacher Resolution: Fixed 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.149932.137294000.24298.1589134500544%40Atlassian.JIRA.
[JIRA] (JENKINS-26336) Compact Columns Plugin does not play well with Folders Plugin
Title: Message Title Tobias Gruetzmacher updated JENKINS-26336 Jenkins / JENKINS-26336 Compact Columns Plugin does not play well with Folders Plugin Change By: Tobias Gruetzmacher Status: Fixed but Unreleased Resolved Released As: https://github.com/jenkinsci/compact-columns-plugin/releases/tag/compact-columns-1.11 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.159998.1420713364000.24302.1589135820500%40Atlassian.JIRA.
[JIRA] (JENKINS-18622) Broken description tool-tip display in Job Name w/ Options
Title: Message Title Tobias Gruetzmacher updated JENKINS-18622 Jenkins / JENKINS-18622 Broken description tool-tip display in Job Name w/ Options Change By: Tobias Gruetzmacher Status: Fixed but Unreleased Resolved Released As: https://github.com/jenkinsci/compact-columns-plugin/releases/tag/compact-columns-1.11 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.149932.137294000.24300.1589135820445%40Atlassian.JIRA.
[JIRA] (JENKINS-44085) have a simple way to limit the number of parallel branches that run concurrently
Title: Message Title Tobias Gruetzmacher commented on JENKINS-44085 Re: have a simple way to limit the number of parallel branches that run concurrently This looks like what the https://github.com/jenkinsci/concurrent-step-plugin wants to achieve. locakable-resources is more for locks between different jobs/runs. cuncurrent-step exposes Java concurrent primitives inside a pipeline run. 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.181710.1494001199000.24306.1589138341097%40Atlassian.JIRA.
[JIRA] (JENKINS-62047) Implement steps with Code Blocks
Title: Message Title Aytunc BEKEN closed an issue as Fixed Jenkins / JENKINS-62047 Implement steps with Code Blocks Change By: Aytunc BEKEN Status: Resolved Closed 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.205939.1587730178000.24369.1589140200508%40Atlassian.JIRA.
[JIRA] (JENKINS-62047) Implement steps with Code Blocks
Title: Message Title Aytunc BEKEN updated JENKINS-62047 Jenkins / JENKINS-62047 Implement steps with Code Blocks Change By: Aytunc BEKEN Status: In Review Resolved Resolution: Fixed 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.205939.1587730178000.24367.1589140200482%40Atlassian.JIRA.
[JIRA] (JENKINS-62047) Implement steps with Code Blocks
Title: Message Title Aytunc BEKEN updated JENKINS-62047 Jenkins / JENKINS-62047 Implement steps with Code Blocks Change By: Aytunc BEKEN 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.205939.1587730178000.24365.1589140200455%40Atlassian.JIRA.
[JIRA] (JENKINS-62046) Convert UI
Title: Message Title Aytunc BEKEN started work on JENKINS-62046 Change By: Aytunc BEKEN 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.205938.158772000.24371.1589142900197%40Atlassian.JIRA.
[JIRA] (JENKINS-62234) jenkins/jenkins:lts fails to ssh connect to EC2 instances
Title: Message Title Brett Delle Grazie created an issue Jenkins / JENKINS-62234 jenkins/jenkins:lts fails to ssh connect to EC2 instances Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2020-05-10 20:37 Environment: Linux Docker jenkins/jenkins:lts container (based on Debian 9/Stretch) Jenkins version 2.222.3 EC2 Plugin 1.50.2 Priority: Minor Reporter: Brett Delle Grazie Due to the recent EC2 SSH Security change in 1.50.2, https://plugins.jenkins.io/ec2/#securing-the-connection-to-unix-amis The expectation is that the SSH connection supports use of StrictHostKeyChecking property with values off, accept-new, yes when connecting to a newly spawned node. Unfortunately Debian 9's ssh client does not support "off" or "accept-new" - it only supports yes/no, which means this plugin breaks in the LTS container. Workaround is to use jenkins/jenkins:lts-slim container which is based on Debian 10/Buster Add Comment
[JIRA] (JENKINS-62235) Default Credentials not used - Authentication failure
Title: Message Title Dominik Jessich created an issue Jenkins / JENKINS-62235 Default Credentials not used - Authentication failure Issue Type: Bug Assignee: Unassigned Attachments: jenkins_global_settings_bitbucket_instance.png, jenkins_multibranch_pipeline_scan_output.png, jenkins_multibranch_pipeline_settings_bitbucket_repository.png Components: atlassian-bitbucket-server-integration-plugin Created: 2020-05-10 22:18 Environment: Jenkins 2.222.3 (installed with RPM using Jenkins YUM repositories) Bitbucket Server 7.2.1 Bitbucket Server Integration Plugin 1.1.0 Priority: Critical Reporter: Dominik Jessich As the plugin documentation from within Jenkins states, when username with password credentials (for build auth) are selected as default for Bitbucket Instance in Jenkins configuration, users are not required to select them and the "global" ones will be used by default. However, leaving the corresponding field for credentials (for build auth) empty in a Multibranch Pipeline Job configuration, results in authentication failure in Bitbucket Server. The repository cannot be scanned, because repository cannot be accessed. This means a core functionality is broken with current plugin version (see environment description). Blocks all users to create a job to checkout from Bitbucket themselves. Workaround: As the admin privileges are required to use the credentials, Jenkins admin needs to select the correct credentials for each job configuration.
[JIRA] (JENKINS-62235) Default Credentials not used - Authentication failure
Title: Message Title Dominik Jessich assigned an issue to Kristy Hughes Jenkins / JENKINS-62235 Default Credentials not used - Authentication failure Change By: Dominik Jessich Assignee: Kristy Hughes 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.206176.1589149087000.24376.1589149260187%40Atlassian.JIRA.
[JIRA] (JENKINS-56508) Service account secret not visible when using folders plugin
Title: Message Title Christopher Orr started work on JENKINS-56508 Change By: Christopher Orr 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.198115.1552334901000.24379.1589150040409%40Atlassian.JIRA.
[JIRA] (JENKINS-33369) Recommended plugins for 2.0 should refer to "agents" rather than "slaves"
Title: Message Title Christopher Orr resolved as Done This is pretty old, and looking at just the plugin names, I think it was just the SSH and Windows slave plugins which were affected — they have since been renamed: https://issues.jenkins-ci.org/browse/JENKINS-59427 https://github.com/jenkinsci/windows-slaves-plugin/pull/15 Jenkins / JENKINS-33369 Recommended plugins for 2.0 should refer to "agents" rather than "slaves" Change By: Christopher Orr Status: Open Resolved Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-33369) Recommended plugins for 2.0 should refer to "agents" rather than "slaves"
Title: Message Title Christopher Orr closed an issue as Done Jenkins / JENKINS-33369 Recommended plugins for 2.0 should refer to "agents" rather than "slaves" Change By: Christopher Orr Status: Resolved Closed Assignee: Christopher Orr 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.168775.1457395431000.24388.1589153220967%40Atlassian.JIRA.
[JIRA] (JENKINS-62236) add/remove folders to the existing roles and add/remove multiple users at one time
Title: Message Title Mehul Oswal created an issue Jenkins / JENKINS-62236 add/remove folders to the existing roles and add/remove multiple users at one time Issue Type: Improvement Assignee: Abhyudaya Sharma Components: folder-auth-plugin Created: 2020-05-11 01:16 Priority: Minor Reporter: Mehul Oswal 1) Can we add option to add/remove folders to the existing roles in UI similar to assign/remove SID. Since it is not available today, we have to delete the role and re-create it with correct folder selections which is very painful especially if you have big list of users as users (SID) are added one at a time. This leads to second improvement. 2) Can we add the feature to add/remove multiple users at one time in UI. This would be very useful when someone needs to add say for example 100 users or remove list of users at a time. Today it's being done one at a time which is time consuming. Add Comment
[JIRA] (JENKINS-44085) have a simple way to limit the number of parallel branches that run concurrently
Title: Message Title jerry wiltse commented on JENKINS-44085 Re: have a simple way to limit the number of parallel branches that run concurrently Yes, i opened issue in February asking for release here: https://github.com/jenkinsci/concurrent-step-plugin/issues/5 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.181710.1494001199000.24396.1589161800963%40Atlassian.JIRA.
[JIRA] (JENKINS-62237) Release new plugin version
Title: Message Title Yi Gong created an issue Jenkins / JENKINS-62237 Release new plugin version Issue Type: Task Assignee: Aleksi Simell Components: influxdb-plugin Created: 2020-05-11 02:10 Priority: Major Reporter: Yi Gong I see the [junit report|https://github.com/jenkinsci/influxdb-plugin/pull/98] is merged. Please release a new version. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-62237) Release new plugin version
Title: Message Title Aleksi Simell commented on JENKINS-62237 Re: Release new plugin version I will, once I fix the failing build issue. Please, be a bit more patient. 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.206178.1589163024000.24454.1589171880120%40Atlassian.JIRA.
[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Ashok T R commented on JENKINS-58987 Re: issue_updated trigger handler can't find "name" field in JSON Hi all, any update on this issue.. 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.201336.1566200967000.24457.1589172540286%40Atlassian.JIRA.
[JIRA] (JENKINS-61006) AWS EC2 plugin failing to connect to Windows Slave
Title: Message Title Raihaan Shouhell commented on JENKINS-61006 Re: AWS EC2 plugin failing to connect to Windows Slave Hey PJ, how do you reproduce this issue? Which version of windows server are you using? I could not replicate this issue on Server 2016 and server 2019. Do you have port 445 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.204476.1581025948000.24467.1589176140177%40Atlassian.JIRA.
[JIRA] (JENKINS-41218) Provide native systemd unit
Title: Message Title Eugen Stan commented on JENKINS-41218 Re: Provide native systemd unit Hello, What can I/we do to have this fix applied? Systemd has become the defacto service manager across major / all distributions. There are new releases in Debian and RHEL that use systemd. There are great benefits to have apps managed by systemd. It would be great to have this upstream. Even if it is disabled and we need to `systemctl enable ` it manually. Looking forward for your feedback. Thanks 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.177980.148483898.24471.1589176260463%40Atlassian.JIRA.
[JIRA] (JENKINS-41218) Provide native systemd unit
Title: Message Title Dirk Heinrichs commented on JENKINS-41218 Re: Provide native systemd unit The above is for running Jenkins in Tomcat, isn't it? It also seems to be RedHat specific (/etc/sysconfig). When running apps in Tomcat, one usually just need to start Tomcat itself, which in turn takes care of starting all the webapps deployed to it. So setting up a "tomcat@.service" for single webapps doesn't seem to be necessary at all (and also feels wrong given that this would mean to start one Tomcat instance for each webapp configured this way). OTOH, this ticket is about a "native" systemd unit, which I think means: One that starts Jenkins standalone, just like the current sys-v init script does. 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.177980.148483898.24485.1589178120431%40Atlassian.JIRA.
[JIRA] (JENKINS-62218) Read-only job configuration for folders
Title: Message Title Francisco Fernández assigned an issue to Unassigned Jenkins / JENKINS-62218 Read-only job configuration for folders Change By: Francisco Fernández Assignee: Francisco Fernández 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.206152.1588928862000.24498.1589178960246%40Atlassian.JIRA.
