let Tycho/Jenkins build fail when p2 site doesn't exist -
i have rcp application build in jenkins using "mvn clean verify" run maven/tycho. when target platform of application contains p2 repository site not available anymore, tycho prints warning still uses it's local cache.
[warning] failed access p2 repository http://download.eclipse.org/technology/babel/update-site/r0.11.1/indigo, use local cache. neither http://download.eclipse.org/technology/babel/update-site/r0.11.1/indigo/content.jar nor http://download.eclipse.org/technology/babel/update-site/r0.11.1/indigo/content.xml found. it took quite time notice problem because jenkins build succeeds without issues , not going read console output...
i notified of issue can take measures when repository moved or deleted. tycho should still use it's cache under normal circumstances.
can solve using jenkins or can instruct tycho fail fast (drawback: fails on temporary outage)?
to partly answer question best solution set local p2 mirror, think requires lot more work.
you can mark jenkins build unstable or failed based on it's output using jenkins text finder plugin.
- manage jenkins plugins , install text finder plugin available plugins.
- edit project add post-build action "jenkins text finder".
- check 'also search console output', set regular expression 'failed access p2 repository' , check 'unstable if found'.
Comments
Post a Comment