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.23.0 #18539

Closed
7 of 12 tasks
nickboldt opened this issue Dec 4, 2020 · 9 comments
Closed
7 of 12 tasks

Release Che 7.23.0 #18539

nickboldt opened this issue Dec 4, 2020 · 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 Dec 4, 2020

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)
  • Che community operator PRs (depends on all of the above)
  • chectl (depends on all of the above)

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-plugin-registry cico_release.sh centos eclipse/che-plugin-registry
@mkuznyetsov che-devfile-registry cico_release.sh centos eclipse/che-devfile-registry
@mkuznyetsov che-parent cico_release.sh centos che-parent
@mkuznyetsov che-dashboard cico_release.sh centos che-dashboard
@mkuznyetsov che-workspace-loader cico_release.sh centos 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
@tolusha che-operator make-release.sh centos eclipse/che-operator
@tolusha chectl make-release.sh travis chectl releases
@nickboldt nickboldt added the kind/release Issue dedicated to a release (content, status, related PR, go/nogo/problem discussion, etc.) label Dec 4, 2020
@nickboldt nickboldt self-assigned this Dec 4, 2020
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Dec 4, 2020
@ibuziuk ibuziuk added team/productization and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Dec 7, 2020
@ibuziuk
Copy link
Member

ibuziuk commented Dec 7, 2020

Have added [Hosted Che] Failed to rollout 7.23.0-SNAPSHOT - Jwks endpoint url not found in keycloak #18553 to the list of pending issues

@nickboldt
Copy link
Contributor Author

E2E tests for Che 7.23.0 are failing in https://ci.centos.org/job/devtools-che-release-che-release/244/console

2020-12-10 01:12:08,649[main]             [ERROR] [s.c.u.WorkspaceDtoDeserializer 55]   - Fail to read workspace template broken_workspace.json for infrastructure /templates/workspace/openshift/broken_workspace.json because com.google.gson.stream.MalformedJsonException: Expected ':' at line 3 column 8 path $.werwerw 

[[1;34mINFO[m] Che Legacy E2E :: Test ............................. [1;31mFAILURE[m [18:13 min]
[[1;34mINFO[m] [1m------------------------------------------------------------------------[m
[[1;34mINFO[m] [1;31mBUILD FAILURE[m
[[1;34mINFO[m] [1m------------------------------------------------------------------------[m
[[1;34mINFO[m] Total time:  45:27 min
[[1;34mINFO[m] Finished at: 2020-12-10T01:30:37Z
[[1;34mINFO[m] [1m------------------------------------------------------------------------[m
[[1;31mERROR[m] Failed to execute goal [32morg.sonatype.plugins:nexus-staging-maven-plugin:1.6.7:deploy[m [1m(default-deploy)[m on project [36mche-selenium-test[m: [1;31mExecution default-deploy of goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.7:deploy failed: Staging rules failure![m -> [1m[Help 1][m

any advice?

@nickboldt
Copy link
Contributor Author

Re-ran build, and it worked. Che server released. Che operator done (except for PR merging).

@ibuziuk
Copy link
Member

ibuziuk commented Dec 15, 2020

@nickboldt Are there any community PRs opened?
It is strange that release takes such a long time, assuming that respin is planned tomorrow

@nickboldt
Copy link
Contributor Author

As noted above, https://github.com/eclipse/che-operator/actions?query=workflow%3A%22Release+community+operator+PRs%22 was set to auto-generate the PRs, but through the last day we've encountered various issues w/ tokens and permissions.

The most recent:

   - Push branch update-eclipse-che-upstream-operator-7.23.0 to https://github.com/che-incubator/community-operators.git
To https://github.com/che-incubator/community-operators.git
 ! [remote rejected]   update-eclipse-che-upstream-operator-7.23.0 -> update-eclipse-che-upstream-operator-7.23.0 (refusing to allow a Personal Access Token to create or update workflow `.github/workflows/deploy_image.yaml` without `workflow` scope)
error: failed to push some refs to 'https://github.com/che-incubator/community-operators.git'

So the plan is to explore splitting this into two actions:

See #18627

@nickboldt
Copy link
Contributor Author

@nickboldt
Copy link
Contributor Author

nickboldt commented Dec 15, 2020

I was also told recently that the chectl release does not depend on the community operators being merged (and in fact @flacatus already released chectl 7.23.0!), so we can change that via this issue:

@nickboldt
Copy link
Contributor Author

Release is done, guide is updated. Followup work in #18627

@nickboldt nickboldt added this to the 7.23 milestone Dec 16, 2020
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