-
Notifications
You must be signed in to change notification settings - Fork 653
CentOS 7 docker based image #1571
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
Conversation
added Dockerfile with clear cenots/7,dotnet core 2.2, gitversion 4.0.0
Thanks for this, @mr-exz. Is it possible to add an automatic test that is run by Travis or similar, somehow? |
@mr-exz thanks for the contribution, we currently publish the docker images as part of the build process. In order to get this PR merged we need to change the way the docker image is built, meaning the image should use the artifact from the build itself and not from Github release, that means we need to include in the build scripts. Currently we have 2 variants of the linux images - one using dotnet core and another using mono. Would be great to have the mono version as well. For the build scripts we'll need to support building for different distros of Linux here and here So for now I would suggest to update the build script to allow building for several distro of Linux, then adjust the DockerFile to use the artifacts from the build itself |
i will check how you did it, and will try fit my Dockerfile into build process |
build.cake
Outdated
@@ -622,6 +623,7 @@ Task("Publish-DockerHub") | |||
{ | |||
DockerPush("linux", "dotnetcore", parameters); | |||
DockerPush("linux", "fullfx", parameters); | |||
DockerPush("linux", "centos", parameters); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please excuse my ignorance, but how is this going to affect the naming on DockerHub? I don't quite understand where the existing repositories gitversion-fullfx
, gitversion-dotnetcore
, gitversion
and libgit2sharp-mono
come from and how they relate to these DockerPush()
statements. Will centos
become a new tag
in the gitversion-dotnetcore
repository?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@asbjornu
gitversion
andlibgit2sharp-mono
are already obsolete, only fullfx and dotnetcore are maintained.
As for centos, that is right, the current changes will not create a tag under dotnetcore - good catch, we'll need to adjust the scripts to allow several distros of linux under dotnetcore and fullfx
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is the method where the tags are created https://github.com/GitTools/GitVersion/blob/master/build/utils.cake#L174
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see. I find it a bit unfortunate that we have 4 different repositories for variations of the same executable. Can we get rid of every repository that isn't called simply gitversion
and follow NGINX' naming scheme for labels to distinguish different versions of the image? That would give us one repository with tags following the scheme {version}-{platform}-{framework}
, for example:
4.0.0-centos
4.0.1-beta2-debian-fx
4.0.0-beta15-windows-dotnetcore
latest-ubuntu
latest-windows
stable-ubuntu
stable-windows
I know doing anything about this scheme is outside the scope of this PR, I just want to have a discussion on this so I know which options we have.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest creating a separate issue, I can then implement it, and after that we can adjust this PR to the new scheme.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@asbjornu please create an issue with the proposed scheme and we can discuss it there
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, I've created #1572 for further discussion.
@arturcic, yep, that's the plan. 😃 |
@mr-exz , I think you should move the Dockerfile to the src/Docker/linux/centos/netcoreapp2.1 folder similar to debian version. This way we'll be able to add net core 2.2 version as well |
Looks great! Thank you for your contribution! |
Not at all |
@arturcic can you provide link on new centos7/fedora27 docker images link ? |
Yesterday when the PR was merged the Linux build has failed, some unit tests for some reason failed, now they work again. The tags can be found at https://hub.docker.com/r/gittools/gitversion/tags |
@mr-exz can you confirm that those docker images are valid and work as expected as I don't have time to test them these days? |
i will, in process |
Thanks |
For me working fine
|
great, thanks for the fedora image as well. |
Not at all :) |
Btw, are you in a position to add a new PR for netcoreapp2.2? for linux images? That would be a great addition |
ok will do, it shouldn't be so difficult |
Hm, I just discovered that the tag |
There is also a tag |
And the versioning here https://github.com/GitTools/GitVersion/blob/master/build/version.cake#L23-L24 |
|
@arturcic, thanks for the explanation. That sounds sensible to me. 👍 |
added Dockerfile with: