Chris opened 2 years ago
|
|||||
Can you please show me the command reporting this error?
|
|||||
Hi,
oh damn I missed this information, sorry! I’m doing version bump things in this step and the failing command is a git fetch.
|
|||||
Robin Shen changed title 2 years ago
|
|||||
Git contained in the Maven image suggested by OneDev (3.6.1-jdk-8) is pretty old. You may specify the image as "maven:3.8.4-jdk-8" to work around the issue. OneDev job suggestion will also be updated to use this image. |
|||||
OneDev changed state to 'Closed' 2 years ago
|
|||||
State changed as code fixing the issue is committed |
|||||
OneDev changed state to 'Released' 2 years ago
|
|||||
State changed as build #2249 is successful |
|||||
Sorry to bump the issue but I think it's somewhat related - is there a way to globally set default image for maven builds (and definition created by 1dev)? I see in the script |
|||||
You may write a custom script returning desired image, something like |
|||||
Any hint how to / where to create such custom script? I checked the documentation / tutorials / blog on medium and sub-sections in build category and haven't found mentions/notion of "scripts". I'm still setting up our 1dev and it would be ideal to have one "template" that would be flexible and configurable via variables/external (global) scripts and use it for all subsequently imported projects that would save a lot of work in the future. (I'm also trying to figure out how to handle deploying maven artifacts to maven repository but that's a separate issue though :-) ) |
|||||
Custom script can be defined here: For instance, you may define a script named
Then you can reference this script in build spec via |
Type |
Bug
|
Priority |
Normal
|
Assignee | |
Affected Versions |
Not Found
|
Hi,
I upgraded from 4.3.0 to 6.2.1 and now some builds are failing with the following error:
This only happens in two of my projects and both of them are using the following image definition: @script:builtin:maven:determine-docker-image@
The SSL/TLS cert for onedev installation is issued by Let's Encrypt, up to date and valid. Is it possible that either using the built-in image is no longer supported or the image is not up to date regarding certificate validation?
Best regards, Chris