CAPAUT-328 docker creation for sonarqube with oidc plugin #1

Merged

marcboehm merged 2 commits from feature/CAPAUT-328 into main 2024-09-15 09:07:17 +02:00

Conversation 5 Commits 2 Files Changed 3 +15

tobiaslehmann commented 2024-09-13 13:59:08 +02:00

Contributor

Copy Link

No description provided.

marcboehm was assigned by tobiaslehmann 2024-09-13 13:59:08 +02:00

tobiaslehmann added 1 commit 2024-09-13 13:59:08 +02:00

CAPAUT-328 docker creation for sonarqube with oidc plugin 5017c87b45

marcboehm commented 2024-09-14 09:38:09 +02:00

Owner

Copy Link

Could you download the plugin within the docker file? You can simply run a wget or curl command to pull the file directly into the image plugin directory. This build is not bound to any other projects build process. In this case we can use the download.

If curl or wget is not present in the parent sonar image just use apt to install it. It is very likly that the image is based on an Debian derivat

>Could you download the plugin within the docker file? You can simply run a wget or curl command to pull the file directly into the image plugin directory. This build is not bound to any other projects build process. In this case we can use the download. If curl or wget is not present in the parent sonar image just use apt to install it. It is very likly that the image is based on an Debian derivat

tobiaslehmann added 1 commit 2024-09-14 12:07:38 +02:00

CAPAUT-438 using curl instead of plugin binary cd3349cefe

tobiaslehmann commented 2024-09-14 12:08:27 +02:00

Author

Contributor

Copy Link

Could you download the plugin within the docker file? You can simply run a wget or curl command to pull the file directly into the image plugin directory. This build is not bound to any other projects build process. In this case we can use the download.

If curl or wget is not present in the parent sonar image just use apt to install it. It is very likly that the image is based on an Debian derivat

fixed

> >Could you download the plugin within the docker file? You can simply run a wget or curl command to pull the file directly into the image plugin directory. This build is not bound to any other projects build process. In this case we can use the download. > > If curl or wget is not present in the parent sonar image just use apt to install it. It is very likly that the image is based on an Debian derivat fixed

marcboehm commented 2024-09-15 08:29:39 +02:00

Owner

Copy Link

You can pass there versions as docker build arg so there will be no static value within the docker file. This enables the possibility to set the version on pipeline level. But then the build call on pipeline/action is not generic anymore(or you spent effort to set vars in a generic way on the pipeline)
Other possibilities is to use latest. On parent image not a problem but maybe there is no latest/current link on plugin URL. Depends how the plugin is published on FTP server. Maybe you can quickly check that

You can pass there versions as docker build arg so there will be no static value within the docker file. This enables the possibility to set the version on pipeline level. But then the build call on pipeline/action is not generic anymore(or you spent effort to set vars in a generic way on the pipeline) Other possibilities is to use latest. On parent image not a problem but maybe there is no latest/current link on plugin URL. Depends how the plugin is published on FTP server. Maybe you can quickly check that

marcboehm commented 2024-09-15 09:07:02 +02:00

Owner

Copy Link

You can pass there versions as docker build arg so there will be no static value within the docker file. This enables the possibility to set the version on pipeline level. But then the build call on pipeline/action is not generic anymore(or you spent effort to set vars in a generic way on the pipeline)
Other possibilities is to use latest. On parent image not a problem but maybe there is no latest/current link on plugin URL. Depends how the plugin is published on FTP server. Maybe you can quickly check that

Ok, it's a gitlab download. The forget my request. To complicated 😆

>You can pass there versions as docker build arg so there will be no static value within the docker file. This enables the possibility to set the version on pipeline level. But then the build call on pipeline/action is not generic anymore(or you spent effort to set vars in a generic way on the pipeline) >Other possibilities is to use latest. On parent image not a problem but maybe there is no latest/current link on plugin URL. Depends how the plugin is published on FTP server. Maybe you can quickly check that Ok, it's a gitlab download. The forget my request. To complicated 😆

marcboehm merged commit 68d0d276df into main 2024-09-15 09:07:17 +02:00

marcboehm deleted branch feature/CAPAUT-328 2024-09-15 09:07:17 +02:00

marcboehm referenced this issue from a commit 2024-09-15 09:07:17 +02:00

CAPAUT-328 docker creation for sonarqube with oidc plugin (#1)

tobiaslehmann commented 2024-09-17 20:34:26 +02:00

Author

Contributor

Copy Link

you are talking about the sonarqube and plugin version ?
where should the versions be defined ? in the gitea properties ? isn#t that more invisible than updating the docker file itself if needed ?

you are talking about the sonarqube and plugin version ? where should the versions be defined ? in the gitea properties ? isn#t that more invisible than updating the docker file itself if needed ?

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

No items

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

marcboehm

No Assignees marcboehm

2 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: captica-oss/de.captica.sonarqube#1