[JIRA] (JENKINS-38476) Always use "-usenonexclusivelock" option

2016-10-19 Thread mustafaulu....@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mustafa Ulu closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Not that useful.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-38476  
 
 
  Always use "-usenonexclusivelock" option   
 

  
 
 
 
 

 
Change By: 
 Mustafa Ulu  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 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-38476) Always use "-usenonexclusivelock" option

2016-09-23 Thread mustafaulu....@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mustafa Ulu created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38476  
 
 
  Always use "-usenonexclusivelock" option   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Raphael CHAUMIER  
 
 
Components: 
 weblogic-deployer-plugin  
 
 
Created: 
 2016/Sep/23 8:50 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Mustafa Ulu  
 

  
 
 
 
 

 
 I believe WebLogic Deployer Plugin fits the definition of "-usenonexclusivelock" option perfectly: 

Deployment operation uses an existing lock, already acquired by the same user, on the domain. This option is helpful in environments where multiple deployment tools are used simultaneously and one of the tools has already acquired a lock on the domain configuration.
 https://docs.oracle.com/cd/E13222_01/wls/docs103/deployment/wldeployer.html  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment