[JIRA] (JENKINS-19058) ec2-plugin cannot add specified instance tags on launched spot instances
Title: Message Title Mykola Marzhan commented on JENKINS-19058 Re: ec2-plugin cannot add specified instance tags on launched spot instances I still don't have tags on spot instances in plugin version 1.39, Jenkins 2.136 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53003) HP Tools Launcher is crash in long runs(13hrs+)
Title: Message Title Omer Kenan created an issue Jenkins / JENKINS-53003 HP Tools Launcher is crash in long runs(13hrs+) Issue Type: Bug Assignee: Rolando-Mihai Vlad Attachments: Crash.PNG, WER4719.tmp.WERInternalMetadata.xml, WER4C19.tmp.appcompat.txt, WER4C68.tmp.mdmp Components: hp-application-automation-tools-plugin Created: 2018-08-13 06:23 Environment: Windows 7SP1 with LR12.57Plugin5.5,Jenkins build 2.121.1 Labels: plugin Priority: Major Reporter: Omer Kenan Free Style Project: Started by user anonymous Building remotely on 10.199.143.201 (LR1257) in workspace C:\Jtest\workspace\LR_FS [LR_FS] $ C:\Jtest\workspace\LR_FS\HpToolsLauncher.exe -paramfile props12082018200213369.txt "Started..." Launcher timeout is 00::13:20:00 Controller Polling Interval: 30 seconds PerScenarioTimeout: 00::00:10:00 minutes FileSystemTestRunner timeout is 13:20:00 Mc connection info is - Mc HostAddress: , McPort: 8080, Username: , TenantId: , UseSSL: 0, UseProxy: 0, ProxyType: 0, ProxyAddress: , ProxyPort: 0, ProxyAuth: 0, ProxyUser: 1 tests found: C:\Jtest\SLA\SLAlongrun.lrs 12/08/2018 20:02:08 Running: C:\Jtest\SLA\SLAlongrun.lrs C:\Jtest\SLA\SLAlongrun.lrs Cleaning up the environment... Preparing scenario C:\Jtest\SLA\SLAlongrun.lrs for execution. Load Generator localhost connected setting scen
[JIRA] (JENKINS-52903) Cloudfoundry plugin creates lock on manifest.yml
Title: Message Title Olivier Lamy assigned an issue to Unassigned Jenkins / JENKINS-52903 Cloudfoundry plugin creates lock on manifest.yml Change By: Olivier Lamy Assignee: Olivier Lamy Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52898) Add support for API KEY authentication for cloudfoundry plugin
Title: Message Title Olivier Lamy assigned an issue to Unassigned Jenkins / JENKINS-52898 Add support for API KEY authentication for cloudfoundry plugin Change By: Olivier Lamy Assignee: Olivier Lamy Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37599) f:repeatable mishandles minimum (was: Custom Groovy Script for Promoted Builds always includes bogus classpath entry)
Title: Message Title ikedam updated JENKINS-37599 Jenkins / JENKINS-37599 f:repeatable mishandles minimum (was: Custom Groovy Script for Promoted Builds always includes bogus classpath entry) Change By: ikedam Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37599) f:repeatable mishandles minimum (was: Custom Groovy Script for Promoted Builds always includes bogus classpath entry)
Title: Message Title ikedam started work on JENKINS-37599 Change By: ikedam Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37599) f:repeatable mishandles minimum (was: Custom Groovy Script for Promoted Builds always includes bogus classpath entry)
Title: Message Title ikedam commented on JENKINS-37599 Re: f:repeatable mishandles minimum (was: Custom Groovy Script for Promoted Builds always includes bogus classpath entry) https://github.com/jenkinsci/jenkins/pull/3583 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44824) "minimum" of f:repeatableProperty is inherit from ancestors
Title: Message Title ikedam updated JENKINS-44824 Looks like the same issue reported in JENKINS-37599. I'll fix that in JENKINS-37599. Please watch that ticket instead. Jenkins / JENKINS-44824 "minimum" of f:repeatableProperty is inherit from ancestors Change By: ikedam Status: Open Fixed but Unreleased Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37599) f:repeatable mishandles minimum (was: Custom Groovy Script for Promoted Builds always includes bogus classpath entry)
Title: Message Title ikedam commented on JENKINS-37599 Re: f:repeatable mishandles minimum (was: Custom Groovy Script for Promoted Builds always includes bogus classpath entry) This looks an issue of Jenkins core rather than that of script-security or promoted-build, and should be fixed in core. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37599) f:repeatable mishandles minimum (was: Custom Groovy Script for Promoted Builds always includes bogus classpath entry)
Title: Message Title ikedam assigned an issue to ikedam Jenkins / JENKINS-37599 f:repeatable mishandles minimum (was: Custom Groovy Script for Promoted Builds always includes bogus classpath entry) Change By: ikedam Assignee: ikedam Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52955) On Saving the Project, error message is displayed
Title: Message Title Daniel Gront commented on JENKINS-52955 Re: On Saving the Project, error message is displayed This issue was resolved in the JENKINS-52752 and you can find a hotfix there, or you can wait for the release which contains the changes to fix it. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52955) On Saving the Project, error message is displayed
Title: Message Title Daniel Gront closed an issue as Fixed Jenkins / JENKINS-52955 On Saving the Project, error message is displayed Change By: Daniel Gront Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52955) On Saving the Project, error message is displayed
Title: Message Title Daniel Gront edited a comment on JENKINS-52955 Re: On Saving the Project, error message is displayed This issue was resolved in the https://issues.jenkins-ci.org/browse/ JENKINS- 52752 52366 and you can find a hotfix there, or you can wait for the release which contains the changes to fix it. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53002) Resource request in declarative pod template ignored
Title: Message Title
Ray Lim updated an issue
Jenkins / JENKINS-53002
Resource request in declarative pod template ignored
Change By:
Ray Lim
I am facing issue with configuring resource limits in declarative pipelines. It is not recognized. Jenkins config and scripted pipeline works. On declarative pipeline and doing describe pod, it always doesn't show the request and limits configured.See pipeline snippet below (maven container doesn't run with the limits stated){code:java}pipeline { agent {kubernetes { label env.BUILD_TAG inheritFrom 'BASE' defaultContainer 'jnlp' yaml """spec: containers: - name: mavenimage: maven: 3.5-jdk-8resourceRequestMemory: 500MiresourceLimitMemory: 1000MialwaysPullImage: truetty: trueworkingDir: /var/lib/jenkinscommand:- cat"""{code}
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32898) Disable Strict Forbidden File Verification option always causes trigger
Title: Message Title Chao Zheng commented on JENKINS-32898 Re: Disable Strict Forbidden File Verification option always causes trigger Same problem. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53002) Resource request in declarative pod template ignored
Title: Message Title
Ray Lim created an issue
Jenkins / JENKINS-53002
Resource request in declarative pod template ignored
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2018-08-13 02:59
Environment:
CJP 2.73 Kubernetes Plugin 1.8.4
Priority:
Minor
Reporter:
Ray Lim
I am facing issue with configuring resource limits in declarative pipelines. It is not recognized. Jenkins config and scripted pipeline works. On declarative pipeline and doing describe pod, it always doesn't show the request and limits configured. See pipeline snippet below (maven container doesn't run with the limits stated)
pipeline {
agent {
kubernetes {
label env.BUILD_TAG
inheritFrom 'BASE'
defaultContainer 'jnlp'
yaml """
spec:
containers:
- name: maven
image: maven: 3.5-jdk-8
resourceRequestMemory: 500Mi
resourceLimitMemory: 1000Mi
alwaysPullImage: true
tty: true
workingDir: /var/lib/jenkins
command:
- cat
"""
[JIRA] (JENKINS-53001) When using the same label 2+ times in a parallel block, plugin only launches one agent
Title: Message Title Owen Mehegan assigned an issue to Philipp Garbe Jenkins / JENKINS-53001 When using the same label 2+ times in a parallel block, plugin only launches one agent Change By: Owen Mehegan Assignee: Jan Roehrich Philipp Garbe Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53001) When using the same label 2+ times in a parallel block, plugin only launches one agent
Title: Message Title
Owen Mehegan created an issue
Jenkins / JENKINS-53001
When using the same label 2+ times in a parallel block, plugin only launches one agent
Issue Type:
Bug
Assignee:
Jan Roehrich
Components:
amazon-ecs-plugin
Created:
2018-08-13 02:01
Environment:
amazon-ecs plugin version 1.16
Priority:
Major
Reporter:
Owen Mehegan
If you have one agent template with labels defined, and you create a Pipeline job that requests nodes of the same label in a parallel block, only one ECS agent will be launched. As a result, the work is only done serially, rather than in parallel as expected, because only one executor is available. Example Pipeline code:
def tasks = [:]
tasks["task_1"] = {
stage ("task_1"){
node('mylabel') {
sh 'echo foo'
}
}
}
tasks["task_2"] = {
stage ("task_2"){
node('mylabel') {
sh 'echo bar'
}
}
}
parallel tasks
If you run two copies of this job, or any other job that uses the same label, an agent will be launched for each job that is running. And if the parallel block of your Pipeline job refers to two different labels, then two agents will be launched. The issue is only with uses of the same label within the parallel branches.
[JIRA] (JENKINS-51636) No pipeline when branch name contains space
Title: Message Title
James Mitchell edited a comment on JENKINS-51636
Re: No pipeline when branch name contains space
I'm also having similar issues, using Perforce for the underlying version control system, using spaces not {{@}}, it appears the string is being encoded twice 'Hello World' becomes 'Hello%2520World" with %25 being '%' and '%20' being the space. NOTE: This only occurs on the branch, not the other parts of the string (e.g. job name)
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51636) No pipeline when branch name contains space
Title: Message Title James Mitchell commented on JENKINS-51636 Re: No pipeline when branch name contains space I'm also having similar issues, using Perforce for the underlying version control system, using spaces not @, it appears the string is being encoded twice 'Hello World' becomes 'Hello%2520World" with %25 being '%' and '%20' being the space. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52999) Error on active directory configaration: Domain Controller is reachable but the service on the specified port is not reachable
Title: Message Title
ARJUN SREEPAD updated an issue
Jenkins / JENKINS-52999
Error on active directory configaration: Domain Controller is reachable but the service on the specified port is not reachable
Change By:
ARJUN SREEPAD
I am getting below error on trying to connect to our comany Active directoryFew points to add:I am using [Jenkins ver. 2.79|https://jenkins.io/] + RHEL + JBoss ServerBut same configaration is working using [Jenkins ver. 2.134|https://jenkins.io/] + Windows + TOmcat on my local machineFrom the server i am able to do telnet and ipconfig for the desired ip{quote}!http://lnxdevvm891:8080/jenkins/static/ec071acf/images/none.gif|width=1,height=16! Domain Controller is reachable but the service on the specified port is not reachablejavax.naming.ServiceUnavailableException: corp.emirates.com:389 X ; socket closed at com.sun.jndi.ldap.Connection.readReply(Connection.java:454) at com.sun.jndi.ldap.LdapClient.ldapBind(LdapClient.java:365) at com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:214) at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2788) at com.sun.jndi.ldap.LdapCtx.ensureOpen(LdapCtx.java:2696) at com.sun.jndi.ldap.LdapCtx.ensureOpen(LdapCtx.java:2670) at com.sun.jndi.ldap.LdapCtx.reconnect(LdapCtx.java:2666) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:703) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:645) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:592) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:557) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:626) at hudson.plugins.active_directory.ActiveDirectoryDomain$DescriptorImpl.doValidateTest(ActiveDirectoryDomain.java:305) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) {quote}h1.
[JIRA] (JENKINS-52999) Error on active directory configaration: Domain Controller is reachable but the service on the specified port is not reachable
Title: Message Title ARJUN SREEPAD updated an issue Jenkins / JENKINS-52999 Error on active directory configaration: Domain Controller is reachable but the service on the specified port is not reachable Change By: ARJUN SREEPAD Attachment: jira error.jpg Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52950) CLI enable-plugin -restart restarts even if no plugins are enabled
Title: Message Title Daniel Beck commented on JENKINS-52950 Re: CLI enable-plugin -restart restarts even if no plugins are enabled Matt Sicker FYI Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52999) Error on active directory configaration: Domain Controller is reachable but the service on the specified port is not reachable
Title: Message Title ARJUN SREEPAD updated an issue Jenkins / JENKINS-52999 Error on active directory configaration: Domain Controller is reachable but the service on the specified port is not reachable Change By: ARJUN SREEPAD Attachment: jira error.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52576) Logs are flooded when sleep/touch are not available in the docker image
Title: Message Title Daniel Beck commented on JENKINS-52576 Re: Logs are flooded when sleep/touch are not available in the docker image Does Durable Task 1.25 fix this? https://plugins.jenkins.io/durable-task mentions JENKINS-52881. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52924) Durable Task 1.23 broke bash scripting on Windows agents via Cygwin
Title: Message Title Daniel Beck closed an issue as Duplicate Apparently fixed in 1.25. Jenkins / JENKINS-52924 Durable Task 1.23 broke bash scripting on Windows agents via Cygwin Change By: Daniel Beck Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52924) Durable Task 1.23 broke bash scripting on Windows agents via Cygwin
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-52924 Durable Task 1.23 broke bash scripting on Windows agents via Cygwin Change By: Daniel Beck Labels: regression Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52594) Cppcheck report XMLs field doesn't retain data after update to 1.22
Title: Message Title Stefan Fleischmann updated JENKINS-52594 Jenkins / JENKINS-52594 Cppcheck report XMLs field doesn't retain data after update to 1.22 Change By: Stefan Fleischmann Status: Closed In Review Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52594) Cppcheck report XMLs field doesn't retain data after update to 1.22
Title: Message Title Stefan Fleischmann commented on JENKINS-52594 Re: Cppcheck report XMLs field doesn't retain data after update to 1.22 After updating from 1.21 to 1.23 I see unreadable data in the old data section in Jenkins for the projects that use cppcheck and I have to reconfigure each one of them. So this update effectively breaks existing projects. Looks like with this fix the data syntax was changed. Old config looks like this: [...] "cppcheck@1.21"> **/cppcheck-*.xml [...] new config: [...] "cppcheck@1.23"> **/cppcheck-*.xml [...] Is it not possible to migrate the old data automatically? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52663) Change the plugin name and the yaml file name for future compatibility
Title: Message Title Abhishek Gautam updated JENKINS-52663 Jenkins / JENKINS-52663 Change the plugin name and the yaml file name for future compatibility Change By: Abhishek Gautam Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52843) Push SPRP specific YAML syntax to sub-element
Title: Message Title Abhishek Gautam started work on JENKINS-52843 Change By: Abhishek Gautam Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52663) Change the plugin name and the yaml file name for future compatibility
Title: Message Title Abhishek Gautam started work on JENKINS-52663 Change By: Abhishek Gautam Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52843) Push SPRP specific YAML syntax to sub-element
Title: Message Title Abhishek Gautam updated JENKINS-52843 Jenkins / JENKINS-52843 Push SPRP specific YAML syntax to sub-element Change By: Abhishek Gautam Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52518) Finalise documentation
Title: Message Title Abhishek Gautam started work on JENKINS-52518 Change By: Abhishek Gautam Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52588) Create blog post for 1.0 SPRP release
Title: Message Title Abhishek Gautam started work on JENKINS-52588 Change By: Abhishek Gautam Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49050) I can view my sequential declarative pipeline stages in the pipeline visualization plugin
Title: Message Title Nicolae Pascu commented on JENKINS-49050 Re: I can view my sequential declarative pipeline stages in the pipeline visualization plugin Hi Marcin Grinberg, this feature will land in the next version of blueocean, which will be 1.8 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52887) Getting error while running jenkins war in command prompt
Title: Message Title Ivan Fernandez Calvo closed an issue as Not A Defect Jenkins / JENKINS-52887 Getting error while running jenkins war in command prompt Change By: Ivan Fernandez Calvo Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53000) Add support for GCP templates
Title: Message Title Karol Lassak created an issue Jenkins / JENKINS-53000 Add support for GCP templates Issue Type: New Feature Assignee: Evan Brown Components: google-compute-engine-plugin Created: 2018-08-12 17:36 Labels: plugin slave Priority: Major Reporter: Karol Lassak Would be nice to have option to set GCP template instead of setting all required variables in plugin configuration. If template would be used only some options would be set in jenkins (like labels and timeouts) That would allow to moving most of configuration related to instance into GCP where could be automatised using terraform or similar tools. That would also allow to set some options that are now not available thru plugins like extra labels, use custom instances, or adding local SSD discs, or any other option that will be added to GCP. And if done correctly would simplify plugin a lot. Add Comment
[JIRA] (JENKINS-52491) Detach snippet generator to extensions.
Title: Message Title Abhishek Gautam updated JENKINS-52491 Pull request is merged. Jenkins / JENKINS-52491 Detach snippet generator to extensions. Change By: Abhishek Gautam Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52491) Detach snippet generator to extensions.
Title: Message Title Abhishek Gautam started work on JENKINS-52491 Change By: Abhishek Gautam Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52491) Detach snippet generator to extensions.
Title: Message Title Abhishek Gautam updated JENKINS-52491 Jenkins / JENKINS-52491 Detach snippet generator to extensions. Change By: Abhishek Gautam Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52999) Error on active directory configaration: Domain Controller is reachable but the service on the specified port is not reachable
Title: Message Title ARJUN SREEPAD updated an issue Jenkins / JENKINS-52999 Error on active directory configaration: Domain Controller is reachable but the service on the specified port is not reachable Change By: ARJUN SREEPAD Priority: Critical Blocker Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52999) Error on active directory configaration: Domain Controller is reachable but the service on the specified port is not reachable
Title: Message Title ARJUN SREEPAD updated an issue Jenkins / JENKINS-52999 Error on active directory configaration: Domain Controller is reachable but the service on the specified port is not reachable Change By: ARJUN SREEPAD Summary: Erro Error on active directory configaration: Domain Controller is reachable but the service on the specified port is not reachable Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52999) Erro on active directory configaration: Domain Controller is reachable but the service on the specified port is not reachable
Title: Message Title ARJUN SREEPAD created an issue Jenkins / JENKINS-52999 Erro on active directory configaration: Domain Controller is reachable but the service on the specified port is not reachable Issue Type: Bug Assignee: Félix Belzunce Arcos Attachments: jira error.png Components: active-directory-plugin Created: 2018-08-12 14:51 Environment: Prod Priority: Critical Reporter: ARJUN SREEPAD I am getting below error on trying to connect to our comany Active directory Few points to add: I am using Jenkins ver. 2.79 + RHEL + JBoss Server But same configaration is working using Jenkins ver. 2.134 + Windows + TOmcat on my local machine From the server i am able to do telnet and ipconfig for the desired ip Domain Controller is reachable but the service on the specified port is not reachable javax.naming.ServiceUnavailableException: corp.emirates.com:389; socket closed at com.sun.jndi.ldap.Connection.readReply(Connection.java:454) at com.sun.jndi.ldap.LdapClient.ldapBind(LdapClient.java:365) at com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:214) at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2788) at com.sun.jndi.ldap.LdapCtx.ensureOpen(LdapCtx.java:2696) at com.sun.jndi.ldap.LdapCtx.ensureOpen(LdapCtx.java:2670) at com.sun.jndi.ldap.LdapCtx.reconnect(LdapCtx.java:2666) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:703) at hudson.plugins.active_directory.ActiveDi
[JIRA] (JENKINS-52997) cifsPublisher plugin not copying right files using wildcards
Title: Message Title Alex Earl commented on JENKINS-52997 Re: cifsPublisher plugin not copying right files using wildcards patternSeparator should not be empty. Either remove it from the parameters, or set to '[ ,]+' Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51960) ClassNotFoundException: org.apache.xerces.parsers.SAXParser
Title: Message Title Daniel Beck commented on JENKINS-51960 Re: ClassNotFoundException: org.apache.xerces.parsers.SAXParser The core update seems unrelated, https://jenkins.io/changelog/#v2.127 has nothing. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51960) ClassNotFoundException: org.apache.xerces.parsers.SAXParser
Title: Message Title Daniel Beck commented on JENKINS-51960 Re: ClassNotFoundException: org.apache.xerces.parsers.SAXParser This looks specific to plugin depending on the aws-java-sdk plugin (or perhaps bundling the AWS SDK, resulting in a conflict). Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51960) ClassNotFoundException: org.apache.xerces.parsers.SAXParser
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-51960 ClassNotFoundException: org.apache.xerces.parsers.SAXParser Change By: Daniel Beck Component/s: aws-java-sdk-plugin Component/s: pipeline-aws-plugin Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52613) cannot relaunch ssh agent, when node dies
Title: Message Title Ivan Fernandez Calvo edited a comment on JENKINS-52613 Re: cannot relaunch ssh agent, when node dies means that fails to connect, because you do not have retries and timeouts configured, Jenkins will wait about 5 min to retry to connect (retention strategy), if you configure 10 retries, 15 seconds between retries, and a timeout of about 240 seconds you will not have to disconnect an reconnect the agent when it happens, it will reconnect automatically if it is possible, and you will see the reconnections on the log. The next version will have those values by default to avoid this confused situation. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52613) cannot relaunch ssh agent, when node dies
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-52613 Re: cannot relaunch ssh agent, when node dies means that fails to connect, because you do not have retries and timeouts configured, Jenkins will wait about 5 min to retry to connect (retention strategy), if you configure 10 retries, 15 seconds between retries, and a timeout of about 240 seconds you will not have to disconnect an reconnect the agent when it happens, it will reconnect automatically if it is possible, and you will see the reconnections on the log. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52613) cannot relaunch ssh agent, when node dies
Title: Message Title Ivan Fernandez Calvo started work on JENKINS-52613 Change By: Ivan Fernandez Calvo Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50861) Update core and Pipeline SCM step dependencies
Title: Message Title Ivan Fernandez Calvo updated JENKINS-50861 Jenkins / JENKINS-50861 Update core and Pipeline SCM step dependencies Change By: Ivan Fernandez Calvo Status: In Review Resolved Resolution: Fixed Released As: subversion-2.11.0 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52981) Pipeline: success after checkout error
Title: Message Title Ivan Fernandez Calvo assigned an issue to Unassigned Jenkins / JENKINS-52981 Pipeline: success after checkout error Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52891) Always log the timeout for a CliGit command
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-52891 Always log the timeout for a CliGit command Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52814) Build status set to failed but not failed immediately
Title: Message Title Nikolas Falco closed an issue as Not A Defect It works as design, the XUnit builder/publisher marks the build status in agreement with the values of thresholds. Only the builder (deprecated) abort the build in case of errors when process reports and the option 'Stop and set the build to 'failed' status if there are errors when processing a result file' is enabled Jenkins / JENKINS-52814 Build status set to failed but not failed immediately Change By: Nikolas Falco Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52891) Always log the timeout for a CliGit command
Title: Message Title René Scheibe updated JENKINS-52891 resolved with https://github.com/jenkinsci/git-client-plugin/pull/350 Jenkins / JENKINS-52891 Always log the timeout for a CliGit command Change By: René Scheibe Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52891) Always log the timeout for a CliGit command
Title: Message Title René Scheibe assigned an issue to Mark Waite Jenkins / JENKINS-52891 Always log the timeout for a CliGit command Change By: René Scheibe Assignee: René Scheibe Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52998) JobRequeue plugin support for Jenkins Job Builder
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-52998 JobRequeue plugin support for Jenkins Job Builder Change By: Oleg Nenashev Labels: plugin other Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52998) JobRequeue plugin support for Jenkins Job Builder
Title: Message Title Oleg Nenashev moved an issue Jenkins / JENKINS-52998 JobRequeue plugin support for Jenkins Job Builder Change By: Oleg Nenashev Project: Infrastructure Jenkins Key: INFRA JENKINS - 1736 52998 Workflow: classic default workflow JNJira + In-Review Component/s: other Component/s: ci Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52997) cifsPublisher plugin not copying right files using wildcards
Title: Message Title Oleg Nenashev moved an issue Jenkins / JENKINS-52997 cifsPublisher plugin not copying right files using wildcards Change By: Oleg Nenashev Project: Infrastructure Jenkins Key: INFRA JENKINS - 1745 52997 Workflow: classic default workflow JNJira + In-Review Component/s: cifs-plugin Component/s: core Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52997) cifsPublisher plugin not copying right files using wildcards
Title: Message Title Oleg Nenashev assigned an issue to Alex Earl Jenkins / JENKINS-52997 cifsPublisher plugin not copying right files using wildcards Change By: Oleg Nenashev Assignee: Alex Earl Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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. For more options, visit https://groups.google.com/d/optout.
