[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title
Anton Yurchenko edited a comment on JENKINS-53952
Re: Linux slaves are not starting anymore
We've got the same issue. Jenkins ver 2.150.1, plugin version 1.41.+That issue occurs only when requesting a spot instance.+{code:java}Dec 19, 2018 7:27:36 AM hudson.plugins.ec2.EC2CloudINFO: Launching instance: nullDec 19, 2018 7:27:36 AM hudson.plugins.ec2.EC2CloudINFO: bootstrap()Dec 19, 2018 7:27:36 AM hudson.plugins.ec2.EC2CloudINFO: Getting keypair...Dec 19, 2018 7:27:37 AM hudson.plugins.ec2.EC2CloudINFO: Using key: ssh-key[..]Dec 19, 2018 7:27:37 AM hudson.plugins.ec2.EC2CloudINFO: Authenticating as ec2-userERROR: Unexpected error in launching an agent. This is probably a bug in Jenkinsjava.lang.NullPointerException at hudson.plugins.ec2.ssh.EC2UnixLauncher.getEC2HostAddress(EC2UnixLauncher.java:367) at hudson.plugins.ec2.ssh.EC2UnixLauncher.connectToSsh(EC2UnixLauncher.java:319) at hudson.plugins.ec2.ssh.EC2UnixLauncher.bootstrap(EC2UnixLauncher.java:283) at hudson.plugins.ec2.ssh.EC2UnixLauncher.launchScript(EC2UnixLauncher.java:130) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:48) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748){code}{code:java}Dec 19, 2018 7:27:35 AM hudson.plugins.ec2.SlaveTemplate provisionSpotINFO: Launching ami-04750af7488d87g5c for template builderDec 19, 2018 7:27:36 AM hudson.plugins.ec2.SlaveTemplate provisionSpotINFO: Spot instance id in provision: sir-8mki4f8kDec 19, 2018 7:27:36 AM hudson.plugins.ec2.EC2RetentionStrategy startINFO: Start requested for builder (sir-8mki4f8k)Dec 19, 2018 7:27:36 AM hudson.plugins.ec2.EC2Cloud logINFO: Launching instance: nullDec 19, 2018 7:27:36 AM hudson.plugins.ec2.EC2Cloud logINFO: bootstrap()Dec 19, 2018 7:27:36 AM hudson.plugins.ec2.EC2Cloud logINFO: Getting keypair...Dec 19, 2018 7:27:37 AM hudson.plugins.ec2.EC2Cloud logINFO: Using key: ssh-key[]Dec 19, 2018 7:27:37 AM hudson.plugins.ec2.EC2Cloud logINFO: Authenticating as ec2-user{code} Manually clicking *Launch Agent* works and instances comes online fine.
Add Comment
[JIRA] (JENKINS-55252) Build Trigger Badge plugin shows me question mark for build by parameterized scheduler
Title: Message Title Marc Brugger assigned an issue to Baptiste Mathus Jenkins / JENKINS-55252 Build Trigger Badge plugin shows me question mark for build by parameterized scheduler Change By: Marc Brugger Assignee: Marc Brugger Baptiste Mathus Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55252) Build Trigger Badge plugin shows me question mark for build by parameterized scheduler
Title: Message Title Marc Brugger commented on JENKINS-55252 Re: Build Trigger Badge plugin shows me question mark for build by parameterized scheduler You got the wrong plugin in this JIRA, I reassigned it to buildtriggerbadge-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55252) Build Trigger Badge plugin shows me question mark for build by parameterized scheduler
Title: Message Title Marc Brugger updated an issue Jenkins / JENKINS-55252 Build Trigger Badge plugin shows me question mark for build by parameterized scheduler Change By: Marc Brugger Component/s: buildtriggerbadge-plugin Component/s: badge-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-53952) Linux slaves are not starting anymore
Title: Message Title Anton Yurchenko commented on JENKINS-53952 Re: Linux slaves are not starting anymore We've got the same issue. Jenkins ver 2.150.1, plugin version 1.41. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54864) github multibranch builds fail to build with latest branch api update
Title: Message Title Andy Airey updated an issue Jenkins / JENKINS-54864 github multibranch builds fail to build with latest branch api update Change By: Andy Airey Attachment: bitbucket-branch-source-plugin-config.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55252) Build Trigger Badge plugin shows me question mark for build by parameterized scheduler
Title: Message Title Jiuk Jeong edited a comment on JENKINS-55252 Re: Build Trigger Badge plugin shows me question mark for build by parameterized scheduler Dear [~bakito] !questionmark.PNG!I sent pull request in Jira. Please check it too.[https://github.com/jenkinsci/buildtriggerbadge-plugin/pull/33] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55252) Build Trigger Badge plugin shows me question mark for build by parameterized scheduler
Title: Message Title Jiuk Jeong updated an issue Jenkins / JENKINS-55252 Build Trigger Badge plugin shows me question mark for build by parameterized scheduler Change By: Jiuk Jeong Attachment: questionmark.PNG Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55252) Build Trigger Badge plugin shows me question mark for build by parameterized scheduler
Title: Message Title Jiuk Jeong commented on JENKINS-55252 Re: Build Trigger Badge plugin shows me question mark for build by parameterized scheduler I sent pull request in Jira. Please check it too. https://github.com/jenkinsci/buildtriggerbadge-plugin/pull/33 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55252) Build Trigger Badge plugin shows me question mark for build by parameterized scheduler
Title: Message Title Jiuk Jeong updated an issue Jenkins / JENKINS-55252 Build Trigger Badge plugin shows me question mark for build by parameterized scheduler Change By: Jiuk Jeong Attachment: jenkins_publish-over-ftp_globalsetting.PNG Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55252) Build Trigger Badge plugin shows me question mark for build by parameterized scheduler
Title: Message Title Jiuk Jeong updated an issue Jenkins / JENKINS-55252 Build Trigger Badge plugin shows me question mark for build by parameterized scheduler Change By: Jiuk Jeong Attachment: jenkins_publish-over-ftp_globalsetting.PNG Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-53952) Linux slaves are not starting anymore
Title: Message Title
Anton Yurchenko edited a comment on JENKINS-53952
Re: Linux slaves are not starting anymore
We've got the same issue. Jenkins ver 2.150.1, plugin version 1.41. +That issue occurs only when requesting a spot instance.+ {code:java}Dec 19, 2018 7:27:36 AM hudson.plugins.ec2.EC2CloudINFO: Launching instance: nullDec 19, 2018 7:27:36 AM hudson.plugins.ec2.EC2CloudINFO: bootstrap()Dec 19, 2018 7:27:36 AM hudson.plugins.ec2.EC2CloudINFO: Getting keypair...Dec 19, 2018 7:27:37 AM hudson.plugins.ec2.EC2CloudINFO: Using key: ssh-key[..]Dec 19, 2018 7:27:37 AM hudson.plugins.ec2.EC2CloudINFO: Authenticating as ec2-userERROR: Unexpected error in launching an agent. This is probably a bug in Jenkinsjava.lang.NullPointerException at hudson.plugins.ec2.ssh.EC2UnixLauncher.getEC2HostAddress(EC2UnixLauncher.java:367) at hudson.plugins.ec2.ssh.EC2UnixLauncher.connectToSsh(EC2UnixLauncher.java:319) at hudson.plugins.ec2.ssh.EC2UnixLauncher.bootstrap(EC2UnixLauncher.java:283) at hudson.plugins.ec2.ssh.EC2UnixLauncher.launchScript(EC2UnixLauncher.java:130) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:48) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748){code} +That issue occurs only when requesting a spot {code:java}Dec 19, 2018 7:27:35 AM hudson.plugins.ec2.SlaveTemplate provisionSpotINFO: Launching ami-04750af7488d87g5c for template builderDec 19, 2018 7:27:36 AM hudson.plugins.ec2.SlaveTemplate provisionSpotINFO: Spot instance id in provision: sir-8mki4f8kDec 19, 2018 7:27:36 AM hudson . + plugins.ec2.EC2RetentionStrategy startINFO: Start requested for builder (sir-8mki4f8k)Dec 19, 2018 7:27:36 AM hudson.plugins.ec2.EC2Cloud logINFO: Launching instance: nullDec 19, 2018 7:27:36 AM hudson.plugins.ec2.EC2Cloud logINFO: bootstrap()Dec 19, 2018 7:27:36 AM hudson.plugins.ec2.EC2Cloud logINFO: Getting keypair...Dec 19, 2018 7:27:37 AM hudson.plugins.ec2.EC2Cloud logINFO: Using key: ssh-key[]Dec 19, 2018 7:27:37 AM hudson.plugins.ec2.EC2Cloud logINFO: Authenticating as ec2-user{code}
Add Comment
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title
Anton Yurchenko edited a comment on JENKINS-53952
Re: Linux slaves are not starting anymore
We've got the same issue. Jenkins ver 2.150.1, plugin version 1.41. {code:java}Dec 19, 2018 7:27:36 AM hudson.plugins.ec2.EC2CloudINFO: Launching instance: nullDec 19, 2018 7:27:36 AM hudson.plugins.ec2.EC2CloudINFO: bootstrap()Dec 19, 2018 7:27:36 AM hudson.plugins.ec2.EC2CloudINFO: Getting keypair...Dec 19, 2018 7:27:37 AM hudson.plugins.ec2.EC2CloudINFO: Using key: ssh-key[..]Dec 19, 2018 7:27:37 AM hudson.plugins.ec2.EC2CloudINFO: Authenticating as ec2-userERROR: Unexpected error in launching an agent. This is probably a bug in Jenkinsjava.lang.NullPointerException at hudson.plugins.ec2.ssh.EC2UnixLauncher.getEC2HostAddress(EC2UnixLauncher.java:367) at hudson.plugins.ec2.ssh.EC2UnixLauncher.connectToSsh(EC2UnixLauncher.java:319) at hudson.plugins.ec2.ssh.EC2UnixLauncher.bootstrap(EC2UnixLauncher.java:283) at hudson.plugins.ec2.ssh.EC2UnixLauncher.launchScript(EC2UnixLauncher.java:130) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:48) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748){code}+That issue occurs only when requesting a spot instance.+
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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
[JIRA] (JENKINS-55252) Build Trigger Badge plugin shows me question mark for build by parameterized scheduler
Title: Message Title Marc Brugger commented on JENKINS-55252 Re: Build Trigger Badge plugin shows me question mark for build by parameterized scheduler Can you pleas provide more information? I don't understand what you mean by "And the jenkins shows me question mark for it. " can you add a Screenshot or stacktrace? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54557) hudson.AbortException: Ansible playbook execution failed
Title: Message Title
Mike DeBruyn edited a comment on JENKINS-54557
Re: hudson.AbortException: Ansible playbook execution failed
Another one here:{noformat}FATAL: command execution failedhudson.AbortException: Ansible playbook execution failed at org.jenkinsci.plugins.ansible.AnsiblePlaybookBuilder.perform(AnsiblePlaybookBuilder.java:262) at org.jenkinsci.plugins.ansible.workflow.AnsiblePlaybookStep$AnsiblePlaybookExecution.run(AnsiblePlaybookStep.java:400) at org.jenkinsci.plugins.ansible.workflow.AnsiblePlaybookStep$AnsiblePlaybookExecution.run(AnsiblePlaybookStep.java:321) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) {noformat}Centos 7.6Jenkins 2. 154 156 Ansible 2.74Ansible plugin 1.0
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-54557) hudson.AbortException: Ansible playbook execution failed
Title: Message Title Mike DeBruyn commented on JENKINS-54557 Re: hudson.AbortException: Ansible playbook execution failed Another one here: FATAL: command execution failed hudson.AbortException: Ansible playbook execution failed at org.jenkinsci.plugins.ansible.AnsiblePlaybookBuilder.perform(AnsiblePlaybookBuilder.java:262) at org.jenkinsci.plugins.ansible.workflow.AnsiblePlaybookStep$AnsiblePlaybookExecution.run(AnsiblePlaybookStep.java:400) at org.jenkinsci.plugins.ansible.workflow.AnsiblePlaybookStep$AnsiblePlaybookExecution.run(AnsiblePlaybookStep.java:321) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Centos 7.6 Jenkins 2.154 Ansible 2.74 Ansible plugin 1.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55253) Client MODTIME is not set using source: depotSource(spec)
Title: Message Title
Alisdair Robertson created an issue
Jenkins / JENKINS-55253
Client MODTIME is not set using source: depotSource(spec)
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
2018-12-19 06:54
Priority:
Major
Reporter:
Alisdair Robertson
We are using the p4sync step in the following way, inside our pipeline to sync some thirdparty libraries:
p4sync charset: 'none',
credential: 'p4-buildserver-credentials',
format: "j-\${NODE_NAME}-\${JOB_NAME}-\${EXECUTOR_NUMBER}-${suffix}",
populate: autoClean(
delete: true,
modtime: true,
parallel: [
enable: true, minbytes: '1024', minfiles: '1', threads: '8'
],
pin: "$env.GLOBAL_P4_CHANGELIST",
quiet: true,
replace: true,
tidy: false
),
source: depotSource(spec) // spec is a variable defined elsewhere
The problem seems to be that the modtime: true appears to be useless, because the workspace as created in perforce does not have the MODTIME option set so files are not being synced with the modification time from the depot, and are having their modification times updated each time by the p4 reconcile command. An argument to depoSource to specify that the workspace should have modtime enabled seems like it would be very useful. Alternatively, perhaps the modtime and other options should be passed to the workspace spec here: https://swarm.workshop.perforce.com/projects/p4-jenkins/files/main/src/main/java/org/jenkinsci/plugins/p4/workflow/source/DepotSource.java#33
[JIRA] (JENKINS-55252) Build Trigger Badge plugin shows me question mark for build by parameterized scheduler
Title: Message Title Jiuk Jeong created an issue Jenkins / JENKINS-55252 Build Trigger Badge plugin shows me question mark for build by parameterized scheduler Issue Type: Bug Assignee: Marc Brugger Components: badge-plugin Created: 2018-12-19 06:16 Priority: Minor Reporter: Jiuk Jeong Dear, I'm using Parameterized Scheduler plugin. https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Scheduler+Plugin And the jenkins shows me question mark for it. Please update it. Thank you! Add Comment
[JIRA] (JENKINS-55250) Upload external test result failed when using API key to login ALM14
Title: Message Title Roy Lu started work on JENKINS-55250 Change By: Roy Lu Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-31641) Unclear error upon launching Windows build node
Title: Message Title
Anton Yurchenko edited a comment on JENKINS-31641
Re: Unclear error upon launching Windows build node
Seems like a network or WinRM issue.I would have tried the following from master while launching the instance: # * ping the instance (see if I were able to reach the machine) # * see that port is reachable with: {code:java}telnet 5985{code} # * connect through *pywinrm* python module:{code:java}import winrms = winrm.Session('', auth=('administrator', ''))r = s.run_cmd('time', ['/t'])print(r.std_out){code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-31641) Unclear error upon launching Windows build node
Title: Message Title
Anton Yurchenko edited a comment on JENKINS-31641
Re: Unclear error upon launching Windows build node
Seems like a network or WinRM issue.I would have tried the following from master while launching the instance: # ping the instance (see if I were able to reach the machine) # see that port is reachable with: {code:java}telnet 5985{code} # connect through *pywinrm* python module: {code:java}import winrms = winrm.Session('', auth=('administrator', ''))r = s.run_cmd('time', ['/t'])print(r.std_out){code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-31641) Unclear error upon launching Windows build node
Title: Message Title
Anton Yurchenko commented on JENKINS-31641
Re: Unclear error upon launching Windows build node
Seems like a network or WinRM issue. I would have tried the following from master while launching the instance:
ping the instance (see if I were able to reach the machine)
see that port is reachable with:
telnet 5985
connect through pywinrm python module:
import winrm
s = winrm.Session('', auth=('administrator', ''))
r = s.run_cmd('time', ['/t'])
print(r.std_out)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-51692) Cannot logout from the Google Login plugin
Title: Message Title Alex Raber updated an issue Jenkins / JENKINS-51692 Cannot logout from the Google Login plugin Change By: Alex Raber Comment: Hello [~sneko] and [~recampbell], A colleague of mine and I are also experiencing this issue on v2.150.1 with google-login 1.3. I'm not sure if either of you found a solution, but if you have please post. :) Best Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-51692) Cannot logout from the Google Login plugin
Title: Message Title Alex Raber edited a comment on JENKINS-51692 Re: Cannot logout from the Google Login plugin Hello [~sneko] and [~recampbell], A colleague of mine and I are also experiencing this issue on v2.150.1 with google-login 1 . 3. I'm not sure if either of you found a solution, but if you have please post. :) Best Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-51692) Cannot logout from the Google Login plugin
Title: Message Title Alex Raber commented on JENKINS-51692 Re: Cannot logout from the Google Login plugin Hello Thomas Ramé and Ryan Campbell, A colleague of mine and I are also experiencing this issue on v2.150.1. I'm not sure if either of you found a solution, but if you have please post. Best Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55251) Builds randomly stuck and fail for the reason of lost connection but the slave is actually online
Title: Message Title Arlen Rick created an issue Jenkins / JENKINS-55251 Builds randomly stuck and fail for the reason of lost connection but the slave is actually online Issue Type: Bug Assignee: Jeff Thompson Attachments: plugins_info.yaml Components: remoting Created: 2018-12-19 04:24 Environment: Master: Jenkins ver. 2.138.2 on Ubuntu 16.04.3 LTS (Xenial Xerus), Java 1.8.0_191 Slave: Unix slave, version 3.25 on Centos 7.5,Java 1.8.0_144 Priority: Major Reporter: Arlen Rick The master is installed with an offline installation package. Tasks are all run on physical machines and are written using declarative pipeline. The browser is Google Chrome 70 I tried UNIX SSH and JNLP - Slave to connect the master node and the slave node, which will cause this phenomenon, but it is slightly different. When using UNIX SSH, the node is still online after the build is interrupted. However, using JNLP - Slave method, the node is not online after the construction interruption ( agent.jar process hangs up ). The construction task reported an error as follows: wrapper script does not seem to be touching the log file in /var/lib/jenkins_node/workspace/FDS/FDS-FdsWebServer-deploy-test@tmp/durable-5927b140 (JENKINS-48300: if on an extremely laggy filesystem, consider
[JIRA] (JENKINS-55117) Both LDAP and 'Use Jenkins Internal Database' can be used
Title: Message Title tang alby updated an issue Jenkins / JENKINS-55117 Both LDAP and 'Use Jenkins Internal Database' can be used Change By: tang alby Component/s: ldap-plugin Component/s: _unsorted Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55232) regarding Authentication response is not success message
Title: Message Title Hokwang Lee commented on JENKINS-55232 Re: regarding Authentication response is not success message Sorry and thank you Ivan Fernandez Calvo I am very beginner about auth, SAML. Can you reply my comment one more please ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-53985) Login to ALM Server at https://xxx/qcbin/ failed. Status Code: 302
Title: Message Title Roy Lu closed an issue as Done Closing it for no response for a long time. Jenkins / JENKINS-53985 Login to ALM Server at https://xxx/qcbin/ failed. Status Code: 302 Change By: Roy Lu Status: Open Closed Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55250) Upload external test result failed when using API key to login ALM14
Title: Message Title Roy Lu created an issue Jenkins / JENKINS-55250 Upload external test result failed when using API key to login ALM14 Issue Type: Bug Assignee: Roy Lu Components: hp-application-automation-tools-plugin Created: 2018-12-19 02:15 Priority: Minor Reporter: Roy Lu Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-39477) Github Plugin with Two Factor Authentication (2FA)
Title: Message Title Tobin Davis reopened an issue Jenkins / JENKINS-39477 Github Plugin with Two Factor Authentication (2FA) Change By: Tobin Davis Resolution: Won't Fix Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-39477) Github Plugin with Two Factor Authentication (2FA)
Title: Message Title Tobin Davis commented on JENKINS-39477 Re: Github Plugin with Two Factor Authentication (2FA) I have another scenario where this is failing. I have a job that worked up until this morning when our SCM admin forced us to use 2FA. Now, no matter what I try, my pipeline jobs fail in strange ways during 'checkout scm'. I have one job that will fail to checkout submodules (some of which aren't even part of our private repos), and PR jobs will fail because they can't figure out what branch to start with (indicating that scm.* is not being populated properly). I have tried all of the workarounds I can think of, including using the syntax generator and hardcoding the Jenkinsfile script with credentialID. Nothing appears to work. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55242) AzureVMCloud: createProvisionedAgent: Deployment failed with timeout
Title: Message Title Jie Shen commented on JENKINS-55242 Re: AzureVMCloud: createProvisionedAgent: Deployment failed with timeout Hi Muhammad Faizan ul haq, could you please provide some detailed configuration like region so that can help me investigate. I think it should be some network issue, maybe you can just change the deployment timeout in the configuration. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55242) AzureVMCloud: createProvisionedAgent: Deployment failed with timeout
Title: Message Title Jie Shen started work on JENKINS-55242 Change By: Jie Shen Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55242) AzureVMCloud: createProvisionedAgent: Deployment failed with timeout
Title: Message Title Jie Shen assigned an issue to Jie Shen Jenkins / JENKINS-55242 AzureVMCloud: createProvisionedAgent: Deployment failed with timeout Change By: Jie Shen Assignee: Azure DevOps Jie Shen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55236) jenkins-2.138.2 dosn't fully support Role-based Authorization Strategy plugin v2.9.0
Title: Message Title harry king updated an issue Jenkins / JENKINS-55236 jenkins-2.138.2 dosn't fully support Role-based Authorization Strategy plugin v2.9.0 Change By: harry king Attachment: 2.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55236) jenkins-2.138.2 dosn't fully support Role-based Authorization Strategy plugin v2.9.0
Title: Message Title harry king updated an issue Jenkins / JENKINS-55236 jenkins-2.138.2 dosn't fully support Role-based Authorization Strategy plugin v2.9.0 Change By: harry king I added a project role and a filter with "test-. * ", after switching the user, all jobs are still there including "test-. * " and "dev-.*". Seems to be a bug there, could you please take a look? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55236) jenkins-2.138.2 dosn't fully support Role-based Authorization Strategy plugin v2.9.0
Title: Message Title harry king updated an issue Jenkins / JENKINS-55236 jenkins-2.138.2 dosn't fully support Role-based Authorization Strategy plugin v2.9.0 Change By: harry king I added a project role and a filter with "test-.*", after changing switching the user, all jobs are still there including "test-.*" and "dev-.*". Seems to be a bug there, could you please take a look? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55236) jenkins-2.138.2 dosn't fully support Role-based Authorization Strategy plugin v2.9.0
Title: Message Title harry king updated an issue Jenkins / JENKINS-55236 jenkins-2.138.2 dosn't fully support Role-based Authorization Strategy plugin v2.9.0 Change By: harry king Attachment: 1.png Attachment: 2.png Attachment: 3.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55236) jenkins-2.138.2 dosn't fully support Role-based Authorization Strategy plugin v2.9.0
Title: Message Title harry king updated an issue Jenkins / JENKINS-55236 jenkins-2.138.2 dosn't fully support Role-based Authorization Strategy plugin v2.9.0 Change By: harry king Attachment: 1.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55236) jenkins-2.138.2 dosn't fully support Role-based Authorization Strategy plugin v2.9.0
Title: Message Title harry king commented on JENKINS-55236 Re: jenkins-2.138.2 dosn't fully support Role-based Authorization Strategy plugin v2.9.0 config.xml Thanks Oleg for looking into the issue, config.xml was uploaded. Thanks again! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55236) jenkins-2.138.2 dosn't fully support Role-based Authorization Strategy plugin v2.9.0
Title: Message Title harry king updated an issue Jenkins / JENKINS-55236 jenkins-2.138.2 dosn't fully support Role-based Authorization Strategy plugin v2.9.0 Change By: harry king Attachment: config.xml Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55163) Not able to Trigger Jenkins Job from shared library file
Title: Message Title Avadh Sharma resolved as Not A Defect Jenkins / JENKINS-55163 Not able to Trigger Jenkins Job from shared library file Change By: Avadh Sharma Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55163) Not able to Trigger Jenkins Job from shared library file
Title: Message Title Avadh Sharma commented on JENKINS-55163 Re: Not able to Trigger Jenkins Job from shared library file Ok. So I figured out the problem. One of the shared file name was build.groovy which was causing conflicts with build pipeline step. Renamed the file and that fixed the issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55243) java.lang.AbstractMethodError in Warnings NG PlugIn while parsing SpotBugs results
Title: Message Title Ulli Hafner resolved as Cannot Reproduce Hmm, this looks like a library version problem. The version of warnings-ng and analysis-model-api must match. Maybe you did not install the latest version of both plugins? Can you please retry with: warnings-ng 1.0.0-beta9 and analysis-model-api 1.0.0-beta20. Jenkins / JENKINS-55243 java.lang.AbstractMethodError in Warnings NG PlugIn while parsing SpotBugs results Change By: Ulli Hafner Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55221) Warnings NG plugin can't resolve absolute paths with gcc4
Title: Message Title Ulli Hafner commented on JENKINS-55221 Re: Warnings NG plugin can't resolve absolute paths with gcc4 I changed the parser now: it resolves all files so that relative elements are removed (i.e. "../"). I'm not sure if this is the problem, can you please check? It is part of warnings-ng 1.0.0-beta9 and analysis-model-api 1.0.0-beta20. If not I need the result of the cat again, it should now show no files with relative elements. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55174) NPE in build state marshalling
Title: Message Title Sam Van Oort commented on JENKINS-55174 Re: NPE in build state marshalling My suspicion is that one of the following is the cause based on the evidence above: 1. Unlikely: a very subtle change in the serialized format causes a net-new bug in JBoss Marshalling that prevents correct serialization. 2. Likely: Some subtlety in how readReplace methods are being handled (perhaps with regards to customizations in workflow or Groovy) – or especially with regards to order of operations here. This is supported by limited differences in the serialized output. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55174) NPE in build state marshalling
Title: Message Title Sam Van Oort commented on JENKINS-55174 Re: NPE in build state marshalling Oleg Nenashev I've attached a bunch of info from investigation above, but am running out of investigative ideas here aside from manually building and bisecting all the JBoss marshalling commits here, or tracing line-by-line through all the mutations of the SerialializableScript in the marshaller (I've done quite a bit of poking with the debugger & breakpoints here already). Would love to know if you have any ideas for how to attack this particular beast. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55174) NPE in build state marshalling
Title: Message Title Sam Van Oort commented on JENKINS-55174 Re: NPE in build state marshalling Writing up results of pair-investigation with Devin Nusbaum today and summarizing some previous findings 0. I'd previously established that the culprit here is a null "binding" field in the WorkflowScript when deserializing, and had not been able to determine how the setting of that field differs between JBoss Marshalling versions 1. This issue appears to occur with even very trivial Pipelines when trying to read the program.dat – see: https://github.com/svanoort/workflow-support-plugin/commit/60dff8f944407a46e70f1fcfc3843cf7da29d974#diff-5592588df61e52ede2b60dbc65f7009bR56 2. Some subtle differences in the serialization format between jboss-marshalling 1.4.12-jenkins-3 and 2.0.5.Final (I'd bisected the issue and confirmed it occurs as early as version 2.0.0 previously) – see attached program.dat files – but analyzing them briefly in a hex editor and via 'strings' does not show substantial differences. I.E. it's not like things simply aren't being serialized, the format is just modified to be a bit more efficient. 3. Stack traces when trying to read the SerializableScript are attached – note that the stacks seem more or less identical, aside froma switch for Java version changes, and different line numbers due to source changes in JBoss marshalling 4. Nothing obvious in the JBoss marshalling JIRA that would reflect this bug 5. Nothing obvious jumping out in the commits for JBoss marshalling that have changed https://github.com/jboss-remoting/jboss-marshalling/compare/1.4.12.Final...2.0.0.Final See data dumps: jboss-NEW-marshaller-unmarshal-thread.txt jboss-old-marshaller-unmarshal-thread.txt test-java8-LEGACY-marshaller-program.dat test-java8-new-marshaller-program.dat Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails
[JIRA] (JENKINS-55174) NPE in build state marshalling
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-55174 NPE in build state marshalling Change By: Sam Van Oort Attachment: test-java8-LEGACY-marshaller-program.dat Attachment: test-java8-new-marshaller-program.dat Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55174) NPE in build state marshalling
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-55174 NPE in build state marshalling Change By: Sam Van Oort Attachment: jboss-NEW-marshaller-unmarshal-thread.txt Attachment: jboss-old-marshaller-unmarshal-thread.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55249) Upstream and Downstream columns are not displaying properly
Title: Message Title Mark Berchem created an issue Jenkins / JENKINS-55249 Upstream and Downstream columns are not displaying properly Issue Type: Bug Assignee: Unassigned Attachments: Jenkins.png, UpstreamDownstreamSource.txt Components: upstream-downstream-view-plugin Created: 2018-12-18 23:07 Environment: Jenkins version 1.146, Upstream Downstream Column Plugin version 1.006 Labels: jenkins Priority: Minor Reporter: Mark Berchem When I upgraded from Jenkins 1.144 to 1.146 the Upstream and Downstream columns no longer displayed properly. The page source shows < where I think a '<' should be (see attached source).
[JIRA] (JENKINS-53146) TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Title: Message Title Ryan Campbell assigned an issue to Alex Taylor Jenkins / JENKINS-53146 TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step Change By: Ryan Campbell Assignee: Oleg Nenashev Alex Taylor Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-38447) Bitbucket hooks don't work for Pipeline jobs
Title: Message Title John Stephenson commented on JENKINS-38447 Re: Bitbucket hooks don't work for Pipeline jobs And ensure you've updated your firewall as necessary (https://bitbucket.org/blog/new-ip-addresses-bitbucket-cloud?_ga=2.183187939.453555296.1545035860-2047301735.1528367903) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54516) Repository polling fails when pull requests are disabled
Title: Message Title Christian Fochler assigned an issue to Stephen Connolly Jenkins / JENKINS-54516 Repository polling fails when pull requests are disabled Change By: Christian Fochler Assignee: Stephen Connolly Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55248) workspace mixup when 2 jobs running on 2 diff nodes at the same time
Title: Message Title Mei Liu created an issue Jenkins / JENKINS-55248 workspace mixup when 2 jobs running on 2 diff nodes at the same time Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2018-12-18 21:10 Priority: Minor Reporter: Mei Liu we have 2 pipelines that performs simple checkout on 2 different branches, scheduled to run at the same time on 2 different nodes every day, say Job-1 & Job-2 sometimes we will get error like this, for example for Job-1 P4 Task: attempt: 1 P4 Task: failed: com.perforce.p4java.exception.P4JavaException: com.perforce.p4java.exception.P4JavaException: hudson.AbortException: P4JAVA: Error(s): Path 'C:\Jenkins\workspace\Job-2/...' is not under client's root 'C:\Jenkins\workspace\Job-2. looks like some sort of race condition going on, it doesn't happen every time. any ideas? Add Comment
[JIRA] (JENKINS-50292) maven-vault-plugin error
Title: Message Title
Nick Carlyle updated an issue
Jenkins / JENKINS-50292
maven-vault-plugin error
Change By:
Nick Carlyle
When we perform a build on a maven project. we receive the error below. Started by user [SCS Admin|http://localhost:8080/user/scs_jenkins_admin]Building in workspace C:\Program Files (x86)\Jenkins\workspace\Southern Company AEM > git.exe rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git.exe config remote.origin.url [https://github.com/southern-it-corporate-services/adobe-aem-southern-platform.git] # timeout=10Fetching upstream changes from [https://github.com/southern-it-corporate-services/adobe-aem-southern-platform.git] > git.exe --version # timeout=10using GIT_ASKPASS to set credentials > git.exe fetch --tags --progress [https://github.com/southern-it-corporate-services/adobe-aem-southern-platform.git] +refs/heads/*:refs/remotes/origin/* > git.exe rev-parse "refs/remotes/origin/develop^\{commit}" # timeout=10 > git.exe rev-parse "refs/remotes/origin/origin/develop^\{commit}" # timeout=10Checking out Revision b9e3f1836a1ddb8e8e6639cf8ca15a4524ca9e62 (refs/remotes/origin/develop) > git.exe config core.sparsecheckout # timeout=10 > git.exe checkout -f b9e3f1836a1ddb8e8e6639cf8ca15a4524ca9e62Commit message: "Merge pull request #153 from southern-it-corporate-services/SOCOS-34" > git.exe rev-list --no-walk b9e3f1836a1ddb8e8e6639cf8ca15a4524ca9e62 # timeout=10Parsing POMsEstablished TCP socket on 49932[Southern Company AEM] $ "C:\Program Files\Java\jdk1.8.0_161/bin/java" -cp "C:\Program Files (x86)\Jenkins\plugins\maven-plugin\WEB-INF\lib\maven35-agent-1.12-alpha-1.jar;C:\Program Files\Apache\maven\boot\plexus-classworlds-2.5.2.jar;C:\Program Files\Apache\maven/conf/logging" jenkins.maven3.agent.Maven35Main "C:\Program Files\Apache\maven" "C:\Program Files (x86)\Jenkins\war\WEB-INF\lib\remoting-3.10.2.jar" "C:\Program Files (x86)\Jenkins\plugins\maven-plugin\WEB-INF\lib\maven35-interceptor-1.12-alpha-1.jar" "C:\Program Files (x86)\Jenkins\plugins\maven-plugin\WEB-INF\lib\maven3-interceptor-commons-1.12-alpha-1.jar" 49932<===[JENKINS REMOTING CAPACITY]===>channel startedExecuting Maven: -B -f C:\Program Files (x86)\Jenkins\workspace\Southern Company AEM\pom.xml mvn clean install -Pauto-deploy-all -Dcq.host=dv-southern-aem.cloudapp.net -Dcq.password=S0uth3rn@dmin -s settings.xml -Dbuild.number=SNAPSHOT[INFO] Scanning for projects...[INFO] Downloading from central: [http://repo.adobe.com/nexus/content/groups/public/com/day/jcr/vault/maven-vault-plugin/maven-metadata.xml] [WARNING] Could not transfer metadata com.day.jcr.vault:maven-vault-plugin/maven-metadata.xml from/to central ([http://repo.adobe.com/nexus/content/groups/public]): sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target[INFO] Downloading from central:
[JIRA] (JENKINS-54893) Error provisioning slaves with ECS plugin 1.18
Title: Message Title Philipp Garbe commented on JENKINS-54893 Re: Error provisioning slaves with ECS plugin 1.18 Yes, it's the same fix, that's why I closed this one. You can try out the 1.19-beta-1 already, if you want. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-41367) Bitbucket webhook URL is being forced to Jenkins.getActiveInstance().getRootUrl()
Title: Message Title Alex Johnson commented on JENKINS-41367 Re: Bitbucket webhook URL is being forced to Jenkins.getActiveInstance().getRootUrl() I have the same problem and would love to help solve it if no one else is presently working on it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55247) Make Ansible Tower Pluging import the output from a sliced job template
Title: Message Title Elyézer Rezende updated an issue Jenkins / JENKINS-55247 Make Ansible Tower Pluging import the output from a sliced job template Change By: Elyézer Rezende Summary: Make Ansible Tower Pluginimport Pluging import the output from a sliced job template Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55246) Add credential button is not working on Ansible Tower Plugin configuration
Title: Message Title Elyézer Rezende updated an issue Jenkins / JENKINS-55246 Add credential button is not working on Ansible Tower Plugin configuration Change By: Elyézer Rezende Summary: Add credential button is not working on Ansible Tower Plugin configuration Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55247) Make Ansible Tower Plugin import the output from a sliced job template
Title: Message Title Elyézer Rezende updated an issue Jenkins / JENKINS-55247 Make Ansible Tower Plugin import the output from a sliced job template Change By: Elyézer Rezende Summary: Make Ansible Tower Pluging Plugin import the output from a sliced job template Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55247) Make Ansible Tower Pluginimport the output from a sliced job template
Title: Message Title Elyézer Rezende created an issue Jenkins / JENKINS-55247 Make Ansible Tower Pluginimport the output from a sliced job template Issue Type: Improvement Assignee: John Westcott Components: ansible-tower-plugin Created: 2018-12-18 18:49 Priority: Minor Reporter: Elyézer Rezende On the latest AXW release it introduces the Job Slicing feature that allows Job Templates to be sliced up, see the docs for more information. The current version of the Ansible Tower Plugin is not able to import the output from a sliced job template because it tries to fetch the output on https://awx.example.com/#/jobs/ but for sliced job templates the output is actually available on https://awx.example.com/#/workflows/ Here are the steps I tried: On AWX, ensure that there is a job template where the Job Slicing value is set to some number greater than 1. On Jenkins, ensure that the Import Tower Output on a Ansible Tower build step. Run the Jenkins job, it should fail with the following message: "ERROR: Failed to get job events from tower: The item does not exist"
[JIRA] (JENKINS-55245) User.current().getId() always return SYSTEM
Title: Message Title Paulo Eduardo Neves closed an issue as Duplicate Jenkins / JENKINS-55245 User.current().getId() always return SYSTEM Change By: Paulo Eduardo Neves Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-14605) Simple means to obtain logged in user's id
Title: Message Title Paulo Eduardo Neves reopened an issue The problem persists. The two commands below return SYSTEM when they are run inside a pipeline script. User.current()Jenkins.getAuthentication().getName() Currently there is no way get the logged in user from a pipeline. Jenkins / JENKINS-14605 Simple means to obtain logged in user's id Change By: Paulo Eduardo Neves Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55246) Add credential button is not working on Ansible Tower configuration
Title: Message Title Elyézer Rezende created an issue Jenkins / JENKINS-55246 Add credential button is not working on Ansible Tower configuration Issue Type: Bug Assignee: John Westcott Components: ansible-tower-plugin Created: 2018-12-18 18:28 Priority: Minor Reporter: Elyézer Rezende The Add credential button on the Ansible Tower configuration section does not work when adding new items. Steps to reproduce: Go to the global Jenkins configuration page On the Ansible Tower section, click on Add to start adding a new Ansible Tower installation On the credentials field, click on the Add button, nothing happens. Expected result: It should show a list of credentials provider when the Add credential button is pressed and allow creating a new credential. Additional details: If you add a Tower Installation and try to click on the Add button for its credentials field it works as expected. Add Comment
[JIRA] (JENKINS-55245) User.current().getId() always return SYSTEM
Title: Message Title Paulo Eduardo Neves created an issue Jenkins / JENKINS-55245 User.current().getId() always return SYSTEM Issue Type: Bug Assignee: Unassigned Components: core, pipeline Created: 2018-12-18 17:34 Environment: Jenkins 2.138.3 Firefox/Google Chrome ava.runtime.version 1.8.0_181-8u181-b13-2~deb9u1-b13 Priority: Major Reporter: Paulo Eduardo Neves During a pipeline declarative script the method User.current().getId() should return the Logged In User Id, but it always returns the string SYSTEM. It is a common issue that you can find in internet forums Add Comment
[JIRA] (JENKINS-43121) Unable to install jenkins in windows 7
Title: Message Title Sagarsb py commented on JENKINS-43121 Re: Unable to install jenkins in windows 7 I have noticed the same issue on Windows 2012 server as well. Steps used: downloaded latest jenkins.war run java -jar jenkins.war Observations: It throws error as mentioned in the above issue. Big blocker to me from product point of view. Using OpenJDK 1.8 Java Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55221) Warnings NG plugin can't resolve absolute paths with gcc4
Title: Message Title David Aldrich commented on JENKINS-55221 Re: Warnings NG plugin can't resolve absolute paths with gcc4 # grep -H fileName /var/lib/jenkins/jobs/Regression_test_SystemC_gcc/builds/lastSuccessfulBuild/*.xml /var/lib/jenkins/jobs/Regression_test_SystemC_gcc/builds/lastSuccessfulBuild/ubuntu16.04-warnings-fixed-issues.xml: /data/hudsonuser/workspace/Regression_test_SystemC_gcc@2/StarLibs/NemeSys/LTE/RRM/../../../StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/post_steps.h /var/lib/jenkins/jobs/Regression_test_SystemC_gcc/builds/lastSuccessfulBuild/ubuntu16.04-warnings-fixed-issues.xml: /data/hudsonuser/workspace/Regression_test_SystemC_gcc@2/StarLibs/Camelot/ScBitTrue/StarUlPhyRxCommonCamelot.h /var/lib/jenkins/jobs/Regression_test_SystemC_gcc/builds/lastSuccessfulBuild/ubuntu16.04-warnings-fixed-issues.xml: "../../issue[2]/fileName"/> /var/lib/jenkins/jobs/Regression_test_SystemC_gcc/builds/lastSuccessfulBuild/ubuntu16.04-warnings-fixed-issues.xml: "../../issue[2]/fileName"/> /var/lib/jenkins/jobs/Regression_test_SystemC_gcc/builds/lastSuccessfulBuild/ubuntu16.04-warnings-new-issues.xml: /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/NemeSys/LTE/NLE/StarUlPhyRxCommonCamelot.h /var/lib/jenkins/jobs/Regression_test_SystemC_gcc/builds/lastSuccessfulBuild/ubuntu16.04-warnings-new-issues.xml: /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/NemeSys/LTE/NLE/StarUlPhyRxCommonCamelot.h /var/lib/jenkins/jobs/Regression_test_SystemC_gcc/builds/lastSuccessfulBuild/ubuntu16.04-warnings-new-issues.xml: /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/NemeSys/LTE/NLE/StarUlPhyRxCommonCamelot.h /var/lib/jenkins/jobs/Regression_test_SystemC_gcc/builds/lastSuccessfulBuild/ubuntu16.04-warnings-new-issues.xml: /data/hudsonuser/workspace/Regression_test_SystemC_gcc@2/StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/stimulus_file.h /var/lib/jenkins/jobs/Regression_test_SystemC_gcc/builds/lastSuccessfulBuild/ubuntu16.04-warnings-new-issues.xml: /data/hudsonuser/workspace/Regression_test_SystemC_gcc@2/StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/post_steps.h /var/lib/jenkins/jobs/Regression_test_SystemC_gcc/builds/lastSuccessfulBuild/ubuntu16.04-warnings-outstanding-issues.xml: /data/hudsonuser/workspace/Regression_test_SystemC_gcc@2/StarLibs/Camelot/ScBitTrue/AlterafpCompiler.cpp /var/lib/jenkins/jobs/Regression_test_SystemC_gcc/builds/lastSuccessfulBuild/ubuntu16.04-warnings-outstanding-issues.xml: /data/hudsonuser/workspace/Regression_test_SystemC_gcc@2/StarLibs/Camelot/ScBitTrue/AlterafpCompiler.cpp /var/lib/jenkins/jobs/Regression_test_SystemC_gcc/builds/lastSuccessfulBuild/ubuntu16.04-warnings-outstanding-issues.xml: /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/NemeSys/LTE/NLE/../../../StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/stimulus_file.h /var/lib/jenkins/jobs/Regression_test_SystemC_gcc/builds/lastSuccessfulBuild/ubuntu16.04-warnings-outstanding-issues.xml: /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/BitTrue/StarAltTurboDecoder.cpp /var/lib/jenkins/jobs/Regression_test_SystemC_gcc/builds/lastSuccessfulBuild/ubuntu16.04-warnings-outstanding-issues.xml: /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/BitTrue/StarAltTurboDecoder.cpp
[JIRA] (JENKINS-55221) Warnings NG plugin can't resolve absolute paths with gcc4
Title: Message Title Ulli Hafner commented on JENKINS-55221 Re: Warnings NG plugin can't resolve absolute paths with gcc4 Seems that all affected files with warnings are part of the files-with-issues. That means the files are there, just the path to the warnings does not match with the checksum I am using... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55221) Warnings NG plugin can't resolve absolute paths with gcc4
Title: Message Title Ulli Hafner commented on JENKINS-55221 Re: Warnings NG plugin can't resolve absolute paths with gcc4 Sorry, I did not see the other comment. I'll check which is missing... Can you use grep -H fileName /var/lib/jenkins/jobs/Regression_test_SystemC_gcc/builds/lastSuccessfulBuild/*.xml so I see the actual filename and not standard input. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55244) Shelved projects footprint increased by factor 10
Title: Message Title Jens Brejner created an issue Jenkins / JENKINS-55244 Shelved projects footprint increased by factor 10 Issue Type: Bug Assignee: Pierre Beitz Components: shelve-project-plugin Created: 2018-12-18 16:16 Environment: Windows Priority: Major Reporter: Jens Brejner Version 2.1 changed the archive format to .tar. Tar files are not compressed, so the size of a .tar archived project is about 10 times an archive produced with earlier version of the plugin. To reproduce: Install shelve-project-plugin version < 2.1 and shelve a project. Take note of the .zip file size Install version 2.1, unshelve the project, then shelve it again. Compare the size of the .tar file to the size of the previous .zip file. Suggest to compress the .tar file into a .tar.gz instead. Add Comment
[JIRA] (JENKINS-55221) Warnings NG plugin can't resolve absolute paths with gcc4
Title: Message Title David Aldrich commented on JENKINS-55221 Re: Warnings NG plugin can't resolve absolute paths with gcc4 You wrote: Can you also open the files in the folder /var/lib/jenkins/jobs/Regression_test_SystemC_gcc/builds/lastSuccessfulBuild/files-with-issues/ and check which files are missing? Can you infer that from my earlier answer? That is: Regarding the second part of your question, there are 8 files in files-with-issues (2 mentioned twice): StarLibs\Camelot\ScBitTrue\AlterafpCompiler.cpp StarLibs\Camelot\ScBitTrue\AlteraDspBuilderFFT\csl\stimulus_file.h StarLibs\Camelot\ScBitTrue\AlterafpCompiler.cpp StarLibs\Camelot\ScBitTrue\AlteraDspBuilderFFT\csl\post_steps.h StarLibs\Camelot\ScBitTrue\StarUlPhyRxCommonCamelot.h StarLibs\Camelot\ScBitTrue\Alterautil.cpp StarLibs\Camelot\ScBitTrue\AlteraDspBuilderFFT\csl\stimulus_file.h StarLibs\Camelot\ScBitTrue\StarAltTurboDecoder.cpp Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55243) java.lang.AbstractMethodError in Warnings NG PlugIn while parsing SpotBugs results
Title: Message Title Christian Asselmeyer commented on JENKINS-55243 Re: java.lang.AbstractMethodError in Warnings NG PlugIn while parsing SpotBugs results Currently I'm back to analysis-model-api 1.0.0-beta15 with warnings-ng 1.0.0-beta6. I'm not sure which analysis-model-api version was installed when upgrading to warnings-ng 1.0.0-beta8, I saw it was upgraded together with warnings-ng and I downgraded it when downgrading back to warnings-ng 1.0.0-beta6. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55221) Warnings NG plugin can't resolve absolute paths with gcc4
Title: Message Title David Aldrich commented on JENKINS-55221 Re: Warnings NG plugin can't resolve absolute paths with gcc4 I hope this is what you are asking for: # cat /var/lib/jenkins/jobs/Regression_test_SystemC_gcc/builds/lastSuccessfulBuild/*.xml | grep -H fileName (standard input): /data/hudsonuser/workspace/Regression_test_SystemC_gcc@2/StarLibs/NemeSys/LTE/RRM/../../../StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/post_steps.h (standard input): /data/hudsonuser/workspace/Regression_test_SystemC_gcc@2/StarLibs/Camelot/ScBitTrue/StarUlPhyRxCommonCamelot.h (standard input): "../../issue[2]/fileName"/> (standard input): "../../issue[2]/fileName"/> (standard input): /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/NemeSys/LTE/NLE/StarUlPhyRxCommonCamelot.h (standard input): /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/NemeSys/LTE/NLE/StarUlPhyRxCommonCamelot.h (standard input): /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/NemeSys/LTE/NLE/StarUlPhyRxCommonCamelot.h (standard input): /data/hudsonuser/workspace/Regression_test_SystemC_gcc@2/StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/stimulus_file.h (standard input): /data/hudsonuser/workspace/Regression_test_SystemC_gcc@2/StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/post_steps.h (standard input): /data/hudsonuser/workspace/Regression_test_SystemC_gcc@2/StarLibs/Camelot/ScBitTrue/AlterafpCompiler.cpp (standard input): /data/hudsonuser/workspace/Regression_test_SystemC_gcc@2/StarLibs/Camelot/ScBitTrue/AlterafpCompiler.cpp (standard input): /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/NemeSys/LTE/NLE/../../../StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/stimulus_file.h (standard input): /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/BitTrue/StarAltTurboDecoder.cpp (standard input): /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/BitTrue/StarAltTurboDecoder.cpp (standard input): /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue/Alterautil.cpp (standard input): /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue/AlterafpCompiler.cpp (standard input): /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue/AlterafpCompiler.cpp (standard input): /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/stimulus_file.h (standard input): /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue/StarUlPhyRxCommonCamelot.h< fileName> (standard input): /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue/StarUlPhyRxCommonCamelot.h< fileName> (standard input): /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue/StarUlPhyRxCommonCamelot.h< fileName> (standard input): /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue/AlteraDspBuilderFFT/csl/stimulus_file.h (standard input): /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue/StarAltTurboDecoder.cpp (standard input): /data/hudsonuser/workspace/Regression_test_SystemC_gcc/StarLibs/Camelot/ScBitTrue/StarAltTurboDecoder.cpp (standard input):
[JIRA] (JENKINS-55220) Multibranch Pipeline jobs get randomly lost
Title: Message Title Jonas Büth commented on JENKINS-55220 Re: Multibranch Pipeline jobs get randomly lost Vivek Pandey I have installed the update but can only confirm the fix after a while when no more loses appear. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55221) Warnings NG plugin can't resolve absolute paths with gcc4
Title: Message Title Ulli Hafner edited a comment on JENKINS-55221 Re: Warnings NG plugin can't resolve absolute paths with gcc4 I have a first guess: maybe the problem is that some warnings are old. And the old warnings may be collected in a @2 workspace. Then they are referenced in the new build. And here the workspace is different... I need to check that. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55221) Warnings NG plugin can't resolve absolute paths with gcc4
Title: Message Title Ulli Hafner commented on JENKINS-55221 Re: Warnings NG plugin can't resolve absolute paths with gcc4 I have a first guess: maybe the problem is that some warnings are old. And the old warnings may be collected in a @2 workspace. Then they are referenced in the new build. And here the workspace is different... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55221) Warnings NG plugin can't resolve absolute paths with gcc4
Title: Message Title Ulli Hafner commented on JENKINS-55221 Re: Warnings NG plugin can't resolve absolute paths with gcc4 This is the first part, yes. Can you please grep with -H so I see in which file the match is? Can you also open the files in the folder /var/lib/jenkins/jobs/Regression_test_SystemC_gcc/builds/lastSuccessfulBuild/files-with-issues/ and check which files are missing? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-22660) More flexible UI for approved signatures
Title: Message Title Leandro Solagna commented on JENKINS-22660 Re: More flexible UI for approved signatures If it's ok, I would like to add my 2 cents on this. After editing scriptApproval.xml, I could not get it loaded with my configurations just by clicking on "Reload Configuration from Disk". I needed to ask the sysadmin to actually do a systemctl restart jenkins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55243) java.lang.AbstractMethodError in Warnings NG PlugIn while parsing SpotBugs results
Title: Message Title Ulli Hafner commented on JENKINS-55243 Re: java.lang.AbstractMethodError in Warnings NG PlugIn while parsing SpotBugs results Which version of analysis-model-api do you have installed? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55220) Multibranch Pipeline jobs get randomly lost
Title: Message Title Vivek Pandey commented on JENKINS-55220 Re: Multibranch Pipeline jobs get randomly lost Jonas Büth Please confirm using bitbucket-branch-source 2.2.16 fixes this issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-37231) CORS allowed origins list never updated
Title: Message Title Devin Nusbaum updated JENKINS-37231 Jenkins / JENKINS-37231 CORS allowed origins list never updated Change By: Devin Nusbaum Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55243) java.lang.AbstractMethodError in Warnings NG PlugIn while parsing SpotBugs results
Title: Message Title
Christian Asselmeyer updated an issue
Jenkins / JENKINS-55243
java.lang.AbstractMethodError in Warnings NG PlugIn while parsing SpotBugs results
Change By:
Christian Asselmeyer
When collectings SpotBugs results, the Warnings NG PlugIn crashes in version 1.0.0-beta8{noformat}[SpotBugs] Using default pattern '**/target/spotbugsXml.xml' since user defined pattern is not set[SpotBugs] Searching for all files in '.../target/spotbugsXml.xml'[SpotBugs] -> found 28 files[SpotBugs] Successfully parsed file .../target/spotbugsXml.xml[SpotBugs] -> found 0 issues (skipped 0 duplicates)[SpotBugs] Successfully parsed file .../target/spotbugsXml.xml[SpotBugs] -> found 0 issues (skipped 0 duplicates)[SpotBugs] Successfully parsed file .../target/spotbugsXml.xml[SpotBugs] -> found 12 issues (skipped 0 duplicates)[SpotBugs] Successfully parsed file .../target/spotbugsXml.xml[SpotBugs] -> found 12 issues (skipped 0 duplicates) ... ERROR: Step ‘Record compiler warnings and static analysis results’ aborted due to exception: Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to Agent1 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:955) at hudson.FilePath.act(FilePath.java:1070) at hudson.FilePath.act(FilePath.java:1059) at io.jenkins.plugins.analysis.core.steps.IssuesScanner.postProcess(IssuesScanner.java:78) at io.jenkins.plugins.analysis.core.steps.IssuesScanner.scan(IssuesScanner.java:62) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.scanWithTool(IssuesRecorder.java:642) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.record(IssuesRecorder.java:610) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.perform(IssuesRecorder.java:585) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1073) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1831) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)java.lang.AbstractMethodError: io.jenkins.plugins.analysis.core.steps.IssuesScanner$DefaultFileSystem.open(Ljava/lang/String;)Ljava/io/InputStream; at edu.hm.hafner.analysis.ModuleDetector.parsePomAttribute(ModuleDetector.java:200) at edu.hm.hafner.analysis.ModuleDetector.parsePom(ModuleDetector.java:193) at edu.hm.hafner.analysis.ModuleDetector.createFilesToModuleMapping(ModuleDetector.java:91) at
[JIRA] (JENKINS-37113) Failed to start TEST_SET
Title: Message Title Ambarish Dash reopened an issue Pasted error log and attached screenshot from ALM Jenkins / JENKINS-37113 Failed to start TEST_SET Change By: Ambarish Dash Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-52750) dir step creates a @tmp directory at level.
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-52750 dir step creates a @tmp directory at level. Change By: Vivek Pandey Labels: pipeline pipeline-triaged Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55243) java.lang.AbstractMethodError in Warnings NG PlugIn while parsing SpotBugs results
Title: Message Title
Christian Asselmeyer updated an issue
Jenkins / JENKINS-55243
java.lang.AbstractMethodError in Warnings NG PlugIn while parsing SpotBugs results
Change By:
Christian Asselmeyer
When collectings SpotBugs results, the Warnings NG PlugIn crashes in version 1.0.0-beta8{noformat} Log bei Fehler: [SpotBugs] Using default pattern '**/target/spotbugsXml.xml' since user defined pattern is not set[SpotBugs] Searching for all files in '.../target/spotbugsXml.xml'[SpotBugs] -> found 28 files[SpotBugs] Successfully parsed file .../target/spotbugsXml.xml[SpotBugs] -> found 0 issues (skipped 0 duplicates)[SpotBugs] Successfully parsed file .../target/spotbugsXml.xml[SpotBugs] -> found 0 issues (skipped 0 duplicates)[SpotBugs] Successfully parsed file .../target/spotbugsXml.xml[SpotBugs] -> found 12 issues (skipped 0 duplicates)[SpotBugs] Successfully parsed file .../target/spotbugsXml.xml[SpotBugs] -> found 12 issues (skipped 0 duplicates)ERROR: Step ‘Record compiler warnings and static analysis results’ aborted due to exception: Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to Agent1 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:955) at hudson.FilePath.act(FilePath.java:1070) at hudson.FilePath.act(FilePath.java:1059) at io.jenkins.plugins.analysis.core.steps.IssuesScanner.postProcess(IssuesScanner.java:78) at io.jenkins.plugins.analysis.core.steps.IssuesScanner.scan(IssuesScanner.java:62) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.scanWithTool(IssuesRecorder.java:642) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.record(IssuesRecorder.java:610) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.perform(IssuesRecorder.java:585) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1073) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1831) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)java.lang.AbstractMethodError: io.jenkins.plugins.analysis.core.steps.IssuesScanner$DefaultFileSystem.open(Ljava/lang/String;)Ljava/io/InputStream; at edu.hm.hafner.analysis.ModuleDetector.parsePomAttribute(ModuleDetector.java:200) at edu.hm.hafner.analysis.ModuleDetector.parsePom(ModuleDetector.java:193) at edu.hm.hafner.analysis.ModuleDetector.createFilesToModuleMapping(ModuleDetector.java:91) at
[JIRA] (JENKINS-55243) java.lang.AbstractMethodError in Warnings NG PlugIn while parsing SpotBugs results
Title: Message Title Christian Asselmeyer created an issue Jenkins / JENKINS-55243 java.lang.AbstractMethodError in Warnings NG PlugIn while parsing SpotBugs results Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2018-12-18 15:42 Environment: Jenkins 2.143, warnings-ng-plugin 1.0.0-beta8 Priority: Minor Reporter: Christian Asselmeyer When collectings SpotBugs results, the Warnings NG PlugIn crashes in version 1.0.0-beta8 Log bei Fehler: [SpotBugs] Using default pattern '**/target/spotbugsXml.xml' since user defined pattern is not set [SpotBugs] Searching for all files in '.../target/spotbugsXml.xml' [SpotBugs] -> found 28 files [SpotBugs] Successfully parsed file .../target/spotbugsXml.xml [SpotBugs] -> found 0 issues (skipped 0 duplicates) [SpotBugs] Successfully parsed file .../target/spotbugsXml.xml [SpotBugs] -> found 0 issues (skipped 0 duplicates) [SpotBugs] Successfully parsed file .../target/spotbugsXml.xml [SpotBugs] -> found 12 issues (skipped 0 duplicates) [SpotBugs] Successfully parsed file .../target/spotbugsXml.xml [SpotBugs] -> found 12 issues (skipped 0 duplicates) ERROR: Step ‘Record compiler warnings and static analysis results’ aborted due to exception: Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to Agent1 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:955) at hudson.FilePath.act(FilePath.java:1070) at hudson.FilePath.act(FilePath.java:1059) at
[JIRA] (JENKINS-37113) Failed to start TEST_SET
Title: Message Title Ambarish Dash updated an issue Jenkins / JENKINS-37113 Failed to start TEST_SET Change By: Ambarish Dash Attachment: screenshot-1.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-37113) Failed to start TEST_SET
Title: Message Title Ambarish Dash commented on JENKINS-37113 Re: Failed to start TEST_SET Hello, I am getting the same issue where my test set type is functional but getting the same error as posted above: Started by user cloudbees Building in workspace /home/cloudbees/.jenkins/workspace/RETINA_Automation_POC [WS-CLEANUP] Deleting project workspace... [WS-CLEANUP] Deferred wipeout is used... [WS-CLEANUP] Done Start login to ALM server... Got authenticate point: http://rkamv823776:80/qcbin/authentication-point/authenticate Logged in successfully to ALM Server http://rkamv823776/qcbin/ using dasha4 Creating session... Session created. Failed to start TEST_SET ID: 23451, ALM Server URL: http://rkamv823776/qcbin (Exception: Server returned HTTP response code: 403 for URL: http://rkamv823776/qcbin/rest/domains/PLAYAREA/projects/SCPDS_Performance_Test/test-sets/23451/startruntestset ) Failed to start TEST_SET ID:23451, run id: Note: You can run only functional test sets and build verification suites using this plugin. Check to make sure that the configured ID is valid (and that it is not a performance test ID). Empty Results Result Status: UNSTABLE Build step 'Execute Micro Focus tests using Micro Focus ALM Lab Management' changed build result to UNSTABLE Recording test results None of the test reports contained any result RunResultRecorder: didn't find any test results to record Finished: UNSTABLE Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-53662) isRestartedRun() is not reset after a successful stage
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-53662 isRestartedRun() is not reset after a successful stage Change By: Vivek Pandey Labels: pipeline-triaged stage-restart-improvements Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54386) preserveStashes does not work with parameter
Title: Message Title Andrew Bayer updated JENKINS-54386 Jenkins / JENKINS-54386 preserveStashes does not work with parameter Change By: Andrew Bayer Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-52777) another Jenkinsfile is used than reported to be used if 'rebuild from stage' is used
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-52777 another Jenkinsfile is used than reported to be used if 'rebuild from stage' is used Change By: Vivek Pandey Labels: pipeline-triaged stage-restart-improvements Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55220) Multibranch Pipeline jobs get randomly lost
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-55220 Multibranch Pipeline jobs get randomly lost Change By: Vivek Pandey Component/s: bitbucket-branch-source-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54928) SCM changes are not noticed and SCMpoll starts the build based on the cron.
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-54928 SCM changes are not noticed and SCMpoll starts the build based on the cron. Change By: Vivek Pandey Labels: bitbucket bitbucket-branch-source-plugin pipeline-triaged Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54869) Multibranch project truncates cloudbees folder workspace paths
Title: Message Title Vivek Pandey assigned an issue to rsandell Jenkins / JENKINS-54869 Multibranch project truncates cloudbees folder workspace paths Change By: Vivek Pandey Assignee: rsandell Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54998) Stash and archive should resolve symlinks
Title: Message Title Andrew Bayer resolved as Duplicate Jenkins / JENKINS-54998 Stash and archive should resolve symlinks Change By: Andrew Bayer Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54869) Multibranch project truncates cloudbees folder workspace paths
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-54869 Multibranch project truncates cloudbees folder workspace paths Change By: Vivek Pandey Labels: pipeline-triaged plugin workspace_corruption Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-43210) Windows Agent can't connect to Master through JNLP
Title: Message Title Matthias Baldi edited a comment on JENKINS-43210 Re: Windows Agent can't connect to Master through JNLP [~gnuheidix] thank you for the information.We checked our Apache config too, but it seems, that our proxy do not reject this headers, so it have to be an other problem.But a workaround is for us currently to deploy first an old Jenkins version and then we can update it without any problems to the newest one.I tried it shortly again with the newest version of Jenkins (2.150.1) and one Slave on the same maschine. Both tests with Docker containers were successful on Windows and on Linux.As soon I can test it, I will try something with a proxy and over multiple servers, maybe it will work now. And I will update the plugins, maybe it is not an issue of Jenkins itself, it could be, that we hit it because of a plugin update. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-43210) Windows Agent can't connect to Master through JNLP
Title: Message Title Matthias Baldi commented on JENKINS-43210 Re: Windows Agent can't connect to Master through JNLP Thomas Heidrich thank you for the information. We checked our Apache config too, but it seems, that our proxy do not reject this headers, so it have to be an other problem. But a workaround is for us currently to deploy first an old Jenkins version and then we can update it without any problems to the newest one. I tried it shortly again with the newest version of Jenkins (2.150.1) and one Slave on the same maschine. Both tests with Docker containers were successful on Windows and on Linux. As soon I can test it, I will try something with a proxy and over multiple servers, maybe it will work now. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.
