diff options
Diffstat (limited to 'zarb-ml/mageia-sysadm/2011-September/003963.html')
| -rw-r--r-- | zarb-ml/mageia-sysadm/2011-September/003963.html | 112 |
1 files changed, 112 insertions, 0 deletions
diff --git a/zarb-ml/mageia-sysadm/2011-September/003963.html b/zarb-ml/mageia-sysadm/2011-September/003963.html new file mode 100644 index 000000000..c8fc52142 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2011-September/003963.html @@ -0,0 +1,112 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-sysadm] Using SQL database for youri + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Using%20SQL%20database%20for%20youri&In-Reply-To=%3C20110921142940.GL21938%40mars-attacks.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="003953.html"> + <LINK REL="Next" HREF="003964.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-sysadm] Using SQL database for youri</H1> + <B>nicolas vigier</B> + <A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Using%20SQL%20database%20for%20youri&In-Reply-To=%3C20110921142940.GL21938%40mars-attacks.org%3E" + TITLE="[Mageia-sysadm] Using SQL database for youri">boklm at mars-attacks.org + </A><BR> + <I>Wed Sep 21 16:29:40 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="003953.html">[Mageia-sysadm] [changelog] cauldron core/release mplayer-1.0-1.rc4.0.r32713.8.mga2 +</A></li> + <LI>Next message: <A HREF="003964.html">[Mageia-sysadm] Using SQL database for youri +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#3963">[ date ]</a> + <a href="thread.html#3963">[ thread ]</a> + <a href="subject.html#3963">[ subject ]</a> + <a href="author.html#3963">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hello, + +While looking at enabling submits to backports_testing repository on +Mageia 1, I noticed that we have the following lines in mgarepo.conf on +valstar (config file used by create-srpm, for package submit) : + +[submit 1] +target = <%= sched_home_dir %>/repsys/srpms +allowed = <A HREF="svn://svn.<%=">svn://svn.<%=</A> domain %>/svn/packages/updates/1 +rpm-macros = global 1 + +It means all submit to mageia 1 should be done with a URL in updates/1 +svn directory. And this is a problem for backports as they are usually +done using the package from cauldron directory. Unfortunatly, it's only +possible to set allowed URLs per release, not per repository, so we +cannot allow updates/1 directory for updates_testing and cauldron +directory for backports. + +We also have a problem with markrelease commits always done on the +cauldron directory, even for mageia 1 updates. Youri always run +markrelease on the cauldron directory because it doesn't know the URL +that was used for the submit, this URL is only known by create-srpm +which only uses it to generate the src.rpm, before sending the src.rpm +to youri. + +So I think we could do this to fix those problems : +1) setup a SQL database (with postgres on alamut), with the following columns : + sha1 of src.rpm (as index), URL used for submit, repository and later + other infos about build +2) change create-srpm to save the URL of the submit in the database + before giving the src.rpm to youri +3) add a new check module in youri to check that the URL used is correct +4) update the youri Action/Markrelease.pm module to do the markerelease + on the URL from the database, instead of the cauldron directory + +All the infos about builds are currently stored by youri in the +filesystem. I think that later we can store them in the database. I +think it would be better because : +- we can keep history about previous builds longer. I think that + currently we only keep history from the last 48h because things become + slow with too many files to parse. +- it's easier to add new infos in the database (we only need to add a + new column in the database) +- we can use SQL query to search infos about builds (it can be useful + if we want to improve build system web page, to add more infos) +- build nodes can add infos in the database directly (for instance + adding the URL of current build logs, if we want to provide access to + the logs before the build is finished) + +What do you think about this ? + +</PRE> + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="003953.html">[Mageia-sysadm] [changelog] cauldron core/release mplayer-1.0-1.rc4.0.r32713.8.mga2 +</A></li> + <LI>Next message: <A HREF="003964.html">[Mageia-sysadm] Using SQL database for youri +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#3963">[ date ]</a> + <a href="thread.html#3963">[ thread ]</a> + <a href="subject.html#3963">[ subject ]</a> + <a href="author.html#3963">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-sysadm">More information about the Mageia-sysadm +mailing list</a><br> +</body></html> |