Deploying java application on remote server

[drapo91]

Hi,

I would like to set up continous deployment enviroment on bitbucket.

I have simple java web app which is running on my remote server (raspberry pi with tomcat container). Now I would like to automatize process of deploying it on the server each time I push new changes to the bitbucket repository.

In documentation I founded only deployment tutorial for app hosted on heroku. 

I would appreciate for some advices.

Lukasz

[Alexey Matveev]

Hello,

You can automate deployment with Bitbucket. You can use Bitbucket Cloud if your remote server is available from the internet. You can use Bitbucket pipelines and Bitbucket deployments. You can read more here:

https://confluence.atlassian.com/bitbucket/bitbucket-deployments-940695276.html

https://confluence.atlassian.com/bitbucket/bitbucket-deployments-940695276.html

[Jon Enriquez]

I was able to run this using:

    - mvn tomcat7:redeploy

Instead of ‘deploy’

[drapo91]

Thank you for your answer.

Now my pipeline looks as below:

image: maven:3.3.9

pipelines:
  default:
    - step:
        caches:
          - maven
        script: 
          - mvn -B verify 
     - step:
        name: Deploy to production
        deployment: production
        script:
          - mvn tomcat7:deploy

But now I am reciving following error during deployment step:

Failed to execute goal org.apache.tomcat.maven:tomcat7-maven-plugin:2.2:deploy (default-cli) on project diagnostykadermatologiczna: Cannot invoke Tomcat manager: Connection reset

Its is probably because I need to specify tomcat server credentials in maven settings.xml file (I need to do that when I was deploying from my local computer). 

So my question is how can I override default maven settings.xml which is used in pipeline?

I found under following link that I can create settings.xml file in the root of my project and push it to bitbucket repo and then use:

- mvn -s settings.xml

But it didnt work for me and failed with error:

No goals have been specified for this build. You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: validate, initialize, generate-sources, etc...

Thanks,

Lukasz