Re: New plugin request: send-to-eclipse
https://github.com/jenkinsci/send-stacktrace-to-eclipse-plugin Welcome aboard! Ulli Am 08.05.2014 um 21:19 schrieb Cees Bos cbos...@gmail.com: Hi Ulli, Thanks for the reply. It is not on Github yet. I read on the wiki page (https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins) that is not necessary. If that is easier for you I can create a repo and push it to there, so you can clone it. I don't know what is easier to do for you? Regards, Cees On Wed, May 7, 2014 at 10:11 PM, Ulli Hafner ullrich.haf...@gmail.com wrote: Is your plugin already in GitHub so we can fork it? Am 25.04.2014 um 11:00 schrieb Cees Bos cbos...@gmail.com: We have developed a plugin which can send a stacktrace of a failing testcase to Eclipse. In Eclipse you need a plugin, which can receive the request. The Eclipse plugin can be found here: http://cbos.github.io/OpenFromExternalEvent/ Jenkins Plugin Name: send-to-eclipse-plugin Github User: cbos Jenkins-ci org account: cbos Regards, Cees -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Message signed with OpenPGP using GPGMail
jenkins-admin does not require voice anymore...
Any ideas why our jenkins-admin command on IRC does not require voice privileges anymore? signature.asc Description: Message signed with OpenPGP using GPGMail
Integration test against Jenkins
Hello, I'm trying to contribute to a Jenkins client lib [1] but the integration tests require a Jenkins instance on port 8080. I'd like to change that to be able to run the integration tests against a specific version of Jenkins. For the moment, I managed to download Jenkins war (maven-dependency-plugin) and unpack it in a specific directory. I tried maven-jetty-plugin to start at pre-integration-test and stop it at post-integration-test but when started, Jenkins doesn't let the integration-test processus go. I tried to forked it or launch it as a daemon, but in those case, the integration-test phase started before Jenkins to be up and ready. My question is: how Jenkins injected tests are made so a Jenkins instance is launch in parallel? Thanks for your help, Regards. -- Adrien [1]: https://github.com/RisingOak/jenkins-client -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Confused by Release Process - Release Repositorys
Hi Folks, I've tried to release today a plugin (my first time). The plugin repo is here: https://github.com/jenkinsci/artifact-promotion-plugin Finally, after fighting with the network here and the release plugin itself (IMHO it's really a pain to work with it and I would suggest to switch to a continuous version number, but this is offtopic here...). I'm a bit confused about which repository server has to be taken for the deployment by the release plugin: repo.jenkins-ci.org or maven.jenkins-ci.org? They are different servers and the maven parent references to the second one. But in the hosting documentation it is stated that we should look in repo.jenkins-ci.org ( https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Help%5C%21Mypluginisnotshowingupintheupdatecenter. ). After finally finishing the release plugins work I only see snapshots in the first server: http://repo.jenkins-ci.org/webapp/search/artifact/?32q=artifact-promotion I assume these versions are from the cloudbees jenkins build job. So, that I'm doing wrong? Setting the distributionManagement manually in the pom to repo.jenkins-ci.org results in 401 errors. Is there any further documentation about the release process? Suggestions are welcome :-) Bye Halil -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Confused by Release Process - Release Repositorys
Am 12.05.2014 um 17:07 schrieb Halil-Cem Gürsoy hcguer...@gmail.com: Hi Folks, I've tried to release today a plugin (my first time). The plugin repo is here: https://github.com/jenkinsci/artifact-promotion-plugin Finally, after fighting with the network here and the release plugin itself (IMHO it's really a pain to work with it and I would suggest to switch to a continuous version number, but this is offtopic here...). I'm a bit confused about which repository server has to be taken for the deployment by the release plugin: repo.jenkins-ci.org or maven.jenkins-ci.org? I thought both are pointing to the same Artifactory instance. The latter one just redirects to the former one in order to be backward compatible. They are different servers and the maven parent references to the second one. But in the hosting documentation it is stated that we should look in repo.jenkins-ci.org (https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Help%5C%21Mypluginisnotshowingupintheupdatecenter.). After finally finishing the release plugins work I only see snapshots in the first server: http://repo.jenkins-ci.org/webapp/search/artifact/?32q=artifact-promotion I assume these versions are from the cloudbees jenkins build job. So, that I'm doing wrong? If you are releasing only snapshots (see your maven console log) then you probably hit a bug in the maven-release-plugin: https://groups.google.com/forum/#!topic/jenkinsci-dev/qkmbl3HrYgk Setting the distributionManagement manually in the pom to repo.jenkins-ci.org results in 401 errors. Is there any further documentation about the release process? Suggestions are welcome :-) Bye Halil -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Message signed with OpenPGP using GPGMail
updates.jenkins-ci.org is terribly slow/down
Hello, Today, most attempts to download plugins from updates.jenkins-ci.org timeout, only sometimes something gets thru. Here're are wget log examples: $ time wget http://updates.jenkins-ci.org/download/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi --2014-05-12 18:09:31-- http://updates.jenkins-ci.org/download/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi Resolving updates.jenkins-ci.org (updates.jenkins-ci.org)... 199.193.196.24 Connecting to updates.jenkins-ci.org (updates.jenkins-ci.org)|199.193.196.24|:80... connected. HTTP request sent, awaiting response... 502 Bad Gateway 2014-05-12 18:10:05 ERROR 502: Bad Gateway. real0m33.956s user0m0.000s sys 0m0.004s $ time wget http://updates.jenkins-ci.org/download/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi --2014-05-12 18:10:11-- http://updates.jenkins-ci.org/download/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi Resolving updates.jenkins-ci.org (updates.jenkins-ci.org)... 199.193.196.24 Connecting to updates.jenkins-ci.org (updates.jenkins-ci.org)|199.193.196.24|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://mirrors.jenkins-ci.org/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi [following] --2014-05-12 18:10:22-- http://mirrors.jenkins-ci.org/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi Resolving mirrors.jenkins-ci.org (mirrors.jenkins-ci.org)... 199.193.196.24 Connecting to mirrors.jenkins-ci.org (mirrors.jenkins-ci.org)|199.193.196.24|:80... connected. HTTP request sent, awaiting response... 502 Bad Gateway 2014-05-12 18:10:59 ERROR 502: Bad Gateway. real0m47.422s user0m0.000s sys 0m0.004s -- Best Regards, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: updates.jenkins-ci.org is terribly slow/down
It's you. $ time wget http://updates.jenkins-ci.org/download/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi --2014-05-12 12:17:11-- http://updates.jenkins-ci.org/download/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi Resolving updates.jenkins-ci.org... 199.193.196.24 Connecting to updates.jenkins-ci.org|199.193.196.24|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://mirrors.jenkins-ci.org/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi [following] --2014-05-12 12:17:11-- http://mirrors.jenkins-ci.org/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi Resolving mirrors.jenkins-ci.org... 199.193.196.24 Connecting to mirrors.jenkins-ci.org|199.193.196.24|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://mirror.xmission.com/jenkins/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi [following] --2014-05-12 12:17:11-- http://mirror.xmission.com/jenkins/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi Resolving mirror.xmission.com... 198.60.22.13, 2607:fa18:0:3::13 Connecting to mirror.xmission.com|198.60.22.13|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 78382 (77K) [application/octet-stream] Saving to: “ssh-credentials.hpi” 100%[] 78,382 297K/s in 0.3s 2014-05-12 12:17:12 (297 KB/s) - “ssh-credentials.hpi” saved [78382/78382] wget 0.03s user 0.01s system 4% cpu 0.978 total On Mon, May 12, 2014 at 11:27 AM, Paul Sokolovsky paul.sokolov...@linaro.org wrote: Hello, Today, most attempts to download plugins from updates.jenkins-ci.org timeout, only sometimes something gets thru. Here're are wget log examples: $ time wget http://updates.jenkins-ci.org/download/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi --2014-05-12 18:09:31-- http://updates.jenkins-ci.org/download/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi Resolving updates.jenkins-ci.org (updates.jenkins-ci.org)... 199.193.196.24 Connecting to updates.jenkins-ci.org (updates.jenkins-ci.org)|199.193.196.24|:80... connected. HTTP request sent, awaiting response... 502 Bad Gateway 2014-05-12 18:10:05 ERROR 502: Bad Gateway. real0m33.956s user0m0.000s sys 0m0.004s $ time wget http://updates.jenkins-ci.org/download/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi --2014-05-12 18:10:11-- http://updates.jenkins-ci.org/download/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi Resolving updates.jenkins-ci.org (updates.jenkins-ci.org)... 199.193.196.24 Connecting to updates.jenkins-ci.org (updates.jenkins-ci.org)|199.193.196.24|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://mirrors.jenkins-ci.org/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi [following] --2014-05-12 18:10:22-- http://mirrors.jenkins-ci.org/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi Resolving mirrors.jenkins-ci.org (mirrors.jenkins-ci.org)... 199.193.196.24 Connecting to mirrors.jenkins-ci.org (mirrors.jenkins-ci.org)|199.193.196.24|:80... connected. HTTP request sent, awaiting response... 502 Bad Gateway 2014-05-12 18:10:59 ERROR 502: Bad Gateway. real0m47.422s user0m0.000s sys 0m0.004s -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: updates.jenkins-ci.org is terribly slow/down
Actually, 502 gateway issues usually indicate that the HTTP proxy is timing out -- meaning the application behind updates.jenkins-ci.org is taking too long to respond. It's probably working beyond capacity (these are my guesses without being able to actually see anything about it) Doug Jacobsen, Ph.D. NERSC Bioinformatics Computing Consultant National Energy Research Scientific Computing Center http://www.nersc.gov | Joint Genome Institute http://genome.jgi.doe.gov dmjacob...@lbl.gov | 510-384-3049 (Cell) - __o -- _ '\,_ --(_)/ (_)__ On Mon, May 12, 2014 at 9:18 AM, jieryn jie...@gmail.com wrote: It's you. $ time wget http://updates.jenkins-ci.org/download/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi --2014-05-12 12:17:11-- http://updates.jenkins-ci.org/download/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi Resolving updates.jenkins-ci.org... 199.193.196.24 Connecting to updates.jenkins-ci.org|199.193.196.24|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://mirrors.jenkins-ci.org/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi [following] --2014-05-12 12:17:11-- http://mirrors.jenkins-ci.org/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi Resolving mirrors.jenkins-ci.org... 199.193.196.24 Connecting to mirrors.jenkins-ci.org|199.193.196.24|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://mirror.xmission.com/jenkins/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi [following] --2014-05-12 12:17:11-- http://mirror.xmission.com/jenkins/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi Resolving mirror.xmission.com... 198.60.22.13, 2607:fa18:0:3::13 Connecting to mirror.xmission.com|198.60.22.13|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 78382 (77K) [application/octet-stream] Saving to: “ssh-credentials.hpi” 100%[] 78,382 297K/s in 0.3s 2014-05-12 12:17:12 (297 KB/s) - “ssh-credentials.hpi” saved [78382/78382] wget 0.03s user 0.01s system 4% cpu 0.978 total On Mon, May 12, 2014 at 11:27 AM, Paul Sokolovsky paul.sokolov...@linaro.org wrote: Hello, Today, most attempts to download plugins from updates.jenkins-ci.org timeout, only sometimes something gets thru. Here're are wget log examples: $ time wget http://updates.jenkins-ci.org/download/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi --2014-05-12 18:09:31-- http://updates.jenkins-ci.org/download/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi Resolving updates.jenkins-ci.org (updates.jenkins-ci.org)... 199.193.196.24 Connecting to updates.jenkins-ci.org (updates.jenkins-ci.org)|199.193.196.24|:80... connected. HTTP request sent, awaiting response... 502 Bad Gateway 2014-05-12 18:10:05 ERROR 502: Bad Gateway. real0m33.956s user0m0.000s sys 0m0.004s $ time wget http://updates.jenkins-ci.org/download/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi --2014-05-12 18:10:11-- http://updates.jenkins-ci.org/download/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi Resolving updates.jenkins-ci.org (updates.jenkins-ci.org)... 199.193.196.24 Connecting to updates.jenkins-ci.org (updates.jenkins-ci.org)|199.193.196.24|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://mirrors.jenkins-ci.org/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi[following] --2014-05-12 18:10:22-- http://mirrors.jenkins-ci.org/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi Resolving mirrors.jenkins-ci.org (mirrors.jenkins-ci.org)... 199.193.196.24 Connecting to mirrors.jenkins-ci.org (mirrors.jenkins-ci.org)|199.193.196.24|:80... connected. HTTP request sent, awaiting response... 502 Bad Gateway 2014-05-12 18:10:59 ERROR 502: Bad Gateway. real0m47.422s user0m0.000s sys 0m0.004s -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: updates.jenkins-ci.org is terribly slow/down
On Mon, 12 May 2014 12:18:35 -0400 jieryn jie...@gmail.com wrote: It's you. No, it was not me, the logs below were from Europe, and I had the same issue from Amazon EC2 us-east-1 availability zone (for duration of ~8 hours today). But whoever fixed it after the mail went out, thanks. $ time wget http://updates.jenkins-ci.org/download/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi --2014-05-12 12:17:11-- http://updates.jenkins-ci.org/download/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi Resolving updates.jenkins-ci.org... 199.193.196.24 Connecting to updates.jenkins-ci.org|199.193.196.24|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://mirrors.jenkins-ci.org/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi [following] --2014-05-12 12:17:11-- http://mirrors.jenkins-ci.org/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi Resolving mirrors.jenkins-ci.org... 199.193.196.24 Connecting to mirrors.jenkins-ci.org|199.193.196.24|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://mirror.xmission.com/jenkins/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi [following] --2014-05-12 12:17:11-- http://mirror.xmission.com/jenkins/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi Resolving mirror.xmission.com... 198.60.22.13, 2607:fa18:0:3::13 Connecting to mirror.xmission.com|198.60.22.13|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 78382 (77K) [application/octet-stream] Saving to: “ssh-credentials.hpi” 100%[] 78,382 297K/s in 0.3s 2014-05-12 12:17:12 (297 KB/s) - “ssh-credentials.hpi” saved [78382/78382] wget 0.03s user 0.01s system 4% cpu 0.978 total On Mon, May 12, 2014 at 11:27 AM, Paul Sokolovsky paul.sokolov...@linaro.org wrote: Hello, Today, most attempts to download plugins from updates.jenkins-ci.org timeout, only sometimes something gets thru. Here're are wget log examples: $ time wget http://updates.jenkins-ci.org/download/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi --2014-05-12 18:09:31-- http://updates.jenkins-ci.org/download/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi Resolving updates.jenkins-ci.org (updates.jenkins-ci.org)... 199.193.196.24 Connecting to updates.jenkins-ci.org (updates.jenkins-ci.org)|199.193.196.24|:80... connected. HTTP request sent, awaiting response... 502 Bad Gateway 2014-05-12 18:10:05 ERROR 502: Bad Gateway. real0m33.956s user0m0.000s sys 0m0.004s $ time wget http://updates.jenkins-ci.org/download/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi --2014-05-12 18:10:11-- http://updates.jenkins-ci.org/download/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi Resolving updates.jenkins-ci.org (updates.jenkins-ci.org)... 199.193.196.24 Connecting to updates.jenkins-ci.org (updates.jenkins-ci.org)|199.193.196.24|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://mirrors.jenkins-ci.org/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi [following] --2014-05-12 18:10:22-- http://mirrors.jenkins-ci.org/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi Resolving mirrors.jenkins-ci.org (mirrors.jenkins-ci.org)... 199.193.196.24 Connecting to mirrors.jenkins-ci.org (mirrors.jenkins-ci.org)|199.193.196.24|:80... connected. HTTP request sent, awaiting response... 502 Bad Gateway 2014-05-12 18:10:59 ERROR 502: Bad Gateway. real0m47.422s user0m0.000s sys 0m0.004s -- Best Regards, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: updates.jenkins-ci.org is terribly slow/down
Our current hypothesis is that either ci.jenkins-ci.org is putting a lot of load and making everything slow, or something is eating up all the connections to Postgres and making mirrorbrain time out. On 05/12/2014 08:27 AM, Paul Sokolovsky wrote: Hello, Today, most attempts to download plugins from updates.jenkins-ci.org timeout, only sometimes something gets thru. Here're are wget log examples: $ time wget http://updates.jenkins-ci.org/download/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi --2014-05-12 18:09:31-- http://updates.jenkins-ci.org/download/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi Resolving updates.jenkins-ci.org (updates.jenkins-ci.org)... 199.193.196.24 Connecting to updates.jenkins-ci.org (updates.jenkins-ci.org)|199.193.196.24|:80... connected. HTTP request sent, awaiting response... 502 Bad Gateway 2014-05-12 18:10:05 ERROR 502: Bad Gateway. real0m33.956s user0m0.000s sys 0m0.004s $ time wget http://updates.jenkins-ci.org/download/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi --2014-05-12 18:10:11-- http://updates.jenkins-ci.org/download/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi Resolving updates.jenkins-ci.org (updates.jenkins-ci.org)... 199.193.196.24 Connecting to updates.jenkins-ci.org (updates.jenkins-ci.org)|199.193.196.24|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://mirrors.jenkins-ci.org/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi [following] --2014-05-12 18:10:22-- http://mirrors.jenkins-ci.org/plugins/ssh-credentials/1.6.1/ssh-credentials.hpi Resolving mirrors.jenkins-ci.org (mirrors.jenkins-ci.org)... 199.193.196.24 Connecting to mirrors.jenkins-ci.org (mirrors.jenkins-ci.org)|199.193.196.24|:80... connected. HTTP request sent, awaiting response... 502 Bad Gateway 2014-05-12 18:10:59 ERROR 502: Bad Gateway. real0m47.422s user0m0.000s sys 0m0.004s -- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ Try Jenkins Enterprise, our professional version of Jenkins -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Problem releasing git-parameter-plugin. Banned? Or problem pushing tag?
Hi Niklaus, I had the same problem months ago. You cannot use the environment variables -Dusername and -Dpassword any longer while releasing a plugin. Edit your Maven settings.xml and add a new server section to it: server idmaven.jenkins-ci.org/id usernameniklaus_giger/username passwordcleartext_pw/password /server See https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins (section Releasing to jenkins-ci.org) for more details on how to modify your settings.xml. Kind regards Björn Am 11.05.2014 um 17:14 schrieb Niklaus Giger niklaus.gi...@gmail.com: Hi I am trying to release my first jenkins plugin. I successfully pushed all my changes to https://github.com/jenkinsci/git-parameter-plugin Calling mvn release:prepare release:perform -Dusername=niklaus_giger -Dpassword=cleartext_pw always resulted in [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building Git Parameter Plug-In 0.3 [INFO] [INFO] [INFO] --- maven-release-plugin:2.2.2:prepare (default-cli) @ git-parameter --- [INFO] Resuming release from phase 'scm-tag' [INFO] Tagging release with the label git-parameter-0.3... [INFO] Executing: /bin/sh -c cd /opt/src/git-parameter.jenkins.ci git tag -F /tmp/maven-scm-790953102.commit git-parameter-0.3 [INFO] Working directory: /opt/src/git-parameter.jenkins.ci [INFO] Executing: /bin/sh -c cd /opt/src/git-parameter.jenkins.ci git push ssh://niklaus_giger:cleartext...@github.com:jenkinsci/git-parameter-plugin.git git-parameter-0.3 [INFO] Working directory: /opt/src/git-parameter.jenkins.ci [INFO] [INFO] [INFO] Skipping Git Parameter Plug-In [INFO] This project has been banned from the build due to previous failures. [INFO] Can anybody tell me why this plugin is banned or whether I must (and then how) resolve the push problem. Best regards in advance. Niklaus Giger P.S. The pom.xml already defines 0.3 (instead of 0.3-SNAPSHOT) as version, as I corrected a few things in the pom.xml. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Confused by Release Process - Release Repositorys
Hi Ullrich, thanks for the hint with the bug in the release plugin (on more in my list...). I've done it now with manual versions:set deploy. The released version is now listed in the repo. Bye Halil Am Montag, 12. Mai 2014 17:25:04 UTC+2 schrieb Ullrich Hafner: Am 12.05.2014 um 17:07 schrieb Halil-Cem Gürsoy hcgu...@gmail.comjavascript: : Hi Folks, I've tried to release today a plugin (my first time). The plugin repo is here: https://github.com/jenkinsci/artifact-promotion-plugin Finally, after fighting with the network here and the release plugin itself (IMHO it's really a pain to work with it and I would suggest to switch to a continuous version number, but this is offtopic here...). I'm a bit confused about which repository server has to be taken for the deployment by the release plugin: repo.jenkins-ci.org or maven.jenkins-ci.org? I thought both are pointing to the same Artifactory instance. The latter one just redirects to the former one in order to be backward compatible. They are different servers and the maven parent references to the second one. But in the hosting documentation it is stated that we should look in repo.jenkins-ci.org ( https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Help%5C%21Mypluginisnotshowingupintheupdatecenter. ). After finally finishing the release plugins work I only see snapshots in the first server: http://repo.jenkins-ci.org/webapp/search/artifact/?32q=artifact-promotion I assume these versions are from the cloudbees jenkins build job. So, that I'm doing wrong? If you are releasing only snapshots (see your maven console log) then you probably hit a bug in the maven-release-plugin: https://groups.google.com/forum/#!topic/jenkinsci-dev/qkmbl3HrYgk Setting the distributionManagement manually in the pom to repo.jenkins-ci.org results in 401 errors. Is there any further documentation about the release process? Suggestions are welcome :-) Bye Halil -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Solidifying acceptance-test-harness API
So I jumped the gun a little bit and cut a release of acceptance-test-harness, as it was blocking me on developing other sets of tests internally. But this triggered a comment from Oliver [1] in terms of what we want to see in the code before we consider the API stable enough. Specifically, I hoped there will be a discussion before making the API public. I wanted to get rid off all the public Controls exposed from page objects because we will not be able to preserve the API as Jenkins UI evolves. Changes like af98505 will surely follow. So first of all, I wanted to set the expectation right that 1.0 and 1.1 I released shouldn't be considered stable. With that said, personally I didn't anticipate that we hold ourselves to the level of backward compatibility that we do for Jenkins, and public final Control fields are nice, namely they are very concise to write. But I'm willing to follow what we want as a whole, so if you have any strong feelings and thoughts on this, this is the opportunity to speak up. [1] https://github.com/jenkinsci/acceptance-test-harness/commit/8a4bacb386ee0b5a34c5dd499bd74f50b35c726d#commitcomment-6297001 -- Kohsuke Kawaguchi http://kohsuke.org/ -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Solidifying acceptance-test-harness API
You know I have *very* strong feelings on a lot of the lower layers... but you also know that I haven't had the time to get the replacement layer published yet... It's coming... there is the possibility that it may break some stuff... but I am reasonably confident that it shouldn't On 12 May 2014 23:28, Kohsuke Kawaguchi k...@kohsuke.org wrote: So I jumped the gun a little bit and cut a release of acceptance-test-harness, as it was blocking me on developing other sets of tests internally. But this triggered a comment from Oliver [1] in terms of what we want to see in the code before we consider the API stable enough. Specifically, I hoped there will be a discussion before making the API public. I wanted to get rid off all the public Controls exposed from page objects because we will not be able to preserve the API as Jenkins UI evolves. Changes like af98505 will surely follow. So first of all, I wanted to set the expectation right that 1.0 and 1.1 I released shouldn't be considered stable. With that said, personally I didn't anticipate that we hold ourselves to the level of backward compatibility that we do for Jenkins, and public final Control fields are nice, namely they are very concise to write. But I'm willing to follow what we want as a whole, so if you have any strong feelings and thoughts on this, this is the opportunity to speak up. [1] https://github.com/jenkinsci/acceptance-test-harness/commit/ 8a4bacb386ee0b5a34c5dd499bd74f50b35c726d#commitcomment-6297001 -- Kohsuke Kawaguchi http://kohsuke.org/ -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Solidifying acceptance-test-harness API
On 05/12/2014 04:09 PM, Stephen Connolly wrote: You know I have *very* strong feelings on a lot of the lower layers... but you also know that I haven't had the time to get the replacement layer published yet... It's coming... there is the possibility that it may break some stuff... but I am reasonably confident that it shouldn't Good point, so there's at least that group of changes that we should expect before we consider it solidified. On 12 May 2014 23:28, Kohsuke Kawaguchi k...@kohsuke.org mailto:k...@kohsuke.org wrote: So I jumped the gun a little bit and cut a release of acceptance-test-harness, as it was blocking me on developing other sets of tests internally. But this triggered a comment from Oliver [1] in terms of what we want to see in the code before we consider the API stable enough. Specifically, I hoped there will be a discussion before making the API public. I wanted to get rid off all the public Controls exposed from page objects because we will not be able to preserve the API as Jenkins UI evolves. Changes like af98505 will surely follow. So first of all, I wanted to set the expectation right that 1.0 and 1.1 I released shouldn't be considered stable. With that said, personally I didn't anticipate that we hold ourselves to the level of backward compatibility that we do for Jenkins, and public final Control fields are nice, namely they are very concise to write. But I'm willing to follow what we want as a whole, so if you have any strong feelings and thoughts on this, this is the opportunity to speak up. [1] https://github.com/jenkinsci/__acceptance-test-harness/__commit/__8a4bacb386ee0b5a34c5dd499bd74f__50b35c726d#commitcomment-__6297001 https://github.com/jenkinsci/acceptance-test-harness/commit/8a4bacb386ee0b5a34c5dd499bd74f50b35c726d#commitcomment-6297001 -- Kohsuke Kawaguchi http://kohsuke.org/ -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscribe@__googlegroups.com mailto:jenkinsci-dev%2bunsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/__optout https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com mailto:jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ Try Jenkins Enterprise, our professional version of Jenkins -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
