Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add the git resource ref to the ResourceResult for git resources. #2238

Merged
merged 1 commit into from
Mar 23, 2020

Conversation

dlorenc
Copy link
Contributor

@dlorenc dlorenc commented Mar 17, 2020

Changes

This includes the full name of the git resource in the resource result for
git resources. We pass this along in the environment variable already, this
includes it back in the resource result so we can tie the commit sha and
branch name in the result.

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

See the contribution guide for more details.

Double check this list of stuff that's easy to miss:

Reviewer Notes

If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.

Release Notes

The `git` PipelineResource now includes the resourceRef in the `resourcesResult` section. For example:

    "resourcesResult": [
      {
        "key": "commit",
        "value": "6ed7aad5e8a36052ee5f6079fc91368e362121f7",
        "resourceRef": {
           "name": "my-resource"
        }
      },

@googlebot googlebot added the cla: yes Trying to make the CLA bot happy with ppl from different companies work on one commit label Mar 17, 2020
@tekton-robot tekton-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Mar 17, 2020
@ghost
Copy link

ghost commented Mar 17, 2020

Could you add a bit of explanation around the intended purpose? Is it related to a specific bug or feature request?

@dlorenc dlorenc force-pushed the namegit branch 2 times, most recently from a04f24b to 715280b Compare March 17, 2020 20:25
This includes the full name of the git resource in the resource result for
git resources. We pass this along in the environment variable already, this
includes it back in the resource result so we can tie the commit sha and
branch name in the result.

Right now Task results contain the exact commit that was cloned from any git
resource inputs, but the "resourceref" field is empty. That makes it hard to
tell which repo was cloned after. In the case of multiple inputs, there is
no way to tell which result corresponds to which.
@dlorenc
Copy link
Contributor Author

dlorenc commented Mar 17, 2020

Could you add a bit of explanation around the intended purpose? Is it related to a specific bug or feature request?

Added some more to the commit message. I think this was something just overlooked, so halfway between a feature request and a bug.

@dlorenc
Copy link
Contributor Author

dlorenc commented Mar 18, 2020

/test pull-tekton-pipeline-integration-tests

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 18, 2020
Copy link
Member

@vdemeester vdemeester left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 23, 2020
@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dibyom, vdemeester

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot merged commit e395279 into tektoncd:master Mar 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cla: yes Trying to make the CLA bot happy with ppl from different companies work on one commit lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants