How do I add my 'p4' plugin to Enterprise/Cloudbees

[pallen]

I have just started to use the Enterprise/Cloudbees hosting for Jenkins and was not able to add the 'p4' plugin.

Do I need to release my plugin to another location or get it 'approved' for the Enterprise version?

Thanks,

Paul

[Kanstantsin Shautsou]

I think this is a question for CloudBees support and not to jenkins.

[Stephen Connolly]

Jesse,

did you ever get around to fixing the matrix-project exclusion hack?

Causing p4 to be excluded IIUC

--
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/629d3d4e-1858-4e5c-b9c1-f7f42e6441e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Stephen Connolly]

Ah, ok, you did.

Paul: I'm seeing p4 in our update centers. We currently are only hiding our DEV@cloud plugins from the CloudBees Jenkins Enterprise update centers.

We were hiding matrix-project for some versions of Jenkins due to compatibility issues (and our update center - being smarter than us - hides any plugin that has a non-optional dependency on a plugin that it has been told to hide) but that was resolved on the 15th of April.

[Paul Allen]

I have recently added support back to Jenkins 1.568 (1.2.2-SNAPSHOT).

If I need to make 'matrix-project’ optional do let me know.

Kind regards,
Paul

> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMwgZF26PA%2BNomVWSJL_vs7y3%2B9Tm_Dghq9Kh-QUk_HJcg%40mail.gmail.com.

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

--------------------------------------------------------------------------------
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed. If
you have received this email in error please notify the system manager. Please
note that any views or opinions presented in this email are solely those of the
author and do not necessarily represent those of Perforce Software. Finally,
the recipient should check this email and any attachments for the presence of
viruses. Perforce Software accepts no liability for any damage caused by any
virus transmitted by this email.

Perforce Software UK Ltd is registered in England and Wales as company no.
3816019 at the following address: West Forest Gate, Wellington Road, Wokingham,
RG40 2AT, UK
--------------------------------------------------------------------------------

[Stephen Connolly]

It will only show up in our 1.580.x.y, 1.596.x.y, OSS LTS (1.596.x) and OSS HEAD (1.611?) update center lines then as 1.568 is not one of the lines we support

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4A206F08-7DB0-4058-A4B8-CE4A33384A39%40perforce.com.

[Paul Allen]

Just like Jesse’s ‘Mercurial' plugin I support back to 1.568 (later version are ok).

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

[Paul Allen]

The current release supports only 1.580.3 and newer.

[Paul Allen]

Thanks for the replies, but I guess I don’t understand the update centre.

The Mercurial plugin is listed and my POM/dependancies are practically the same, I must be missing something.

Latest SNAPSHOT:
https://github.com/jenkinsci/p4-plugin/blob/master/pom.xml

Last RELEASE:
https://github.com/jenkinsci/p4-plugin/blob/6d414673da44f776b03494a27f56f98b1fbf3678/pom.xml

Any ideas?

Thanks,
Paul

> On 27 Apr 2015, at 15:46, Stephen Connolly <stephen.al...@gmail.com> wrote:
>

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

[Stephen Connolly]

Your release is using Jenkins 1.580.3 as a baseline.

We use one update centre URL and redirect to the corresponding update centre based on the version in the ?jenkins_version= parameter on the request URL.

So this will not show up if using CJE 14.05. I see p4 when ?jenkins_version=1.580.1.1

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/B154FE4F-4029-4CCD-9F30-1BD70C965CC8%40perforce.com.

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

--
Sent from my phone

[Jesse Glick]

On Mon, Apr 27, 2015 at 5:52 AM, pallen <pal...@perforce.com> wrote:
> I have just started to use the Enterprise/Cloudbees hosting for Jenkins and
> was not able to add the 'p4' plugin.

$ curl -sL 'http://jenkins-updates.cloudbees.com/update-center.json?version=1.580.13.1'
| tail -n +2 | head -n -1 | json_pp | fgrep p4.hpi
"url" :
"http://jenkins-updates.cloudbees.com/download/plugins/p4/1.2.1/p4.hpi",

so it should be there already for Jenkins Enterprise. If you are
talking about DEV@cloud,

$ curl -sL 'http://dac-updates.cloudbees.com/update-center/restricted/update-center.json?version=1.580.3.2'
| tail -n +2 | head -n -1 | json_pp | fgrep p4.hpi

it is not currently there, since that update center uses a whitelist.
I staged it for inclusion but did not push the button, pending sanity
tests.

[Paul Allen]

Thank you for the explanation.

I think I was confusing the Enterprise with the DEV@Cloud. I have not seen or used the Enterprise version and we have just started to evaluate the DEV@Cloud.

(https://mataway.ci.cloudbees.com/)

One update centre makes sense, I had wondered if I had need to deploy it else where.

I guess there is a CJE version to Jenkins version map.

> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMy%2BLZX7zZT0TjftLu%2BuNZFLqqKy7zTdWpVSp3ehQ74RYg%40mail.gmail.com.

[Paul Allen]

Thanks. Lets hope the sanity tests pass.

Will this require an update to the white list every time I release a new version?

> --
> 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/CANfRfr2GMc_6W8jHdyDVHb-Nv3A33hvT1Y8pWYWH2R%3Dc%3DeZmMg%40mail.gmail.com.

[Kanstantsin Shautsou]

I think contacting CloudBees will be more efficient rather then asking on jenkins-maillist where this nuances knows only CB employers and not the whole jenkins community. 

From CB side it will be really effectively to document this on some of their documentation page.

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/DocwWFyYEdM/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/7A62F95A-155F-48F0-A50C-DD6096DCB31D%40perforce.com.

[Paul Allen]

You have a valid point. I contacted 'in...@cloudbees.com’ (on the 27th, via the website), but have not had a reply.

I guess the overlap is that the plugins are used in at least three communities OpenSource/Enterprise/Cloud, but developed in the OpenSource space. Deployment is where it gets specific, but I wan’t sure where to start asking.

> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/2296C9F6-241C-430D-9358-AF56C3162E7B%40gmail.com.

[Kanstantsin Shautsou]

I think CB filtering part of OpenSource plugins (review like iOS apps?). So this definitely not jenkins / infra problem.

> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/91C0E281-F340-4338-804E-E340C854ABB0%40perforce.com.

[Jesse Glick]

On Wed, Apr 29, 2015 at 9:34 AM, Paul Allen <pal...@perforce.com> wrote:
> You have a valid point. I contacted 'in...@cloudbees.com’ (on the 27th, via the website), but have not had a reply.

Our apologies. Please use a cloudbees.com channel for related
questions going forward. (If you have an account, as you seem to, then
it would be most straightforward to just file a support ticket, so you
can be assured someone is assigned to handle it.)