7.2 builds snaps server full ?
-
No new full builds since: pfSense-Full-Update-1.2.3-20091106-2354
-
I think that the builder system won't start a new build now unless there has been a commit to the repo for that branch. So if there have been no changes, a build would just be unnecessary. This is a recent change.
-
So this has been "synced" but not commited?
http://redmine.pfsense.org/issues/show/132
-
Not sure. That was committed into the tools repo, not the repo for 1.2.x, so it might not work quite the same way.
-
Does this change in the tools repo show up on the next build?
Back to topic … there is only a new 4G image online, no 2G ???
-
Each time a builder run is completed, it's just for one image size. The next run will be for a different size. We tried to make it produce all sizes on each run, but there were some complications that led to problems.
I haven't looked at the code for the build cycle lately so I'm not sure if the tools repo commits are factored in or not. Any commit there will show up in the next build if it's relevant to that platform/branch, though.
-
This is what Chris said in lists some time ago:
On Thu, Aug 6, 2009 at 10:24 PM, Evgeny Yurchenko evg.yurch@rogers.comwrote:
So devlopers work hard from time to time commiting their work (kind of
moving it towards snapshots). And at some point somebody decides "ok, it's
time to draw a line" and creates the next snapshot which becomes available
to public. Something like this?Snapshots build non-stop (with the exceptions of build server
adds/moves/changes/problems) in a loop, it's all automatic. For
packages, those get updated within 5 minutes of the commit and are
then immediately available on all versions where the package was
updated. I suspect Scott had forgotten this was a package commit when
he said to use a snapshot earlier, as package changes don't require
base system updates generally./evg.yurch@rogers.comSo, tools repo (packages) are not related to pfSense repo. (?)
-
That was before the changes I am talking about.
The tools repo is used to build FreeBSD, the system base packages, libraries, etc, and then the pfSense repo is added to this to form the various distributions. The packages repo is separate and not tied into this process.
-
Each time a builder run is completed, it's just for one image size. The next run will be for a different size. We tried to make it produce all sizes on each run, but there were some complications that led to problems
So it looks we have to wait one week or even longer to get for example the new 2gb nanobsd image. :(
Is it possible to make a different size build also when no change has been made on that day? -
Each time a builder run is completed, it's just for one image size. The next run will be for a different size. We tried to make it produce all sizes on each run, but there were some complications that led to problems
So it looks we have to wait one week or even longer to get for example the new 2gb nanobsd image. :(
Is it possible to make a different size build also when no change has been made on that day?I hope that's not true, but as long as the 2G update is the next one built, that should be ok. ;D
