[JIRA] [teamconcert] (JENKINS-20994) Make Just accept and fetch from a build workspace more full featured
Christian Höltje commented on JENKINS-20994 Make Just accept and fetch from a build workspace more full featured I currently delete the workspace before and after a build anyway; I don't trust Jazz to clean out the directory. I'd trust if there was a checkbox to reset the workspace to prestine. In "git" lingo that'd be: "git reset; git checkout ; git clean -xfd" So deleting the .jazz directory wouldn't be horrible for me. But it has to hapen at exactly the right time After maven release has finished creating the snapshot and pushing it up, but before it starts building the release copies. re: "well-formed" it is really a convention, I guess... I didn't have a good name for it. But it is any Component that: 1) Only has one directory at the top-level. 2) The directory must match the component name. 3) Has no other files in the top-level. The people in the group seem to think this is a normal convention for RTC. If it isn't, I'd like to hear more. re: automated creation of build definitions Let me explain how I set this up without the build definitions and then explain how I'd automate build definitions... I have several jobs: Create-and-destroy-workspaces: This creates workspaces matching the pattern: Jenkins_(component_name)_(suffix_for_stream). In pseudo-code: For each stream: For each component in stream: create workspace unless workspace exists For each workspace matching /Jenkins_.*/ delete workspace unless stream and component exists List workspaces: Basically, it runs: scm workspaces list --json workspaces.json Build Jobs: For each workspace in workspaces.json: Create job using the Job DSL plugin So what I'd do is add a forth job that would use the workspaces.json and generate the build definitions. Or I could add it in the Create-and-destroy-workspaces job, if needed extra info only available there. I hope that answers your questions. If you want a demo, contact me at IBM. I'm choltje in the US. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-20994) Make Just accept and fetch from a build workspace more full featured
Christian Höltje edited a comment on JENKINS-20994 Make Just accept and fetch from a build workspace more full featured I currently delete the workspace before and after a build anyway; I don't trust Jazz to clean out the directory. I'd trust if there was a checkbox to reset the workspace to prestine. In "git" lingo that'd be: "git reset; git checkout ; git clean -xfd" So deleting the .jazz directory wouldn't be horrible for me. But it has to hapen at exactly the right time After maven release has finished creating the snapshot and pushing it up, but before it starts building the release copies. re: "well-formed" it is really a convention, I guess... I didn't have a good name for it. But it is any Component that: 1) Only has one directory at the top-level. 2) The directory must match the component name. 3) Has no other files in the top-level. The people in the group seem to think this is a normal convention for RTC. If it isn't, I'd like to hear more. re: automated creation of build definitions Let me explain how I set this up without the build definitions and then explain how I'd automate build definitions... I have several jobs: Create-and-destroy-workspaces: This creates workspaces matching the pattern: Jenkins_(component_name)_(suffix_for_stream). In pseudo-code: For each stream: For each component in stream: create workspace unless workspace exists For each workspace matching /Jenkins_.*/ delete workspace unless stream and component exists List workspaces: Basically, it runs: scm workspaces list --json workspaces.json Build Jobs: For each workspace in workspaces.json: Create job using the Job DSL plugin So what I'd do is add a forth job that would use the workspaces.json and generate the build definitions. Or I could add it in the Create-and-destroy-workspaces job, if needed extra info only available there. I hope that answers your questions. If you want a demo, contact me at IBM. I'm choltje in the US. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-20994) Make Just accept and fetch from a build workspace more full featured
Heather Fraser-Dube commented on JENKINS-20994 Make Just accept and fetch from a build workspace more full featured Removing the .jazz directory is not ideal. It will result in a complete re-load (as opposed to just the files that changed). I have raised 296206: Make "Just accept and fetch from a build workspace" more full featured in jazzdev to help us track this. I am curious, how do you decide if the component is "well-formed"? Is this something you do as part of the build or when setting up the build. Also can you describe how you would use "automated creation of build definitions" if that feature was available? I guess I am wondering when it would be automatically generated, which pieces would be configured? What were the other reasons for not using a build definition? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-20994) Make Just accept and fetch from a build workspace more full featured
Christian Höltje commented on JENKINS-20994 Make Just accept and fetch from a build workspace more full featured Yup. I've tried "Use custom workspace" but it doesn't do what I want. Regardless of what $WORKSPACE is set to, everything is checked out in $WORKSPACE... I want to be able to specify an alternative directory to checkout in, relative to $WORKSPACE. Specifically I have several cases: 1) If the Component is well formed (e.g. the component name is FuBar and it contains only one top-level directory FuBar) then I'd like to check the contents of FuBar out to the root of $WORKSPACE 2) For components that aren't well formed (e.g. the component name is FuBar and it contains multiple top-level files and directories) then I want to check the contents out at $WORKSPACE/rtc-ws/ (for example). In addition, I need case 2 for when doing Maven releases, because the Maven Release Plugin cannot checkout a second copy of the repository (needed for some odd reason) within the target directory. This is a known limitation with Jazz SCM. To work around it I need to create a second directory (e.g. $WORKSPACE/release-copy) and tell Maven to use that for the release. There must not be a $WORKSPACE/.jazz directory in this case. Obviously I can remove the .jazz directory in a pre-build step, but that seems rather disgusting to me and I'm unclear if it would effect the TeamCenter plugin. Hopefully I was clear in my description. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-20994) Make Just accept and fetch from a build workspace more full featured
Scott Cowan updated JENKINS-20994 Make Just accept and fetch from a build workspace more full featured Change By: Scott Cowan (13/Dec/13 2:05 PM) Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-20994) Make Just accept and fetch from a build workspace more full featured
Heather Fraser-Dube commented on JENKINS-20994 Make Just accept and fetch from a build workspace more full featured Have you tried changing the Jenkins workspace directory? You can do this in the configuration of the Job. Go to the Advanced Project Options section. Under there is a checkbox for "Use custom workspace" if you enable this, you can specify an alternate location of the Job's workspace. Or is it that you require further customization of where to load within the Jenkins workspace directory? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-20994) Make Just accept and fetch from a build workspace more full featured
Christian Höltje created JENKINS-20994 Make Just accept and fetch from a build workspace more full featured Issue Type: Bug Assignee: Unassigned Components: teamconcert Created: 12/Dec/13 6:03 PM Description: There are a lot of features that could be added to the "build workspace" method that would make it much more useful. I understand the advantage of the Build Definition method, but there are reasons not to use this, including the fact you cannot automate the creation of Build Definitions in RTC. Things I'd like to see: For example, being able to choose the Load Directory would be useful. Project: Jenkins Priority: Minor Reporter: Christian Höltje This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
