upload-artifact | uploads artifacts from your workflow | BPM library

Tkinter is already included in the ubuntu-latest image. No particular setup is needed.

Don't rely on:

Check first:

• that your gradlew clean is executed from the root folder of your project,
• and that your settings.gradle is not in your .gitignore in that same repository.
• The root folder is MyApplication, not My Application.

You can add a ./MyApplication/gradlew tasks to see how gradle is configured.

For this to work, you will need sudo without password to be allowed.

sudo prints this error message, if it tries to prompt for a password but can't.

Based on the above problem statement, we understood that you are looking to clear the web app cache post the deployment.

In order to achieve this, you can add an app settings WEBSITE_LOCAL_CACHE_OPTION=Always which help you in clearing the local cache of the web app.

for any App Service, its related contents (code files, resources etc.) are being hosted in a Shared Content Folder in order to provision all the features of the App Service like Load Balancing etc. So, if there are 2 VMs configure for Load Balancing then there would just one shared location where all the content of the App Service is hosted.

When these Web Apps refer to the Content Folder, there might be chances of Latency issues (although, Azure takes care of most of these issues) which might slow down the performance of the websites a bit. In such Performance-critical application, we can leverage the features of “Azure App Service Local Cache”.

For more information, you refer to this Azure documentation on Azure App Service Local Cache & this blog post as well .

After countless hours working on this, it seems that ultimately the issue was that our internal Web Application Firewall was blocking some part of the transfer of artefacts to the server, or the response back from it. With the WAF reconfigured not to block traffic from the machine running the GitLab Runner, the artefacts are successfully uploaded and the job succeeds.

This would have been significantly easier to diagnose if the logging from GitLab was better. As per my comment on this issue, it should be possible to see the content of the response from the GitLab server after uploading artefacts, even when the response code is 200.

What's strange - and made diagnosing the issue even harder - is that when I worked through the issue with the admin of our GitLab instance, digging through logs and running it in debug mode, the artefact upload process was uploading something successfully. We could see, for example, the GitLab Runner's log had been uploaded to the server. Clearly the WAF's blocking was selective and didn't block everything in both directions.

This seems to be an error message emitted by your program:

Please execute this program with the input file name included as an argument.

We can't know what goes wrong because you don't show the part of your program that emits this.

You say

I have written a program which takes in an single command line argument

but you give multiple arguments:

So yes, I figured out how I can solve this pain.

So all I had to do is create .env file before the build, see the full yml below: