fix distance oracle entrypoint

closes #199 (closed)

added RN-binary label

assigned to @HugoTrentesaux

added 1 commit

• 49e8a94c - remove max depth

Compare with previous version

Is there an easy way to test that it works without releasing new version?

@c-geek for example in this case, I would like to release a new image with correct entrypoint but no change to runtime (so no gitlab release). In my vision I would only need to cherry-pick this commit on the release branch and press the "release docker" button.

Currently no, there is no way to use the CI to publish a new client version without creating a release branch.

It could be done quite quickly in the CI but I've not time today to have a look on it.

To be exact, I'm not saying I want to publish without a release branch, but to merge on master and cherry-pick in the release branch of the network (or rebase on it the release branch of the network). See #195 (closed) for the scheme. Not in a hurry ^^

Oh yes, you can create a release branch and press the gdev_docker_deploy button in the CI. The image tag will be the release branch name without the release/ prefix. E.g. client-800.2 for release/client-800.2 branch.

You could test this.

I tried on https://git.duniter.org/nodes/rust/duniter-v2s/-/pipelines/36274 but get only

no deploy docker. Maybe because there is both when "manuel" and when "never"?

      when: manual
    - when: never

Never understood the link between the gitlab-ci.yml and what we see in the gitlab interface

You should give a try to writing your own .gitlab-ci file for one project, a very basic one. Actually it's rather easy, but most importantly very helpful to automate releasing tasks. Maybe trying could motivate you to go deeper in the comprehension.

Duniter's .gitlab-ci.yml is a bit complex, it's definitely not the best place to start.

I bet that investing a single day will make you understand and maybe master Duniter's CI file.

I tried it for gcli, it was very basic but I was not satisfied with the workflow and the documentation. So poka took it over and I'm happy with what he did ^^

For the moment it does not fit with my logic but maybe some day I'll go back to this. Maybe after experimenting with drone CI for my personal infra.

added 2 commits

• 7e75570b - 1 commit from branch master
• 0e707b23 - fix distance oracle entrypoint

Compare with previous version

added 2 commits

• 95e85915 - 1 commit from branch master
• a6b2aebf - fix distance oracle entrypoint

Compare with previous version

added 1 commit

• caf8e7b3 - fix distance oracle entrypoint

Compare with previous version

merged

mentioned in commit 1cf65df0

mentioned in commit ceb5d93c