Bug 122 - Daily/Weekly Build in ISO
Summary: Daily/Weekly Build in ISO
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: Release (media or process) (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Anne Nicolas
QA Contact:
URL:
Whiteboard:
Keywords:
: 4369 4662 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-02-20 06:04 CET by Clodelio Delfino
Modified: 2020-08-22 18:31 CEST (History)
10 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Clodelio Delfino 2011-02-20 06:04:48 CET
Description of problem:
Is there a possibility to have Mageia a daily or weekly build that can be downloaded in ISO?

Version-Release number of selected component (if applicable):


How reproducible:
Not Applicable

Steps to Reproduce:
1. Setup a download link with daily or weekly ISO build.
2. For example:
http://weekly.mageia.org/iso/02202011-mageia-dvd_build.iso
http://weekly.mageia.org/iso/02202011-mageia-dvd_source.iso

This way, people who downloaded the alpha version which doesn't have internet connection can rebuild/fix their current alpha release setup with updated packages.

I think this is similar to "rawhide" in fedora which they have nightly build I believe.

Reproducible: 

Steps to Reproduce:
D Morgan 2011-02-20 17:03:15 CET

CC: (none) => ennael1

Comment 1 Frank Griffin 2011-02-20 17:16:12 CET
If they don't have nternet, how are they going to get weekly ISOs ?

CC: (none) => ftg

Ahmad Samir 2011-02-22 01:50:00 CET

Assignee: bugsquad => ennael1

Comment 2 Clodelio Delfino 2011-02-22 06:13:02 CET
Actually, the purpose of this is that those packages that were already fixed from the weekly ISO and apply it on their system.

Scenario:
Mageia1_office(with Internet) = daily update from development is no problem.
Mageia2_home(no Internet) = Option1: copy all packages from /var/pkg or similar path then transfer to home pc or Option2: download the weekly ISO build in office and update home pc installation.

Just a suggestion as I've seen ISO in Slackware and Fedora such as these...
Comment 3 Anne Nicolas 2011-02-22 10:12:01 CET
Your use case is not the right one I guess as I think those people will rather use regular updates. If you do it on a daily base, it's not that big.

Anyway we plan also to have daily/weekly isos done for test purpose to avoid issues during official releases. This is not yet done. Stay tuned
Comment 4 Clodelio Delfino 2011-02-23 05:45:42 CET
Thanks a lot Anne...
Thierry Vignaud 2011-03-03 18:05:46 CET

Assignee: ennael1 => bugsquad
CC: (none) => thierry.vignaud
Component: Installation => Release (media, process)

D Morgan 2011-04-07 20:58:09 CEST

CC: (none) => dmorganec
Assignee: bugsquad => ennael1

Comment 5 Marja Van Waes 2011-10-05 17:38:34 CEST
@ Ennael

Any news?

CC: (none) => marja11

Manuel Hiebel 2011-11-17 15:05:51 CET

CC: (none) => sysadmin-bugs

Comment 6 Romain d'Alverny 2012-02-01 09:04:54 CET
*** Bug 4369 has been marked as a duplicate of this bug. ***

CC: (none) => junk_no_spam

Comment 7 Romain d'Alverny 2012-02-01 09:39:18 CET
Summarizing:
* we have all the tools we need for that [1],
* a daily set of ISOs takes about 20GB of storage,
* we don't have enough bandwidth yet to provide such daily sets of ISOs - ideally we need a dedicated host to build and publish the ISOs (we won't use regular mirrors for that).

So, contributions welcome for:
* a dedicated host with enough storage (easy) and bandwidth;
* a working build chain;
* isocheck improvements (finish it, add more specific/config tests, publish reports);
* more automatic test tools on ISOs;
* growing the QA team (having a daily set is one thing, applying tests on it and acting on those is another).

I emphasize that just in case: nightlies/dailies/weeklies/whatever will _not_ be for everyday users (and should be configured as such with appropriate warnings along the whole chain). Those builds are going to be really interesting only for:
* the automatic build/install/post-install test reports we will be able to set up later;
* very occasional testing by QA or developers.

--
[1] that is:
 * bcd to build ISOs (http://svnweb.mageia.org/soft/build_system/bcd/)
 * isocheck to check these ISOs for basic stuff (http://svnweb.mageia.org/soft/isocheck/)
 * it needs a script to chain them (trigger the build/check/move/notify steps)
Comment 8 Manuel Hiebel 2012-02-23 22:03:09 CET
*** Bug 4662 has been marked as a duplicate of this bug. ***

CC: (none) => kristoffer.grundstrom1983

Bit Twister 2012-02-23 23:04:21 CET

CC: junk_no_spam => (none)

Comment 9 Marja Van Waes 2012-05-26 13:06:58 CEST
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 10 Dave Hodgins 2012-05-28 03:07:50 CEST
This is an enhancement request, so should remain assigned to cauldron.

Keywords: NEEDINFO => (none)
CC: (none) => davidwhodgins

Comment 11 Kristoffer Grundström 2015-11-30 12:44:05 CET
BUMP!

What has happened to this?
Is it still possible?
Comment 12 Mauricio Andrés Bustamante Viveros 2018-03-16 08:16:57 CET
Reading this bug, I see that was intended to mageia alpha testing iso update

The end user that used or use the alpha, beta iso, is an QA user
Giving weekly, or daily update ISO has no sense to me, because end users using alpha or beta ISOs, must upgrade with official ISO to have support
Weekly or daily updates overloads the MGA team, in infraestructure, QA testing

In other (more recent) update enhancement, I said the following: publish an update ISO with all the core updates every six month, to ensure the end user can upgrade the system (bug fixing, because a non connected device is no risk at all) QA is not overloaded

May be this is possible in the measure that core updates published ISOs preserves order, but avoiding the end user use the more recent ISO without the past updates already installed because makes the mageia system weak and unstable

CC: (none) => neoser10

Comment 13 Aurelien Oudelet 2020-08-22 18:31:43 CEST
Hi,
What about this old bug, no longer commented from 2+ years?

Suggestion:
Today, we have a netinstall ISO.
What about a Debian-like release of Classic Installer ISO, like having Mageia 7.1, 7.2 or 7.3 from a snapshot of our stable repos?

I don't know how ISO are created but this could be doable?

CC: (none) => ouaurelien


Note You need to log in before you can comment on or make changes to this bug.