[JIRA] [clone-workspace-plugin] (JENKINS-30567) Flexible publish and clone workspace

2015-12-01 Thread henrik.steu...@googlemail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Steudel started work on  JENKINS-30567 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Henrik Steudel 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [clone-workspace-plugin] (JENKINS-30567) Flexible publish and clone workspace

2015-12-01 Thread henrik.steu...@googlemail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Steudel stopped work on  JENKINS-30567 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Henrik Steudel 
 
 
 

Status:
 
 In Progress Open 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [clone-workspace-plugin] (JENKINS-30567) Flexible publish and clone workspace

2015-10-09 Thread de...@ikedam.jp (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ikedam updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30567 
 
 
 
  Flexible publish and clone workspace  
 
 
 
 
 
 
 
 
 
 
I added Clone Workspace SCM Plugin to the list of known plugins that doesn't work with Flexible Publish: https://wiki.jenkins-ci.org/display/JENKINS/Flexible+Publish+Plugin#FlexiblePublishPlugin-Knownpluginsthatdoesn%27tworkwithFlexiblePublish 
 
 
 
 
 
 
 
 
 

Change By:
 
 ikedam 
 
 
 

Component/s:
 
 flexible-publish-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [clone-workspace-plugin] (JENKINS-30567) Flexible publish and clone workspace

2015-09-24 Thread de...@ikedam.jp (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ikedam commented on  JENKINS-30567 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Flexible publish and clone workspace  
 
 
 
 
 
 
 
 
 
 
Clone-workspace-scm plugin lists up project that configured with CloneWorkspacePublisher, and fails to know a project is configured with that publisher when it is wrapped in flexible-publish. https://github.com/jenkinsci/jenkins-clone-workspace-scm-plugin/blob/clone-workspace-scm-0.6/src/main/java/hudson/plugins/cloneworkspace/CloneWorkspaceSCM.java#L347 
Though there's no "best" way as Jenkins doesn't support nesting publishers like flexible-publish, there're following ways clone-workspace-scm can do: 
 

Implement Publisher#getProjectActions and use the action as a marker. 
 

This is usually used for adding UI menues to projects configured with the publisher.
 

flexible-publish calls it for nested publishers.
 
 
 

Detect flexible-publish and look up nested CloneWorkspacePublisher. 
 

It may be a little complicated as you have to add plugin dependencies and flexible-publish may wrap multiple publishers.
 
 
 

Allow to input project names manually. 
 

This also allow you use variables to specify source projects.
 
 
 

Add a conditional execurion feature to clone-workspace-scm.
 
 
Anyway, there's nothing flexible-publish can do for this issue... 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 

[JIRA] [clone-workspace-plugin] (JENKINS-30567) Flexible publish and clone workspace

2015-09-21 Thread atrau...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexander Trauzzi created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30567 
 
 
 
  Flexible publish and clone workspace  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 abayer 
 
 
 

Components:
 

 clone-workspace-plugin, flexible-publish-plugin 
 
 
 

Created:
 

 21/Sep/15 1:19 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Alexander Trauzzi 
 
 
 
 
 
 
 
 
 
 
When I have a clone-workspace post-build action configured, it doesn't show up in the list of options for selection on a consuming project. 
I'm currently able to get around this by temporarily populating a "dummy" clone-workspace post-build action and then making the selection in my consuming project. Then I can delete it from the "producing" project. 
Any time I edit the consuming project however, I have to make sure the dummy is recreated, otherwise I lose the setting. 
Is there any way to make clone workspace aware of flexible publish? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment