[JIRA] (JENKINS-54917) Github pull request builds created but not triggered
Title: Message Title Vincent de Lagabbe closed an issue as Not A Defect Mea culpa. I didn't add the build strategy "Changes requests" to the config. Sorry again for the noise. Jenkins / JENKINS-54917 Github pull request builds created but not triggered Change By: Vincent de Lagabbe Status: Open Closed 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-54917) Github pull request builds created but not triggered
Title: Message Title Vincent de Lagabbe created an issue Jenkins / JENKINS-54917 Github pull request builds created but not triggered Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2018-11-28 13:26 Environment: Jenkins version: 2.138.3 Github branch source plugin version: 2.4.1 Labels: github github-branch-source-plugin pull-request Priority: Minor Reporter: Vincent de Lagabbe I use the github branch source plugin with a github.com hosted organization The organization setup is: Discover branches: "Exclude branches that are also files as PR" Discover pull requests from origin: "Both the current pull request revision and the pull request merged with the current target branch revision" I recursively updates sub modules and checkout over SSH When a PR is created, the two pull request jenkins jobs "PR-head" and "PR-merge" are created, but Jenkins does not start them The "Organization event" log shows messages: > No automatic builds for PR-XX-head > No automatic builds for PR-XX-merge Why are the PRs jobs not built ? Thank you very much
[JIRA] [conditional-buildstep] (JENKINS-20543) error on delete job - java.lang.NoSuchMethodError: org.jenkinsci.plugins.conditionalbuildstep.ConditionalBuildStepHelper
vinz r commented on JENKINS-20543 error on delete job - java.lang.NoSuchMethodError: org.jenkinsci.plugins.conditionalbuildstep.ConditionalBuildStepHelper Hi, Verified this new plugin version 1.3.3 and no error occurred when deleting projects. Jenkins version is 1.538. Thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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/groups/opt_out.
[JIRA] [ec2] (JENKINS-20352) computer/*/configure view doesn't render completely and displays exception
vinz r commented on JENKINS-20352 computer/*/configure view doesnt render completely and displays exception I've deployed the new ec2 plugin version 1.20. But the errors are still there. Jenkins version is 1.538. Thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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/groups/opt_out.
[JIRA] (JENKINS-17264) m2release build fails with java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject
vinz r commented on JENKINS-17264 m2release build fails with java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject I still encountered this error on 1.507. Thanks, Vinz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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/groups/opt_out.
[JIRA] (JENKINS-15319) Failure starting slave nodes
vinz r commented on JENKINS-15319 Failure starting slave nodes I also encounter the same problem. Any update on this? Thanks, Vinz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15609) New created EC2 instance SCP Error
vinz r created JENKINS-15609 New created EC2 instance SCP Error Issue Type: Bug Affects Versions: current Assignee: Francis Upton Components: ec2, scp Created: 24/Oct/12 1:14 PM Description: When starting the new EC2 instance as slave node encountered a problem: java full version "1.6.0_24-b24" Copying slave.jar ERROR: Error during SCP transfer. java.io.IOException: Error during SCP transfer. at com.trilead.ssh2.SCPClient.put(SCPClient.java:523) at com.trilead.ssh2.SCPClient.put(SCPClient.java:476) at hudson.plugins.ec2.ssh.EC2UnixLauncher.launch(EC2UnixLauncher.java:126) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:57) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:200) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) Caused by: java.io.IOException: Remote scp terminated unexpectedly. at com.trilead.ssh2.SCPClient.readResponse(SCPClient.java:50) at com.trilead.ssh2.SCPClient.sendBytes(SCPClient.java:140) at com.trilead.ssh2.SCPClient.put(SCPClient.java:519) ... 9 more But re-lunching the slave nodes it runs properly. Is this a bug for EC2 plugin? Current Jenkins version 1.487 and Amazon EC2 Plugins is 1.17 Thanks, Vinz Fix Versions: current Project: Jenkins Priority: Critical Reporter: vinz r This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15609) New created EC2 instance SCP Error
vinz r
updated JENKINS-15609
New created EC2 instance SCP Error
Change By:
vinz r
(24/Oct/12 1:22 PM)
Description:
WhenstartingthenewEC2instanceasslavenodeencounteredaproblem:
{noformat}
javafullversion1.6.0_24-b24Copyingslave.jarERROR:ErrorduringSCPtransfer.java.io.IOException:ErrorduringSCPtransfer. atcom.trilead.ssh2.SCPClient.put(SCPClient.java:523) atcom.trilead.ssh2.SCPClient.put(SCPClient.java:476) athudson.plugins.ec2.ssh.EC2UnixLauncher.launch(EC2UnixLauncher.java:126) athudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:57) athudson.slaves.SlaveComputer$1.call(SlaveComputer.java:200) atjava.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) atjava.util.concurrent.FutureTask.run(FutureTask.java:166) atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) atjava.lang.Thread.run(Thread.java:636)Causedby:java.io.IOException:Remotescpterminatedunexpectedly. atcom.trilead.ssh2.SCPClient.readResponse(SCPClient.java:50) atcom.trilead.ssh2.SCPClient.sendBytes(SCPClient.java:140) atcom.trilead.ssh2.SCPClient.put(SCPClient.java:519) ...9more
{noformat}
OnMasterJenkinstheErrorlogssays{noformat}ct24,20126:06:43AMhudson.slaves.NodeProvisionerupdateWARNING:ProvisionedslaveJenkinsSlaves(ami-4afe4623)failedtolaunchjava.util.concurrent.ExecutionException:java.io.IOException:Slavefailedtoconnect,eventhoughthelauncherdidntreportit.Seethelogoutputfordetails. atjava.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:252) atjava.util.concurrent.FutureTask.get(FutureTask.java:111) athudson.plugins.ec2.EC2Cloud$1.call(EC2Cloud.java:253) athudson.plugins.ec2.EC2Cloud$1.call(EC2Cloud.java:239) atjava.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) atjava.util.concurrent.FutureTask.run(FutureTask.java:166) atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) atjava.lang.Thread.run(Thread.java:636)Causedby:java.io.IOException:Slavefailedtoconnect,eventhoughthelauncherdidntreportit.Seethelogoutputfordetails. athudson.slaves.SlaveComputer$1.call(SlaveComputer.java:221) ...5more{noformat}
Butre-lunchingtheslavenodesitrunsproperly.IsthisabugforEC2plugin?CurrentJenkinsversion1.487andAmazonEC2Pluginsis1.17Thanks,Vinz
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
