Publishing plugin: update-center.json is not updated

[Dzmitry Kashlach]

Hi,

I have a published plugin, which I'd like to update and make this update visible through Jenkins update center.

https://wiki.jenkins-ci.org/display/JENKINS/BlazeMeter+Plugin

I've synced up jenkinsci fork with my repository and marked stable revision with a tag.

Few questions:

1. Is running "mvn release:prepare release:perform" required operation for Jenkins update center? I do not want to have "SNAPSHOT" ending in plugin version, but mvn requires it.

2. Are any other configurations in pom.xml required?

Thanks in advance.

P.S. I've a newbie on this procedure. Please, point me to appropriate WIKI page if it's already described there.

[Ullrich Hafner]

Am 16.04.2015 um 10:58 schrieb Dzmitry Kashlach <dzmitry...@gmail.com>:

Hi,

I have a published plugin, which I'd like to update and make this update visible through Jenkins update center.

https://wiki.jenkins-ci.org/display/JENKINS/BlazeMeter+Plugin

I've synced up jenkinsci fork with my repository and marked stable revision with a tag.

Few questions:

1. Is running "mvn release:prepare release:perform" required operation for Jenkins update center?

Yes

I do not want to have "SNAPSHOT" ending in plugin version, but mvn requires it.

Because Maven automatically crates a non SNAPSHOT version during release. 

2. Are any other configurations in pom.xml required?

Besides the options shown in the Wiki nothing special is required.

Thanks in advance.

P.S. I've a newbie on this procedure. Please, point me to appropriate WIKI page if it's already described there.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/b6c1ad0a-6230-4d7e-acf2-74ef5920c769%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Dzmitry Kashlach]

Thanks, Ullrich,

I'v followed Hosting+Plugins instruction and tried to run both

mvn release:prepare release:perform -Dusername=<jenkinsci_user> -Dpassword=<jenkinsci_pass>

and

 mvn release:prepare release:perform

In both cases I get

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 1:20.112s

[INFO] Finished at: Fri Apr 17 09:17:46 MSK 2015

[INFO] Final Memory: 13M/196M

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5:prepare (default-cli) on project BlazeMeterJenkinsPlugin: Unable to commit files

[ERROR] Provider message:

[ERROR] The git-push command failed.

[ERROR] Command output:

[ERROR] ssh: Could not resolve hostname zmicerkashlach: Name or service not known

[ERROR] fatal: Could not read from remote repository.

[ERROR] 

[ERROR] Please make sure you have the correct access rights

[ERROR] and the repository exists.

I'm sure that I've specified right repository and I can push code to it.

What should I check?

[Daniel Beck]

On 17.04.2015, at 08:24, Dzmitry Kashlach <dzmitry...@gmail.com> wrote:

> What should I check?

Complete guess, but since the pom looks good, did you make sure you don't have weird settings in ~/.m2/settings.xml?

[Dzmitry Kashlach]

I run maven 3.0.4 and my settings.xml are in $M2_HOME/conf.

Here is it's content:

<?xml version="1.0" encoding="UTF-8"?>

<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" 

          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 

          xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">

  <pluginGroups>

   <pluginGroup>org.jenkins-ci.tools</pluginGroup>

  </pluginGroups>

  <proxies>

  </proxies>

  <servers>

<server>

<id>github</id>

<username>[GITHUB_USER]</username>

<password>[GITHUB_PASSWORD]</password>

</server>    

  </servers>

  <mirrors>

    <mirror>

      <id>repo.jenkins-ci.org</id>

      <url>http://repo.jenkins-ci.org/public/</url>

      <mirrorOf>m.g.o-public</mirrorOf>

    </mirror>   

  </mirrors>

  <profiles>

    <profile>

      <id>jenkins</id>

      <activation>

        <activeByDefault>true</activeByDefault> <!-- change this to false, if you don't like to have it on per default -->

      </activation>

      <repositories>

        <repository>

          <id>repo.jenkins-ci.org</id>

          <url>http://repo.jenkins-ci.org/public/</url>

        </repository>

      </repositories>

      <pluginRepositories>

        <pluginRepository>

          <id>repo.jenkins-ci.org</id>

          <url>http://repo.jenkins-ci.org/public/</url>

        </pluginRepository>

      </pluginRepositories>

    </profile>   

  </profiles>

</settings>

Can version of maven be the course of problem? AFAIK, there are some issues with releasing with MAVEN 3.X

On Thursday, April 16, 2015 at 11:58:22 AM UTC+3, Dzmitry Kashlach wrote:

[Dzmitry Kashlach]

It was my problem with ssh connection to GITHUB.

On Thursday, April 16, 2015 at 11:58:22 AM UTC+3, Dzmitry Kashlach wrote:

[Kanstantsin Shautsou]

+ https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Releasingtojenkinsci.org and not GITHUB credentials, or do you use the same login and password?

[Dzmitry Kashlach]

Thanks, Kanstantin.

I've released plugin.

My SSH GITHUB key was out-dated.

No issues for now, plugin is in update-center.

On Thursday, April 16, 2015 at 11:58:22 AM UTC+3, Dzmitry Kashlach wrote: