[
https://issues.apache.org/jira/browse/FINCN-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juhan Aasaru updated FINCN-148:
-------------------------------
Description:
We need to build pull requests with Travis CI server to verify that there are
no compilation errors.
To build pull requests we need dependent fineract-cn- projects to be available
in Artifactory.
For these two reasons build scripts need to be configured to build pull
requests and when a pull request is merged to develop branch - new artifacts
need to be built and uploaded to artifactory to be available for dependent
projects.
I will work on this issue.
was:
In order to set up travis-ci.*com* (not travis-ci.*org* as it is deprecated!)
to build fineract-cn projects following is needed:
Someone with admin access to Github repos needs to:
1. Create travis projects for each repository:
[https://travis-ci.com/apache/fineract-cn-lang]
... all the 30+ fineract-cn-* projects ...
this step shouldn't need much configuration, just create the projects
I don't yet have access to the github projects so I cannot do it myself yet.
2. I have set up JFrog Artifactory and created user "travis-ci" there.
Once the travis projects have been created I can encode user "travis-ci"
password
with each of the public keys of these travis projects and create pull requests.
3. Once pull requests are merged github repos need to be configured to build
pull requests with Travis.
> Build fineract-cn-* projects with travis-ci.com and publish to JFrog
> Artifactory
> --------------------------------------------------------------------------------
>
> Key: FINCN-148
> URL: https://issues.apache.org/jira/browse/FINCN-148
> Project: Fineract Cloud Native
> Issue Type: Improvement
> Reporter: Juhan Aasaru
> Priority: Major
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> We need to build pull requests with Travis CI server to verify that there are
> no compilation errors.
> To build pull requests we need dependent fineract-cn- projects to be
> available in Artifactory.
> For these two reasons build scripts need to be configured to build pull
> requests and when a pull request is merged to develop branch - new artifacts
> need to be built and uploaded to artifactory to be available for dependent
> projects.
> I will work on this issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
