OCPBUGS-794: remove dependence on OLM_VERSION file

[ankitathomas]

The olm binary was using the stale upstream OLM_VERSION file for versioning. This resulted in downstream builds inaccurately displaying version.

This change switches to using the ART provided OS_GIT_VERSION or a default 0.0.0- version to version downstream olm so downstream builds can display the openshift versions they are built for.

[openshift-ci-robot]

@ankitathomas: This pull request references Jira Issue OCPBUGS-794, which is invalid:

• expected the bug to target the "4.13.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

The olm binary was using the stale upstream OLM_VERSION file for versioning. This resulted in downstream builds inaccurately displaying version.

This change switches to using the ART provided OS_GIT_VERSION or a default 0.0.0- version to version downstream olm so downstream builds can display the openshift versions they are built for.

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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ankitathomas

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:

• OWNERS [ankitathomas]

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

[openshift-ci]

@ankitathomas: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[perdasilva]

/lgtm

[perdasilva]

/jira refresh

[openshift-ci-robot]

@perdasilva: This pull request references Jira Issue OCPBUGS-794, which is invalid:

• expected the bug to target the "4.13.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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.

[perdasilva]

/jira refresh

[openshift-ci-robot]

@perdasilva: This pull request references Jira Issue OCPBUGS-794, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.13.0) matches configured target version for branch (4.13.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @jianzhangbjz

In response to this:

/jira refresh

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.

[openshift-ci-robot]

@ankitathomas: All pull requests linked via external trackers have merged:

• openshift/operator-framework-olm#462

Jira Issue OCPBUGS-794 has been moved to the MODIFIED state.

In response to this:

The olm binary was using the stale upstream OLM_VERSION file for versioning. This resulted in downstream builds inaccurately displaying version.

This change switches to using the ART provided OS_GIT_VERSION or a default 0.0.0- version to version downstream olm so downstream builds can display the openshift versions they are built for.

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.

[jianzhangbjz]

/label qe-approved

[openshift-ci-robot]

@ankitathomas: Jira Issue OCPBUGS-123: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-123 has been moved to the MODIFIED state.

Jira Issue OCPBUGS-456 is in an unrecognized state (Closed) and will not be moved to the MODIFIED state.

In response to this:

The olm binary was using the stale upstream OLM_VERSION file for versioning. This resulted in downstream builds inaccurately displaying version.

This change switches to using the ART provided OS_GIT_VERSION or a default 0.0.0- version to version downstream olm so downstream builds can display the openshift versions they are built for.

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.

[openshift-ci-robot]

@ankitathomas: Jira Issue OCPBUGS-794 is in an unrecognized state (Verified) and will not be moved to the MODIFIED state.

In response to this:

The olm binary was using the stale upstream OLM_VERSION file for versioning. This resulted in downstream builds inaccurately displaying version.

This change switches to using the ART provided OS_GIT_VERSION or a default 0.0.0- version to version downstream olm so downstream builds can display the openshift versions they are built for.

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.