[JIRA] (JENKINS-38053) JellyTagException on Multijob project view with Jenkins 2.7.3 LTS
Title: Message Title Jurgen Van Bouchaute commented on JENKINS-38053 Re: JellyTagException on Multijob project view with Jenkins 2.7.3 LTS Not exactly the same stacktrace, but downgrading to plugin version 1.21 solves the issue ! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38053) JellyTagException on Multijob project view with Jenkins 2.7.3 LTS
Title: Message Title Jurgen Van Bouchaute created an issue Jenkins / JENKINS-38053 JellyTagException on Multijob project view with Jenkins 2.7.3 LTS Issue Type: Bug Assignee: Unassigned Attachments: multijob error stacktrace.txt, multijob error1.jpg Components: multijob-plugin Created: 2016/Sep/08 6:20 AM Environment: Jenkins 2.7.3 LTS Multijob plugin version 1.22 Labels: multijob Priority: Critical Reporter: Jurgen Van Bouchaute Jenkins project view does not show contents when it's a multijob project after upgrading to Jenkins 2.7.x : Instead it show an error page with a stacktrace : (JellyTagException). See attachments.
[JIRA] [core] (JENKINS-29028) Jenkins build is stuck in (pending) without explanation for indefinite time
Title: Message Title Jurgen Van Bouchaute commented on JENKINS-29028 Re: Jenkins build is stuck in (pending) without explanation for indefinite time Same issue here when upgrading from LTS 1.596.2 version to LTS 1.609.1 but when using another option (block build while certain jobs are running) : Linux OS Java 1.8 Tomcat 8 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] [core] (JENKINS-29028) Jenkins build is stuck in (pending) without explanation for indefinite time
Title: Message Title Jurgen Van Bouchaute updated an issue Jenkins / JENKINS-29028 Jenkins build is stuck in (pending) without explanation for indefinite time Change By: Jurgen Van Bouchaute Attachment: screenshot-1.png 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] [vsphere-cloud-plugin] (JENKINS-25956) New buildstep : restart Guest
Jurgen Van Bouchaute created JENKINS-25956 New buildstep : restart Guest Issue Type: New Feature Assignee: Unassigned Components: vsphere-cloud-plugin Created: 08/Dec/14 1:07 PM Description: This is typically used in context where a set of Windows Test Vm's need to be rebooted to be in a clean state before a build / test job executes on Jenkins. Now this needs to be accomplished using 2 different buildsteps (stop + start) Project: Jenkins Priority: Minor Reporter: Jurgen Van Bouchaute 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] [vsphere-cloud-plugin] (JENKINS-25955) New buildstep : restart Guest
Jurgen Van Bouchaute created JENKINS-25955 New buildstep : restart Guest Issue Type: New Feature Assignee: Unassigned Components: vsphere-cloud-plugin Created: 08/Dec/14 1:05 PM Description: This is typically used in context where a set of Windows Test Vm's need to be rebooted to be in a clean state before a build / test job executes on Jenkins. Now this needs to be accomplished using 2 different buildsteps (stop + start) Project: Jenkins Priority: Minor Reporter: Jurgen Van Bouchaute 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] [vsphere-cloud-plugin] (JENKINS-25956) New buildstep : restart Guest
Jurgen Van Bouchaute closed JENKINS-25956 as Duplicate New buildstep : restart Guest dupe Change By: Jurgen Van Bouchaute (08/Dec/14 1:09 PM) Status: Open Closed Resolution: Duplicate 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] [vsphere-cloud-plugin] (JENKINS-25957) Buildstep : allow multiple VM's to be managerd with a single buildstep
Jurgen Van Bouchaute created JENKINS-25957 Buildstep : allow multiple VMs to be managerd with a single buildstep Issue Type: New Feature Assignee: Unassigned Components: vsphere-cloud-plugin Created: 08/Dec/14 1:16 PM Description: Allow multiple VM names to be managed in a single vsphere plugin buildstep (such as stop / start). IN context of using a Selenium grid farm that relies on a large number of Windows VM's to execute Webdriver tests, we want to use this plugin to stop start the farm so that all the VM's are in a clean state before job execution on Jenkins. Typically there's one job that triggers execution of the Selenium test suite. With the current plugin implementation , we have to define a long list of vsphere build steps (one for each VM in the farm) to be able to manage this. Allowing multiple entries would simplify dramatically our setup. Project: Jenkins Labels: configuration Priority: Major Reporter: Jurgen Van Bouchaute 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] [vsphere-cloud-plugin] (JENKINS-25957) Buildstep : allow multiple VM's to be managed with a single buildstep
Jurgen Van Bouchaute updated JENKINS-25957 Buildstep : allow multiple VMs to be managed with a single buildstep Change By: Jurgen Van Bouchaute (08/Dec/14 1:18 PM) Summary: Buildstep:allowmultipleVMstobe managerd managed withasinglebuildstep 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] [junit] (JENKINS-17883) flags skipNoTestFiles and failIfNotNew are not saved properly [since xunit 1.56]
Jurgen Van Bouchaute commented on JENKINS-17883 flags skipNoTestFiles and failIfNotNew are not saved properly [since xunit 1.56] Noticed same problem behaviour in 1.55 as well (downgrade from 1.58) 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-multijob-plugin] (JENKINS-17291) No separate view for multijob builds.
Jurgen Van Bouchaute commented on JENKINS-17291 No separate view for multijob builds. Support for regex job filtering would be great (just like the standard job view) 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-17254) Multijon view last succes / last failure columns shows status instead of #of days/hours since
Jurgen Van Bouchaute created JENKINS-17254 Multijon view last succes / last failure columns shows status instead of #of days/hours since Issue Type: Bug Assignee: Unassigned Attachments: 18-03-2013 14-50-04.png Components: jenkins-multijob-plugin Created: 18/Mar/13 1:55 PM Description: The last success / last failure columns on the multijob view should mention the number of days / hours since this last success/failure, not a status ball See screenshot. Project: Jenkins Priority: Major Reporter: Jurgen Van Bouchaute 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-17254) Multijob view last succes / last failure columns shows status instead of #of days/hours since
Jurgen Van Bouchaute updated JENKINS-17254 Multijob view last succes / last failure columns shows status instead of #of days/hours since Change By: Jurgen Van Bouchaute (18/Mar/13 1:55 PM) Summary: Multijon Multijob viewlastsucces/lastfailurecolumnsshowsstatusinsteadof#ofdays/hourssince 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-16974) Build Now link on MultiJob page doesn't work
Jurgen Van Bouchaute commented on JENKINS-16974 Build Now link on MultiJob page doesnt work Same issue here. Please fix. 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-16924) Slave nodes : install as windows service not availabe anymore + slave connectivity issues since 1.502
Jurgen Van Bouchaute created JENKINS-16924 Slave nodes : install as windows service not availabe anymore + slave connectivity issues since 1.502 Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: jenkinsmaster1.png, jenkinsmaster2.png, jenkinsslave1.png Components: master-slave Created: 22/Feb/13 7:16 AM Description: Verrsion 1.502 Master on Linux Slaves on Windows XP VM When launching slave as JNLP, then mention : connected, but they are not seen as connected by the master ON the master there is an exception displayed (connection reset) The option to register the slave windows as windows service has disappeared since moving to 1.502 Happens on the 2 slaves nodes. No logs created on the slaves. Did try to uninstall the service / relaunch the via JNLP , but no success. Issues started when migrated from 1.498 to 1.502 Did work previously fine with 1.498. Environment: Windows XP SP3 32 bits (slaves), Linux SLES 11 (master) Project: Jenkins Priority: Critical Reporter: Jurgen Van Bouchaute 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-16924) Slave nodes : install as windows service not availabe anymore + slave connectivity issues since 1.502
Jurgen Van Bouchaute resolved JENKINS-16924 as Not A Defect Slave nodes : install as windows service not availabe anymore + slave connectivity issues since 1.502 Caused by the chromedriver plugin not able to upload the plugin to the slaves. Issue closed. Change By: Jurgen Van Bouchaute (22/Feb/13 7:25 AM) Status: Open Resolved Resolution: NotADefect 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-15156) Builds Disappear from Build History after Completion
Jurgen Van Bouchaute commented on JENKINS-15156 Builds Disappear from Build History after Completion Same problem on 1.498 version (Linux) - very annoying 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
[JIRA] (JENKINS-15606) CloverPHP : error during configuration of cloverPHP in job
Jurgen Van Bouchaute commented on JENKINS-15606 CloverPHP : error during configuration of cloverPHP in job The main reason for this error is that the plugin does not support multiple jenkins nodes (machines). It tries to verify the existence of certain files on the main host, whereas the job workspace is located on the executor remote host. 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-15606) CloverPHP : error during configuration of cloverPHP in job
Jurgen Van Bouchaute created JENKINS-15606 CloverPHP : error during configuration of cloverPHP in job Issue Type: Bug Affects Versions: current Assignee: sogabe Attachments: 24-10-2012 14-26-46.png Components: cloverphp-plugin Created: 24/Oct/12 12:29 PM Description: If I add a post-build step "publish Clover PHP Coverage report" to a job, I get a 404 resource not found twice on the configuration panel Environment: Jenkins version 1.464 Windows Project: Jenkins Labels: plugin exception Priority: Major Reporter: Jurgen Van Bouchaute 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
