[JIRA] (JENKINS-61592) Enable auto refresh button os missing

2020-04-17 Thread from_jenk...@dondorp.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Erwin Dondorp commented on  JENKINS-61592  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Enable auto refresh button os missing   
 

  
 
 
 
 

 
 Daniel Beck Was the function removed because the refresh-function from the browser should be used instead, or that Jenkins now always keeps is screens up-to-date?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205289.1584636825000.13269.1587149940363%40Atlassian.JIRA.


[JIRA] (JENKINS-56476) multi-branch pipeline creates new job for tag but job is not executed

2019-03-08 Thread from_jenk...@dondorp.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Erwin Dondorp created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56476  
 
 
  multi-branch pipeline creates new job for tag but job is not executed   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 pipeline  
 
 
Created: 
 2019-03-08 09:42  
 
 
Environment: 
 Jenkins ver. 2.167, Git plugin 3.9.3, Pipeline Multibranch 2.20 (and several others)  (everything up-to-date at this time)  
 
 
Labels: 
 pipeline  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Erwin Dondorp  
 

  
 
 
 
 

 
 Multibranch pipeline works as expected for branches. Jobs are automatically created for new branches, build on any updates and deleted when the branch is removed. For TAGS, the situation is different. Jobs are automatically created for new tags (ok). But there is never a build triggered automatically. the job is deleted when te tag is deleted though. A simple manual build works properly; but automation is preferred of course.