Summary: | postingDirectory properties are confusing | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | David Williams <david_williams> |
Component: | Releng | Assignee: | David Williams <david_williams> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 4.2 | ||
Target Milestone: | 4.2 M7 | ||
Hardware: | PC | ||
OS: | Linux | ||
Whiteboard: | |||
Bug Depends on: | |||
Bug Blocks: | 355430 |
Description
David Williams
2012-03-31 13:13:53 EDT
I've made these less confusing, by redefining them :) Essentially mimicking the "final structure" on downloads.eclipse.org. postingDirectory=${siteDir}/eclipse/downloads/drops4 mkdir -p $postingDirectory echo "postingDirectory: $postingDirectory" equinoxPostingDirectory=${siteDir}/equinox mkdir -p $equinoxPostingDirectory echo "equinoxPostingDirectory: $equinoxPostingDirectory" localUpdateSite=${siteDir}/updates mkdir -p $localUpdateSite echo "localUpdateSite: $localUpdateSite" where "siteDir" is currently defined "at the top" of our specific build area on build.eclipse.org. writableBuildRoot=/shared/eclipse/eclipse4 export siteDir=$writableBuildRoot/siteDir In theory, if/when this got running in a smooth error resistant way, we could probably define "siteDir" directly to "downloads" server file system. But, for now, we'll have a separate step to "update" the files once relatively sure the build went ok. |