Ticket #1695 (closed support-request: worksforme)

Opened 2 years ago

Last modified 2 years ago

Entering the wrong URL for custom builds shouldn't change slave status

Reported by: pitrou Owned by:
Priority: minor Milestone: undecided
Version: 0.8.2 Keywords:
Cc: pitrou

Description

At python.org, we sometimes get such builds:  http://www.python.org/dev/buildbot/all/builders/i386%20Ubuntu%203.x/builds/490

As far as I know, this is because some web bots or crawlers sometimes push the "force build" button without any branch info, triggering a new build which fails immediately on SVN. It happens irregularly but is quite annoying when it happens, since lots of builders then become in the "mauve" state (what's the name for it?). It would be nice if entering the wrong SVN branch or URL when filling these forms didn't produce such a status change.

Change History

comment:1 follow-up: ↓ 2 Changed 2 years ago by dustin

  • Status changed from new to closed
  • Type changed from undecided to support-request
  • Resolution set to worksforme

I think that the appropriate solution is to put some authentication on the force-build button, rather than try to detect the problem after the fact. How do you detect a "wrong" SVN branch? Matching it against spam databases? :)

Recent versions of Buildbot do support authenticating all web-based actions.

comment:2 in reply to: ↑ 1 Changed 2 years ago by pitrou

Replying to dustin:

I think that the appropriate solution is to put some authentication on the force-build button, rather than try to detect the problem after the fact. How do you detect a "wrong" SVN branch?

The fact that the SVN step fails would be good enough for us, IMO.

Recent versions of Buildbot do support authenticating all web-based actions.

Sure, but we don't have site-wide authentication and we don't want people to enter yet another login just to push the build button.

comment:3 follow-up: ↓ 4 Changed 2 years ago by dustin

We use a single username/password for the metabuildbot, which is well-known to the devs who care to use the force system. That may be an option.

The SVN step can fail for a number of reasons - you don't want them all to be considered "OK", do you?

comment:4 in reply to: ↑ 3 Changed 2 years ago by pitrou

Replying to dustin:

The SVN step can fail for a number of reasons - you don't want them all to be considered "OK", do you?

Indeed. However, when it's a blank branch entry (as seems to be the case here), perhaps it should be detected early?

comment:5 follow-up: ↓ 6 Changed 2 years ago by dustin

You might want to consider a ChangeFilter that filters out such changes. A blank 'branch' is valid for lots of Buildbot configs.

comment:6 in reply to: ↑ 5 Changed 2 years ago by pitrou

Replying to dustin:

You might want to consider a ChangeFilter that filters out such changes.

Apparently not:

RuntimeError: cannot specify both change_filter and either branch or categories

The thing is, our schedulers are branch specific (because the builders are), but they can also be used for any custom build (I'm not sure why it works currently but it does).

Note: See TracTickets for help on using tickets.