Am 01/20/17 um 00:30 schrieb Christian Schulte: > Am 01/20/17 um 00:09 schrieb Anton Tanasenko: >> New ITs should run successfully against 3.3.9 and 3.5.0-SNAPSHOT+changes. >> It doesn't make sense to test a feature which is not in. > > The Maven core master branch of the maven-jenkinsfile job is at > 3.5.0-SNAPSHOT. If the updated ITs are run (from the MNG-5958 branch) > against that master branch (without the MNG-5958 changes) instead of the > MNG-5958 branch, the ITs would fail. That would be expected. Showing the > updated ITs do run successfully against 3.5.0-SNAPSHOT means they need > to run from the MNG-5958 branch against the core MNG-5958 branch. If we > want to show that the updated ITs still run successfully against 3.3.9 > in addition, we would need to add that to the pipeline (run the updated > ITs from the MNG-5958 branch against Maven 3.3.9 instead of > 3.5.0-SNAPSHOT). That would make sense. I would not mind if this job > takes 3 days to complete. > > Regards, >
While at it: Adding the plugin ITs to that pipeline also makes a lot of sense. So that the core integration testing ITs need to succeed and all plugin ITs also need to succeed. There is this minor issue that you will build the trunk of the plugins for this to have an easy setup. Otherwise you would need to update that Jenkinsfile whenever a new plugin is released to the most recent tag. Well. Maybe all released versions of all plugins. I also would not mind if this job takes a whole month to complete. Hmm. Ok. That'd be a bit too long. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
