Open cleanerx opened 7 years ago
Why don't you just issue a mvn deploy
command?
I thought the jenkins plugin would atomically deploy artifacts when everything has been built successfully. A mvn deploy does upload artifacts right away, doesn't it? Or do I need to do a maven deploy to the local repository and upload artifacts from that repository via the plugin ?
That is right. You can also deploy the zipped P2 repository.
My missing bits and pieces were the details from here with respect how to setup nexus p2 upload functionality. http://www.vogella.com/tutorials/EclipseTycho/article.html Especially the "don't deploy everything" setting in the parent pom and deploy the p2 project setting was the thing I thought was worth to mention.
Did I oversee that in the documentation or is it missing somehow ?
I don't know what you mean. This article seems to target Nexus. However this is package drone. I don't really know Nexus, so I can't really help here.
The configuration setup for a tycho generated p2 repository that is uploaded to nexus is pretty much the same and can be used for package drone as well. So I suggest to add that to the documentation like: If you want to build with tycho and push p2 repository zips to package drone this procedure applies to package drone as well.
A mvn deploy does upload artifacts right away, doesn't it? Yes by default, no if you setup deployAtEnd to true
Any way any documentation about pdrone server part is not related to this jenkins plugin
I want to deploy tycho generated artifacts to package drone via the Jenkins plugin.
Either I'm missing the correct configuration or the feature is missing.
If I do a maven clean deploy I get timestamped data. If I upload the files via a */.jar filter I get snapshot versions.
This issue is therefor either one of a) Document the Feature b) Implement P2 aware upload functionality