Le samedi 10 février 2018, 00:10:14 CET Olivier Lamy a écrit :
> Policy: snaphots from master branches (and possibly long lived maintenance
> branches) are deployed automatically.
+1
for long lived branches, the version must have some differentiator from master
>
> Build setup: downstream
Policy: snaphots from master branches (and possibly long lived maintenance
branches) are deployed automatically.
Build setup: downstream projects must be build after a master build and
deploy.
On 9 February 2018 at 13:03, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Write down
Write down the policy you would like
On 9 February 2018 at 12:25, Olivier Lamy wrote:
> On 9 February 2018 at 12:01, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > Document what you think the policy should be and we'll go from there.
> >
> > My (current)
On 9 February 2018 at 12:01, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Document what you think the policy should be and we'll go from there.
>
> My (current) preferred policy is:
>
> There is no automatic deployment of snapshots. Developers can manually
> publish snapshots
Document what you think the policy should be and we'll go from there.
My (current) preferred policy is:
There is no automatic deployment of snapshots. Developers can manually
publish snapshots on an as needed basis and if they require downstream
builds to pick those up then they need to
Perso I don't want anything else than master deployed..
wip feature branch doesn't make really sense to be deployed.
and makes our life easier :-)
On 9 February 2018 at 07:40, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> I personally think there are a lot of issues with CI