the generated applications probably shouldn't contain the entirety of the booster's GitHub repo

[Ladicek]

I'm thinking mainly of the .openshiftio directory, but maybe there's more.

[gastaldi]

You mean as a ZIP or deployed in Openshift? It should be removed when you choose to download as a ZIP

[Ladicek]

Let me check the .zip, but I'm seeing the .openshiftio directory in my GitHub repo.

... which doesn't go through the backend, so this is the wrong issue tracker, right? :-)

[gastaldi]

I believe that folder is needed to run the pipelines in Jenkins? Anyway, the backend is responsible to removing the .openshiftio dir, so if we should do that for the Open in Openshift button, this is the correct issue tracker :)

[Ladicek]

The Jenkinsfile is needed for the pipeline, but that's not in the .openshiftio directory. That only has the booster.yaml file.

Actually I was thinking about using the .openshiftio directory to store a Jenkinsfile for our own CI (which might be different from the top-level Jenkinsfile), that's why I had the idea that the .openshiftio directory should be removed.

[Ladicek]

If you ever get to removing .openshiftio from generated Git repos / .zip archives, please make a noise. When migrating boosters tests to Arquillian Cube, we made some tests use the .openshiftio pieces (e.g. to deploy a DB in the CRUD booster). This will have to be fixed.