create-text-file plugin - New hosting reuest

[Sanketh P B]

Dear Team,

Please find the new plugin details below.

GitHub url: https://github.com/sankethpb/create-text-file-plugin.git
Name of plugin: create-text-file
GitHub username and jenkins-ci.org user name: sankethpb
Description: Provides a build step to create a new text file, overwrite, append to end of file or insert at beginning of file. File can be saved in any extension.

Kindly provide the required access to host this plugin.

Thanks,
Sanketh

[Victor Martinez]

Hi Sanketh,

I've seen your plugin folder layout and I would suggest to use "org.jenkinsci.plugins.*" although it's not a mandatory feature but it might help to use the same layout as others.

You are also missing the wiki url which it's a mandatory field. See the below url:

https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins

May I ask you what's the use case of this plugin?

Cheers

[Daniel Beck]

On 06.12.2015, at 17:31, Victor Martinez <victormar...@gmail.com> wrote:

> I've seen your plugin folder layout and I would suggest to use "org.jenkinsci.plugins.*" although it's not a mandatory feature but it might help to use the same layout as others.

We don't really care about this. Tons of plugins use a custom group, and it's supported in hpi:create.

[Kanstantsin Shautsou]

Btw, is there any licenses about using "jenkins" as package/class names?

[Sanketh P B]

Use case is to generate a ReadMe.txt file after build with some info about changes and custom details.

I thought the wiki page has to be created after I get the required access to host the plugin, please correct me if I am wrong.
I could only remove "jenkins" from the group, if it's not allowed. I have seen a lot of plugins using custom group.

[Victor Martinez]

I didn't want sound rude at all, in case i was, sorry about it.

You can create it at anytime before releasing it, afaik there is already a new upcoming policy which won't show any plugins without any wiki references in the update center.

Cheers

[Christopher Orr]

On 06/12/15 19:45, Victor Martinez wrote:
> I didn't want sound rude at all, in case i was, sorry about it.
>
> You can create it at anytime before releasing it, afaik there is already a new upcoming policy which won't show any plugins without any wiki references in the update center.

This has been enforced for all new plugins since June.

But it's best add the wiki page and the POM tag *after* the plugin has
been forked, since the plugin may be renamed (or merged into another).
This is why creating a wiki page isn't listed in the "Prerequisites" or
"Request hosting" sections of the plugin hosting wiki page.

Regards,
Chris

[Sanketh P B]

Dear All,

I am currently waiting for hosting access for two plugins. Could you please provide the same? Kindly inform me in case anything needs to be changed.

Thanks,
Sanketh

[James Nord]

Whilst "we" don't care I do and "we" should.
It's ever so helpful when you see class names to be able to instantly know the plugin that contributes them rather than having to search (GitHub search sucks)
Using the mavens groupid.artifactid as the top level package is good form and provides this link.

[Sanketh P B]

Dear James,

Could you please suggest preferred group id? This plugin is a contribution from my organization, so we would like to have the organization name in group id.

Current group id: com.etas.jenkins.plugins

[Sanketh P B]

Any updates here?

[Oleg Nenashev]

Hi Sanketh,

I don't see any requirements regarding the group ID.
So IMHO the current approach is acceptable.

BTW my recommendation would be to adjust the plugin ID. Since you support not only "createFile" operations, maybe a wider "text-file-operations-plugin" would be better

пятница, 11 декабря 2015 г., 18:27:37 UTC+3 пользователь Sanketh P B написал:

Any updates here?

[Sanketh P B]

Dear Team,
Changed artifact id as per recommendation.

GitHub url: https://github.com/sankethpb/text-file-operations-plugin.git
Name of plugin: text-file-operations-plugin

GitHub username and jenkins-ci.org user name: sankethpb
Description: Provides a build step to create a new text file, overwrite, append to end of file or insert at beginning of file. File can be saved in any extension.

Kindly provide the required access to host this plugin.

Thanks,
Sanketh

[Daniel Beck]

Forked into https://github.com/sankethpb/text-file-operations-plugin

I also created a component of the same name on issues.jenkins-ci.org.

Remember to set a <url> in the pom.xml that points to a wiki.jenkins-ci.org plugin page, and to add the <scm> element to tag your releases.

> --
> 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/9f920825-45db-4be6-98f1-7c614bcfddd5%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Sanketh P B]

Thanks for forking it.

I am unable to commit to https://github.com/jenkinsci/text-file-operations-plugin.git, could you please provide commit access for the same?

Error:
remote: Permission to jenkinsci/text-file-operations-plugin.git denied to sankethpb.
fatal: unable to access 'https://github.com/jenkinsci/text-file-operations-plugin.git/': The requested URL returned error: 403

Thanks and Best Regards,
Sanketh

[Daniel Beck]

On 15.12.2015, at 17:06, Sanketh P B <pbsa...@gmail.com> wrote:

> could you please provide commit access for the same?

I did. You just need to accept the invitation into the jenkinsci organization by GitHub.

[Sanketh P B]

Hello All,

I need some help to perform release. I tried for second time now. I get the below error. Kindly suggest how to proceed?

[INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on project text-file-operations: Failed to deploy
 artifacts: Could not transfer artifact com.etas.jenkins.plugins:text-file-opera
tions:pom:1.2 from/to maven.jenkins-ci.org (http://maven.jenkins-ci.org:8081/con
tent/repositories/releases): Failed to transfer file: http://maven.jenkins-ci.or
g:8081/content/repositories/releases/com/etas/jenkins/plugins/text-file-operatio
ns/1.2/text-file-operations-1.2.pom. Return code is: 503, ReasonPhrase: Service
Unavailable. -> [Help 1]
[INFO] [ERROR]
[INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with the
-e switch.
[INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
[INFO] [ERROR]
[INFO] [ERROR] For more information about the errors and possible solutions, ple
ase read the following articles:
[INFO] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExe
cutionException
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 08:46 min
[INFO] Finished at: 2015-12-19T12:12:34+05:30
[INFO] Final Memory: 17M/304M

[Victor Martinez]

Hi,
You've got a Return code is: 503, ReasonPhrase: Service not available

Can you check if you can reach that URL?
Cheers

[Sanketh P B]

Hello Victor,

The url is reachable and the plugin is uploaded to https://repo.jenkins-ci.org/webapp/#/artifacts/browse/tree/General/public/com/etas/jenkins/plugins/text-file-operations/1.2, later it fails I tried thrice already.
I use the command mvn release:prepare release:perform -Dusername=... -Dpassword=

Thanks in advance,
Sanketh

[Victor Martinez]

Indeed

And that's exactly the information you can see in the below url:

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

I hope someone else might help you since it seems more a networking issue as far as I see

Cheers

[Sanketh P B]

Hello All,

Any hints to solve this issue?

Thanks,
Sanketh