[JIRA] [buildresult-trigger-plugin] (JENKINS-31933) Workflow can't be triggered with BuildResultTrigger
Title: Message Title Przemek Hejman updated an issue Jenkins / JENKINS-31933 Workflow can't be triggered with BuildResultTrigger Change By: Przemek Hejman Component/s: buildresult-trigger-plugin Component/s: buildresulttrigger Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [urltrigger-plugin] (JENKINS-31933) Workflow can't be triggered with BuildResultTrigger
Title: Message Title Przemek Hejman updated an issue Jenkins / JENKINS-31933 Workflow can't be triggered with BuildResultTrigger Change By: Przemek Hejman Component/s: urltrigger-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [xtrigger-plugin] (JENKINS-31933) Workflow can't be triggered with BuildResultTrigger
Title: Message Title Przemek Hejman commented on JENKINS-31933 Re: Workflow can't be triggered with BuildResultTrigger I've encountered exactly the same issue with URLTrigger plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [workflow-plugin] (JENKINS-31933) Workflow can't be triggered with BuildResultTrigger
Title: Message Title Przemek Hejman created an issue Jenkins / JENKINS-31933 Workflow can't be triggered with BuildResultTrigger Issue Type: Bug Assignee: Jesse Glick Attachments: workflow2.jpg Components: workflow-plugin Created: 07/Dec/15 9:37 AM Environment: Jenkins ver. 1.638, BuildResultTrigger Plug-in 0.17 Priority: Major Reporter: Przemek Hejman I would like to have my workflow triggered by BuildResultTrigger. When I configure this in 'Build Triggers' section and click "Save", I end up with following page (screenshot attached). Here's pasted stack trace: javax.servlet.ServletException: java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowJob cannot be cast to hudson.model.AbstractProject at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at
[JIRA] [core] (JENKINS-27292) Very first build on slave takes significantly much time than next ones
Przemek Hejman updated JENKINS-27292 Very first build on slave takes significantly much time than next ones Change By: Przemek Hejman (09/Mar/15 1:38 PM) Summary: Veryfirstbuildonslavetakes significantlymuchtimethannextones 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/d/optout.
[JIRA] [core] (JENKINS-27292) Very first build on slave takes
Przemek Hejman created JENKINS-27292 Very first build on slave takes Issue Type: Bug Assignee: Francis Upton Components: core, ec2-plugin, slave-utilization Created: 09/Mar/15 1:36 PM Description: Hi everyone, I've recently stepped into a really strange issue to me, I wonder if you could explain me mechanisms that are happening during my build processes. I am using the EC2 plugin to spawn a slave agents. I've prepared provisioned slave image with all necessary packages, repository cloned, and artifacts downloaded, but when a job is being run for the very first time, step below: 00:00:00.004 Building remotely on EC2 Android-runner (i-eb81dd28) (ubuntu-java-ec2) in workspace /home/ubuntu/workspace/Android-Devel 00:01:29.496 git rev-parse --is-inside-work-tree # timeout=10 use to run for longer than minute. After this first job is completed and I trigger one more build on that slave and this "Building remotely..." step takes only a second. Could you explain me what is being done there so that it takes so long for the very first time after launching slave? Exactly the same time difference appears in the last step 00:08:31.055 Recording test results 00:10:21.737 Finished: SUCCESS versus: 00:04:32.545 Recording test results 00:05:18.314 Finished: SUCCESS It seems like the long-lasting tasks are all involving some master-slave communication, but I couldn't find any information about this in logs.. Could you please tell me why such a differences between first and the following builds appear? My plans were to spawn a node per built, but when total build time takes twice the time than build on long-running slave it seems not to have sense at all.. Project: Jenkins Priority: Minor Reporter: Przemek Hejman 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/d/optout.
[JIRA] [core] (JENKINS-27292) Very first build on slave takes significantly much time than next ones
Przemek Hejman commented on JENKINS-27292 Very first build on slave takes significantly much time than next ones Hi Daniel, I've already discussed this issue up there. Don't you consider my situation as a bug?? 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/d/optout.
