Need easy way to link releases and commits / prs
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-release-tools |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
This is a request to be able to source (and ideally display on reports.vapour.ws!) which commits are in which released version of juju (and which CI build), as well as which PR's. This would make our triage work SO much easier and more straightfoward for us.
We want to easily answer the following questions:
What is the difference between CI build X and CI build X+n? What PR's landed? What commit is CI build X, and what commit is CI build X+n?
What is the difference between juju 2.X and juju 2.X.X? What PR's landed? What commit is juju 2.X and juju 2.X.X?
This means new bugs can easily be blamed on specific PR's. It also means release calls can pinpoint which PR's are included and ensure only those desired go into a release. Finally, it allows for easy git bisects using the known good and bad commits.
| description: | updated |
| no longer affects: | juju-ci-tools |
| Changed in juju-release-tools: | |
| importance: | Undecided → Wishlist |
| Changed in juju-reports: | |
| importance: | Undecided → Wishlist |
| no longer affects: | juju-reports |
| Changed in juju-release-tools: | |
| status: | New → Triaged |
| Aaron Bentley (abentley) wrote | #1 |
There are different things going on here. "sourcing" which commits are present in a revision build can be done using git and the tags, e.g. git log juju-2.
Similarly, "sourcing" which commits are present it a build revision can be done using the revision id provided by that revision.
If you want it easier than that, it should be trivial to script.
This satisfies the bug, since you said displaying it on reports.vapour.ws would be ideal, not necessary.