Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Implement custom artifact storages in Maven Tekton pipelines #106

Closed
Artem-Zahumonnyi opened this issue Jan 23, 2024 · 1 comment
Closed

Implement custom artifact storages in Maven Tekton pipelines #106

Artem-Zahumonnyi opened this issue Jan 23, 2024 · 1 comment
Assignees
@Artem-Zahumonnyi
Labels
enhancement New feature or request

Comments

@Artem-Zahumonnyi
Copy link
Contributor

In order to better manage and control distributed development, we want to implement the flexibility of using different package registries in our Maven Tekton pipelines. The registries under consideration include Nexus, GitLab, GitHub, and Azure DevOps.

Acceptance Criteria:

  • The user can use different package registries like as Nexus, GitLab, GitHub, Azure DevOps Registries
@Artem-Zahumonnyi Artem-Zahumonnyi added the enhancement New feature or request label Jan 23, 2024
@Artem-Zahumonnyi Artem-Zahumonnyi self-assigned this Jan 23, 2024
epmd-edp pushed a commit that referenced this issue Jan 23, 2024
@Artem-Zahumonnyi
chore: Add examples for using various artifactory storages in Maven (#…
09b163e 
…106)

The configuration for GitLab, GitHub, and Azure DevOps servers has been
added to Maven settings.xml file.
Specific profiles have also been added for each of these servers.
To use profiles, the user can change the active profile to match
the intended repository.

Jira: EPMDEDP-13184
Related: #106

Change-Id: I921381607c99355d76a8830db517f75a7f84ba3e
epmd-edp pushed a commit that referenced this issue Jan 23, 2024
@Artem-Zahumonnyi
chore: Remove 'get-nexus-repository-url' task (#106)
5f9623e 
The task 'get-nexus-repository-url' was removed from the maven
Tekton pipelines.
This task was previously used to get the URL of the Nexus repository
for publishing artifacts.

Jira: EPMDEDP-13184
Related: #106

Change-Id: Ic0ff894685b66146f0314befae53b5dd80c815a1
epmd-edp pushed a commit that referenced this issue Jan 23, 2024
@Artem-Zahumonnyi @SergK
chore: Remove unused Nexus-specific properties, Gerrit VCS (#106)
81b8ff7 
The Nexus-specific properties
-Dartifactory.baseUrl,
-Dartifactory.releasePath,
-Dartifactory.snapshotsPath,
and -Dartifactory.groupPath were removed from the Tekton Tasks.

This information was previously used for artifact management via Nexus.

Jira: EPMDEDP-13184
Related: #106

Change-Id: I33754689056721846a6e7d0f6f245a5dc87fb71e
epmd-edp pushed a commit that referenced this issue Jan 23, 2024
@Artem-Zahumonnyi @SergK
chore: Remove unused Nexus-specific properties, GitHub VCS (#106)
ea675f8 
The Nexus-specific properties
-Dartifactory.baseUrl,
-Dartifactory.releasePath,
-Dartifactory.snapshotsPath,
and -Dartifactory.groupPath were removed from the Tekton Tasks.

This information was previously used for artifact management via Nexus.

Jira: EPMDEDP-13184
Related: #106

Change-Id: I25071f67edf346b7c985ed47e65fd1fed987ebd0
epmd-edp pushed a commit that referenced this issue Jan 23, 2024
@Artem-Zahumonnyi @SergK
chore: Remove unused Nexus-specific properties, GitLab VCS (#106)
a5b2167 
The Nexus-specific properties
-Dartifactory.baseUrl,
-Dartifactory.releasePath,
-Dartifactory.snapshotsPath,
and -Dartifactory.groupPath were removed from the Tekton Tasks.

This information was previously used for artifact management via Nexus.

Jira: EPMDEDP-13184
Related: #106

Change-Id: I92e5186d716e843eb29269f8cea5e978e4aea3c9
epmd-edp pushed a commit that referenced this issue Jan 24, 2024
@Artem-Zahumonnyi
chore: Update maven-deploy-plugin syntax for Java 8 and 11 compatibil…
bdbbf9f 
…ity (#106)

The new syntax `id::default::url` replaces the previous id::url
to ensure compatibility with Java 8 and Java 11 applications.

Jira: EPMDEDP-13184
Related: #106

Change-Id: I638a18d538cf2a1c89e5c082a935776d715d3514
epmd-edp pushed a commit that referenced this issue Jan 25, 2024
@Artem-Zahumonnyi
feat: Add secret for authentication in package registries (#106)
d147bc8 
The user can control the creation of the secret by the
`packageRegistriesSecret.enabled` flag.

The secret contains placeholders for GitLab, GitHub,
and Azure DevOps authentication values.

Jira: EPMDEDP-13184
Related: #106

Change-Id: Ieabd71e93e7dc92307ee61fae17b4c12cb82c37a
epmd-edp pushed a commit that referenced this issue Jan 29, 2024
@Artem-Zahumonnyi
feat: Add ability to use custom Maven settings.xml (#106)
d05d3e1 
The 'tekton.configs.mavenConfigMap' parameter has been added to
support a custom Maven settings.xml file.

By default, the 'custom-maven-settings' configuration map is created
by the Helm chart and used by Tekton Pipelines.

To use a different custom Maven settings.xml configuration file,
user should create a new configuration map and update
the 'mavenConfigMap' parameter

Jira: EPMDEDP-13184
Related: #106

Change-Id: I8e89e4530338828c4af78d18ec257f62b11fefba
@Artem-Zahumonnyi
Copy link
Contributor Author

The Maven settings.xml file allows the user to use different package registries for pulling and publishing packages.

The new "tekton.packageRegistriesSecret" parameter allows the user to inject a Kubernetes secret to maven Tekton Pipelines. This secret can contain key-value records.

The new "tekton.configs" parameter allows the user to redefine the Maven settings.xml file which is used in Pipelines.
Ref: https://github.com/epam/edp-tekton/blob/master/charts/pipelines-library/values.yaml

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Artem-Zahumonnyi Artem-Zahumonnyi

Labels
enhancement New feature or request
Projects
KubeRocketCI (EPAM Delivery Platform)
Status: Done
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Artem-Zahumonnyi