Hi,
We have a project split in two components: core and application where application depends on core. For both we have configured on-commit builds to run tests.
We use gradle to build these components and there's a parameter that can override which version of core should the application use.
What we'd like to achieve is when there's a successful build of core (which includes a snapshot release to Artifactory) then the application component should be built as well with the latest snapshot.
Now it would be possible to duplicate the application build plan so we'd have:
- one without overriding for testing changes only on application using the last stable version of core referenced in application
- and one with overriding core version to latest snapshot to test whether changes in core does not break application.
The problem is that the build plan for application is quite extensive and might change frequently so maintaining two very similar plans is undesired. Also there are multiple projects like this so the plan maintenance overhead would be quite significant.
One solution would be if the core plan would be able to trigger the application plan with setting some sort of flag or parameter. Is this possible? (Basically an equivalent of this Jenkins plugin: https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.