buildbot / buildbot/buildbot

Issues upgrading from 0.8.* to 1.5.0

Open
#4,582 1 comment 0 reactions 0 assignees View on GitHub
eight regression usability
Dominant language
Python
Stars
5.5k
Forks
1.7k
Avg merge
2d 7h
Merged PRs (30d)
6

Description

I have run into the following issues while migrating to 1.5.0 and have wondered if there are good recipes available already (or already addressed in > 1.5)? Hopefully the feedback is constructive and not too whiny. Been a fan since I deployed 0.8.*, but to be honest I was shocked at how disruptive upgrading would be.

1. when buildbot master restarts, waterfall, console and grid view don't show all the builders. Only recently run builders are shown. This is a problem for us as we have builders for past releases that we like to go back to in a few months (for patch releases, etc).

2. console view is actually slower than 0.8.* (takes about 4 second for me), and it omits all builders that don't have recent runs.

3. in console view, forced builds with forced revision show up as unknown. This is a bit confusing for the users.

4. grid view loading is super slow, like 15 seconds, even though it omits all builders that don't have recent runs (in the 15 second case, only 2 builders showed up).

5. list of builds for a builder take a long time to load (at least 3-5x slower compared to 0.8.*. for example, http://myurl/#/builders/9 takes 5 seconds to load 200 builds. I'm running this on 32 core skylake @ 3GHz with tons of RAM (0.8.* was running on a slower machine).

6. Web API changes. I was using JSON in 0.8.*. Trying to migrate to the V2 API, but couldn't quite get to the blamelist.

7. Back in 0.8.* we used to refer to a particular build by e-mail using the builder name.
I'm trying to do the same with 1.5.0 but had no success. For example, http://myurl:8010/#/builders//builds/558

8. We used to have scripts that go through years of past logs to extract information such as which tests never fail. It seems like nowadays everything is stored in the DB. What's the best way to do this now? Does http API v2 allow us to go through the logs?

9. can the pruning of logs be configured such that old logs be archived instead of deleted?

10. we used to create tags for releases and used T-Grid URLs to send to people to look at all the builders for past releases. It seems like only the builders page has functional tag filter? I see that console view does attempt to show some tag information but it seems to be missing in a lot of columns.

Final question, I upgraded because we might migrate to git and I was thinking that newer versions have better git support. Did I make a mistake? Perhaps git support was sufficient even back in 0.8.*?

Thanks!!

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.