When using GitHub it is super easy. Docker has a built-in support for GitHub, so every time I commit to master branch a new Docker image is generated automatically.
However, if I want to skip on using GitHub entirely, what would be the best way to submit a new image version to Docker on commit?
Is there any support for this in 1dev?
Docker offers some REST API which could be used for this, but I guess it would require some plugin or component in 1dev to use it.
Robin Shen commented 3 years ago
You may create a CI job running each time upon branch update, and in this job build your docker image, and push to docker hub. For instance, OneDev publishes image upon each release via this script:
You may choose to tag your image with build number (using variable @build_number@), commit id (using variable @commit_hash@) or some form of build version parsed from your project file.
Hi,
When using GitHub it is super easy. Docker has a built-in support for GitHub, so every time I commit to master branch a new Docker image is generated automatically.
However, if I want to skip on using GitHub entirely, what would be the best way to submit a new image version to Docker on commit?
Is there any support for this in 1dev?
Docker offers some REST API which could be used for this, but I guess it would require some plugin or component in 1dev to use it.