New plugin Build-name-updater

202 views
Skip to first unread message

Lev Mishin

unread,
Oct 9, 2015, 12:24:55 PM10/9/15
to jenkin...@googlegroups.com
  • Github link: https://github.com/Le0Michine/Jenkins-Build-name-updater-plugin/tree/master 
  • Repo name: "Build-name-updater-plugin"
  • User name the same as in the URL
  • jenkins-ci.org username: Le0;
  • Description: my plugin updates a build name during the build process, it was necessary because custom build name could tell some useful information. Sometimes we just unable to set custom build name before build or in pre-build steps because we just don't know that so using my plugin you can set the build name in a separate build step, you can use a file in the build workspace or environment variable or both of them as the build name source.
--

Kind regards,
Lev Mishin

Victor Martinez

unread,
Oct 9, 2015, 12:50:15 PM10/9/15
to Jenkins Developers
Hi Lev, 
 Have you considered adding that feature to the build-name-setter plugin?
Cheers,
Víctor

Lev Mishin

unread,
Oct 9, 2015, 1:46:08 PM10/9/15
to Jenkins Developers
Yes I have. But I considered this way again and decided to create pull request.
Message has been deleted

Lev Mishin

unread,
Oct 14, 2015, 9:17:17 AM10/14/15
to Jenkins Developers
The last repo update was commited two years ago so the repo looks abandoned, could you give me write rights for it please?

Oleg Nenashev

unread,
Oct 17, 2015, 12:05:07 PM10/17/15
to Jenkins Developers, Kohsuke Kawaguchi
The response came in a separate thread. Added the plugin's maintainer to Cc.
I'd bet that KK will allow it.

I've also added some comments to your pull request. IMO needs an update before merging

Hi,
Great if you want to adopt a plugin.

Basically, the TL;DR is: you want to ping the current/last maintainer(s) to check they are OK to give ownership.
If they give their agreement or don't answer within some days, then you'll be given permissions to become the official maintainer.

Cheers

среда, 14 октября 2015 г., 16:17:17 UTC+3 пользователь Lev Mishin написал:

Lev Mishin

unread,
Oct 17, 2015, 1:27:48 PM10/17/15
to Jenkins Developers, k...@kohsuke.org
Thanks for your comments, I am going to apply them tomorrow.

Lev Mishin

unread,
Oct 21, 2015, 2:53:14 AM10/21/15
to Jenkins Developers, k...@kohsuke.org
sorry for the delay, I've just applied your comments


On Saturday, October 17, 2015 at 7:05:07 PM UTC+3, Oleg Nenashev wrote:

Oleg Nenashev

unread,
Oct 21, 2015, 4:14:13 AM10/21/15
to Jenkins Developers, k...@kohsuke.org
Hi Lev,

I'll ping Kohsuke regarding the ownership handover.

Best regards,
Oleg

среда, 21 октября 2015 г., 9:53:14 UTC+3 пользователь Lev Mishin написал:

Lev Mishin

unread,
Oct 21, 2015, 5:07:15 AM10/21/15
to Jenkins Developers, k...@kohsuke.org

Thanks!


--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/i9bjjyF75bw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/a8210308-b935-472b-8e6c-f538b8244a1b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Lev Mishin

unread,
Oct 26, 2015, 6:36:01 AM10/26/15
to Jenkins Developers, k...@kohsuke.org
Just to remind

Thanks!


To unsubscribe from this group and all its topics, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.

Oleg Nenashev

unread,
Oct 27, 2015, 3:12:00 AM10/27/15
to Jenkins Developers, k...@kohsuke.org
Hi Lev,

I've granted you developer permissions & changed the default assignee in JIRA.
Now you should be able to merge PRs and release the plugin on your own.

Best regards,
Oleg

понедельник, 26 октября 2015 г., 13:36:01 UTC+3 пользователь Lev Mishin написал:

Thanks!


To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.

Lev Mishin

unread,
Oct 27, 2015, 3:21:53 AM10/27/15
to Jenkins Developers, k...@kohsuke.org
Hi Oleg,
Thanks a lot! I've just merged pull-request and I'm going to update plugin wiki page. How could I add new release?


For more options, visit https://groups.google.com/d/optout.

Baptiste Mathus

unread,
Oct 27, 2015, 4:32:36 AM10/27/15
to jenkin...@googlegroups.com
Hi Lev,
Read https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Releasingtojenkinsci.org main gotcha: beware forcing recent maven-release-plugin versions if you depend on an old Jenkins version for the plugin.

Cheers

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/CAGAc5LXd%3DLnZ2xqNQOG%2B8NrY8ZqQ5JEq67ZTOvyjUFctMqafEw%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.



--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

Lev Mishin

unread,
Nov 3, 2015, 3:18:43 PM11/3/15
to Jenkins Developers
Hi again
I have read all the article but I unable to deploy a new version. I try to run mvn release:prepare release:perform -Dusername=... -Dpassword=... with login/pass, but the error occurs:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on project build-name-setter: Failed to deploy artifacts: Could not transfer artifact org.jenkins-ci.plugins:build-name-setter:hpi:1.5 from/to maven.jenkins-ci.org (http://maven.jenkins-ci.org:8081/content/repositories/releases): Failed to transfer file: http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/build-name-setter/1.5/build-name-setter-1.5.hpi. Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1]

I guess it is connected with:
However if your plugin is hosted on GitHub and you have different username and/or password for GitHub and jenkins-ci.org use of the command-line arguments for username/password will result in errors.

Am I right?
I have set up ssh-agent using the following instructions:
But maven still fails with the error above



On Friday, October 9, 2015 at 7:24:55 PM UTC+3, Lev Mishin wrote:

Lev Mishin

unread,
Nov 3, 2015, 3:22:24 PM11/3/15
to Jenkins Developers
Hmm, quite strange, I've just run 'deploy' target from 'lifecycle' in Idea and plugin was successfully released. Will it appear here?

Kanstantsin Shautsou

unread,
Nov 3, 2015, 3:44:11 PM11/3/15
to Jenkins Developers
Please check that you also uploaded sources and javadocs (action that maven-release-plugin do).

Lev Mishin

unread,
Nov 3, 2015, 3:54:24 PM11/3/15
to Jenkins Developers
In log I see only

Do I have to upload some more? How could I do that?

Lev Mishin

unread,
Nov 4, 2015, 6:28:14 AM11/4/15
to Joachim Kuhnert, jenkin...@googlegroups.com
Thanks! I will try that

On Wed, Nov 4, 2015 at 12:44 PM Joachim Kuhnert <Joachim...@piketec.com> wrote:

Hello,

 

since my mail to the developer list seems not to be delivered I send you this mail directly again:

 

I had the same problem not long ago that releasing with maven did not work. The solution was to omit username and password (only call “mvn release:prepare release:perform”) and instead set username and password in the maven ~/.m2/settings.xml as described in https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Releasingtojenkinsci.org by adding:

 

  <servers>

    <server>

      <id>maven.jenkins-ci.org</id> <!-- For parent 1.397 or newer; before this use id java.net-m2-repository -->

      <username>yourUserName</username>

      <password>yourPassword</password>

    </server>

  </servers>

 

Best Regards

Joachim

 

---------------------------------------------------

Joachim Kuhnert

fon: +49 30 394 09 683 39

 

PikeTec GmbH, Waldenserstr. 2-4, 10551 Berlin

Management: Eckard Bringmann, Andreas Krämer, Jens Lüdemann

Location of the company: Berlin (Germany)

Trade register: Amtsgericht Berlin HRB 105491 B

Website: www.piketec.com

 

Joachim Kuhnert

unread,
Nov 7, 2015, 2:49:30 PM11/7/15
to leomi...@gmail.com, jenkin...@googlegroups.com

Joachim Kuhnert

unread,
Nov 7, 2015, 2:49:30 PM11/7/15
to jenkin...@googlegroups.com

Hello,

 

I had the same problem not long ago. The solution was to omit username and password (only call “mvn release:prepare release:perform”) and instead set username and password in the maven ~/.m2/settings.xml as described in https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Releasingtojenkinsci.org by adding:

 

  <servers>

    <server>

      <id>maven.jenkins-ci.org</id> <!-- For parent 1.397 or newer; before this use id java.net-m2-repository -->

      <username>yourUserName</username>

      <password>yourPassword</password>

    </server>

  </servers>

 

Best Regards

Joachim

---------------------------------------------------

Joachim Kuhnert

fon: +49 30 394 09 683 39

 

PikeTec GmbH, Waldenserstr. 2-4, 10551 Berlin

Management: Eckard Bringmann, Andreas Krämer, Jens Lüdemann

Location of the company: Berlin (Germany)

Trade register: Amtsgericht Berlin HRB 105491 B

Website: www.piketec.com

 

--

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.

Baptiste Mathus

unread,
Nov 11, 2015, 10:02:46 AM11/11/15
to jenkin...@googlegroups.com
Hi Lev,

Just noticed that https://wiki.jenkins-ci.org/display/JENKINS/Build+Name+Setter+Plugin still has the 'adopt-a-plugin' tag. I guess you should remove it. I see that you seem to have released a new version yesterday.

Btw, I guess you could (should?) simply remove kohsuke from the pom.xml, so that he doesn't appear on that page anymore as a maintainer.
Since IIUC it's indeed not the case anymore (and hence better tell the right info to users landing on that page).

My 2 cents.

Cheers


--
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/CAGAc5LV6JCSbd4Dixw7SHXL2eEQwJbjPge43mgY2XWVce9wQig%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages