Build# and dynamic PipelineResource creation to be used as input to the next Task.

[khteh]

Is there a concept of build#? I would like to append that number as the last digit of version number (1.0.0.Build#). This version number string is then used to dynamically build a PipelineResource which is used as input in the next Task, to build and push the container image, for instance. How is this achieved? Thanks.

[ppitonak]

Hi, no there is no traditional concept of a build ID (as a sequence of natural numbers) but you could achive something similar with uid variable, see https://github.com/tektoncd/pipeline/blob/master/docs/variables.md

See also tektoncd/pipeline#2957

[khteh]

Ok. I could probably use part of the uid variable value for image tagging. How do I define that tag dynamically in PipelineResource which is used by the Task which builds the container image based on information provided in PipelineResource? The reference code is hard-coding :latest in the image url.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.