[opensuse-packaging] auto submit to factory?
Hi, During the conference there was some discussion that some developers would like to have something submit their packages as soon as they succeed for factory - if they are devel package of course. Some projects (like KDE and GNOME that follow release cycles) obviously do not want that, but it still sounds like we should discuss it. We can for sure implement something that does this, but we have several options: - We can have an option in osc that you need to enable, so osc ci will automatically submit too if it's a _link - We can have an attribute in the devel projects that either enables or disables that a script automatically submits factory devel packages with a diff in .changes file - We can do the above, but automatically open a review for the devel project to accept before the package is commited to factory. This has the drawback atm, that no mail notifcation will go out and people tend to ignore these reviews (only the webui will show them if you login). But this is something that needs fixing in hermes anyway. - We can rely purely on mail reminders in case of unsubmitted changes This mail reminder I want to implement most definitely - and with some chance I'll use next week for it, but I would still like to hear if people are interested in auto submit. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Thursday 2011-09-22 10:35, Stephan Kulow wrote:
We can for sure implement something that does this, but we have several options:
- We can have an option in osc that you need to enable, so osc ci will automatically submit too if it's a _link - We can have an attribute in the devel projects that either enables or disables that a script automatically submits factory devel packages with a diff in .changes file
It should be settable per-package at least (per-project is too coarse). You should probably also anticipate that autosubmit may generate an SR storm: user submits from home: to devel:, package succeeds, generates an SR. User notices something is still missing (e.g. no baselibs.conf), submits to devel: again, new SR is created. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am Donnerstag, 22. September 2011 schrieb Jan Engelhardt:
On Thursday 2011-09-22 10:35, Stephan Kulow wrote:
We can for sure implement something that does this, but we have several options:
- We can have an option in osc that you need to enable, so osc ci will
automatically submit too if it's a _link
- We can have an attribute in the devel projects that either enables or
disables that a script automatically submits factory devel packages with a diff in .changes file
It should be settable per-package at least (per-project is too coarse).
You should probably also anticipate that autosubmit may generate an SR storm: user submits from home: to devel:, package succeeds, generates an SR. User notices something is still missing (e.g. no baselibs.conf), submits to devel: again, new SR is created.
SRs are easily superseeded - and I rather have packages resubmitted with fixes than no submits at all Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Thursday 2011-09-22 10:55, Stephan Kulow wrote:
Am Donnerstag, 22. September 2011 schrieb Jan Engelhardt:
On Thursday 2011-09-22 10:35, Stephan Kulow wrote:
We can for sure implement something that does this, but we have several options:
- We can have an option in osc that you need to enable, so osc ci will
automatically submit too if it's a _link
- We can have an attribute in the devel projects that either enables or
disables that a script automatically submits factory devel packages with a diff in .changes file
It should be settable per-package at least (per-project is too coarse).
You should probably also anticipate that autosubmit may generate an SR storm: user submits from home: to devel:, package succeeds, generates an SR. User notices something is still missing (e.g. no baselibs.conf), submits to devel: again, new SR is created.
SRs are easily superseeded - and I rather have packages resubmitted with fixes than no submits at all
Though the state change means that you will get two new mails that don't really tell you anything new (from: "automated sr" to "automated sr (resend)"). Oh well, won't be me who's getting them :) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 09/22/2011 10:35 AM, Stephan Kulow wrote:
Hi,
During the conference there was some discussion that some developers would like to have something submit their packages as soon as they succeed for factory - if they are devel package of course.
This functionality would be appreciated. I still get confused by: osc bco openSUSE:Factory somepackage (checkouts devel project) cd develproject/somepackage FIX osc ci osc results osc sr created request id XXXXX go home... package did not go to Factory. Why? (I know why, but I don't find the answer intuitive nor the process straightforward). -- Duncan Mac-Vicar P. - http://www.suse.com/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am Freitag, 23. September 2011, 09:40:33 schrieb Duncan Mac-Vicar P.:
On 09/22/2011 10:35 AM, Stephan Kulow wrote:
Hi,
During the conference there was some discussion that some developers would like to have something submit their packages as soon as they succeed for factory - if they are devel package of course.
This functionality would be appreciated.
I still get confused by:
osc bco openSUSE:Factory somepackage (checkouts devel project) cd develproject/somepackage FIX osc ci osc results osc sr
created request id XXXXX
go home...
package did not go to Factory. Why? (I know why, but I don't find the answer intuitive nor the process straightforward).
osc rq show XXXXXXXX ? -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de
* V Friday 23. September 2011, 09:44:19 [CEST] Adrian Schröter napsal:
Am Freitag, 23. September 2011, 09:40:33 schrieb Duncan Mac-Vicar P.:
On 09/22/2011 10:35 AM, Stephan Kulow wrote:
Hi,
During the conference there was some discussion that some developers
would like to have something submit their packages as soon as they
succeed for factory - if they are devel package of course.
This functionality would be appreciated.
I still get confused by:
osc bco openSUSE:Factory somepackage
(checkouts devel project)
cd develproject/somepackage
FIX
osc ci
osc results
osc sr
created request id XXXXX
go home...
package did not go to Factory. Why? (I know why, but I don't find the
answer intuitive nor the process straightforward).
osc rq show XXXXXXXX
The problem here is that the submit request goes to the devel project, not to openSUSE:Factory, which was intuitively expected. -- Vita Cizek
On Friday 2011-09-23 11:32, Vitezslav Cizek wrote:
osc bco openSUSE:Factory somepackage (checkouts devel project) cd develproject/somepackage [...] package did not go to Factory. Why? (I know why, but I don't find the answer intuitive nor the process straightforward).
osc rq show XXXXXXXX
The problem here is that the submit request goes to the devel project, not to openSUSE:Factory, which was intuitively expected.
As always, users expect and assume too much. And it's not any different in, for example, the Linux kernel world. There too, if you submit the developers something that is developed against $base, the develprj maintainer that ultimately gets your submission may ask you to rebase on $develprj. So BS automatically diverting the branch command seems like a proper default to me. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Hi,
During the conference there was some discussion that some developers would like to have something submit their packages as soon as they succeed for factory - if they are devel package of course.
Some projects (like KDE and GNOME that follow release cycles) obviously do not want that, but it still sounds like we should discuss it.
We can for sure implement something that does this, but we have several options:
- We can have an option in osc that you need to enable, so osc ci will automatically submit too if it's a _link - We can have an attribute in the devel projects that either enables or disables that a script automatically submits factory devel packages with a diff in .changes file Rather a per package attribute, some packages need to wait for others (I like this idea very much) and while we're on the subject, how about being able to make conditional submissions that wait for others, gstreamer is a good example to follow for this and it would enable
On 09/22/2011 10:35 AM, Stephan Kulow wrote: this automation to be used in gnome and kde. This will benifit everyone and allow more time for getting difficult packages ready like lilypond.
- We can do the above, but automatically open a review for the devel project to accept before the package is commited to factory. This has the drawback atm, that no mail notifcation will go out and people tend to ignore these reviews (only the webui will show them if you login). But this is something that needs fixing in hermes anyway. - We can rely purely on mail reminders in case of unsubmitted changes
This mail reminder I want to implement most definitely - and with some chance I'll use next week for it, but I would still like to hear if people are interested in auto submit.
Greetings, Stephan
-- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Le jeudi 22 septembre 2011, à 10:35 +0200, Stephan Kulow a écrit :
Hi,
During the conference there was some discussion that some developers would like to have something submit their packages as soon as they succeed for factory - if they are devel package of course.
Some projects (like KDE and GNOME that follow release cycles) obviously do not want that, but it still sounds like we should discuss it.
We can for sure implement something that does this, but we have several options:
- We can have an option in osc that you need to enable, so osc ci will automatically submit too if it's a _link - We can have an attribute in the devel projects that either enables or disables that a script automatically submits factory devel packages with a diff in .changes file - We can do the above, but automatically open a review for the devel project to accept before the package is commited to factory. This has the drawback atm, that no mail notifcation will go out and people tend to ignore these reviews (only the webui will show them if you login). But this is something that needs fixing in hermes anyway. - We can rely purely on mail reminders in case of unsubmitted changes
I tend to prefer the options with the attribute for the autosubmit feature. But we do want the mail reminder in all cases, since it will be useful for other things like "your package fails to build for 100 days!!!" I might play with the attribute options next week, unless someone wants to step up already (or another option is preferred) :-) Cheers, Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am Thu, 22 Sep 2011 10:35:54 +0200 schrieb Stephan Kulow <coolo@suse.de>:
Hi,
During the conference there was some discussion that some developers would like to have something submit their packages as soon as they succeed for factory - if they are devel package of course.
Some projects (like KDE and GNOME that follow release cycles) obviously do not want that, but it still sounds like we should discuss it.
We can for sure implement something that does this, but we have several options:
- We can have an option in osc that you need to enable, so osc ci will automatically submit too if it's a _link
Actually having the "forward to FACTORY" option of the webui in "osc request accept" would be a good first step. Or even better "schedule forward to factory", as I personally like to have my packages sit in the develproject for a few days to check if they break something else... -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (8)
-
Adrian Schröter -
Dave Plater -
Duncan Mac-Vicar P. -
Jan Engelhardt -
Stefan Seyfried -
Stephan Kulow -
Vincent Untz -
Vitezslav Cizek