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

fix(pipeline-service-account) copy Service account while rerunning Pipelines #2229

Conversation

abhinandan13jan
Copy link
Contributor

Addresses issue:
https://jira.coreos.com/browse/ODC-1501

POST-FIX

rerunning pipeline
Screenshot from 2019-07-31 18-46-18

pipelinerun running
Screenshot from 2019-07-31 18-46-30

pipelinerun successful
Screenshot from 2019-07-31 18-46-46

serviceAccount of pipelineRun
Screenshot from 2019-07-31 18-47-02

@openshift-ci-robot openshift-ci-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. component/dev-console Related to dev-console labels Jul 31, 2019
@abhinandan13jan
Copy link
Contributor Author

/cc @christianvogt

serviceAccount:
latestRun && latestRun.spec && latestRun.spec.serviceAccount
? latestRun.spec.serviceAccount
: pipeline && pipeline.spec && pipeline.spec.serviceAccount
Copy link
Contributor

Choose a reason for hiding this comment

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

Trying to find where in the docs it says that a pipeline has a serviceAccount property. I cannot find. Please confirm if this is correct.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

As there is no creation flow in place for Pipeline, if resources, params and serviceAccount is added to the Pipeline YAML in Spec, all the data should cascade down to every corresponding PipelineRuns when Start Pipeline/rerun Pipeline is triggered.
Is there any other option to specifically borrow these properties to pass on to the first-pipelinerun for a pipeline if not present in the Pipeline itself? @siamaksade @vdemeester @sspeiche

@christianvogt
Copy link
Contributor

/lgtm
/approve

We do not support the start scenario yet and can address the serviceAccount later for that scenario.

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 31, 2019
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinandan13jan, christianvogt

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

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 31, 2019
@openshift-merge-robot openshift-merge-robot merged commit c616dbb into openshift:master Jul 31, 2019
@spadgett spadgett added this to the v4.2 milestone Aug 7, 2019
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. component/dev-console Related to dev-console 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