Mailinglist Archive: opensuse-packaging (140 mails)

< Previous Next >
Re: [opensuse-packaging] Automatic submission of changes to Factory
On Mon, Jan 30, 2012 at 3:54 AM, Vincent Untz <vuntz@xxxxxxxxxxxx> wrote:
Hi all,

For a while, we've had the issue of packages with changes in devel
projects not always being submitted to Factory. At the last openSUSE
Conference, it appeared that not everyone was aware that this had to be
manually done, and one solution that was discussed involved automatic

After some push from coolo, I finished a script I started working on a
while ago, and we now have obs-autosubmit:

To put it simply, it submits unsubmitted changes to Factory. It tries
hard to be clever, for instance:

 - it only submits changes if the .changes entry is different
 - it doesn't submit a change that is already submitted
 - it doesn't submit a change that was declined/superseded

Coupled with the factory-auto checks, this means that changed packages
that don't build won't get through. (This has one issue, though: if a
package failed to build because of another package being broken and got
automatically submitted, it won't be automatically submitted again when
the other package gets fixed)

However, automatic submission is something that some people might not
want. For instance, in GNOME:Factory, that'd be insane as we generally
need to push several packages together and we do this after testing G:F.
Therefore, there's a way to disable this automatic submission for either
a whole project, or specific packages. Right now, this way is a
hardcoded list, but we'll likely use attributes in the future.

If you want to *not* have automatic submission for your project or your
package, please tell me!

For reference, a test run on Friday gave this result:

 - 375 packages to be automatically submitted.
 - 179 packages with changes, but no difference in .changes.
 - 73 packages with changes, already submitted in the past but
 - 78 packages with changes, already submitted.
 - 5 packages with changes, but autosubmit disabled.



I think there should also be a "minimal stable time" requirement.

For instance if the changes file was updated and if NO changes have
occurred in 2 weeks, it is a candidate for auto-submission.

That would give the maintainer a couple weeks to test things before
they are auto-submitted.

4-weeks might be even better considering this mechanism is supposed to
be a fallback solution, not the primary solution.

To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups