Successfully deployed but link does not change

[drawanz]

Hey guys, needing some help in a particular issue that I am facing...

I am responsible for deploying a new version of an app in my job, the app is already on and working fine on a AWS machine t3a.small.

I have connected into the AWS instance and have add the dokku remote on my local machine, as I try to push, I am receiving this:

git push dokku master                             
Enumerating objects: 15, done.
Counting objects: 100% (15/15), done.
Delta compression using up to 12 threads
Compressing objects: 100% (6/6), done.
Writing objects: 100% (8/8), 613 bytes | 613.00 KiB/s, done.
Total 8 (delta 3), reused 0 (delta 0), pack-reused 0
-----> Cleaning up...
-----> Building jobcenter from Dockerfile
remote: build context to Docker daemon  25.03MB
Step 1/10 : FROM openjdk:8-jdk-alpine
 ---> a3562aa0b991
Step 2/10 : ARG JAR_FILE=build/libs/job_center.jar
 ---> Using cache
 ---> 4012d42131c8
Step 3/10 : COPY ${JAR_FILE} app.jar
 ---> Using cache
 ---> 53d244ad6a2c
Step 4/10 : ENTRYPOINT ["java","-jar","/app.jar"]
 ---> Using cache
 ---> b9477e3d8afa
Step 5/10 : LABEL com.dokku.app-name=XXX
 ---> Using cache
 ---> 04394e2af4b9
Step 6/10 : LABEL com.dokku.builder-type=dockerfile
 ---> Using cache
 ---> 7c4ede0fe759
Step 7/10 : LABEL com.dokku.image-stage=build
 ---> Using cache
 ---> d80249de9c61
Step 8/10 : LABEL dokku=
 ---> Using cache
 ---> f2bd4dbf8ce1
Step 9/10 : LABEL org.label-schema.schema-version=1.0
 ---> Using cache
 ---> d89d3d1efcfe
Step 10/10 : LABEL org.label-schema.vendor=dokku
 ---> Using cache
 ---> 966f4ec44ad8
Successfully built 966f4ec44ad8
Successfully tagged dokku/XXX:latest
-----> Releasing XXX...
-----> Checking for predeploy task
       No predeploy task found, skipping
-----> Checking for release task
       No release task found, skipping
-----> No Procfile found in app image
=====> Processing deployment checks
       No CHECKS file found. Simple container checks will be performed.
       For more efficient zero downtime deployments, create a CHECKS file. See https://dokku.com/docs/deployment/zero-downtime-deploys/ for examples
-----> Deploying XXX via the docker-local scheduler...
-----> Deploying web (count=1)
       Attempting pre-flight checks (web.1)
       Waiting for 10 seconds (web.1)
       Default container check successful (web.1)
       Scheduling old container shutdown in 60 seconds (web.1)
-----> Running post-deploy
-----> Configuring XXX...(using built-in template)
-----> Creating https nginx.conf
       Enabling HSTS
       Reloading nginx
-----> Renaming containers
       Found previous container(s) (1edf71073882) named XXX.web.1
       Renaming container (1edf71073882) XXX.web.1 to XXX.web.1.1664538544
       Renaming container XXX.web.1.upcoming-10301 (dd93cb2f7b75) to XXX.web.1
-----> Checking for postdeploy task
       No postdeploy task found, skipping
-----> Shutting down old containers in 60 seconds
=====> Application deployed:
       http://XXX
       https://XXX

To 18.231.160.0:XXX
   aef68b3..a40f584  master -> master

The app is using this Dockerfile:

FROM openjdk:8-jdk-alpine
ARG JAR_FILE=build/libs/job_center.jar
COPY ${JAR_FILE} app.jar
ENTRYPOINT ["java","-jar","/app.jar"]

The problem is: When I went to check if the new version was online, the URL's deploy was showing the old application, don't know how to procede from here.

PS: I have already try to clean the cache on the dokku's app server.

The XXX are sensitive information

[josegonzalez]

Is the file build/libs/job_center.jar changing in any commit? If not, the COPY won't bust cache.