[JIRA] [integrity-plugin] (JENKINS-28573) Integrity Plugin does not change serverConfig when job is cloned

2015-08-11 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon resolved as Fixed 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-28573 
 
 
 
  Integrity Plugin does not change serverConfig when job is cloned  
 
 
 
 
 
 
 
 
 

Change By:
 
 SCM/JIRA link daemon 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [integrity-plugin] (JENKINS-28573) Integrity Plugin does not change serverConfig when job is cloned

2015-08-11 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-28573 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Integrity Plugin does not change serverConfig when job is cloned  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Cletus D'Souza Path: src/main/java/hudson/scm/ItemListenerImpl.java http://jenkins-ci.org/commit/integrity-plugin/591cf12f4c0bfdd1dac793bcbd49bbf381bfd5c2 Log: [FIXED JENKINS-28573] Resolved issue where Confguration Name is copied when Job is cloned. Configuration Name is now reset to a unique identifier just like when a new Job is created. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [integrity-plugin] (JENKINS-28573) Integrity Plugin does not change serverConfig when job is cloned

2015-06-24 Thread cletusdso...@hotmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Cletus D'Souza commented on  JENKINS-28573 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Integrity Plugin does not change serverConfig when job is cloned  
 
 
 
 
 
 
 
 
 
 
I'm investigating ways to prevent the configuration name from being copied when a job is cloned. As a temporary work around you could open the xml files that contain the job configuration can blank out the configuration name. This would then cause the plugin to regenerate a new unique configuration name. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [integrity-plugin] (JENKINS-28573) Integrity Plugin does not change serverConfig when job is cloned

2015-05-26 Thread lone...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robert Bitel commented on  JENKINS-28573 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Integrity Plugin does not change serverConfig when job is cloned  
 
 
 
 
 
 
 
 
 
 
Here is a groovy script for testing 
ListString configurations = [] as String[]; 
for (item in Hudson.instance.items) { scm = item.getScm() if (scm.getClass() == hudson.scm.IntegritySCM) { if(configurations.contains(scm.getConfigurationName())) println(item.getName()) configurations.push(scm.getConfigurationName()) } 
 else if (scm.getClass() == org.jenkinsci.plugins.multiplescms.MultiSCM) { for (subscm in scm.getConfiguredSCMs()) { if (subscm.getClass() == hudson.scm.IntegritySCM) { if(configurations.contains(subscm.getConfigurationName())) println(item.getName()) configurations.push(subscm.getConfigurationName()) } 
 } } } 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [integrity-plugin] (JENKINS-28573) Integrity Plugin does not change serverConfig when job is cloned

2015-05-26 Thread lone...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robert Bitel updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-28573 
 
 
 
  Integrity Plugin does not change serverConfig when job is cloned  
 
 
 
 
 
 
 
 
 

Change By:
 
 Robert Bitel 
 
 
 

Priority:
 
 Minor Major 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [integrity-plugin] (JENKINS-28573) Integrity Plugin does not change serverConfig when job is cloned

2015-05-26 Thread lone...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robert Bitel created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-28573 
 
 
 
  Integrity Plugin does not change serverConfig when job is cloned  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Cletus D'Souza 
 
 
 

Components:
 

 integrity-plugin 
 
 
 

Created:
 

 26/May/15 12:23 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Robert Bitel 
 
 
 
 
 
 
 
 
 
 
When cloneing a job for a new one, the configuration is cloned entirely. The configurationName (which is supossed to be unique) is no longer unique. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message