Don't require FORCE_REBUILD when CI train can work out there is somethign new

Bug #1505742 reported by Iain Lane on 2015-10-13
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
CI Train [cu2d]
Fix Released
Low
Robert Bruce Park

Bug Description

Look at

  https://ci-train.ubuntu.com/job/ubuntu-landing-010-1-build/248/console

I had edited the landing to add a new merge proposal and ran the 'Build' job with all the defaults. The job failed.

Could the CI train have figured out that I added a merge proposal (or pushed commits to an already attached one) and ran the job successfully?

Robert Bruce Park (robru) wrote :

If you want to rebuild a package without having "rebuild forced" added to your changelog, the UI for that is to enter the package name into the PACKAGES_TO_REBUILD field.

Changed in cupstream2distro:
assignee: nobody → Robert Bruce Park (robru)
importance: Undecided → Low
Iain Lane (laney) wrote :

Thanks!

I know there's a UI for it - I was saying that I think it's possible for CI train to figure out that there is new stuff since the last time it built so I don't need to tell it what to rebuild when there are new revs or branches on the landing.

Yes it's certainly possible, just not trivial to check that, so it's not
something i can get to terribly soon. Patches welcome ;-)
On Oct 14, 2015 1:35 AM, "Iain Lane" <email address hidden> wrote:

> Thanks!
>
> I know there's a UI for it - I was saying that I think it's possible for
> CI train to figure out that there is new stuff since the last time it
> built so I don't need to tell it what to rebuild when there are new revs
> or branches on the landing.
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1505742
>
> Title:
> Don't require FORCE_REBUILD when CI train can work out there is
> somethign new
>
> Status in CI Train [cu2d]:
> New
>
> Bug description:
> Look at
>
> https://ci-train.ubuntu.com/job/ubuntu-
> landing-010-1-build/248/console
>
> I had edited the landing to add a new merge proposal and ran the
> 'Build' job with all the defaults. The job failed.
>
> Could the CI train have figured out that I added a merge proposal (or
> pushed commits to an already attached one) and ran the job
> successfully?
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cupstream2distro/+bug/1505742/+subscriptions
>

Robert Bruce Park (robru) wrote :

The code for this is BuildManager.choose_packages() at:

http://bazaar.launchpad.net/~cupstream2distro-maintainers/cupstream2distro/trunk/view/head:/citrain/build.py#L77

It would need to iterate on self.silo_state.mps and automatically include things that are found to have new commits/new MPs.

Changed in cupstream2distro:
status: New → Fix Released
Robert Bruce Park (robru) wrote :

Heh, just by total coincidence I happened to touch a related piece of code, and then this change suddenly became very easy. Enjoy!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers