Opened 5 years ago

Last modified 22 months ago

#1418 new change

[abp] Generate devbuild update manifests on the update servers

Reported by: fhd Assignee:
Priority: Unknown Milestone:
Module: Infrastructure Keywords:
Cc: Blocked By:
Blocking: Platform: Unknown
Ready: no Confidential: no
Tester: Unknown Verified working: no
Review URL(s):



Generating update manifests for devbuilds is currently happening right after we build those. We should generate and host these update manifests on the update servers - next to the stable ones.

What to change

There are multiple ways of achieving this. What I think would be the cleanest (but not easiest) way is to publish devbuilds by pushing them to a repository (e.g. downloads) as opposed to pulling them directly from the build server.

Then we could generate the update manifests the same way we generate the stable ones: By looking at what's in the downloads repository. All the build server would have to do is push the new version into the repository.

Change History (3)

comment:1 Changed 5 years ago by fhd

  • Cc trev added

I deliberately didn't set this to ready, nor did I set a priority - up to you.

I'm not sure if it's practical to manage binaries that change multiple times a day in a Mercurial repository as I suggested, but IMO we do need some kind of repository for build artifacts - and if it's just a plain file server. Once we have that for the devbuilds, we can move devbuild generation to a dedicated build server.

comment:2 Changed 3 years ago by ferris

  • Summary changed from Generate devbuild update manifests on the update servers to [abp] Generate devbuild update manifests on the update servers
  • Tester set to Unknown

comment:3 Changed 22 months ago by fhd

  • Cc trev removed
Note: See TracTickets for help on using tickets.