Update and rename .github/workflows/dockerimage.yml to dockerimage.yml

[mmornati]

No description provided.

[pascalandy]

Cool stuff Marco! Is this part of the Github Action beta?

[sr229]

Cool stuff Marco! Is this part of the Github Action beta?

Yep, GitHub Actions has a new YAML sytax to keep up with their new CIs.

[sr229]

@mmornati You might need to fix your GPG keys first before I merge this

[mmornati]

Yes sorry for the GPG. I changed my personal laptop and I didn't take time to complete the first setup.
I just wanted to test the CI :)
And it is not complete yet. I need to complete the image_name part as the env variable was not working. And then add the push to Docker Hub.
All other stuff seems working like on Travis... Even if the performances are not the same (it is 2 times slower than Travis ci)

[sr229]

Looks like a empty variable problem in the GitHub CI. Fix that first.

[mmornati]

Looks like a empty variable problem in the GitHub CI. Fix that first.

Yes. I sent an email to GitHub yesterday evening. They answered that it should work with this script and the env variables should be visible in all the steps. But actually is not.
I will check it later. I put the answer into this PR just to share it with anybody:

The way you defined the variable environment should work for the whole step, and the subsequent runs within this step should be able to access this environment variable. Please try retrieving the variable with ${IMAGE_NAME} and let us know if this is working better for you. You can also use some of the default environment variables if they are used to build the image name.

[sr229]

Yeah I think we should give GitHub support another hit since our environment variables in this config is not reading properly.

[pascalandy]

I have a similar challenge regarding VARs. Here is the issue.

[pascalandy]

@mmornati here is the solution I found — actions/starter-workflows#68 (comment)

[mmornati]

Just for your information @pascalandy and @sr229 I received this week a new mail from the GitHub support. It seems they created stuffs right now to correctly fix the problem. ❤️

There are a couple of ways to share environment variables between steps in a job:

• Inside an action, use @actions/core exportVariable
• Or from a shell, use ::set-env
  Between jobs, if it's a static, non-programmatic variable, you could consider using secrets. Otherwise, you might look at uploading and downloading artifacts.

I thought the best one was the ::set-env: quick way to share env variable. And it is working finally !! 😄

[mmornati]

Do not merge for the moment as I would like to add the docker image pushes when a PR is merged (like the check we had in travis)

[mmornati]

It should be good... but a part of the workflow can be really tested only after the merge. I will push it and fix if needed.