Date
1 - 4 of 4
autorelease-validate-central job?
|
Robert Varga
Hey,
we are currently releasing to Central, but there is no guarantee those artifacts do not require nexus.opendaylight.org to actually work. There are important differences, as our nexus is a mirror, which contains additionally seeded artifacts -- see https://jira.opendaylight.org/browse/ODLPARENT-210 for details. Also compare https://repo1.maven.org/maven2/com/bea/xml/jsr173-ri/1.0/ to content of nexus. In order to validate that this really is the case, we really should be running autorelease *without* nexus.opendaylight.org, i.e. making sure we depend *only* on the content of Central. This might be a drastic step, so can we first have a weekly job which performs autorelease-release, but does nothing else? Regards, Robert P.S.: this is something we definitely would want for MRI's maven-stage jobs -- that way we have assurance that our upstream artifacts have been successfully replicated on Central. |
|
|
|
JamO Luhrsen
I'm not really sure what we'd have to do here to get what Robert
toggle quoted message
Show quoted text
wants. Thanh, Anil, anyone else know if this is feasible and/or easy to setup? Thanks, JamO On 12/18/19 9:24 AM, Robert Varga
wrote:
Hey, we are currently releasing to Central, but there is no guarantee those artifacts do not require nexus.opendaylight.org to actually work. There are important differences, as our nexus is a mirror, which contains additionally seeded artifacts -- see https://jira.opendaylight.org/browse/ODLPARENT-210 for details. Also compare https://repo1.maven.org/maven2/com/bea/xml/jsr173-ri/1.0/ to content of nexus. In order to validate that this really is the case, we really should be running autorelease *without* nexus.opendaylight.org, i.e. making sure we depend *only* on the content of Central. This might be a drastic step, so can we first have a weekly job which performs autorelease-release, but does nothing else? Regards, Robert P.S.: this is something we definitely would want for MRI's maven-stage jobs -- that way we have assurance that our upstream artifacts have been successfully replicated on Central. |
|
|
|
Thanh ha <zxiiro@...>
This is pretty simple, all of the ODL jobs have a mvn-global-settings and mvn-settings parameters which must be passed. They default to "global-settings" and "autorelease-settings" respectively. The global settings file contains the LF definitions for ODL's Nexus repo, and the autorelease-settings contains the credentials for the autorelease project to authenticate with Nexus. I suspect the job might fail if we pass it an empty string so I see 2 ways to proceed: 1. As LF to setup a empty-settings file which as the name implies is entirely empty. We can then set empty-settings as the settings for both global and mvn-settings. 2. Create a version of the job that does not provide any mvn settings. I think option 1 would be the most clean as we can reuse the same existing jobs we already have. Anil, is this something you can take care of? Regards, Thanh On Wed, 18 Dec 2019 at 16:38, JamO Luhrsen <jluhrsen@...> wrote:
|
|
|
|
Anil Belur
On Fri, Dec 20, 2019 at 12:17 AM Thanh ha <zxiiro@...> wrote:
Sorry, missed this email. I've taken care of this now, by creating the settings files on the infra. So going with approach 1. as Thanh suggested I've created two files. 1. For the Global settings: empty-settings 2. For the maven settings: empty-maven-settings Both these files are actually empty as the name suggests. Where does this need to be updated in releng/builder, is this in the JJB defaults or the specific job. Thanks, Anil |
|
|