Release & deployment v2 #19

New Issue

2022-05-10T21:22:26+02:00

MK13 commented

2022-05-10 21:22:26 +02:00

(Migrated from 77zzcx7.de)

So the previous approach of #8, #9, #15 and #18 did not work as expected. So the new idea is more simple:

Keep the release plugin and corresponding Jenkins config in place but the release job will not trigger the deployment
Instead, it will just build the release and upload it to reposilite
Then, there should be documentation explaining the deployment process:
** Provide a systemd service that can be tuned
** Provide a script that downloads a given version from reposilite and copies it to the location specified. It can then also daemon-reload and restart on behalf of the user
Add support to reads config files from e.g. /etc (--spring.config.additional-location="file:///etc/nbscloud/blabla.properties")

This is also more to like a "real" OS package. So in the future there could be a job to build e.g. a PKGBUILD for Arch based on this approach.

So the previous approach of #8, #9, #15 and #18 did not work as expected. So the new idea is more simple: * Keep the release plugin and corresponding Jenkins config in place but the release job will not trigger the deployment * Instead, it will just build the release and upload it to reposilite * Then, there should be documentation explaining the deployment process: ** Provide a systemd service that can be tuned ** Provide a script that downloads a given version from reposilite and copies it to the location specified. It can then also `daemon-reload` and `restart` on behalf of the user * Add support to reads config files from e.g. `/etc` (`--spring.config.additional-location="file:///etc/nbscloud/blabla.properties"`) This is also more to like a "real" OS package. So in the future there could be a job to build e.g. a `PKGBUILD` for Arch based on this approach.

MK13 commented

2022-05-11 22:21:39 +02:00

(Migrated from 77zzcx7.de)

Just released and deployed v15 with this approach and it works better than the more sophisticated one before.

Solved.

Just released and deployed v15 with this approach and it works better than the more sophisticated one before. Solved.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: MK13/NoBullShit-cloud#19