[JIRA] (JENKINS-55921) When SCM polling fails, the result is logged as "no changes"

2019-02-08 Thread j...@genexus.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 José Lamas resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55921  
 
 
   When SCM polling fails, the result is logged as "no changes"   
 

  
 
 
 
 

 
Change By: 
 José Lamas  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 https://github.com/jenkinsci/genexus-plugin/releases/tag/genexus-1.5  
 

  
 
 
 
 

 
 
 

 
 
 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-55921) When SCM polling fails, the result is logged as "no changes"

2019-02-01 Thread j...@genexus.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 José Lamas created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55921  
 
 
   When SCM polling fails, the result is logged as "no changes"   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 José Lamas  
 
 
Components: 
 genexus-plugin  
 
 
Created: 
 2019-02-01 21:14  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 José Lamas  
 

  
 
 
 
 

 
 This was reported in BuildAndDeploy forum https://groups.google.com/a/genexus.com/forum/#!msg/buildanddeploy/mFdIsnRLQKE/MJjUrFD8AQAJ There's also a similar issue about git-client-plugin at https://issues.jenkins-ci.org/browse/JENKINS-32712  When a project uses SCM polling, if the polling fails (eg: bad credentials) although the plugin throws an exception, the engine takes that as "no changes", the build is not triggered and it's hard to note the problem.      
 

  
 
 
 
 

 
 
 

 
 
 Add Comment