#834  Automated build for a project with many repositories
Closed
Artur opened 2 weeks ago

Hi,

Our software code for the Tigase XMPP Server is split into multiple reopsitories. We have one main repo with the core server code and then many repositories with components, extensions and so on.

How would you suggest to handle automated builds of the server if there is a code change in a component repository?

Robin Shen commented 2 weeks ago

How does your server code pull artifacts of component/extension code? For instance, in OneDev, it is done via Maven dependency.

Artur commented 2 weeks ago

I think it is gradle or something like this. But, I guess it does not really matter.

The thing is, when we push to the component, the component code can be automatically built on the push. Now, can we trigger a build in some other project then? I mean the master project to build the server package.

Robin Shen commented 2 weeks ago

You may trigger other builds with the post-build action.

Robin Shen changed state to 'Closed' 1 week ago
Previous Value Current Value
Open
Closed
issue 1 of 1
Type
Support Request
Priority
Normal
Assignee
Issue Votes (0)
Watchers (4)
Reference
issue onedev/server#834
Please wait...
Page is in error, reload to recover