Publish EZ-Templates plugin

[JoelJ]

I'm the admin of this plugin repo: https://github.com/JoelJ/ez-templates

This plugin is for creating templates for your jobs. You create a Template job (which functions as any job), then when you're creating a new job of the same type you can select the templates and it will copy the configuration over, except for the parameters. It will also keep the implementing job in sync with the template.

This plugin is actually being used by many people/companies who have just been compiling and deploying manually. We have a BuildHive job running for it now, and I think it's time we make it publicly accessible. :)

[Mark White]

+1

This is a great plugin and it would be great to be able to use and update it without building it manually.

Mark.

[Ioannis Moutsatsos]

+1 as well! 

Reading the git docs I'ma bit confused as to how project parameters in these templates are inherited?

I have several jobs that share a group of parameters. Could I create a job template that would allow derived jobs to inherit them?

Thanks and best regards

Ioannis

[Kanstantsin Shautsou]

What is "ez" ?

Do you really need require 1.574 ?

Do you really need skip InjectedTests?

[Krishna Gundala]

+1 

--
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/8cb01704-64fe-490f-9ee3-79e823c7ed38%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Brantone]

+100 ... would be great to see this published and into the main listing..

[Daniel Beck]

Yeah it looks like we dropped the ball on this one.

Joel, are you still interested in hosting in the jenkinsci org and the Jenkins update site?

> --
> 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/5b90915c-8596-4993-8144-0141f53e2937%40googlegroups.com.

[Marc Carter]

Update site - hell yes. But what is the benefit of migrating the source into jenkinsci?

[JoelJ]

No worries. We are still very interested in bringing it in and get requests on nearly a weekly basis from users to have it made available :) So I'm sure the Jenkins community will appreciate having better access to this plugin.

[dana...@gmail.com]

I am waiting to play with this plugin :D....put it in already (in a dirty way :) )

[Daniel Beck]

On 16.07.2015, at 21:59, JoelJ <johnson...@gmail.com> wrote:

> No worries. We are still very interested in bringing it in and get requests on nearly a weekly basis from users to have it made available :) So I'm sure the Jenkins community will appreciate having better access to this plugin.

Great!

I forked the repo to https://github.com/jenkinsci/ez-templates-plugin and made you a committer. Welcome aboard!

Please review https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins to find out what to do now. The next steps include:
- Set up a jenkins-ci.org account and tell us your account name so we can set up a component on issues.jenkins-ci.org.
- Adjust the SCM information in the pom.xml so you release from the jenkinsci org repo in the future.
- Create a plugin page on wiki.jenkins-ci.org and reference that in the <url> element in the POM.

[Brenton]

Happy Dance!!!

Looking forward to seeing this active in the repo!!!

--
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/NVLHCFegfYw/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/8C698734-841C-4927-A003-095F09D5A99F%40beckweb.net.

[JoelJ]

Thanks! My Jenkins username is: "joelj"

[Daniel Beck]

Done! There's now a component 'ez-templates-plugin' in JIRA, and you're the default assignee.

[Brantone]

@JoelJ - any further movement on your end??

[Mark Sinclair]

I'm in the process of installing maven just so I can get this plugin.  It would be fantastic if it were available directly through Jenkins.

[Baptiste Mathus]

Hi,
The thing is it could, granted there's actually someone ready to maintain it. Maybe try and ping the authors to get a release.

-- Baptiste

Le 2 déc. 2015 10:09 PM, "Mark Sinclair" <msin...@juniper.net> a écrit :

I'm in the process of installing maven just so I can get this plugin.  It would be fantastic if it were available directly through 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-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/05debb66-e229-4945-ae65-1ab5b8ff71f8%40googlegroups.com.

[Marc Carter]

Hi all,

I am the other maintainer on ez-templates. To finish off co-opting it into the jenkinsci family could you please:
* Add 'drekbour' as a committer
* Enable Issues for jenkinsci/ez-templates.
** I'm sure this has been discussed elsewhere but for a small plugin hosted in GH I see no reason to have issues anywhere else than right next to the code.

Regards, Marc

[Baptiste Mathus]

Hi,

Added you as a committer to the plugin.

As for issues, actually (apart from the fact I don't have permissions to enable it anyway), many if not the majority of plugins are small, and generally issues are not enabled and are managed inside the Jenkins JIRA. (You can see JIRA listed in the associated wiki page: https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Requesthosting)

Makes it easy to link issues between plugins and so on. And gives a central place to search for issues. And the issues of a plugin have an autogenerated link from the plugin wiki page macro (note: plugin wiki page is compulsory to get your plugin visible from the update center).

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/bb391fc1-95ec-42e1-a771-06b3f6b50400%40googlegroups.com.

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

--

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

[Kanstantsin Shautsou]

Hi Marc,

You should have admin perm inside your repo (if jenkins bot didn’t fail again) and you should be able enable it yourself (don’t forget accept invitation in GH).

You may ignore JIRA issues (like many people do ;), but if you will have some relative core/other plugins issues you should better fill JIRA issues and link them against. 

In my plugins i’m using GH issues and wikis as it more allows me faster development.

Wiki badge (macros), that mentioned @batmat is hardcoded to provide link only to JIRA issues. You can wrote in wiki documentation that you accepting issues only via GH issues. Main goal exclude barrier for people that wants report issue and wiki page with it’s badge today is entry point for plugin (so you should describe where issues, PRs, repo, docs and changelogs are available). 

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/NVLHCFegfYw/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/CANWgJS40R8vzWR6qd6mDNyKuefYuSGv6K-Xt1RzErFWr7gJ0%3Dw%40mail.gmail.com.

[Marc Carter]

Thanks all.
I have an email "You’ve been added to the ez-templates-plugin Developers team" which seems to tally up with the inability to enable Issues. Hopefully that will sort itself out soon.

Thanks for the tips regarding GitHub / Jira. I'll point users in the same direction, plugin-specific issues via GH, anything wider reaching will get "promoted" into JIRA.

[Marc Carter]

Initial plugin deployment didn't work very smoothly. It clearly edited the pom, added it, then did NOT commit that before tagging 1.0.
Hence, what is uploaded to the marketplace is now 1.0-SNAPSHOT.

I'm using Maven 3.3.9 but the plugin's parent POM is quite old at 1.574.
Can anyone advise?


[INFO] Checking in modified POMs...
[INFO] Executing: /bin/sh -c cd ~/dev/jenkins/ez-templates-plugin && git add -- pom.xml
[INFO] Working directory: ~/dev/jenkins/ez-templates-plugin
[INFO] Executing: /bin/sh -c cd ~/dev/jenkins/ez-templates-plugin && git status
[INFO] Working directory: ~/dev/jenkins/ez-templates-plugin
[INFO] Tagging release with the label 1.0...
[INFO] Executing: /bin/sh -c cd ~/dev/jenkins/ez-templates-plugin && git tag -F /tmp/maven-scm-1081470449.commit 1.0
[INFO] Working directory: ~/dev/jenkins/ez-templates-plugin
[INFO] Executing: /bin/sh -c cd ~/dev/jenkins/ez-templates-plugin && git push ssh://g...@github.com/jenkinsci/ez-templates-plugin.git 1.0
[INFO] Working directory: /home/marc/dev/jenkins/ez-templates-plugin
[INFO] Executing: /bin/sh -c cd ~/dev/jenkins/ez-templates-plugin && git ls-files
[INFO] Working directory: ~/dev/jenkins/ez-templates-plugin
[INFO] Transforming 'EZ Templates'...
[INFO] Not removing release POMs
[INFO] Checking in modified POMs...
[INFO] Executing: /bin/sh -c cd [INFO] Checking in modified POMs...

[Baptiste Mathus]

Hi,

As you rely on an old parent pom indeed, the maven-release-plugin you're using is borked.

See https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues

See https://github.com/jenkinsci/buildtriggerbadge-plugin/blob/master/pom.xml#L62 for a live example to prevent that issue in the future and not be forced to use the fully qualified CLI maven call (better for long term as even if *you* remember to use that form, every other maintainers must think about it too when releasing).

HTH

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/37e5d37a-9556-48b2-a017-62b91cf11ff4%40googlegroups.com.

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

[Marc Carter]

Thanks for that - I guessed as much. So ... What is the policy on plugin dependencies? Clearly ez-templates has no hard-req on anything newer than 1.574 but I don't just want to force users onto the latest LTS (and would that be the initial LTS or the newest maintenance release on that base...). What is recommended?

[Marc Carter]

Can an admin please purge some bad versions of ez-templates from the plugin repo
  http://repo.jenkins-ci.org/public/org/jenkins-ci/plugins/ez-templates/

1.0-SNAPSHOT is mistake caused by myself
1.0.0, 1.0.1 and 1.0.2 were uploaded by someone random a month ago and are not official (nor newer than 1.0). I'm sure they were just eager to see it uploaded but let's clear house please.

Marc

[Daniel Beck]

On 13.12.2015, at 22:47, Marc Carter <drek...@gmail.com> wrote:

> 1.0-SNAPSHOT is mistake caused by myself

Snapshots don't matter.

> 1.0.0, 1.0.1 and 1.0.2 were uploaded by someone random a month ago and are not official (nor newer than 1.0). I'm sure they were just eager to see it uploaded but let's clear house please.

Could you confirm that the user 'arpitgold' has never been a contributor to or maintainer of ez-templates, and no reason to publish this plugin into our repo?

FWIW we've always blacklisted versions from the update site in the past -- not sure whether it was easier than removing artifacts or for a different reason, so I'd like to keep to the established process for now. Alternatively, if you could release a 1.1, that would probably be best.

> What is the policy on plugin dependencies? Clearly ez-templates has no hard-req on anything newer than 1.574 but I don't just want to force users onto the latest LTS (and would that be the initial LTS or the newest maintenance release on that base...). What is recommended?

No fixed rules. Keeping to an older core dependency is fine. A while back I added a section to this wiki page explaining the trade-off:
https://wiki.jenkins-ci.org/display/JENKINS/Choosing+Jenkins+version+to+build+against

Note that we *really* do prefer use of Jira for various reasons even if a small number of plugin developers disagrees -- while I doubt we'll ever shut down established GH trackers, we're disabling GH issues when forking for a reason.

[Marc Carter]

Arpit does have a PR open on Github but was not a developer in the sense of direct repo access. I'm sure he was just being keen as we evidently took several months to push this publication process through.

I'll just release 1.1 as described.

[Marc Carter]

#1
ez-templates-1.1 was deployed to the repo on Dec 14th ...
  http://repo.jenkins-ci.org/public/org/jenkins-ci/plugins/ez-templates/
... but it's plugin info on the wiki page is blank ...
  https://wiki.jenkins-ci.org/display/JENKINS/EZ+Templates+Plugin
... and it doesn't appear in the update center...
  https://updates.jenkins-ci.org/download/plugins/

What did I miss?

#2
Can I have admin on jenkinsci/ex-templates-plugin please

[Daniel Beck]

On 16.12.2015, at 08:41, Marc Carter <drek...@gmail.com> wrote:

> #1
> ez-templates-1.1 was deployed to the repo on Dec 14th ...
> http://repo.jenkins-ci.org/public/org/jenkins-ci/plugins/ez-templates/
> ... but it's plugin info on the wiki page is blank ...
> https://wiki.jenkins-ci.org/display/JENKINS/EZ+Templates+Plugin
> ... and it doesn't appear in the update center...
> https://updates.jenkins-ci.org/download/plugins/
>
> What did I miss?

My apologies. It seems I blacklisted version 1.1 from the update center for being broken and resulting in errors during update site generation (I think there was a POM but nothing else). 1.1.1 should go through without problem though.

> #2
> Can I have admin on jenkinsci/ex-templates-plugin please

Anything specific I can set up for you?

[Daniel Beck]

On 17.12.2015, at 02:10, Daniel Beck <m...@beckweb.net> wrote:

> I blacklisted version 1.1 from the update center

20 days ago, by the way -- unrelated to anything you released.

>>
>> #2
>> Can I have admin on jenkinsci/ex-templates-plugin please
>
> Anything specific I can set up for you?

To clarify, I'm not opposed, just trying to understand the need.

[Marc Carter]

1.1.1 deployed although Maven failed with the below (after clearly uploading successfully) , will check back tomorrow.

[INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on project ez-templates: Failed to deploy artifacts: Could not transfer artifact org.jenkins-ci.plugins:ez-templates:hpi:1.1.1 from/to maven.jenkins-ci.org (http://maven.jenkins-ci.org:8081/content/repositories/releases): Access denied to: http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/ez-templates/1.1.1/ez-templates-1.1.1.hpi, ReasonPhrase: Forbidden. -> [Help 1]

>> #2
>> Can I have admin on jenkinsci/ex-templates-plugin please
>
> Anything specific I can set up for you?

To clarify, I'm not opposed, just trying to understand the need.

Just the issue tracker. I understand the desire for centralised management but, from the other end of this process, I see that github issue tracker as lingua franca of community interaction for a tiny project. Although under jenkinsci, it's still a "tiny project" to us !

[Baptiste Mathus]

Seems to me that though hosting plugins come with very few restrictions/rules, it's sad to find cases like here: It'll more complex for users, less unified. 

And as Daniel said, hosting has never actually been designed to use GH issues, and the wiki page macro will just point to something wrong...

 

--

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/81c8cf71-4bbf-40db-8794-0b1cf211118f%40googlegroups.com.

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

[Marc Carter]

Ok. I'll hold off on the Issues issue and see how it goes.

ez-templates-1.1.1 has still not emerged into the update center!

[Slide]

I've seen it take up to 24 hours...

On Thu, Dec 17, 2015 at 1:06 PM Marc Carter <drek...@gmail.com> wrote:

Ok. I'll hold off on the Issues issue and see how it goes.

ez-templates-1.1.1 has still not emerged into the update center!

--

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/03f3bc19-0765-4238-9cd8-289b87099cc5%40googlegroups.com.

[Baptiste Mathus]

IIUC, update job is currently running https://ci.jenkins-ci.org/job/infra_update_center_v3/

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

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

[Daniel Beck]

On 17.12.2015, at 21:06, Marc Carter <drek...@gmail.com> wrote:

> ez-templates-1.1.1 has still not emerged into the update center!

We're having some issues with the update site generation right now. If you're really bored, monitor https://ci.jenkins-ci.org/job/infra_update_center_v3/

[Daniel Beck]

The update sites have been updated.

I'll blacklist the rogue releases, they are offered in the 1.565 update sites as they have a lower Jenkins core requirement.