Verify git-lfs download

[saper]

Follow-up to #1143 - just for some Docker images for review - as suggested in #1143 (comment)

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests - that demonstrates feature works or fixes the issue

[dduportal]

Thanks a lot @saper , this method sounds good! Do you mind generalizing it to all images?

[MarkEWaite]

I like the technique very much but have been unable to understand why the build process fails both on ci.jenkins.io and for me locally. The ci.jenkins.io failure example is at https://ci.jenkins.io/blue/organizations/jenkins/Packaging%2Fdocker/detail/PR-1144/4/pipeline#step-43-log-1514 . When running a first build, I see the same failure.

[dduportal]

@MarkEWaite

• Build Download deb files and install explicit version #4 received a termination signal during the linux build steps. You can diagnose it by looking at the build output for the "CANCELED" occurences (such as https://ci.jenkins.io/blue/organizations/jenkins/Packaging%2Fdocker/detail/PR-1144/4/pipeline/40#step-43-log-1444). => It's an OOM or CPU overusage, because all the builds are done at the same time. If the agent are reused from previous builds, their behavior is erratic under this kind of pressure. Enable parallel flag in bats #1128 aims to solve this erratic behavior.
• Builds Set jenkins user home to /var/jenkins_home #5 and Failed to listen to incoming slave connection #6 were manually stopped, I'm not sure to understand why?
• Build #7 successfully passed the build step => the PR is good for me on the method, only have to make it the same for all linux machines

[dduportal]

Thanks @saper ! It looks like that gpg is missing on the alpine JDK8 as per: https://ci.jenkins.io/blue/organizations/jenkins/Packaging%2Fdocker/detail/PR-1144/16/pipeline#step-198-log-121

[saper]

Thanks @saper ! It looks like that gpg is missing on the alpine JDK8 as per: https://ci.jenkins.io/blue/organizations/jenkins/Packaging%2Fdocker/detail/PR-1144/16/pipeline#step-198-log-121

Yeah, love that duplication in Dockerfiles... fixed.

[dduportal]

Thanks ! I’m not aware of a builtin situation (i would argue that we don’t need multiple distribution for this image), but do you think it could be useful to factorize this logic to shell script (and then copy + run in the dockerfile) to centralize the version management ?

…

Le 25 juil. 2021 à 11:23, Marcin Cieślak ***@***.***> a écrit :  Thanks @saper ! It looks like that gpg is missing on the alpine JDK8 as per: https://ci.jenkins.io/blue/organizations/jenkins/Packaging%2Fdocker/detail/PR-1144/16/pipeline#step-198-log-121 Yeah, love that duplication in Dockerfiles... fixed. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.