You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reason will be displayed to describe this comment to others. Learn more.
I am pretty sure that guvnor depends on droolsjbpm-integration and therefore it needs to be build be before guvnor. It's strange though that guvnor is build before drools-wb?
On 25 Jul 2013 19:35, "Geoffrey De Smet" ***@***.*** wrote:
cc @manstishttps://github.com/manstis
—
Reply to this email directly or view it on GitHubhttps://github.com/droolsjbpm/droolsjbpm-build-bootstrap/commit/aedf4d88875edfd09af0074d47630b57ba9df4b2#commitcomment-3718940
.
The reason will be displayed to describe this comment to others. Learn more.
Thank for the info
@mbiarnes Since the repository list order has changed, the jenkins jobs triggering must change accordingly. When a jenkins jobs successfully builds, it is configured to build downstream projects. For example, when drools successfully builds, it triggers a jbpm build (because changes in drools can break jbpm (even though there are no changes in jbpm and therefore the jbpm job wouldn't start on it's own).
The jenkins job "jbpm" triggered "droolsjbpm-integration" which triggered "guvnor" - that order needs to be adjusted so it's in sync with the repository-list.txt.
aedf4d8There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am pretty sure that guvnor depends on droolsjbpm-integration and therefore it needs to be build be before guvnor. It's strange though that guvnor is build before drools-wb?
aedf4d8There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cc @manstis
aedf4d8There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
aedf4d8There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank for the info
@mbiarnes Since the repository list order has changed, the jenkins jobs triggering must change accordingly. When a jenkins jobs successfully builds, it is configured to build downstream projects. For example, when drools successfully builds, it triggers a jbpm build (because changes in drools can break jbpm (even though there are no changes in jbpm and therefore the jbpm job wouldn't start on it's own).
The jenkins job "jbpm" triggered "droolsjbpm-integration" which triggered "guvnor" - that order needs to be adjusted so it's in sync with the repository-list.txt.
aedf4d8There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I 've extracted that jenkins issue in a separate jira for mbiarnes and explained it better: https://issues.jboss.org/browse/DROOLS-203