Hi Vitalii, Florent, Yevhen & all
I was looking at this a bit and I see we have already
place to push our npm packages to. When I was looking at how packages get there, I see they get published by
this job - and it's just packages from che-theia repo.
What we would like to do is to have the package from eclipse/che repo, e2e directory published there as well (ideally as part of nigtly builds & release builds). What's the easiest and best way to do this?
What I've thought of so far is something like this:
1) We will add `e2e` folder as mvn module - meaning we will have also pom.xml in the `e2e` folder, which will just do something like `npm build` on compile phase and `npm publish` on install phase. (Ugh... I don't like that already - mixing mvn & npm :-D). This way, the npm package should be built & published as part of each build.
2) Somebody with rights to edit jenkins jobs will add credentials for pushing to eclipse-che space in npm registry (`NPM_AUTH_TOKEN` from jenkins secrets store) to che nightly & release builds.
I'm aware the build part is a bit tricky, as it has to be done in docker container to ensure all dependencies are present (basically the same way dashboard is being built right now) and also there would have to be some logic to not push to npm registry, when credentials are not provided...
Does this plan sound ok? Who should we cooperate on editing the jenkins job config? Is it you, Vitalii?
Thanks
Radim