Replacing the maintainer of the WhiteSource Plugin

[Itai Marko]

Hi,

I'd like to replace the current maintainer of the WhiteSource plugin.
Edo Shor, the current maintainer, does not work in our company any longer.

My GitHub ID is itaimarko.
I'll need commit access to the Whitesource plugin repo.

Thanks,

Itai

[Christopher Orr]

Done. You should have commit access to
https://github.com/jenkinsci/whitesource-plugin

On 12/03/15 02:53, Itai Marko wrote:
> Hi,
>
> I'd like to replace the current maintainer of the WhiteSource plugin

> <https://github.com/whitesource-edo/jenkins-whitesource-plugin>.

> Edo Shor, the current maintainer, does not work in our company any longer.

> My GitHub ID is itaimarko <https://github.com/itaimarko>.

> I'll need commit access to the Whitesource plugin repo.
>
> Thanks,
> Itai
>

> --
> 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
> <mailto:jenkinsci-de...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/67bbf01f-2bd8-4df0-b3be-f46656ad5659%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/67bbf01f-2bd8-4df0-b3be-f46656ad5659%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.

[Itai Marko]

Hi,

I'm trying to push some changes to the WhiteSource plugin but I get:

remote: Permission to jenkinsci/whitesource-plugin.git denied to itaimarko.
fatal: unable to access 'https://github.com/jenkinsci/whitesource-plugin.git/': The requested URL returned error: 403

On GitHub, there's only one contributor listed for this repo whose not working in our company any longer.

Can you please add me as contributor?

My GitHub ID is itaimarko.

Thanks,

Itai

--
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/teT0-_H9640/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/55020882.8060101%40orr.me.uk.

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

--

Itai Marko, Senior Software Developer,

White Source,

itai....@whitesourcesoftware.com

http://www.whitesourcesoftware.com/
+972-54-6326621

[Daniel Beck]

Weird.

You should have an invitation here: https://github.com/jenkinsci

Once you accept that, you have commit access.

Tell us your jenkins-ci.org username, and we'll also make you lead and default assignee of the Jira component for the plugin on issues.jenkins-ci.org.

Daniel

> 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/CA%2BxT4nmYMmv-d4E9WtOC-7owRHqcZLFbxeBReLrZhkHSiWFR3Q%40mail.gmail.com.

[Itai Marko]

Thanks, I've pushed my changes successfully and created a new release.

However, I don't see the new release in update center. The new release is 1.5.1 and I see only the one before that - release 1.4.

The build on jenkins.ci.cloudbees.com passes.

Am I missing something?

BTW, my jenkins-ci.org username is itaimarko.

Thanks,

Itai

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4E0FEB41-12C3-4C9B-A3E4-D0932BC64677%40beckweb.net.

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

[Baptiste Mathus]

How did you release? This doesn't seem to be a /correct/ tag. Did you only create a tag and push it IIUC?

You have to use the maven-release-plugin to get a release out (which will basically create a correct tag + push the binaries into the Jenkins binary repo)

Example of a seemingly correct tag: https://github.com/jenkinsci/whitesource-plugin/commit/b192e524e171cf714f5a044ce10c760e006f8c96

Please read the guide here for details and recommendations: https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Releasingtojenkinsci.org

Cheers

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BxT4nkkmyy-6GOBxS2_O9ty3CR54dzhpsNGdft_GOAv3JgFGg%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 !

[Itai Marko]

No, I actually used maven-release-plugin. We run it on a Jenkins instance with the following:
release:clean release:prepare release:perform whitesource:update -PRelease

The credentials, version-to-release and next-dev-version are specified as properties. Here's the line that gets invoked from the log:
mvn -DRELEASE_VERSION=1.5.1 -DNEXT_DEV_VERSION=1.5.2 -Dtag=release-tag-1.5.1 -Dpassword=******** -DreleaseVersion=1.5.1 -DdevelopmentVersion=1.5.2-SNAPSHOT -Dusername=itaimarko release:clean release:prepare release:perform whitesource:update -PRelease

I made sure that my jenkins-ci.org credentials will match my github credentials.

What is incorrect in the tag?

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7nU3ZdcaxvgLZ4Yaz8yaSMtrK0rmmDt2WMbKdNNzs%3DnQ%40mail.gmail.com.

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

[Baptiste Mathus]

What is the maven-release-plugin version that was used during release? And version for Maven itself?

Check the version that was used for the maven-release-plugin in the logs, I suspect you're having the issue https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues

That is: force the maven-release-plugin to use the latest in your pom.xml (example).

As for the tag: well, see the commit log format, it should have the one I gave the link of in general, if you didn't override it.

Cheers

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BxT4nmF%3D5N76e2U65QvA3hLqR_BEuf6m3Z6UrDSoannbxrerw%40mail.gmail.com.

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

[Itai Marko]

I switched to maven-release-plugin version 2.5.3 and that fixed missing commits problem.

Still, the commits were pushed yesterday evening but release 1.5.1 of the plugin is not available in the update center.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS4AK-LyufxKfosA86XgoBygDLrvQWcbch2dT5S-Kr9Yzg%40mail.gmail.com.

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

[Daniel Beck]

On 23.11.2015, at 09:59, Itai Marko <itai....@whitesourcesoftware.com> wrote:

> Still, the commits were pushed yesterday evening but release 1.5.1 of the plugin is not available in the update center.
>

We had a problem with the update center generation. It should be fixed now, a new build is running. Expect it later today.

[Itai Marko]

The latest version of the White Source Jenkins plugin is still the previous 1.4 (I pushed 1.5.1)

--
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/teT0-_H9640/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/9667AFC0-D211-41D4-95F7-29745879469D%40beckweb.net.

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

[Itai Marko]

Great! now the new version is available in update center.

Thanks for your help.

Itai