Opened 8 years ago

Closed 4 years ago

#9071 closed defect (wontfix)

Publish customization keys used to create images with Activities

Reported by: mchua Owned by: dgilmore
Priority: normal Milestone: 9.1.0-cancelled
Component: build-system Version: not specified
Keywords: cjbfor9.1.0 Cc: arjs, pgf, cscott
Blocked By: Blocking:
Deployments affected: Action Needed: never set
Verified: no


When an image containing Activities is published, that image contains both an underlying build plus Activities from some customization key. For instance, build 767 + some customization key = our latest G1G1 image.

It would be easy and useful to publish the customization key used to create images with Activities, perhaps in the image folder itself (imagine

One could imagine an Activity maintainer wanting to know what version of her Activity was shipped, or a user who wanted to keep their current build but update just the G1G1 activities, or a developer wondering what versions they'd get if they clean-installed.

Change History (6)

comment:1 Changed 8 years ago by mchua

See for a description of the saga that inspired this ticket.

comment:2 Changed 8 years ago by mstone

  • Cc pgf cscott added

Is unsatisfactory?

Perhaps what you really want is, as pgf suggested, a README?

comment:3 Changed 8 years ago by cjb

Oh, hey, check that out. (mchua had asked me if we published customization keys for releases and I said no.)

comment:4 Changed 8 years ago by mchua

Ah, thanks - I didn't recognize that. A README with a URL pointing to a wiki page containing an explanation of the various files would resolve my confusion.

I wrote up some text on the build systems wiki page that could be included or linked to within a README at (sanity fact-checking requested).

comment:5 Changed 8 years ago by mstone-xmlrpc

  • Keywords cjbfor9.1.0 added
  • Milestone changed from 8.2.1 to 9.1.0

Pushing out to 9.1.0, per edmcnierney's request.

comment:6 Changed 4 years ago by dsd

  • Resolution set to wontfix
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.