Which steps are necessary to migrate a GitLab CE 11 omnibus installation to Docker?
I found this blog post -
https://blog.jscrambler.com/migrating-your-gitlab-infrastructure-into-docker/
But the content seems pretty irrelevant and the commands are all messed up, like too much whitespace and the wrong methods in the dockerfile. Seems pretty dated when comparing the current release to the release this was written for. Could be a good start point though.
Related
I have a self hosted gitlab-ce in a docker environment.
As upgrading GitLab is a pain, I did not do it for a while and now it looks way too complex.
Also there are no good material on how to do this step wise.
Has anyone done this before: what process are you following?
The main advice from the official documentation is to avoid skiping a major version.
In your case, upgrade first to 13.11.
Then 14.1.0.
That way, you can detect any specific setting to update fro one version to the next.
Recently been trying to learn Airflow, but a majority of resources online depended on this repo https://github.com/puckel/docker-airflow which unfortunately has been removed.
I am not familiar with docker so I'm just trying to set up locally and play around with Airflow. I'm on a windows setup and have already gotten docker working on my computer. Does Airflow have a quick-set-up file for a docker-compose? Or is there any other resources I can look at? Thanks.
Its a duplicate question.
Use official official docker-compose.yml see here
I recently added a quick start guides to the official Apache Airflow documentation. Unfortunately, this guide has not been released yet. It will be released in Airflow 2.0.1.
For now, you can use the development version, and when a stable version is released it will be very easy for you to migrate. I don't expect any major changes to our docker-compose.yaml files.
http://apache-airflow-docs.s3-website.eu-central-1.amazonaws.com/docs/apache-airflow/latest/start/docker.html
I want to use Cppcheck's XML report for SonarQube.
https://github.com/SonarOpenCommunity/sonar-cxx/wiki/Code-checkers
But on Cppcheck's official site, I did not find any help with the installation on a Linux server.
Has somebody any working solution for this?
Edit:
I like how the sonarqube tag disappeared, thank you #G. And again, for the constant "support". How convenient just to remove it, instead of helping, or letting someone to help who had these issues as well. Unrelated to the question, yes.
Then guess what: My boss wanted to demo this tool, but certainly told him now not to buy the commercial edition. Everything is unrelated with everything. Good marketing for 2017.
As far as I know, there are no Cppcheck packages built for Linux. However, you may easily clone the Cppcheck repository from GitHub (https://github.com/danmar/cppcheck) and build it yourself. It has no extra dependencies and therefore is easy to build:
cd cppcheck-master
make
Also, I'm not sure about integrating Cppcheck with SonarQube, but there's a detailed article about SonarQube configuration, probably you may find something useful there: https://www.viva64.com/en/m/0037/
I'm new to both of these tools, and I'm also very new to Linux system administration, so I apologize ahead of time for what may seem like a total n00b question.
Basically, I'm starting a whole new project from scratch. Yaaay! Exciting! However, I'm a little lost on how to set up the project. I've installed both git and maven on my dev machine and run through some tutorials. I've also set up git on my server, and have successfully pushed code to it and pulled code from it.
So, first question : Is it even a good idea to use git and maven together? Git seems like the best source control system, and Maven seems like the best build system. Are they known to work well together? Or am I needlessly creating trouble for myself at this early (and precarious) stage of the project? I've used ant enough to know that I don't want to use it, and I'm not really a fan of svn, although I'll use it if I have to.
Second question : Given that these two tools work well together, what's the Best Practices way of setting them up? I know that git is "peer-to-peer", although I suppose nothing is stopping you from setting up a single repository for the git user and having all the devs sync up with that repo when it's time to do a build. Is that the right way to go? How about Maven? Maven seems kinda single-user oriented. Like, everybody sets up Maven on their own machine and has their own Maven repo, right? Or wrong? Would it make sense to create a "Maven user" on my server, and have that user do all my builds from the "main" git repo?
Apologies if I'm totally mistaken on how to use these tools. As I said, I'm pretty new to these things. Any help you have is appreciated.
(also, I'm working on Linux, doing Java dev work in Eclipse, using Spring for the framework, mysql for the data store, and Hibernate as an ORM. Don't know of any of that matters)
Thanks!
Q1: Yes, git will work well with any build systems. Usually your VCS is well abstracted with any modern build system. Ensure that you set up your .gitignore file so that you are not tracking any artifacts from builds.
Q2: The best practice is to have an integration branch to build from. While developing, use topic or feature branches. When ready, merge into the integration branch and push that up to the central repository where maven can build from. Google git-flow for more ideas. You generally want a central build server if you are working on a team to ensure you are building on the same machine. This is not the case if you are working alone or maybe just one developer.
Hope this helps.
Just riding on the BDD wave for the past 2 days.. I was intrigued with Aslak Hellesoy's InfoQ video on RSpec. Specifically with the language agnostic integration testing framework claims.. SO I was looking at testing a .Net app with Cucumber which seems to be the latest avatar of the BDD story runner.
Followed the examples on cukes.info and the wiki pages to do this. Installed IronRuby too..
However the end-result was different in that I get a huge stacktrace.
Posted a comment on the IronRuby Issue Tracking page for the bug
If anyone has worked around this or knows whats up... please leave a response. Thanks.
I spent yesterday working with IronRuby and Cucmber. I don't have a solution to your codeplex ticket, but here's what worked for me.
I used IronRuby 0.9 in c:\ironruby and with ir built from DLR change set 27223 (I have those two on my machine).
I added c:\ironruby\bin to my path, so cucumber.bat can find ir.exe.
I used igem install rspec followed by igem install cucumber
I had to steal rubygem files from my ruby install and put them in my source files to bring rubygems up from 1.2 to > 1.3. igem update --system didn't want to work for me.
I then forced an install of hoe (which had been failing) igem install hoe
At that point, I wrote a cucumber feature, had the step definitions look at White.Core.dll to exercise my app under test, and ran c:\ironruby\lib\ironruby\gems\1.8\bin\cucumber --no-color features with success on XP SP3. The --no-color flag is important, or you'll get terminal codes all over the screen.
I avoid the shared gems model if at all possible. I got confused when I tried that, so I went with what seemed easiest. It's worked for me since 0.6.
JFYI - Got this working after a bit of thrashing about with cryptic errors. Although this is supposed to be fixed in the next release as per the IronRuby developers, Posting my steps to get this working as of today with the 0.9 release
http://madcoderspeak.blogspot.com/2009/09/testing-net-code-with-cucumber-and.html