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.

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

Release Che 7.24.0 #18725

Closed
7 of 13 tasks
nickboldt opened this issue Jan 5, 2021 · 9 comments
Closed
7 of 13 tasks

Release Che 7.24.0 #18725

nickboldt opened this issue Jan 5, 2021 · 9 comments
Assignees
Labels
kind/release Issue dedicated to a release (content, status, related PR, go/nogo/problem discussion, etc.)
Milestone

Comments

@nickboldt
Copy link
Contributor

nickboldt commented Jan 5, 2021

List of pending issues / PRs

Release status

In series, the following will be released via che-release:

  • che-theia, che-machine-exec, che-devfile registry,
  • che-plugin-registry (once che-theia and machine-exec are done)
  • che-parent, che-dashboard, che-workspace-loader, and che (server assembly), including release to Maven Central
  • che-operator

Then, these steps will be done, which still require some manual intervention (PR verification is not yet automated):

  • generation of OperatorHub PRs
  • chectl
  • che-theia, che-machine-exec, che-devfile-registry, che-plugin-registry
  • che-parent, che-dashboard, che-workspace-loader, che
  • che-operator (depends on all of the above)
  • chectl (depends on che-operator)
  • Che community operator PRs (depends on che-operator)

If this is a .0 release:

Owner Process Script CI Artifact(s) + Container(s)
@mkuznyetsov che-theia cico_release.sh centos eclipse/che-theia
@mkuznyetsov che-machine-exec cico_release.sh centos eclipse/che-machine-exec
@mkuznyetsov che-devfile-registry make-release.sh GH action eclipse/che-devfile-registry
@mkuznyetsov che-plugin-registry make-release.sh GH action eclipse/che-plugin-registry
@mkuznyetsov che-parent make-release.sh centos che-parent
@mkuznyetsov che-dashboard make-release.sh GH action che-dashboard
@mkuznyetsov che-workspace-loader make-release.sh GH action che-workspace-loader
@mkuznyetsov che cico_release.sh centos che.core,
eclipse/che-server,
eclipse/che-endpoint-watcher,
eclipse/che-keycloak,
eclipse/che-postgres,
eclipse/che-server,
eclipse/che-e2e
@mkuznyetsov che-operator make-release.sh GH action eclipse/che-operator
@mkuznyetsov chectl make-release.sh GH action chectl releases
@nickboldt nickboldt added the kind/release Issue dedicated to a release (content, status, related PR, go/nogo/problem discussion, etc.) label Jan 5, 2021
@nickboldt nickboldt added this to the 7.24 milestone Jan 5, 2021
@mkuznyetsov
Copy link
Contributor

after transitioning to GH actions, now having some issues with gpg key usage during release of che-server

@nickboldt nickboldt modified the milestones: 7.24, 7.25 Jan 8, 2021
@ibuziuk
Copy link
Member

ibuziuk commented Jan 11, 2021

@mkuznyetsov @nickboldt are the maven artifacts available on the central? is the release status correctly reflected in the issue?

@mkuznyetsov
Copy link
Contributor

mkuznyetsov commented Jan 11, 2021

@ibuziuk maven artifacts should be available, in fact the release is complete on our side, only waiting for community operator approval

@ibuziuk
Copy link
Member

ibuziuk commented Jan 11, 2021

@mkuznyetsov Currently I can not build Hosted Che against 7.24.0 - Could not find artifact org.eclipse.che:che-parent:pom:7.24.0

Installing all dependencies lasted 265 seconds.
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) Maven home: /opt/apache-maven Java version: 11.0.9.1, vendor: Red Hat, Inc., runtime: /usr/lib/jvm/java-11-openjdk-11.0.9.11-2.el7_9.x86_64 Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "3.10.0-1160.11.1.el7.x86_64", arch: "amd64", family: "unix"
Running devtools-rh-che-rh-che-prcheck-dev.rdu2c.fabric8.io PR: #2026, build number #3144 for che-version:[ERROR] [ERROR] Some problems were encountered while processing the POMs: [FATAL] Non-resolvable parent POM for com.redhat.che:fabric8-ide-parent:1.0.0-SNAPSHOT: Could not find artifact org.eclipse.che:che-parent:pom:7.24.0 in ossrh (https://oss.sonatype.org/content/repositories/snapshots/) and 'parent.relativePath' points at wrong local POM @ line 17, column 13 @ [ERROR] The build could not read 1 project -> [Help 1] [ERROR] [ERROR] The project com.redhat.che:fabric8-ide-parent:1.0.0-SNAPSHOT (/root/payload/pom.xml) has 1 error [ERROR] Non-resolvable parent POM for com.redhat.che:fabric8-ide-parent:1.0.0-SNAPSHOT: Could not find artifact org.eclipse.che:che-parent:pom:7.24.0 in ossrh (https://oss.sonatype.org/content/repositories/snapshots/) and 'parent.relativePath' points at wrong local POM @ line 17, column 13 -> [Help 2] [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/ProjectBuildingException [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException

Central link - https://mvnrepository.com/artifact/org.eclipse.che/che-parent

@mkuznyetsov
Copy link
Contributor

@ibuziuk the root artifact has been renamed to che-server
https://mvnrepository.com/artifact/org.eclipse.che/che-server

@ibuziuk
Copy link
Member

ibuziuk commented Jan 11, 2021

@mkuznyetsov hmmm.. missed it somehow, could you clarify why this was done and how was it announced?

@mkuznyetsov
Copy link
Contributor

@ibuziuk this looks like PR where it was done
#18639

as for announcements, I can't tell since I wasn't aware of it too.

@ibuziuk
Copy link
Member

ibuziuk commented Jan 11, 2021

@skabashnyuk can you shed some light on it ? ;-)

@nickboldt
Copy link
Contributor Author

nickboldt commented Jan 11, 2021

FWIW, I was surprised by the change and had to work around it in crw root pom too. :)

redhat-developer/devspaces@6ff95b8

Note too that the evil license checker plugin may break your build if your copyright dates are not up to date. That was also a fun change. :|

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/release Issue dedicated to a release (content, status, related PR, go/nogo/problem discussion, etc.)
Projects
None yet
Development

No branches or pull requests

3 participants