version control - automatic, implicit, easy and reliable source revision indicator for maven+jenkins multi-module SNAPSHOT builds? -


I currently have a set of Maven modules, whose versions are set to 1.0-SNAPSHOT, which specifies the current trunk Are there. Those modules are made individually inside Jenkins, share the same SVN repo, but do not share any checkout, so I can not take svn amendment of checkout modification of build - and this has become my main problem : I usually wait for all the activities to stop in Jenkins and everything is green (or blue), so I know that everything is fine and SVN research of the final production product All sources of trunk-based modules are in line with the revision.

If you can not follow me to this point, please tell me.

Is there any way to improve it, that is, make it more automatic? Two possible disadvantages I can see with that solution: First of all, the Jenkins dependency proposal may be broken, etc.. This can lead to an incompatible mapping between the last product modification and possibly the old dependency modification (because their construction was not triggered). Second, there may be some race between final product creation and a new source svn commit.

Question: How do you go about it? Yes, I know, it will be cleaner to use clear release management, but because the builds will not leave some internal division, it seems that this is an unnecessary overhead. Is there any way to disseminate all the dependencies' SVN modification in the final product creation using something similar to the SVN modification of each module and using something similar to "MVN Dependence: Trees"? Is it possible to provide a source code modification to snapshot versions without changing the snapshot version references?

Update:

There is some solution for storing svn amendment inside the manifest etc. However, there is some flaw in this: How can I ensure that these modifications are included in the final creation?

Ideally, the svn modification "1.0-SNAPSHOT" revision identifier will be added, i.e. "1.0-SNAPSHOT-4783", however, breaks the ability to refer to the latest snapshot build using "1.0-SNAPSHOT" on dependent modules ... i ... 1.0-SNAPSHOT in the dependent module to refer to SAPASH bills ], But it seems that such snapshot identifier is not considered by SNAPSHOT by Nexus (I can not deploy them to snapshot repo).


Comments

Popular posts from this blog

Editing Python Class in Shell and SQLAlchemy -

import - Python ImportError: No module named wmi -

uislider - In a MATLAB GUI, how does one implement a continuously varying slider from a GUIDE created .m file? -