-
Feature Request
-
Resolution: Unresolved
-
Optional
-
None
-
EAP64 1.5.2.GA, EAP70 1.5.3.GA
-
Jboss builder images
jboss-eap64-openshift,
jboss-eap70-openshift
-
User Experience
-
-
Customer is using OpenShift 3.5 and a jboss-eap64-openshift image to build software written in Java. The software is source-controlled in a Git repository.
Customer has encountered a case where they need to be able to change the active branch of my Git repository at build time, after I have created a BuildConfig. Currently do this because git is not installed in any of the JBoss builder images.
Use case:
Sure. My customer has two git repositories with Java sources. Call the
repositories A and B.
A depends on B. Both A and B use maven to build. We are trying to use the
chained-build pattern to build B, then build A.
The issue is that for any branch of A that needs to be built, a particular
branch of B is required.
A and B's branches have no correspondence with each other; the only way to
determine what branch
of B to build is to parse A's root pom.xml file. In practice, this means I
need to chain the following
actions:
1. create container with repo A to parse B's branch from pom.xml
2. create container with repo B and build appropriate branch determined in
step 1
3. create container with repo A and build using artifacts copied from step 2
Even after determining the required branch of B in step 1, I have no means
to to provide
the branch to a BuildConfig responsible for the container in step 2.
After parsing pom.xml in step 1, I can provide branch name to the container
in step 2 via a
streamed file. However, having the name of the branch available to me while
inside
the container does me no good because I don't have git, so I can't change
branches.