search

qbicsoftware / parent-poms

We keep all parent POMs under this single repository.
2 stars 1 forks source link

Add .travis.yml to automate deployment of poms #1

Closed chahuistle closed 6 years ago

chahuistle commented 6 years ago

I am getting tired of deploying every single time I make a change, so this should be automated under the assumption that releases come only from the master branch and snapshots come only from the development branch.

Zethson commented 6 years ago

I suggest that snapshots come from the testing branch. So far the development branch has been the branch on which every kind of version has been at some point, on testing only versions which should be deployable on portal-testing are pushed.

So: master - release testing - snapshots development - nothing

chahuistle commented 6 years ago

Good idea. I was not aware that the automatic deployment from Jenkins was done globally and that this was part of QBiC's process, thank you!

I took the liberty of creating a separate issue as a bug, because this is not an enhancement: it would break the build process if released as is!

See: https://github.com/qbicsoftware/portlet-template/issues/43

On Mon, May 14, 2018 at 4:45 PM Lukas Heumos notifications@github.com wrote:

I suggest that snapshots come from the testing branch. So far the development branch has been the branch on which every kind of version has been at some point, on testing only versions which should be deployable on portal-testing are pushed.

So: master - release testing - snapshots development - nothing

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/qbicsoftware/parent-poms/issues/1#issuecomment-388843180, or mute the thread https://github.com/notifications/unsubscribe-auth/ABd0peXOvVoYPr7CZpgIjluQiQwB42Btks5tyZiVgaJpZM4T2-2J .

chahuistle commented 6 years ago

Taken care of in https://github.com/qbicsoftware/cookiecutter-templates-cli