|
||||||||
|
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.
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.