-
Notifications
You must be signed in to change notification settings - Fork 57
Updating to the latest upstream '7.0.0-rc-4.0' version #1481
Conversation
@ibuziuk The che server [build 1651] has been successfully deployed. |
From the
But I haven't looked into it further. |
[test] |
@ibuziuk The che server [build 1679] failed.If the build or deployment fails, the artifacts will not be present. Don't panic, just grab a towel. |
Currently failing with:
|
@ibuziuk The che server [build 1680] 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 1681] 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 1682] failed.If the build or deployment fails, the artifacts will not be present. Don't panic, just grab a towel. |
[test] |
Failing on functional tests, which isn't surprising since the dashboard has changed in |
@ibuziuk The che server [build 1685] failed.If the build or deployment fails, the artifacts will not be present. Don't panic, just grab a towel. |
@ScrewTSW @Katka92 could you please investigate the test failures - https://ci.centos.org/job/devtools-rh-che-rh-che-prcheck-dev.rdu2c.fabric8.io/1685/console |
57915f4
to
c1a5951
Compare
PR is ready for review. Once test are fixed we will be able to promote |
@ibuziuk The che server [build 1698] 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 1701] 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 1702] failed.If the build or deployment fails, the artifacts will not be present. Don't panic, just grab a towel. |
Ok, looks like we need to update the build due to the initial cleanup of Che 6 legacy code - eclipse-che/che#13788 |
c1a5951
to
e522a22
Compare
Signed-off-by: Ilya Buziuk <ibuziuk@redhat.com>
…web.xml Signed-off-by: Ilya Buziuk <ibuziuk@redhat.com>
Signed-off-by: Ilya Buziuk <ibuziuk@redhat.com>
…ies' due to removal of the 'che-core-dynamodule-maven-plugin' Signed-off-by: Ilya Buziuk <ibuziuk@redhat.com>
Signed-off-by: Ilya Buziuk <ibuziuk@redhat.com>
Signed-off-by: Angel Misevski <amisevsk@redhat.com>
@ibuziuk The che server [build 1716] failed.If the build or deployment fails, the artifacts will not be present. Don't panic, just grab a towel. |
- Remove modules deprecated alongside removal of che6 legacy code - Update fabric8-ide-assembly-ide-war to use upstream assembly-root-war Signed-off-by: Angel Misevski <amisevsk@redhat.com>
4326a31
to
bce228b
Compare
@ibuziuk The che server [build 1717] 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 1718] failed.If the build or deployment fails, the artifacts will not be present. Don't panic, just grab a towel. |
Restore wsmaster analytics plugin as it provides a required endpoint for RhCheKeycloak.js Signed-off-by: Angel Misevski <amisevsk@redhat.com>
@ibuziuk The che server [build 1719] failed.If the build or deployment fails, the artifacts will not be present. Don't panic, just grab a towel. |
Signed-off-by: Angel Misevski <amisevsk@redhat.com>
@ibuziuk The che server [build 1720] has been successfully deployed. |
@@ -48,7 +41,7 @@ | |||
</dependency> | |||
<dependency> | |||
<groupId>org.eclipse.che</groupId> | |||
<artifactId>assembly-ide-war</artifactId> | |||
<artifactId>assembly-root-war</artifactId> |
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.
maybe it makes sense to rename the folder also to assembly-root-war
to make it consistent ?
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.
we could probably consider renaming as part of another PR
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.
I'm +1 on renaming, I didn't do it here to avoid messing with the build too much at once.
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.
agree PR was already BIG, we could handle it separately
…lugin-analytics-wsagent' deprecation Signed-off-by: Ilya Buziuk <ibuziuk@redhat.com>
@ibuziuk The che server [build 1722] has been successfully deployed. |
Signed-off-by: Ilya Buziuk <ibuziuk@redhat.com>
What does this PR do?
Updating to the latest upstream '7.0.0-rc-4.0' version
What issues does this PR fix or reference?
#1489
How have you tested this PR?
PR check CI