Details
-
Task
-
Status: Closed
-
L3 - Default
-
Resolution: Fixed
-
None
-
None
-
None
Description
After the implementation of INFRA-784 we found that the following functionality in the release parentÂ
https://github.com/camunda/camunda-release-parent/blob/49c8fa857efc1fe03774762b9f432d9633b771c0/pom.xml#L231-L274
that offers the ci to configure the nexus repositories as per the needs (bucketrepo for PR for example).
is overridden in the platform-ee project and cannot be easily configured for that project in our ci:
https://github.com/camunda/camunda-bpm-platform-ee/blob/master/pom.xml#L26
The precedence of the properties is the following:
https://jira.camunda.com/browse/INFRA-892?focusedCommentId=129323&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-129323
So we want to implement a temporary workaround to add/duplicate the profiles in the platform-ee
<profile> <id>override-snapshot-repository</id> <activation> <property> <name>env.NEXUS_SNAPSHOT_REPOSITORY</name> </property> </activation> <properties> <nexus.snapshot.repository>${env.NEXUS_SNAPSHOT_REPOSITORY}</nexus.snapshot.repository> </properties> </profile> <profile> <id>override-snapshot-repository-id</id> <activation> <property> <name>env.NEXUS_SNAPSHOT_REPOSITORY_ID</name> </property> </activation> <properties> <nexus.snapshot.repository.id>${env.NEXUS_SNAPSHOT_REPOSITORY_ID}</nexus.snapshot.repository.id> </properties> </profile> <profile> <id>override-release-repository</id> <activation> <property> <name>env.NEXUS_RELEASE_REPOSITORY</name> </property> </activation> <properties> <nexus.release.repository>${env.NEXUS_RELEASE_REPOSITORY}</nexus.release.repository> </properties> </profile> <profile> <id>override-release-repository-id</id> <activation> <property> <name>env.NEXUS_RELEASE_REPOSITORY_ID</name> </property> </activation> <properties> <nexus.release.repository.id>${env.NEXUS_RELEASE_REPOSITORY_ID}</nexus.release.repository.id> </properties> </profile>
The removing the nexus.snapshot.repository and nexus.release.repository properties from the platform-ee will be tackled in a separate ticket as it needs to be planned due to the effort of implementing it. We need to ensure that the ci is configured correctly first and INFRA-1039 is created for that.