concourse / pool-resource

atomically manages the state of the world (e.g. external environments)
Apache License 2.0
56 stars 36 forks source link

Git commit messages should contain build information #4

Closed chendrix closed 8 years ago

chendrix commented 9 years ago

Ideally instead of just the text "claiming: LOCK_NAME", there should also be a URL that opens the specific job and build number where the lock was claimed.

If you cannot construct the URL, at least the pipeline/job/build information

Use case

We often want to investigate whether our environments can be unclaimed manually because the pipeline failed intermittently and was fixed out of band, etc. Currently the best we can do is look at the time at which the lock was claimed and try to correlate that to a run-through of our pipeline.

concourse-bot commented 9 years ago

Hi there!

We use Pivotal Tracker to provide visibility into what our team is working on. A story for this issue has been automatically created.

The current status is as follows:

This comment, as well as the labels on the issue, will be automatically updated as the status in Tracker changes.

concourse-bot commented 8 years ago

Hello again!

All stories related to this issue have been accepted, so I'm going to automatically close this issue.

At the time of writing, the following stories have been accepted:

If you feel there is still more to be done or have any questions, feel free to reopen!