Opened 11 years ago

Closed 7 years ago

#3524 closed enhancement (worksforme)

Buildbot

Reported by: ghtdak Owned by: ghtdak
Priority: critical Milestone: sage-duplicate/invalid/wontfix
Component: build Keywords:
Cc: mhansen, mvngu, drkirkby, leif, jdemeyer, kini Merged in:
Authors: Reviewers: Maarten Derickx
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Description (last modified by mpatel)

Buildbot is a continuous integration system for software projects.

Links:

Alternatives:

Important relevant tickets: #8677, #9433, #9739, #9799, #9811, #9876, #10040.
We also need to speed up t2's ATLAS build (cf. #4949, #6705, #9780).

See this page for Sage-related Buildbots. TODO for the Sage Buildbot.

Change History (23)

comment:1 Changed 11 years ago by was

I do not think this is sufficiently precise to be a trac ticket. This should be made into a single precise clear task that somebody volunteers to do or closed as invalid.

comment:2 Changed 11 years ago by ghtdak

Buildbot Implementation Plan

1) Setup Buildbot master and slaves for release testing: Implement shellcommand interfaces to download, build and test candidate tarballs

  • includes configuring status delivery via mail / web and irc

2) Integration with Hg: finer grained use of distributed testing through Hg pull

3) Twisted PB integration: Buildbot supports PB and can be used for real-time status

3) Integration with test framework: unittest and doctest

comment:3 Changed 11 years ago by ghtdak

  • Resolution set to invalid
  • Status changed from new to closed

comment:4 Changed 11 years ago by mabshoff

  • Milestone changed from sage-3.1.1 to sage-duplicate/invalid

comment:5 Changed 10 years ago by mpatel

  • Cc mhansen mvngu drkirkby added
  • Description modified (diff)
  • Milestone sage-duplicate/invalid/wontfix deleted
  • Priority changed from minor to critical
  • Report Upstream set to N/A
  • Resolution invalid deleted
  • Status changed from closed to new

I'm reopening this, because it's important and overdue. We can discuss possible approaches on sage-devel.

comment:6 Changed 9 years ago by mpatel

  • Component changed from distribution to build
  • Description modified (diff)

comment:7 Changed 9 years ago by mpatel

  • Description modified (diff)

comment:8 Changed 9 years ago by mpatel

  • Description modified (diff)

comment:9 Changed 9 years ago by mpatel

  • Description modified (diff)

comment:10 Changed 9 years ago by mpatel

  • Description modified (diff)

comment:11 Changed 9 years ago by mpatel

  • Description modified (diff)

comment:12 Changed 9 years ago by mpatel

  • Description modified (diff)

comment:13 Changed 9 years ago by leif

  • Cc leif added

comment:14 Changed 9 years ago by mpatel

  • Description modified (diff)

comment:15 follow-ups: Changed 9 years ago by drkirkby

Can this now be closed, since the buildbot is working?

Dave

comment:16 in reply to: ↑ 15 Changed 9 years ago by mpatel

  • Cc jdemeyer added

Replying to drkirkby:

Can this now be closed, since the buildbot is working?

"Sounds" good!

comment:17 Changed 8 years ago by leif

  • Cc kini added

What IRC integration would be desirable?

comment:18 Changed 8 years ago by kini

Oh, I just wanted to improve sagebot's trac reporting. I also want to do some other stuff with trac tracking, but none of this is related to the buildbot.

comment:19 in reply to: ↑ 15 Changed 8 years ago by jdemeyer

Replying to drkirkby:

Can this now be closed, since the buildbot is working?

It's working, but not very well.

Anybody has any clue what's wrong with

http://build.sagemath.org/sage/builders/Skynet%20download

comment:20 Changed 8 years ago by mderickx

  • Status changed from new to needs_review

I'm putting this to needs review, since the buildbot is clearly already an active part of the release process. If there are things to be improved there should be a new ticket (not this one whose goal was to get something running in the first place).

comment:21 Changed 7 years ago by kini

  • Status changed from needs_review to positive_review

What is there to review? It seems to me like you are proposing to close this ticket outright, in which case the correct status should be positive_review (so the release manager sees it).

comment:22 Changed 7 years ago by kini

  • Milestone set to sage-duplicate/invalid/wontfix

comment:23 Changed 7 years ago by jdemeyer

  • Resolution set to worksforme
  • Reviewers set to Maarten Derickx
  • Status changed from positive_review to closed
Note: See TracTickets for help on using tickets.