Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Building ECF Release 3.2"
(→Building ECF Release 3.2) |
|||
| Line 1: | Line 1: | ||
Please use this page for planning and discussing build issues related to the upcoming ECF 3.2 Release. | Please use this page for planning and discussing build issues related to the upcoming ECF 3.2 Release. | ||
| − | We're targeting | + | We're targeting February 19, 2010 for the ECF 3.2 release. What does this mean? |
It means on the morning (PST which is -8 hours UTC) of Feb 19, we have a built, signed, and tested set of bundles. So actually this means Feb 18 for Europe. | It means on the morning (PST which is -8 hours UTC) of Feb 19, we have a built, signed, and tested set of bundles. So actually this means Feb 18 for Europe. | ||
| Line 14: | Line 14: | ||
Past experience has shown that sometimes the release build just doesn't work. The network may have timed out and only a subset of the files got uploaded. Or the permissions on the dev.eclipse.org directories were not correct. Or the certificate we use to upload can't be accessed. Or a variety of reasons that have nothing to do with the correctness of the ECF software. And we don't want to clutter up the real 3.2 directory (and overwrite the good but old stuff that may be there) until we know that we have a complete build. | Past experience has shown that sometimes the release build just doesn't work. The network may have timed out and only a subset of the files got uploaded. Or the permissions on the dev.eclipse.org directories were not correct. Or the certificate we use to upload can't be accessed. Or a variety of reasons that have nothing to do with the correctness of the ECF software. And we don't want to clutter up the real 3.2 directory (and overwrite the good but old stuff that may be there) until we know that we have a complete build. | ||
| + | |||
| + | ==== When does the release build happen? ==== | ||
| + | |||
| + | It's forced. It does not occur on a schedule. You have to use the Hudson web interface to ecf2.osuosl.org to kick off a build. And you have to have an account there. [https://ecf2.osuosl.org/hudson/] | ||
Revision as of 15:29, 12 January 2010
Please use this page for planning and discussing build issues related to the upcoming ECF 3.2 Release.
We're targeting February 19, 2010 for the ECF 3.2 release. What does this mean?
It means on the morning (PST which is -8 hours UTC) of Feb 19, we have a built, signed, and tested set of bundles. So actually this means Feb 18 for Europe.
How to follow what's building
Builds (success and failure) are tweeted to ecfbuildmonkey. Failures and failure-fixes are mailed to ecf-build@eclipse.org.
Where does the release build go?
The build is uploaded (by our build script) to dev.eclipse.org. It goes to downloads/rt/ecf/3.2Test/3.6/site.p2. Currently, it really goes to downloads/rt/ecf/3.2Test/3.5/site.p2, but that will be changed shortly. What's key to note here is that the directory is 3.2Test, not 3.2.
The Test here does not mean that there is actually any ECF testing performed on dev.eclipse.org. When we're making release builds, we want to first test that the build is made correctly and gets uploaded correctly. Scott looks at the 3.2Test directory; and if he likes what he sees, he moves the files over to 3.2.
Past experience has shown that sometimes the release build just doesn't work. The network may have timed out and only a subset of the files got uploaded. Or the permissions on the dev.eclipse.org directories were not correct. Or the certificate we use to upload can't be accessed. Or a variety of reasons that have nothing to do with the correctness of the ECF software. And we don't want to clutter up the real 3.2 directory (and overwrite the good but old stuff that may be there) until we know that we have a complete build.
When does the release build happen?
It's forced. It does not occur on a schedule. You have to use the Hudson web interface to ecf2.osuosl.org to kick off a build. And you have to have an account there. [1]