tracker.org
This commit is contained in:
parent
102dddb7ce
commit
45ff5526ed
1 changed files with 8 additions and 4 deletions
12
tracker.org
12
tracker.org
|
@ -2069,13 +2069,17 @@ We have a change that will imply a change in how we deploy our app.
|
|||
We would like to use the code from Dar's team.
|
||||
So mainly they just need to provide assets (js, html, css, imgs, etc…)
|
||||
|
||||
The behavior we would like is:
|
||||
We would like to use:
|
||||
|
||||
- On INT, use the `master` branch of their repo,
|
||||
- On TEST/PROD, use the matching release branch of their repo.
|
||||
|
||||
On INT, use their `master` branch.
|
||||
On TEST/PROD, use the matching release branch of their repo.
|
||||
|
||||
One option is to ask them to deploy a new `SNAPSHOT` versionned jar for
|
||||
every commit in master and depend on it, and ask them to deploy a release
|
||||
version of the jar for the release branch.
|
||||
|
||||
I think it would be a lot easier if could depend directly on a git
|
||||
specific commit. Ambrose I think you did touch something like that.
|
||||
|
||||
|
||||
**** MEETING Registration Simplification Weekly :work:meeting:
|
||||
|
|
Loading…
Reference in a new issue