Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

setup.sh build failure #14

Open
jakubklimek opened this issue May 10, 2023 · 0 comments
Open

setup.sh build failure #14

jakubklimek opened this issue May 10, 2023 · 0 comments

Comments

@jakubklimek
Copy link

jakubklimek commented May 10, 2023 •
edited
Loading

running yti-compose/src/script/setup.sh, I hit several build failures like:

Handling yti-docker-java-base
--------------------------
build component:yti-docker-java-base option:
--------------------------
[+] Building 36.6s (6/9)
 => [internal] load .dockerignore                                                                                                                                                                           0.0s
 => => transferring context: 2B                                                                                                                                                                             0.0s
 => [internal] load build definition from Dockerfile                                                                                                                                                        0.0s
 => => transferring dockerfile: 532B                                                                                                                                                                        0.0s
 => [internal] load metadata for docker.io/library/amazoncorretto:17@sha256:04d53492ebeee876914966424e25f86e6ccd44395356ee0d9ec9c451726a4684                                                                0.8s
 => CACHED [1/5] FROM docker.io/library/amazoncorretto:17@sha256:04d53492ebeee876914966424e25f86e6ccd44395356ee0d9ec9c451726a4684                                                                           0.0s
 => [internal] load build context                                                                                                                                                                           0.0s
 => => transferring context: 69B                                                                                                                                                                            0.0s
 => ERROR [2/5] RUN set -x     && yum update && yum upgrade     && yum install bash fontconfig                                                                                                             35.8s
------
 > [2/5] RUN set -x     && yum update && yum upgrade     && yum install bash fontconfig:
#0 0.224 + yum update
#0 0.555 Loaded plugins: ovl, priorities
#0 5.690 https://yum.corretto.aws/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://yum.corretto.aws/x86_64/repodata/repomd.xml: (28, 'Resolving timed out after 5000 milliseconds')
#0 5.691 Trying other mirror.
#0 10.70 https://yum.corretto.aws/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://yum.corretto.aws/x86_64/repodata/repomd.xml: (28, 'Resolving timed out after 5000 milliseconds')
#0 10.70 Trying other mirror.
#0 15.71 https://yum.corretto.aws/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://yum.corretto.aws/x86_64/repodata/repomd.xml: (28, 'Resolving timed out after 5000 milliseconds')
#0 15.71 Trying other mirror.
#0 20.71 https://yum.corretto.aws/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://yum.corretto.aws/x86_64/repodata/repomd.xml: (28, 'Resolving timed out after 5000 milliseconds')
#0 20.71 Trying other mirror.
#0 25.72 https://yum.corretto.aws/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://yum.corretto.aws/x86_64/repodata/repomd.xml: (28, 'Resolving timed out after 5000 milliseconds')
#0 25.72 Trying other mirror.
#0 30.73 https://yum.corretto.aws/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://yum.corretto.aws/x86_64/repodata/repomd.xml: (28, 'Resolving timed out after 5000 milliseconds')
#0 30.73 Trying other mirror.
#0 35.74 https://yum.corretto.aws/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://yum.corretto.aws/x86_64/repodata/repomd.xml: (28, 'Resolving timed out after 5000 milliseconds')
#0 35.74 Trying other mirror.
#0 35.75
#0 35.75
#0 35.75  One of the configured repositories failed (Amazon Corretto),
#0 35.75  and yum doesn't have enough cached data to continue. At this point the only
#0 35.75  safe thing yum can do is fail. There are a few ways to work "fix" this:
#0 35.75
#0 35.75      1. Contact the upstream for the repository and get them to fix the problem.
#0 35.75
#0 35.75      2. Reconfigure the baseurl/etc. for the repository, to point to a working
#0 35.75         upstream. This is most often useful if you are using a newer
#0 35.75         distribution release than is supported by the repository (and the
#0 35.75         packages for the previous distribution release still work).
#0 35.75
#0 35.75      3. Run the command with the repository temporarily disabled
#0 35.75             yum --disablerepo=AmazonCorretto ...
#0 35.75
#0 35.75      4. Disable the repository permanently, so yum won't use it by default. Yum
#0 35.75         will then just ignore the repository until you permanently enable it
#0 35.75         again or use --enablerepo for temporary usage:
#0 35.75
#0 35.75             yum-config-manager --disable AmazonCorretto
#0 35.75         or
#0 35.75             subscription-manager repos --disable=AmazonCorretto
#0 35.75
#0 35.75      5. Configure the failing repository to be skipped, if it is unavailable.
#0 35.75         Note that yum will try to contact the repo. when it runs most commands,
#0 35.75         so will have to try and fail each time (and thus. yum will be be much
#0 35.75         slower). If it is a very temporary problem though, this is often a nice
#0 35.75         compromise:
#0 35.75
#0 35.75             yum-config-manager --save --setopt=AmazonCorretto.skip_if_unavailable=true
#0 35.75
#0 35.75 failure: repodata/repomd.xml from AmazonCorretto: [Errno 256] No more mirrors to try.
#0 35.75 https://yum.corretto.aws/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://yum.corretto.aws/x86_64/repodata/repomd.xml: (28, 'Resolving timed out after 5000 milliseconds')
#0 35.75 https://yum.corretto.aws/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://yum.corretto.aws/x86_64/repodata/repomd.xml: (28, 'Resolving timed out after 5000 milliseconds')
#0 35.75 https://yum.corretto.aws/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://yum.corretto.aws/x86_64/repodata/repomd.xml: (28, 'Resolving timed out after 5000 milliseconds')
#0 35.75 https://yum.corretto.aws/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://yum.corretto.aws/x86_64/repodata/repomd.xml: (28, 'Resolving timed out after 5000 milliseconds')
#0 35.75 https://yum.corretto.aws/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://yum.corretto.aws/x86_64/repodata/repomd.xml: (28, 'Resolving timed out after 5000 milliseconds')
#0 35.75 https://yum.corretto.aws/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://yum.corretto.aws/x86_64/repodata/repomd.xml: (28, 'Resolving timed out after 5000 milliseconds')
#0 35.75 https://yum.corretto.aws/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://yum.corretto.aws/x86_64/repodata/repomd.xml: (28, 'Resolving timed out after 5000 milliseconds')
------
Dockerfile:12
--------------------
  11 |     # Install common tools
  12 | >>> RUN set -x \
  13 | >>>     && yum update && yum upgrade \
  14 | >>>     && yum install bash fontconfig
  15 |
--------------------
ERROR: failed to solve: process "/bin/sh -c set -x     && yum update && yum upgrade     && yum install bash fontconfig" did not complete successfully: exit code: 1
/opt

klimek@tietomallit:/opt$ sudo yti-compose/src/script/setup.sh
Starting development environment Setup
Handling yti-spring-security
publish component:yti-spring-security
--------------------------
/opt/build.master/yti-spring-security

> Configure project :
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.9/userguide/command_line_interface.html#sec:command_line_warnings

BUILD SUCCESSFUL in 1s
5 actionable tasks: 2 executed, 3 up-to-date
DONE yti-spring-security
/opt
Handling yti-spring-migration
publish component:yti-spring-migration
--------------------------
/opt/build.master/yti-spring-migration

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine java version from '11.0.18'.

> Task :frontend:yarnInstall
yarn install v1.22.5
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
warning [email protected]: Invalid bin field for "mini-css-extract-plugin".
warning [email protected]: Invalid bin field for "url-loader".
info [email protected]: The platform "linux" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
info [email protected]: The platform "linux" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
[4/5] Linking dependencies...
warning " > [email protected]" has unmet peer dependency "[email protected] - 3".
warning " > [email protected]" has unmet peer dependency "popper.js@^1.14.3".
[5/5] Building fresh packages...
Done in 106.87s.

> Task :web-api:compileJava FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':web-api:compileJava'.
> Could not resolve all files for configuration ':web-api:compileClasspath'.
   > Could not find fi.vm.yti:yti-spring-security:0.1.17.
     Required by:
         project :web-api

Handling yti-codelist-public-api-service
--------------------------
build component:yti-codelist-public-api-service option:


[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  1.696 s
[INFO] Finished at: 2023-05-10T11:25:06Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project yti-codelist-content-intake-service: Could not resolve dependencies for project fi.vm.yti.codelist:yti-codelist-content-intake-service:jar:0.1-SNAPSHOT: Failure to find fi.vm.yti:yti-spring-security:jar:0.1.17 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException

Handling yti-codelist-content-intake-service
--------------------------
build component:yti-codelist-content-intake-service option:
--------------------------

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  1.696 s
[INFO] Finished at: 2023-05-10T11:25:06Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project yti-codelist-content-intake-service: Could not resolve dependencies for project fi.vm.yti.codelist:yti-codelist-content-intake-service:jar:0.1-SNAPSHOT: Failure to find fi.vm.yti:yti-spring-security:jar:0.1.17 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException

Handling yti-datamodel-api
--------------------------
build component:yti-datamodel-api option:
--------------------------
Starting a Gradle Daemon (subsequent builds will be faster)
Download https://plugins.gradle.org/m2/com/github/ManifestClasspath/com.github.ManifestClasspath.gradle.plugin/0.1.0-RELEASE/com.github.ManifestClasspath.gradle.plugin-0.1.0-RELEASE.pom
Download https://plugins.gradle.org/m2/org/jfrog/buildinfo/build-info-extractor-gradle/4.24.16/build-info-extractor-gradle-4.24.16.pom
Download https://plugins.gradle.org/m2/org/owasp/dependency-check-gradle/6.1.6/dependency-check-gradle-6.1.6.pom
Download https://plugins.gradle.org/m2/gradle/plugin/com/github/viswaramamoorthy/gradle-util-plugins/0.1.0-RELEASE/gradle-util-plugins-0.1.0-RELEASE.pom
Download https://plugins.gradle.org/m2/org/eclipse/jgit/org.eclipse.jgit/maven-metadata.xml
Download https://repo.maven.apache.org/maven2/org/eclipse/jgit/org.eclipse.jgit/maven-metadata.xml
Download https://jcenter.bintray.com/org/eclipse/jgit/org.eclipse.jgit/maven-metadata.xml
Download https://plugins.gradle.org/m2/org/jfrog/buildinfo/build-info-extractor-gradle/4.24.16/build-info-extractor-gradle-4.24.16.jar
Download https://plugins.gradle.org/m2/gradle/plugin/com/github/viswaramamoorthy/gradle-util-plugins/0.1.0-RELEASE/gradle-util-plugins-0.1.0-RELEASE.jar

FAILURE: Build failed with an exception.

* Where:
Build file '/opt/build.master/yti-datamodel-api/build.gradle' line: 14

* What went wrong:
An exception occurred applying plugin request [id: 'org.springframework.boot', version: '2.5.12']
> Failed to apply plugin [id 'org.springframework.boot']
   > Spring Boot plugin requires Gradle 6.8.x, 6.9.x, or 7.x. The current version is Gradle 4.4.1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 18s
[+] Building 0.7s (3/3) FINISHED
 => [internal] load .dockerignore                                                                                                                                                                           0.0s
 => => transferring context: 2B                                                                                                                                                                             0.0s
 => [internal] load build definition from Dockerfile                                                                                                                                                        0.0s
 => => transferring dockerfile: 237B                                                                                                                                                                        0.0s
 => ERROR [internal] load metadata for docker.io/library/yti-docker-java11-base:alpine                                                                                                                      0.7s
------
 > [internal] load metadata for docker.io/library/yti-docker-java11-base:alpine:
------
Dockerfile:1
--------------------
   1 | >>> FROM yti-docker-java11-base:alpine
   2 |
   3 |     ADD build/libs/yti-datamodel-api.jar yti-datamodel-api.jar
--------------------
ERROR: failed to solve: yti-docker-java11-base:alpine: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jakubklimek