As Karanbir announced it today, there will be "nightly builds" happening every day, starting from today (the first one being scheduled to start at 8PM UTC). The whole process will be automated and would also start to reflect those new trees. That means that the url to enter for new network install, and yum repositories will need to be using the 'latest' symlink when that one will appear. (Normally full URL would be http://buildlogs.centos.org/centos/7/os/x86_64-latest) As it will be the first time we'll test the end-to-end automation script, we have no real ETA, but we estimate the "time-to-process" between 3 and 4 hours (so content would be available on buildlogs.centos.org around 11 pm UTC, or slightly later)
We've also worked today on the Live Media iso images, so those ones will also be pushed on buildlogs.centos.org (later today, during the "nightly build" process) (see also https://git.centos.org/summary/sig-core!livemedia.git)
As a reminder : * RPM packages are still unsigned * yum config files are still missing (but you can point yum to the mentioned repository) * that tree is still "not production" ready and still needs to be investigated (branding hunt, anyone ?) * we count on you to provide feedback (positive or negative, but feedback requested please) * use #centos-devel (irc.freenode.net), @centos-devel list (here), but also file bugs reports on our bugs tracking system (http://bugs.centos.org) and report those under the "CentOS-7" project
So , (ab)use the tree, break it, fix it (by filing bug reports - patches *welcome* :-) )
On Mon, 16 Jun 2014, Fabian Arrotin wrote:
As Karanbir announced it today, there will be "nightly builds" happening every day, starting from today (the first one being scheduled to start at 8PM UTC). The whole process will be automated and would also start to reflect those new trees. That means that the url to enter for new network install, and yum repositories will need to be using the 'latest' symlink when that one will appear. (Normally full URL would be http://buildlogs.centos.org/centos/7/os/x86_64-latest) As it will be the first time we'll test the end-to-end automation script, we have no real ETA, but we estimate the "time-to-process" between 3 and 4 hours (so content would be available on buildlogs.centos.org around 11 pm UTC, or slightly later)
We've also worked today on the Live Media iso images, so those ones will also be pushed on buildlogs.centos.org (later today, during the "nightly build" process) (see also https://git.centos.org/summary/sig-core!livemedia.git)
As a reminder :
- RPM packages are still unsigned
- yum config files are still missing (but you can point yum to the
mentioned repository)
- that tree is still "not production" ready and still needs to be
investigated (branding hunt, anyone ?)
- we count on you to provide feedback (positive or negative, but
feedback requested please)
- use #centos-devel (irc.freenode.net), @centos-devel list (here), but
also file bugs reports on our bugs tracking system (http://bugs.centos.org) and report those under the "CentOS-7" project
So , (ab)use the tree, break it, fix it (by filing bug reports - patches *welcome* :-) )
What is being "rebuilt" with these nightly rebuilds?
-Connie Sieh
On 16/06/14 20:36, Connie Sieh wrote:
On Mon, 16 Jun 2014, Fabian Arrotin wrote:
As Karanbir announced it today, there will be "nightly builds" happening every day, starting from today (the first one being scheduled to start at 8PM UTC). The whole process will be automated and would also start to reflect those new trees. That means that the url to enter for new network install, and yum repositories will need to be using the 'latest' symlink when that one will appear. (Normally full URL would be http://buildlogs.centos.org/centos/7/os/x86_64-latest) As it will be the first time we'll test the end-to-end automation script, we have no real ETA, but we estimate the "time-to-process" between 3 and 4 hours (so content would be available on buildlogs.centos.org around 11 pm UTC, or slightly later)
We've also worked today on the Live Media iso images, so those ones will also be pushed on buildlogs.centos.org (later today, during the "nightly build" process) (see also https://git.centos.org/summary/sig-core!livemedia.git)
As a reminder :
- RPM packages are still unsigned
- yum config files are still missing (but you can point yum to the
mentioned repository)
- that tree is still "not production" ready and still needs to be
investigated (branding hunt, anyone ?)
- we count on you to provide feedback (positive or negative, but
feedback requested please)
- use #centos-devel (irc.freenode.net), @centos-devel list (here), but
also file bugs reports on our bugs tracking system (http://bugs.centos.org) and report those under the "CentOS-7" project
So , (ab)use the tree, break it, fix it (by filing bug reports - patches *welcome* :-) )
What is being "rebuilt" with these nightly rebuilds?
-Connie Sieh _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel Received: from lithium.arrfab.net (unknown [172.19.5.1]) by radium.arrfab.net (Postfix) with ESMTP id 14B9E39C646 for fabian.arrotin@arrfab.net; Mon, 16 Jun 2014 20:36:27 +0200 Received: from mail.centos.org (mail.centos.org [72.26.200.202]) by lithium.arrfab.net (8.13.8/8.13.8) with ESMTP id s5GIaNpP017948 for fabian.arrotin@arrfab.net; Mon, 16 Jun 2014 20:36:24 +0200 Received: from mail.centos.org (voxeldev.centos.org [127.0.0.1]) by mail.centos.org (Postfix) with ESMTP id A67F5817EBA; Mon, 16 Jun 2014 18:36:23 +0000 Received: from ex-smtp.fnal.gov (mail04v-smtp02.fnal.gov [131.225.199.27]) by mail.centos.org (Postfix) with ESMTP id 1525467B1A for centos-devel@centos.org; Mon, 16 Jun 2014 18:36:21 +0000 Received: from dhcp-131-225-22-38.dhcp.fnal.gov (131.225.22.38) by ex-smtp.fnal.gov (131.225.199.27) with Microsoft SMTP Server (TLS) id 14.3.174.1; Mon, 16 Jun 2014 13:36:24 -0500 Subject: Re: [CentOS-devel] CentOS 7 "nightly builds" and Live Media iso images From: =indows-1252?Q?Connie_Sieh?= csieh@fnal.gov To: =indows-1252?Q?The_CentOS_developers_mailing_list.? centos-devel@centos.org Date: Mon, 16 Jun 2014 18:36:19 +0000 Mime-Version: 1.0 Content-Type: text/plain; charset=ndows-1252 Content-Transfer-Encoding: quoted-printable In-Reply-To: 539F3687.2070903@arrfab.net References: 539F3687.2070903@arrfab.net X-Mailer: Zarafa 6.40.7-26119 Sender: =indows-1252?Q?csieh@fnal.gov?= centos-devel-bounces@centos.org Reply-To: =indows-1252?Q?The_CentOS_developers_mailing_list.? centos-devel@centos.org Precedence: list List-Id: "The CentOS developers mailing list." <centos-devel.centos.org> List-Unsubscribe: http://lists.centos.org/mailman/listinfo/centos-devel, mailto:centos-devel-request@centos.org?subject=subscribe List-Archive: http://lists.centos.org/pipermail/centos-devel List-Post: mailto:centos-devel@centos.org List-Help: mailto:centos-devel-request@centos.org?subject=lp List-Subscribe: http://lists.centos.org/mailman/listinfo/centos-devel, mailto:centos-devel-request@centos.org?subject=bscribe X-Spam-Status: No X-Beenthere: centos-devel@centos.org X-Mailman-Version: 2.1.9 X-Original-To: centos-devel@centos.org X-X-Sender: csieh@dhcp-131-225-22-38.dhcp.fnal.gov X-Arrfab-Bluewall-Mailscanner-Information: Please contact the ISP for more information X-Arrfab-Bluewall-Mailscanner-Id: s5GIaNpP017948 X-Arrfab-Bluewall-Mailscanner: Found to be clean X-Arrfab-Bluewall-Mailscanner-From: centos-devel-bounces@centos.org Message-Id: alpine.LRH.2.02.1406161334570.21751@dhcp-131-225-22-38.dhcp.fnal.gov
On Mon, 16 Jun 2014, Fabian Arrotin wrote:
As Karanbir announced it today, there will be "nightly builds" happening every day, starting from today (the first one being scheduled to start at 8PM UTC). The whole process will be automated and would also start to reflect those new trees. That means that the url to enter for new network install, and yum repositories will need to be using the 'latest' symlink when that one will appear. (Normally full URL would be http://buildlogs.centos.org/centos/7/os/x86_64-latest) As it will be the first time we'll test the end-to-end automation script, we have no real ETA, but we estimate the "time-to-process" between 3 and 4 hours (so content would be available on buildlogs.centos.org around 11 pm UTC, or slightly later)
We've also worked today on the Live Media iso images, so those ones will also be pushed on buildlogs.centos.org (later today, during the "nightly build" process) (see also https://git.centos.org/summary/sig-core!livemedia.git)
As a reminder :
- RPM packages are still unsigned
- yum config files are still missing (but you can point yum to the
mentioned repository)
- that tree is still "not production" ready and still needs to be
investigated (branding hunt, anyone ?)
- we count on you to provide feedback (positive or negative, but
feedback requested please)
- use #centos-devel (irc.freenode.net), @centos-devel list (here), but
also file bugs reports on our bugs tracking system (http://bugs.centos.org) and report those under the "CentOS-7" project
So , (ab)use the tree, break it, fix it (by filing bug reports - patches *welcome* :-) )
What is being "rebuilt" with these nightly rebuilds?
-Connie Sieh
Packages reported by community (on bugs.centos.org) that need to be modified: * for CentOS/Branding issue or * for functional issue (for example, http://bugs.centos.org/view.php?id=7172 -> anaconda modification, tagged as .centos and patched through git.centos.org)
Cheers,
Hi
On 06/16/2014 07:25 PM, Fabian Arrotin wrote:
As Karanbir announced it today, there will be "nightly builds" happening every day, starting from today (the first one being scheduled to start at 8PM UTC).
skipping todays build, lots of iterations around process and automation instead. Should have builds tomorrow.
Also, a gentle nudge, we will start rolling in patches for branding from tomorrow AM. So start sending those through, we've only had a few so far at bugs.centos.org ( which is where they should all end up at ).
- KB
On 06/16/2014 08:25 PM, Fabian Arrotin wrote:
As Karanbir announced it today, there will be "nightly builds" happening every day, starting from today (the first one being scheduled to start at 8PM UTC). The whole process will be automated and would also start to reflect those new trees. That means that the url to enter for new network install, and yum repositories will need to be using the 'latest' symlink when that one will appear. (Normally full URL would be http://buildlogs.centos.org/centos/7/os/x86_64-latest) As it will be the first time we'll test the end-to-end automation script, we have no real ETA, but we estimate the "time-to-process" between 3 and 4 hours (so content would be available on buildlogs.centos.org around 11 pm UTC, or slightly later)
We've also worked today on the Live Media iso images, so those ones will also be pushed on buildlogs.centos.org (later today, during the "nightly build" process) (see also https://git.centos.org/summary/sig-core!livemedia.git)
As a reminder :
- RPM packages are still unsigned
- yum config files are still missing (but you can point yum to the
mentioned repository)
- that tree is still "not production" ready and still needs to be
investigated (branding hunt, anyone ?)
- we count on you to provide feedback (positive or negative, but
feedback requested please)
- use #centos-devel (irc.freenode.net), @centos-devel list (here), but
also file bugs reports on our bugs tracking system (http://bugs.centos.org) and report those under the "CentOS-7" project
So , (ab)use the tree, break it, fix it (by filing bug reports - patches *welcome* :-) )
Here is nice Youtube tutorial for installing from RC build, but it is same with Alpha version except the URL: https://www.youtube.com/watch?v=PfL86GXuc3U
On 06/16/2014 08:25 PM, Fabian Arrotin wrote:
As Karanbir announced it today, there will be "nightly builds" happening every day, starting from today (the first one being scheduled to start at 8PM UTC). The whole process will be automated and would also start to reflect those new trees. That means that the url to enter for new network install, and yum repositories will need to be using the 'latest' symlink when that one will appear. (Normally full URL would be http://buildlogs.centos.org/centos/7/os/x86_64-latest)
It would be nice to have "-latest" URL ready for announcement purposes, so others know it will exist.
On 06/17/2014 02:10 PM, Ljubomir Ljubojevic wrote:
On 06/16/2014 08:25 PM, Fabian Arrotin wrote:
As Karanbir announced it today, there will be "nightly builds" happening every day, starting from today (the first one being scheduled to start at 8PM UTC). The whole process will be automated and would also start to reflect those new trees. That means that the url to enter for new network install, and yum repositories will need to be using the 'latest' symlink when that one will appear. (Normally full URL would be http://buildlogs.centos.org/centos/7/os/x86_64-latest)
It would be nice to have "-latest" URL ready for announcement purposes, so others know it will exist.
latest is something we want to do - its been spokean about as well, but remember we are replacing rpms without a bump in Epoc:Version-Release, so there is no way for yum etc to know that something has changed under it.
hence, the only real testing path is to reinstall and re-evaluate newer releases.
- KB
On 06/17/2014 08:55 AM, Karanbir Singh wrote:
On 06/17/2014 02:10 PM, Ljubomir Ljubojevic wrote:
On 06/16/2014 08:25 PM, Fabian Arrotin wrote:
As Karanbir announced it today, there will be "nightly builds" happening every day, starting from today (the first one being scheduled to start at 8PM UTC). The whole process will be automated and would also start to reflect those new trees. That means that the url to enter for new network install, and yum repositories will need to be using the 'latest' symlink when that one will appear. (Normally full URL would be http://buildlogs.centos.org/centos/7/os/x86_64-latest)
It would be nice to have "-latest" URL ready for announcement purposes, so others know it will exist.
latest is something we want to do - its been spokean about as well, but remember we are replacing rpms without a bump in Epoc:Version-Release, so there is no way for yum etc to know that something has changed under it.
hence, the only real testing path is to reinstall and re-evaluate newer releases.
- KB
I want to point out here for those who think this might look chaotic ... this process is very similar to what we have done only with our private QA team in the past.
We would do these temporary tree pushes, etc. to the QA team and they would test, find issues, post the issues to bugs or the QA mailing list and we would fix. We have opened this up totally to the public to make the test group larger and hopefully find and fix issues faster, etc.
However, the packages released here are going to do things LIKE ... be replaced with different builds that are newer with exactly the same EVR strings, etc. We may do other crazy things too.
The bottom line is that these packages should ABSOLUTELY NOT be used on anything that is even slightly important .. although, you may be able to point to a newer repo and do something like "yum distro-sync full" to get all the new packages.
That said, be careful with these packages and don't keep/use them except for this testing. Once we get a stabilized tree and that is released, then we can use that for real production things :)
On 06/17/2014 04:24 PM, Johnny Hughes wrote:
On 06/17/2014 08:55 AM, Karanbir Singh wrote:
On 06/17/2014 02:10 PM, Ljubomir Ljubojevic wrote:
On 06/16/2014 08:25 PM, Fabian Arrotin wrote:
As Karanbir announced it today, there will be "nightly builds" happening every day, starting from today (the first one being scheduled to start at 8PM UTC). The whole process will be automated and would also start to reflect those new trees. That means that the url to enter for new network install, and yum repositories will need to be using the 'latest' symlink when that one will appear. (Normally full URL would be http://buildlogs.centos.org/centos/7/os/x86_64-latest)
It would be nice to have "-latest" URL ready for announcement purposes, so others know it will exist.
latest is something we want to do - its been spokean about as well, but remember we are replacing rpms without a bump in Epoc:Version-Release, so there is no way for yum etc to know that something has changed under it.
hence, the only real testing path is to reinstall and re-evaluate newer releases.
- KB
I want to point out here for those who think this might look chaotic ... this process is very similar to what we have done only with our private QA team in the past.
We would do these temporary tree pushes, etc. to the QA team and they would test, find issues, post the issues to bugs or the QA mailing list and we would fix. We have opened this up totally to the public to make the test group larger and hopefully find and fix issues faster, etc.
However, the packages released here are going to do things LIKE ... be replaced with different builds that are newer with exactly the same EVR strings, etc. We may do other crazy things too.
The bottom line is that these packages should ABSOLUTELY NOT be used on anything that is even slightly important .. although, you may be able to point to a newer repo and do something like "yum distro-sync full" to get all the new packages.
That said, be careful with these packages and don't keep/use them except for this testing. Once we get a stabilized tree and that is released, then we can use that for real production things :)
That is understood, at least by me.
The reason I asked for this was that Youtube video emerged for people to test C7 and Fabian posted message about "latest", so since I already posted his message on Facebook and Google+ as a comment to Youtube Install video, it would be nice to have (by tomorrow?) "latest" pointing to last/only build so people do not start asking too many questions why it is missing.
And I will make sure to warn them about non-production, even tho I do not think that will be the problem since those who want to try it only want to look at it.
On 06/17/2014 05:57 PM, Ljubomir Ljubojevic wrote:
On 06/17/2014 04:24 PM, Johnny Hughes wrote:
On 06/17/2014 08:55 AM, Karanbir Singh wrote:
On 06/17/2014 02:10 PM, Ljubomir Ljubojevic wrote:
On 06/16/2014 08:25 PM, Fabian Arrotin wrote:
As Karanbir announced it today, there will be "nightly builds" happening every day, starting from today (the first one being scheduled to start at 8PM UTC). The whole process will be automated and would also start to reflect those new trees. That means that the url to enter for new network install, and yum repositories will need to be using the 'latest' symlink when that one will appear. (Normally full URL would be http://buildlogs.centos.org/centos/7/os/x86_64-latest)
It would be nice to have "-latest" URL ready for announcement purposes, so others know it will exist.
latest is something we want to do - its been spokean about as well, but remember we are replacing rpms without a bump in Epoc:Version-Release, so there is no way for yum etc to know that something has changed under it.
hence, the only real testing path is to reinstall and re-evaluate newer releases.
- KB
I want to point out here for those who think this might look chaotic ... this process is very similar to what we have done only with our private QA team in the past.
We would do these temporary tree pushes, etc. to the QA team and they would test, find issues, post the issues to bugs or the QA mailing list and we would fix. We have opened this up totally to the public to make the test group larger and hopefully find and fix issues faster, etc.
However, the packages released here are going to do things LIKE ... be replaced with different builds that are newer with exactly the same EVR strings, etc. We may do other crazy things too.
The bottom line is that these packages should ABSOLUTELY NOT be used on anything that is even slightly important .. although, you may be able to point to a newer repo and do something like "yum distro-sync full" to get all the new packages.
That said, be careful with these packages and don't keep/use them except for this testing. Once we get a stabilized tree and that is released, then we can use that for real production things :)
That is understood, at least by me.
The reason I asked for this was that Youtube video emerged for people to test C7 and Fabian posted message about "latest", so since I already posted his message on Facebook and Google+ as a comment to Youtube Install video, it would be nice to have (by tomorrow?) "latest" pointing to last/only build so people do not start asking too many questions why it is missing.
And I will make sure to warn them about non-production, even tho I do not think that will be the problem since those who want to try it only want to look at it.
might also want to make a note about distro-sync, that helps in this sort of a setup, massively.
and also make sure people expire their yum repo configs in time
On 06/17/2014 07:01 PM, Karanbir Singh wrote:
The bottom line is that these packages should ABSOLUTELY NOT be used on
anything that is even slightly important .. although, you may be able to point to a newer repo and do something like "yum distro-sync full" to get all the new packages.
That said, be careful with these packages and don't keep/use them except for this testing. Once we get a stabilized tree and that is released, then we can use that for real production things:)
Noted. I plan to just copy Johnny's text:
"These packages should ABSOLUTELY NOT be used on anything that is even slightly important .. although, you may be able to point to a newer repo and do something like "yum distro-sync full" to get all the new packages.
That said, be careful with these packages and don't keep/use them except for this testing. Once we get a stabilized tree and that is released, then we can use that for real production things. Johnny Hughes"
On 06/17/2014 08:01 PM, Karanbir Singh wrote:
[...]
might also want to make a note about distro-sync, that helps in this sort of a setup, massively.
and also make sure people expire their yum repo configs in time
In this context, has anyone tested a lower value for metadata_expire ( the default is 6h, according to the docs ) ?
On Mon, Jun 16, 2014 at 08:25:11PM +0200, Fabian Arrotin wrote:
As Karanbir announced it today, there will be "nightly builds" happening every day, starting from today (the first one being scheduled to start at 8PM UTC). The whole process will be automated and would also start to reflect those new trees. That means that the url to enter for new network install, and yum repositories will need to be using the 'latest' symlink when that one will appear. (Normally full URL would be http://buildlogs.centos.org/centos/7/os/x86_64-latest) As it will be the first time we'll test the end-to-end automation script, we have no real ETA, but we estimate the "time-to-process" between 3 and 4 hours (so content would be available on buildlogs.centos.org around 11 pm UTC, or slightly later)
We've also worked today on the Live Media iso images, so those ones will also be pushed on buildlogs.centos.org (later today, during the "nightly build" process) (see also https://git.centos.org/summary/sig-core!livemedia.git)
As a reminder :
- RPM packages are still unsigned
- yum config files are still missing (but you can point yum to the
mentioned repository)
There are only a few things I know about using yum, and how to point it to a repo for which I don't have a .repo config file is not one of them. Can someone drop a hint on how to use yum with http://buildlogs.centos.org/centos/7/os/x86_64-latest ???
Thanks!
On 06/18/2014 11:59 PM, Fred Smith wrote:
On Mon, Jun 16, 2014 at 08:25:11PM +0200, Fabian Arrotin wrote:
As Karanbir announced it today, there will be "nightly builds" happening every day, starting from today (the first one being scheduled to start at 8PM UTC). The whole process will be automated and would also start to reflect those new trees. That means that the url to enter for new network install, and yum repositories will need to be using the 'latest' symlink when that one will appear. (Normally full URL would be http://buildlogs.centos.org/centos/7/os/x86_64-latest) As it will be the first time we'll test the end-to-end automation script, we have no real ETA, but we estimate the "time-to-process" between 3 and 4 hours (so content would be available on buildlogs.centos.org around 11 pm UTC, or slightly later)
We've also worked today on the Live Media iso images, so those ones will also be pushed on buildlogs.centos.org (later today, during the "nightly build" process) (see also https://git.centos.org/summary/sig-core!livemedia.git)
As a reminder :
- RPM packages are still unsigned
- yum config files are still missing (but you can point yum to the
mentioned repository)
There are only a few things I know about using yum, and how to point it to a repo for which I don't have a .repo config file is not one of them. Can someone drop a hint on how to use yum with http://buildlogs.centos.org/centos/7/os/x86_64-latest ???
Thanks!
drop this into your /etc/yum.repos.d/CentOS-QA.repo
[qa-nightly] name=qa-nightly baseurl=http://buildlogs.centos.org/centos/7/os/x86_64-latest enabled=1 gpgcheck=0
On Thu, Jun 19, 2014 at 12:10:40AM +0100, Karanbir Singh wrote:
On 06/18/2014 11:59 PM, Fred Smith wrote:
On Mon, Jun 16, 2014 at 08:25:11PM +0200, Fabian Arrotin wrote:
As Karanbir announced it today, there will be "nightly builds" happening every day, starting from today (the first one being scheduled to start at 8PM UTC). The whole process will be automated and would also start to reflect those new trees. That means that the url to enter for new network install, and yum repositories will need to be using the 'latest' symlink when that one will appear. (Normally full URL would be http://buildlogs.centos.org/centos/7/os/x86_64-latest) As it will be the first time we'll test the end-to-end automation script, we have no real ETA, but we estimate the "time-to-process" between 3 and 4 hours (so content would be available on buildlogs.centos.org around 11 pm UTC, or slightly later)
We've also worked today on the Live Media iso images, so those ones will also be pushed on buildlogs.centos.org (later today, during the "nightly build" process) (see also https://git.centos.org/summary/sig-core!livemedia.git)
As a reminder :
- RPM packages are still unsigned
- yum config files are still missing (but you can point yum to the
mentioned repository)
There are only a few things I know about using yum, and how to point it to a repo for which I don't have a .repo config file is not one of them. Can someone drop a hint on how to use yum with http://buildlogs.centos.org/centos/7/os/x86_64-latest ???
Thanks!
drop this into your /etc/yum.repos.d/CentOS-QA.repo
[qa-nightly] name=qa-nightly baseurl=http://buildlogs.centos.org/centos/7/os/x86_64-latest enabled=1 gpgcheck=0
Thanks!
-
Connie Sieh -
Fabian Arrotin -
Fred Smith -
Johnny Hughes -
Karanbir Singh -
Ljubomir Ljubojevic -
Manuel Wolfshant