Community
Participate
Working Groups
when configuring a job to deploy an artifact to eclipse nexus, the deployment failes due to 401, ReasonPhrase: Unauthorized. we have two examples for papyrus project https://hudson.eclipse.org/papyrus/view/Tools/job/emfgen-deploy/1/console and https://hudson.eclipse.org/papyrus/view/Tools/job/emfgen-deploy/ It seems to be related to: https://bugs.eclipse.org/bugs/show_bug.cgi?id=442933 where the solution was to "we updated the password for the deployment user and it looks like the settings file was missed." Moreover it seems that the maven deploy configuration is not anymore available in Hudson (new version?) https://wiki.eclipse.org/Services/Nexushttps://wiki.eclipse.org/Services/Nexushttps://wiki.eclipse.org/Services/Nexus The official documentation stands: "Finally your deploy job should invoke an instance of Maven 3 with the "deploy" goal. The only additional option you need to ensure that's configured is to click Advanced and configure the Settings option and set it to Deploy to repo.eclipse.org. This custom settings file contains the necessary credentials in order for you to deploy to repo.eclipse.org" I am not sure of my analysis, do not hesitate to correct it. This bug is blocking for us. Thanks for your help
+1
Hello, perhaps I have missed to precise that initially these jobs (mvn clean deploy) were successful. it is clearly a regression since the upgrade of hudson, perhaps it is just because we do not upgraded our password. Could you provide the same fix (https://bugs.eclipse.org/bugs/show_bug.cgi?id=442933) for the following repositories: https://repo.eclipse.org/content/repositories/papyrus-releases/ https://repo.eclipse.org/content/repositories/papyrus-snapshots/ If you need more information or that I test something, pelase do not hesitate. Francois from France
Fix for bug 442933 can not be applied as your installation properly has the .m2/security-settings.xml file. I am investigating.
Hey Mikael, Thanks for taking care of our problem. This actual version is already able to deploy the artifacts in the Papyrus's nexus eclipse repsoitory. ( for instance: https://repo.eclipse.org/content/repositories/papyrus-snapshots/) Could you give me precision on the file you mentionned, the .m2/security-settings.xml Is this file editable by an admin of papyrus? Admin of Papyrus are able to login(ssh) to edit it? Because we wanted to add an additional login/password to be able to deploy the site? Could you give us the process? Please do not hesitate to provide you additional information? I am available to make test. Have a good day. Francois
(In reply to Francois Le Fevre from comment #4) > Hey Mikael, > Thanks for taking care of our problem. > > This actual version is already able to deploy the artifacts in the Papyrus's > nexus eclipse repsoitory. ( for instance: > https://repo.eclipse.org/content/repositories/papyrus-snapshots/) I am a bit lost. Are you saying that you are not facing the issue anymore? > > Could you give me precision on the file you mentionned, the > .m2/security-settings.xml It is the file that contains the password to upload artifacts to the nexus repository (see https://maven.apache.org/guides/mini/guide-encryption.html) > > Is this file editable by an admin of papyrus? > Admin of Papyrus are able to login(ssh) to edit it? No as it contains sensitive information about the infrastructure. > Because we wanted to add an additional login/password to be able to deploy > the site? > Could you give us the process? Do you mean that you want to deploy the website build by maven? It won't be the way to go as websites on the Eclipse Foundation infra are stored in git repos which are polled frequently to update the actual website. So if you want to publish a website from your HIPP, I can do the necessary things so that you can push to the website's git repo (https://git.eclipse.org/c/www.eclipse.org/papyrus.git/). Of course, I will need a +1 from a Papyrus's project lead for that.
Quick comment about https://repo.eclipse.org/content/repositories/papyrus-snapshots/fr/cea/list/lise/emfgen/. I don't think you are allowed to push things on Eclipse's infra under the name fr.cea.list. Adding Ed Merks from the modeling PMC to let him comment about it.
I'm not sure there are rules about folder names, but this does seem decidedly odd. I'd expect project names/namespaces to be used...
Dear all, 1-topic fr.cea on repository sure, the fr.cea has to be deleted, it was an error due to a test of deploy. now we respect org.eclipse.papyrus project/namespace. we wanted with Camille to ask you to delete the fr.cea, but as it was the migration of Hudson, we didn't want to disturb you with that. >>Please feel free to delete the fr folders and update the nexus repository. 2-topic web site deploy we will have to discuss about your proposition which is very interessant. we have made an initial protoype that publish the developer web site directly on github because we didn't want to stress the eclipse git infrastructure by multiple push just for site publishing. the configuration for the test was there: https://git.eclipse.org/r/#/c/44693/7/plugins/doc/pom.xml the live web site for testing purpose: http://flefevre.github.io/testpapy/index.html the only difficulty is that we have to pass the credential of the repo in the settings.xml. so perhaps I can adapt the initial maven pom referenced before, to publish directly on the official papyrus git eclipse repository. can we create a separate bug/enhancement for this point? if yes, under which components? 3-topic for hudson About "I am a bit lost. Are you saying that you are not facing the issue anymore?" We do have the problem, I have just wanted to stress the fact that the initial code under the papyrus git repository was able to make the deploy. So the bug we are facing (problem of deploy) is more related to hudson configuration rather than a problem in maven deploy configuration. (I am sorry for the english, perhaps the confusion could from my poor englsih) Thanks a lot for your help and your expertise ! Francois
(In reply to Ed Merks from comment #7) > I'm not sure there are rules about folder names, but this does seem > decidedly odd. I'd expect project names/namespaces to be used... Thanks Ed. It seems that it was just a mistake and the folder will be deleted.
(In reply to Francois Le Fevre from comment #8) > >>Please feel free to delete the fr folders and update the nexus repository. Done. > > 2-topic web site deploy > > we will have to discuss about your proposition which is very interessant. > we have made an initial protoype that publish the developer web site > directly on github because we didn't want to stress the eclipse git > infrastructure by multiple push just for site publishing. > > the configuration for the test was there: > https://git.eclipse.org/r/#/c/44693/7/plugins/doc/pom.xml > the live web site for testing purpose: > http://flefevre.github.io/testpapy/index.html > > the only difficulty is that we have to pass the credential of the repo in > the settings.xml. so perhaps I can adapt the initial maven pom referenced > before, to publish directly on the official papyrus git eclipse repository. > > can we create a separate bug/enhancement for this point? if yes, under which > components? Sure. Create a bug under community / git. > > 3-topic for hudson > > About "I am a bit lost. Are you saying that you are not facing the issue > anymore?" > We do have the problem, I have just wanted to stress the fact that the > initial code under the papyrus git repository was able to make the deploy. > So the bug we are facing (problem of deploy) is more related to hudson > configuration rather than a problem in maven deploy configuration. Ok I understand better. I am still investigating. > > (I am sorry for the english, perhaps the confusion could from my poor > englsih) No worry. I ask when it's unclear. > > Thanks a lot for your help and your expertise ! You're welcome!
For some reasons, the settings to deploy to repo.eclipse.org disappeared. I restored it and set the configuration of https://hudson.eclipse.org/papyrus/job/emfgen-deploy/ to use it (as explained here https://wiki.eclipse.org/Services/Nexus#Hudson_Job_Setup). Please reopen if you still face the issue.
Thanks a lot, it is operational with emfgen. I will deploy this solution also for another project. Does anyone know why core eclipse projects, do not make the use of the eclipse nexus repsoitory? It will be great if Eclipse EMF, GMF deploy their simple artifact to such platfom. Have a good day.
(In reply to Francois Le Fevre from comment #12) > Thanks a lot, > it is operational with emfgen. > > I will deploy this solution also for another project. I'm glad it works. > > Does anyone know why core eclipse projects, do not make the use of the > eclipse nexus repsoitory? > It will be great if Eclipse EMF, GMF deploy their simple artifact to such > platfom. Each project choose how to distribute its artifacts. Their is no rule enforcing the deployment to thenEclipse Maven repository.
