[JIRA] (JENKINS-38877) Build History by Node doesn't work with Pipeline

2019-01-14 Thread alex.do...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dover edited a comment on  JENKINS-38877  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Build History by Node doesn't work with Pipeline   
 

  
 
 
 
 

 
 Essential feature with no alternatives. Can ; ' t believe it's just abandoned :(  
 

  
 
 
 
 

 
 
 

 
 
 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-38877) Build History by Node doesn't work with Pipeline

2019-01-14 Thread alex.do...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dover commented on  JENKINS-38877  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Build History by Node doesn't work with Pipeline   
 

  
 
 
 
 

 
 Essential feature with no alternatives. Can;t believe it's just abandoned   
 

  
 
 
 
 

 
 
 

 
 
 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-52922) slave is getting disconnected in the middle of the job

2018-12-17 Thread alex.do...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dover assigned an issue to Alex Dover  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52922  
 
 
  slave is getting disconnected in the middle of the job   
 

  
 
 
 
 

 
Change By: 
 Alex Dover  
 
 
Assignee: 
 Jeff Thompson Alex Dover  
 

  
 
 
 
 

 
 
 

 
 
 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-32027) Jobs with very long configuration cause script errors in browser and extremely long loading times (10+ minutes)

2016-08-25 Thread alex.do...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dover commented on  JENKINS-32027  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jobs with very long configuration cause script errors in browser and extremely long loading times (10+ minutes)   
 

  
 
 
 
 

 
 Hi, Thanks for the fix! Any idea when this change is going to make it into the LTS release?  
 

  
 
 
 
 

 
 
 

 
 
 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] [postbuildscript-plugin] (JENKINS-26079) Jobs triggered through execute build command using parameterized build trigger seem to wait indefinetely

2014-12-16 Thread alex.do...@gmail.com (JIRA)














































Alex Dover
 created  JENKINS-26079


Jobs triggered through execute build command using parameterized build trigger seem to wait indefinetely















Issue Type:


Bug



Assignee:


Gregory Boissinot



Components:


postbuildscript-plugin



Created:


16/Dec/14 11:19 AM



Description:


We have multiple jobs (A B C) that trigger that all trigger the same job ( D ) as post build "Build Steps"
What we see is that each of A,B or C would randomly hang on "Waiting for the completion of D" despite the fact that the D instance they called has completed long time ago (we're talking jobs hanging for days sometimes)
The only thing we saw in JVM monitoring that was weird was things like one instance of A waiting for another instance of A with "waiting for Check point COMPLETED on A#XYZ)
All the jobs in question have concurrent execution enabled.
Unfortunately we're unable to provide an exact scenario in which the hang happens as it appears random and happens on some days but not others.
Let me know if there is something in Jenkins logs i should look for to provide more debug info.
This issue is critical for us, since we need to execute post-build events in a blocking manner and it seems this plugin is the only one giving us this ability.




Environment:


Jenkins 1.503

PostBuildScript 0.16




Project:


Jenkins



Priority:


Critical



Reporter:


Alex Dover

























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] (JENKINS-13815) scm-sync-configuration raises unexpectedError() loading job configuration in IE8

2012-10-29 Thread alex.do...@gmail.com (JIRA)














































Alex Dover
 commented on  JENKINS-13815


scm-sync-configuration raises unexpectedError() loading job configuration in IE8















Same still occurs in 0.0.6.1



























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