This PR is meant initial support and will run the daily builds on windows environment.
The built-in git bash will be used almost everywhere.
AdoptOpenJDK 11 is currently used.
Couchbase and Cassandra tests are removed because of docker problem.
No docker-compose will be run because of docker problem.
End-To-End testing is not included this time
@pascalgrimaud I have tested this pipeline. The builds are not much stable, sometimes getting the following kind of error.
After re-running again, the builds are passed.
The entity EntityWithServiceImplPaginationAndDTO is being updated.
WARNING! This entity has the DTO option, and it has a relationship with entity "operation" that doesn't have the DTO option. This will result in an error.
WARNING! jpaMetamodelFiltering is missing in .jhipster/Label.json, using 'no' as fallback
WARNING! jpaMetamodelFiltering is missing in .jhipster/FieldTestMapstructEntity.json, using 'no' as fallback
WARNING! jpaMetamodelFiltering is missing in .jhipster/FieldTestServiceImplEntity.json, using 'no' as fallback
WARNING! jpaMetamodelFiltering is missing in .jhipster/EntityWithServiceClass.json, using 'no' as fallback
WARNING! jpaMetamodelFiltering is missing in .jhipster/EntityWithServiceImpl.json, using 'no' as fallback
WARNING! jpaMetamodelFiltering is missing in .jhipster/EntityWithServiceClassAndPagination.json, using 'no' as fallback
WARNING! jpaMetamodelFiltering is missing in .jhipster/EntityWithServiceImplAndPagination.json, using 'no' as fallback
WARNING! jpaMetamodelFiltering is missing in .jhipster/EntityWithServiceClassAndDTO.json, using 'no' as fallback
WARNING! jpaMetamodelFiltering is missing in .jhipster/EntityWithServiceImplAndDTO.json, using 'no' as fallback
WARNING! jpaMetamodelFiltering is missing in .jhipster/EntityWithServiceClassPaginationAndDTO.json, using 'no' as fallback
WARNING! jpaMetamodelFiltering is missing in .jhipster/EntityWithServiceImplPaginationAndDTO.json, using 'no' as fallback
events.js:174
throw er; // Unhandled 'error' event
^
ShellJSInternalError: EEXIST: file already exists, mkdir 'C:\Users\VssAdministrator\app\src\main\resources'
at Object.mkdirSync (fs.js:752:3)
at mkdirSyncRecursive (C:\Users\VssAdministrator\generator-jhipster\node_modules\shelljs\src\mkdir.js:32:6)
at mkdirSyncRecursive (C:\Users\VssAdministrator\generator-jhipster\node_modules\shelljs\src\mkdir.js:29:3)
at mkdirSyncRecursive (C:\Users\VssAdministrator\generator-jhipster\node_modules\shelljs\src\mkdir.js:29:3)
at C:\Users\VssAdministrator\generator-jhipster\node_modules\shelljs\src\mkdir.js:81:9
at Array.forEach (<anonymous>)
at Object._mkdir (C:\Users\VssAdministrator\generator-jhipster\node_modules\shelljs\src\mkdir.js:59:8)
at Object.mkdir (C:\Users\VssAdministrator\generator-jhipster\node_modules\shelljs\src\common.js:384:25)
at module.exports.generateKeyStore (C:\Users\VssAdministrator\generator-jhipster\generators\generator-base.js:1488:21)
at module.exports.setUp (C:\Users\VssAdministrator\generator-jhipster\generators\server\files.js:1750:18)
Emitted 'error' event at:
at Immediate.setImmediate (C:\Users\VssAdministrator\generator-jhipster\node_modules\yeoman-generator\lib\index.js:433:22)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
This PR is meant initial support and will run the daily builds on windows environment.
@pascalgrimaud I have tested this pipeline. The builds are not much stable, sometimes getting the following kind of error. After re-running again, the builds are passed.