-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integration on GitLab CI #76
Comments
Closing for inactivity. Please feel free to reopen. |
@VictorLamoine if you had a chance to integrate industrial_ci on GitLab, did it work? |
I have made a working version of an https://gitlab.com/VictorLamoine/ros_gitlab_ci Thanks to Docker this was pretty easy to do! |
What I wanted to mean is that it would have been great if I understand that there are cases that creating new ci config makes sense for the needs (e.g. moveit_ci was needed to handle their needs #75). I'm not experienced at all with it but are there specific requirements GitLab enforced you to create a new CI pkg @VictorLamoine ? I'm simply curious and if there's a chance of integrating the two I'll be happy to cooperate. |
I understand what you mean, it would be nice to be able to use the same CI repository with Travis, GitLab etc.
I don't think there are any technical obstacles into integrating GitLab CI into these scripts. If someone has some time available to work on this I'll be happy to spend an hour explaining what I have done and how my repository works; but I can't integrate my current scripts inside this repository right now because I lack time. |
Thanks for the explanation @VictorLamoine. Then I reopen this and leave it open to mark as a possible future-todo. |
Closed via #98. |
From @VictorLamoine at ML:
Running
industrial_ci
on non-Travis CI systems should be possible; main script is currently named as travis.sh, but should be designed to be agnostic from any particular CI system. However I haven't tested on other CIs so can't guarantee.In your CI config on Gitlab, you need to define the same environment variables and run
git clone
, as you do for Travis in your.travis.yml
.I'd be curious how things go with you, so feel free to ask further here if you face issues.
The text was updated successfully, but these errors were encountered: