-
Notifications
You must be signed in to change notification settings - Fork 51
Updating to the latest 7.0.0-RC-2.0
upstream version
#1445
Conversation
@ibuziuk The che server [build 1555] has been successfully deployed. |
[test] |
@ibuziuk The che server [build 1558] has been successfully deployed. |
[test] |
@ibuziuk The che server [build 1561] has been successfully deployed. |
[test] |
@ibuziuk The che server [build 1565] has been successfully deployed. |
[test] |
@ibuziuk The che server [build 1568] has been successfully deployed. |
[test] |
@ibuziuk The che server [build 1570] failed.If the build or deployment fails, the artifacts will not be present. Don't panic, just grab a towel. |
[test] |
@ibuziuk The che server [build 1572] has been successfully deployed. |
[test] |
@ibuziuk The che server [build 1576] has been successfully deployed. |
[test] |
@ibuziuk The che server [build 1577] failed.If the build or deployment fails, the artifacts will not be present. Don't panic, just grab a towel. |
[test] |
@ibuziuk The che server [build 1579] failed.If the build or deployment fails, the artifacts will not be present. Don't panic, just grab a towel. |
@Katka92 @ScrewTSW looks like there were changes in upstream and RC2 update started to fail:
|
[test] |
@ibuziuk The che server [build 1580] failed.If the build or deployment fails, the artifacts will not be present. Don't panic, just grab a towel. |
@ibuziuk The che server [build 1582] failed.If the build or deployment fails, the artifacts will not be present. Don't panic, just grab a towel. |
[test] |
@ibuziuk The che server [build 1583] has been successfully deployed. |
[test] |
@ibuziuk The che server [build 1592] has been successfully deployed. |
@ibuziuk Note that before merging this PR we should double check upstream dashboard changes; we're currently overriding upstream functionality in an unintended way -- I'll take a closer look. |
I've added a commit to adapt upstream devfile changes to this PR, but haven't had a chance to test it much. The relevant upstream PR: eclipse-che/che#13469 |
7.0.0-RC-2.0
upstream version7.0.0-RC-2.0
upstream version
Prod is updated to CR 1.1 - so we are ready to promote CR 2 to prod-preview |
Update downstream overridden 'create workspace' page to match upstream changes around devfile-based workspaces. See commits b197f3d85f and 98062a88f7 from upstream for details. Signed-off-by: Angel Misevski <amisevsk@redhat.com>
Signed-off-by: Angel Misevski <amisevsk@redhat.com>
912e0a2
to
185aac7
Compare
@ibuziuk The che server [build 1620] failed.If the build or deployment fails, the artifacts will not be present. Don't panic, just grab a towel. |
@rhopp @Katka92 so, looks like che 7 tests are using dashboard UI:
I believe the PR check tests need to be updated to use new devfile based apporach |
[test] |
1 similar comment
[test] |
@ibuziuk The che server [build 1621] failed.If the build or deployment fails, the artifacts will not be present. Don't panic, just grab a towel. |
@ibuziuk The che server [build 1641] has been successfully deployed. |
@ibuziuk Once this PR is merged, tests against production will fail due to the change in test. If the update on production will come e.g. next day after update on prod-preview, I think we can be OK with that. If you expect few days between updating prod-preview and prod, I would assume to add switch to the test. |
@Katka92 we will update prod only with GA version, so in the meantime, I would propose to merge this PR and start testing the latest version of upstream Che ASAP and adjust prod test suite to use stacks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By merging that, Che 7 test against prod-preview production will be broken. Issue is known and @tdancs will work on that ASAP. +1 for merge.
@ibuziuk Sorry, my fault, I fixed my comment. |
@Katka92 ok, but is it a blocker for merging the PR. We could simply merge and fix the prod periodic tests separately? |
Sure, that's why I wrote +1 for merging that PR. I hope that tomorrow we will have PR with the fix merged, so we will loose only 1 day of reports. |
What does this PR do?
Updating to the latest
7.0.0-RC-2.0
upstream versionWhat issues does this PR fix or reference?
#1444
How have you tested this PR?
PR check against dev cluster