ci-cd for nodejs application

[ajoysinhactc]

If I run following command to generate jenkinsfile .

jhipster ci-cd --blueprints nodejs

Jenkinsfile is generated but it is not for nodejs application, rather than it is for java application.
It seems to me that ci-cd for nodejs application has not been implemented yet.

Following are the comment out of execution of generator command.

INFO! No custom commands found within blueprint: generator-jhipster-nodejs
INFO! Using JHipster version installed locally in current project's node_modules
INFO! No custom commands found within blueprint: generator-jhipster-nodejs
INFO! Executing jhipster:ci-cd
INFO! Options: blueprints: nodejs, from-cli: true
🚀 Welcome to the JHipster CI/CD Sub-Generator 🚀
? What CI/CD pipeline do you want to generate? Jenkins pipeline
? Would you like to perform the build in a Docker container ? Yes
? Would you like to send build status to GitLab ? Yes
? What tasks/integrations do you want to include ? Build and publish a Docker image
identical Jenkinsfile
identical src\main\resources\idea.gdsl
identical src\main\docker\jenkins.yml
identical src\main\docker\docker-registry.yml
INFO! Congratulations, JHipster execution is complete!

[ghost]

Hi @ajoysinhactc, thanks for the issue!
Yes, the blueprint does not implement ci-cd submodule, so the command that you have run use the standard jhipster generation. If you want to contribute with the development or a donation you are welcome!

[ghost]

@mraible I'm trying to customize ci-cd subgenerator, but I note that the jhipster ci-cd index.js file extends the generator-base, and not the generator-base-blueprint. So when I perform the jhipster --blueprints nodejs ci-cd command, always the jhipster ci-cd generator is called. Do you know a method to rewrite that? Thanks in advance.

[ghost]

The development is stopped because we need before to update to jhipster 7

[ghost]

$200 bug bounty claim: https://opencollective.com/generator-jhipster/expenses/47076

[pascalgrimaud]

@amanganiello90 : approved