Looking at the things that wxPython Phoenix buildbot creates, what's the role of having build-XXX-pyXX besides having dist-XXX-pyXX? Does the snapshot build (the dist-XXX-pyXX thing) of wxPython Phoenix include all the latest changes/commits to its source code even if the build-XXX-pyXX was not built with all the latest changes/commits to the source code? What's the story behind that? Are build-... and dist-... dependent to each other? Can't really wrap my mind around this.
"Bo�tjan Mejak" wrote:
Looking at the things that wxPython Phoenix buildbot creates, what's the role of having build-XXX-pyXX besides having dist-XXX-pyXX? Does the snapshot build (the dist-XXX-pyXX thing) of wxPython Phoenix include all the latest changes/commits to its source code even if the build-XXX-pyXX was not built with all the latest changes/commits to the source code? What's the story behind that? Are build-... and dist-... dependent to each other?
This is pretty much standard operating procedure for Python projects.
It's the same way setuptools works when you install an add-on module.
Build by-products go in the "build" tree, and when it's time to prepare
a distribution, that goes into the "dist" tree. There's duplication,
but there are often things you build that don't need to be distributed.
···
--
Tim Roberts, timr@probo.com
Providenza & Boekelheide, Inc.
I’m sorry but that doesn’t answer my question.
Reading both messages I think your question is answered:-) .
Werner
···
On 31/07/2013 19:45, Bo�tjan Mejak wrote:
I'm sorry but that doesn't answer my question.
Bo�tjan Mejak wrote:
Looking at the things that wxPython Phoenix buildbot creates, what's the role of having build-XXX-pyXX besides having dist-XXX-pyXX? Does the snapshot build (the dist-XXX-pyXX thing) of wxPython Phoenix include all the latest changes/commits to its source code even if the build-XXX-pyXX was not built with all the latest changes/commits to the source code? What's the story behind that? Are build-... and dist-... dependent to each other? Can't really wrap my mind around this.
The build-* builders in the BuildBot are triggered whenever there is a new commit to the Phoenix or wxWidgets source trees. They update a workspace with the new code from SVN and run only a build.
The dist-* and the build-docs builders are triggered once per day. They clean the workspace and do a full checkout, and then do a full build and the bdist command and upload the results.
···
--
Robin Dunn
Software Craftsman