Your build(s) need to be entered in the ART build system. OpenShift uses the issues.redhat.com Jira server for work tracking. If you need to request access, please follow the instructions here: https://mojo.redhat.com/docs/DOC-1081313#jive_content_id_OpenShift_Jira_Access 

 Note: Make sure you are logged into Jira to begin

Fill out this Jira Request Template: ART-85 to have your build(s) added. Read through the request form carefully. The process requires you to provide your image and/or RPM source in a Git repository that conforms to the standards below.

Example Repository: GitHub: An example repo that builds an RPM and an image that could ship with OCP.

Unless otherwise negotiated, upstream source repositories for OCP builds must:

• For RPMs:
  • Place single RPM spec file in the root of the repository
  • The .spec must be based on this template
  • If you require more than one RPM package to be built per GitHub repo, you must use a single spec file with sub-packages
• For containers:
  • Place Dockerfile(s) within the path containing any other resources required for the build.
    • The path may be a subdir of the repo, and should be if the entire repo is not required for the build.
    • The Dockerfile may be in a subdir of the path.
  • Read the example Dockerfiles in the above linked repo for more details about the content of these Dockerfiles
  • As noted below in Productization - Dockerfile Differences, you may carry multiple Dockerfiles. One carrying tweaks specific to OCP builds may have a suffix such as .rhel
• For either:
  • Sources must be fully under the control of Red Hat. We will not automate builds based on sources that third parties have the ability to modify. If you are working with upstream code you may need to work from a Red Hat-controlled fork instead.