OpenShift-没有源存储库的S2I [英] OpenShift - S2I without source repository

查看:82
本文介绍了OpenShift-没有源存储库的S2I的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在使用作为minishift部署在笔记本电脑上的OpenShift群集.当我更改源代码时,必须在 之前提交到GitHub存储库,然后才能触发构建和部署.我正在使用源代码构建策略.

I am working with an OpenShift cluster deployed on a laptop asminishift. When I make changes to my source code, I have to commit to the GitHub repository before I can trigger a build and a deploy. I am using the Source build strategy.

在我触发构建并在本地OpenShift集群上部署之前,提交到GitHub似乎有点round回.我能想到的一种方法是在本地(至少在LAN上)基于GitLab的安装提交代码.但是,有没有办法完全放弃对GitHub/GitLab的提交?还是git存储库是最低要求?

It seems a bit roundabout to commit to GitHub before I trigger a build and deploy on my local OpenShift cluster. One way I can think of is to have a GitLab based installation locally (at least, on LAN) to which code is committed. However, is there a way to do away with commit to GitHub/GitLab completely? Or a git repository is a minimum requirement?

推荐答案

我在Ubuntu上尝试 GitLab CE ;但是,由于某种原因,登录页面永远不会出现.因此,我最终使用了git-http-server package ;不理想,但是可以解决问题.

I tried GitLab CE on Ubuntu; but, for some reason the login page won't come up ever. So, I ended up using git-http-server package; not ideal, but it does the trick.

:rolleyes:

这篇关于OpenShift-没有源存储库的S2I的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆