Skip to content
This repository has been archived by the owner on Jun 15, 2024. It is now read-only.

Use build/step-metadata #20

Open
flosell opened this issue Jan 15, 2017 · 1 comment
Open

Use build/step-metadata #20

flosell opened this issue Jan 15, 2017 · 1 comment

Comments

@flosell
Copy link
Owner

flosell commented Jan 15, 2017

The next lambdacd-release (0.13.0) will contain support for build-metadata (flosell/lambdacd#138).
This could be used to make git-information more visible (e.g. to display the commit message that's being built prominently in the UI).

@flosell
Copy link
Owner Author

flosell commented Mar 29, 2017

Two approaches are possible:

  • Set git-information on build-metadata:
    • Useful for most pipelines, could just work out of the box.
    • Drawback: Could produce unpredictable results if pipeline contains more than one git-step. Could be resolved by adding a flag to disable setting metadata (in this case users would need the handle this themselves)
  • Set git-information on step-metadata (not implemented in LambdaCD yet, see Introduce a concept of step-metadata lambdacd#86):
    • More fine-grained, does support multiple git steps out of the box
    • Would need extra work in UI, finding the right git-information to display for a step

tbd: Do we set metadata on clone or on successful wait-for?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant