I'm not sure if I can provide enough information here in my first question, but I will try:
In my company we use Stash. My project is a project with several repositories (Client, Server, Common). We use Gitflow as a branching model. The modules themselves are all in Java, built through Ant, and ivy is used to manage dependencies. So far, we have used Jenkins instances "only" to run our tests and analyze static code, since the build process requires the builds to run in a dedicated environment. Therefore, we have a Jenkins instance installation to create from development. A common project is a common relationship between a server and client project. Therefore, our Jenkins projects are installed with a downstream dependency between the common → {server, client}. The general project contains a post-assembly task to publish the general assembly project to our internal company (JFrogg).This will be used during the execution of jenkins (ivy) client and server projects.
Well, hopefully this will give a good overview. Now my real question is:
We are currently playing with an invitation to a Stash Pull request so that jenkins runs assemblies for our function branches when we create a carry request for them. However, due to our dependency configuration, I want to achieve the following:
1) if we have a function branch for the same ticket (the Jira ticket number is used in the branch) in Common and (Client or Server) - first create a common one - publish the usual one with artifactory with the jira ticket number - build a request for a downstream with the correct dependency (use the just published assembly on artifactory with a specific branch)
2),
-
- artifactory jira
- "" ( )
3) :
- /, artifactory.
( ) , , , , , , .
, :
- , artifactory .
- ,
- Dependency for common , , .
- , ?
. 😉
,