{14} Changes to Any Tickets (50 matches)

Put ?REPORTER=<username> in the URL to see tickets reported by a particular person.

Only the last 50 changes are included.

This makes a great RSS feed!

Ticket Author Summary Field Time
Description
#941 bsavelev Loose branch in builder with AnyBranchScheduler comment 10:55:06

buildbot have several builders with Git step: 

factory.addStep(buildbot.steps.source.Git(                                                                                              
      timeout       = 3600,                                                                                                                 
      repourl       = builder.branch or 'git://url/repo.git',                               
      branch        = builder.release.fullname(),                                                                                           
      haltOnFailure = True                                                                                                                  
    ))

when I click button 'Force build' all is ok.

each builder have scheduler with fake ImportantFiles? that equal name of builder

for 0.8.1 it look like that: 

c['schedulers'].append(buildbot.schedulers.basic.AnyBranchScheduler(                                                                      
    name = 'cron_' + builder.fullname(),                                                                                                    
    builderNames = (builder.fullname(),),                                                                                                   
    treeStableTimer = 60,                                                                                                                   
    branches = None,                                                                                                                        
    properties = {'forgetsource': 'yes'},                                                                                                   
    fileIsImportant = lambda c, builder = "cron_%s" % builder.fullname(): builder in c.files                                                
  ))
#763 bsavelev debug client calls now-missing perspective_requestBuild comment 10:39:45
#763 bsavelev debug client calls now-missing perspective_requestBuild cc 10:39:45

boris.savelev@…

#939 catlee scheduler_changes accumulates data for Nightly schedulers when onlyIfChanged is False comment 09:41:15

In that for every classify_changes call you need exactly one retire_changes call? No, I don't think so.

Having slept on this, I don't think the Nightly scheduler should be calling classify_changes unless it knows it needs them. It should still retire any changes associated with it when it runs a build.

#939 dustin scheduler_changes accumulates data for Nightly schedulers when onlyIfChanged is False comment 08:54:00

Do the calls to classify_changes and retire_changes need to be balanced?

#931 dustin SIGKILL doesn't kill children processes comment 14:49:53

This has remained a major, unsolved problem for a long time, because there really is no complete solution. Iterating over children requires some access to the kernel's process table, and even then will miss "daemonized" children (those whose parents have already exited). There's an ordering constraint, too - if Buildbot makes a list of all processes to kill before killing them, then new processes may be spawned in the interim.

The code is in slave/buildslave/runprocess.py, if you want to take a look.

#931 dustin SIGKILL doesn't kill children processes milestone 14:49:53

0.8.+

#931 dustin SIGKILL doesn't kill children processes type 14:49:53

enhancement

#938 dustin multiMaster insufficiently explained comment 14:47:06

Yes, this should get better-documented now that it's been used a bit in the wild. We wanted to be quiet about it initially, until the bugs were worked out.

#938 dustin multiMaster insufficiently explained milestone 14:47:06

0.8.2

#938 dustin multiMaster insufficiently explained type 14:47:06

enhancement

#938 dustin multiMaster insufficiently explained keywords 14:47:06

docs

#934 Dustin J. Mitchell PB-based? comment 11:52:09

Remove the phrase 'PB-Based', as it's irrelevant

Also, remove some dreamy documentation for stuff that was never actually written.

Fixes #934.

Changeset: b0d3251da3ad06b48100e684193469624912a807

#934 Dustin J. Mitchell PB-based? resolution 11:52:09

fixed

#934 Dustin J. Mitchell PB-based? status 11:52:09

closed

#935 Dustin J. Mitchell Take "Problem" out of the documentation comment 11:50:34

Remove reference to futuristic "Problem" and other nonesense

Fixes #935

Changeset: a35b59c7c13c8fb605b08d347c8fbf2cccc7cd14

#935 Dustin J. Mitchell Take "Problem" out of the documentation resolution 11:50:34

fixed

#935 Dustin J. Mitchell Take "Problem" out of the documentation status 11:50:34

closed

#935 dustin Take "Problem" out of the documentation comment 11:42:04

This was an idea of Brian's back in the 0.6.x days - I have no idea what he was talking about.

#935 dustin Take "Problem" out of the documentation summary 11:42:04

Take "Problem" out of the documentation

#935 dustin Take "Problem" out of the documentation milestone 11:42:04

0.8.2

#935 dustin Take "Problem" out of the documentation keywords 11:42:04

docs

#933 Dustin J. Mitchell Introduction of properties comment 11:40:32

Move documentation for the 'owner' property to the appropriate place

Fixes #933

Changeset: b89d67dd9559f0fea44b4450241758525534a53e

#933 Dustin J. Mitchell Introduction of properties resolution 11:40:32

fixed

#933 Dustin J. Mitchell Introduction of properties status 11:40:32

closed

#933 dustin Introduction of properties comment 11:34:51

Yeah, that's probably the wrong place to describe that property.

#933 dustin Introduction of properties milestone 11:34:51

0.8.2

#933 dustin Introduction of properties keywords 11:34:51

docs

#932 dustin Unexplained, unlinked references in doc comment 10:10:28

Probably the best solution is to rephrase that in general terms, since the buildbot terms are not introduced yet. Do you want to draft up some new language, and I'll commit it?

#932 dustin Unexplained, unlinked references in doc milestone 10:10:28

0.8.2

#932 dustin Unexplained, unlinked references in doc keywords 10:10:28

docs

#931 acanis SIGKILL doesn't kill children processes comment 20:53:47

Could you loop over all children processes and send them all SIGKILL?

If you point me to the right place in the code I can send you a patch.

#930 dustin _purgeAndUpdate attempts to delete svn externals comment 17:02:53

With tests and everything!

#930 dustin _purgeAndUpdate attempts to delete svn externals milestone 17:02:53

0.8.2

#930 dustin _purgeAndUpdate attempts to delete svn externals type 17:02:53

defect

#930 dustin _purgeAndUpdate attempts to delete svn externals keywords 17:02:53

svn

#930 Dustin J. Mitchell _purgeAndUpdate attempts to delete svn externals comment 17:02:24

Merge branch 'master' of  git://github.com/TimothyFitz/buildbot

* 'master' of  git://github.com/TimothyFitz/buildbot:

Make SVN's purgeAndUpdate correctly not delete svn:external directories.

Fixes #930.

Changeset: af8b299e511eeb38dbfa2e4075f5241c962ab708

#930 Dustin J. Mitchell _purgeAndUpdate attempts to delete svn externals resolution 17:02:24

fixed

#930 Dustin J. Mitchell _purgeAndUpdate attempts to delete svn externals status 17:02:24

closed

#930 TimothyFitz _purgeAndUpdate attempts to delete svn externals comment 16:18:12

Fixed by Curtis and myself in  http://github.com/TimothyFitz/buildbot/commit/780a6bc0e3d34095931b4480458b0c091d20d897

#929 Benoît Allard Visual Studio steps not working in v 0.8.1 comment 09:12:20

Fix handling of VisualStudio? steps args, add VCExpress 2008

Original patch by Giuseppe Corbelli <cowo78@…>; fixes #929.

Changeset: bd6b3c22ecaf692b368c252b616a6f7e85e96acb

#929 Benoît Allard Visual Studio steps not working in v 0.8.1 resolution 09:12:20

fixed

#929 Benoît Allard Visual Studio steps not working in v 0.8.1 status 09:12:20

closed

#929 Ben Visual Studio steps not working in v 0.8.1 comment 03:33:01

I looked at it and modified it a bit, but just saw you made the same corrections as I did. The only thing I did more (beside empty lines modifications) is that I aliased VC8 as VC9 and then VS2008 as VC9

Attaching my one for completeness.

#929 Ben Visual Studio steps not working in v 0.8.1 owner 03:33:01

Ben

#929 Ben Visual Studio steps not working in v 0.8.1 status 03:33:01

accepted

#929 dustin Visual Studio steps not working in v 0.8.1 comment 09:45:49

I pushed this here:

 http://github.com/djmitche/buildbot/commit/bug929

Ben, can you take a look and let me know if this looks ok? If so, I'll push it (or you can).

#789 dustin Source stamp filtering, sorting, and clustering in web views comment 18:30:47
#789 dustin Source stamp filtering, sorting, and clustering in web views description 18:30:47

The current "revision" column/row in the grid view isn't enough if there are builds from different repositories.

By grouping by repository (and showing said repository) we get a better display of what's actually going on.

I believe showing the latest build for each rev/builder config is what we still want to do here.

Related:

#928 dustin Allow builder to be associated with multiple categories comment 18:30:32

I think that the better way to do this right now is to use longer strings for categories and match them with regexes. The web interface doesn't currently support filtering with regexes, but bug #789 might fix that.

Note: See TracReports for help on using and creating reports.