Dear Team,
Please find the new plugin details below.
GitHub url: https://github.com/sankethpb/assemblyInfo-updater
Name of plugin: assemblyInfo-updater
GitHub username and jenkins-ci.org user name: sankethpb
Description: Provides a build step to update file version, product version and
copy
In case anyone considers working on this please also consider
https://issues.jenkins-ci.org/browse/JENKINS-26231 :)
Thanks! Br,
Christoph
On Friday, December 4, 2015 at 10:04:39 PM UTC+1, Richard Bywater wrote:
>
> Can I suggest we change the content type to application/javascript then at
> lea
On 05/12/15 16:22, Christopher Orr wrote:
> Similarly, "project spaces" is not further expanded upon — all jenkinsci
> repos? jenkins-infra? plugin repos/wikis/websites?
My previous email was a bit long, so I wanted to try and list the spaces
that I could think of, where it seems that adherence to
Hi there,
Thanks for the update!
While the Contributor Covenant seems reasonable, it also appears to be a
pretty generic template, and I find it leaves a lot of ambiguity that
could be expanded upon.
>From the first sentence, the Code of Conduct applies to "this project" —
which I would assume m
+1 indeed, shoud've done that in the first place. Gonna rename just now.
Maybe meister is a bit less generic, but having the same issue.
2015-12-05 15:11 GMT+01:00 Daniel Beck :
> Given how generic the name is, could we rename the plugin (artifactId) to
> openmake-release-engineer, and the repo t
Given how generic the name is, could we rename the plugin (artifactId) to
openmake-release-engineer, and the repo to openmake-release-engineer-plugin?
Additionally, the plugin description in the POM needs to be improved to
actually explain what the plugin does.
On 05.12.2015, at 08:29, Baptiste
+1
On Fri, Dec 4, 2015, 18:09 R. Tyler Croy wrote:
>
> As the Jenkins community has grown, it has become clear that we need to
> write
> down what behaviors we welcome in our community, but more importantly,
> what is
> not welcome.
>
> I would like to invite you all to review and provide feedb
please ignore may previous email. I do have commit access.
sorry for the confusion.
kind regards.-
On Sat, Dec 5, 2015 at 11:20 AM, Federico Larsen wrote:
> Hi Baptise,
>
> I didn't get commit access to the repo. My github id is: larsenfed
>
> Thanks in advance for your help.
> Kind regards.
> D
Hi Baptise,
I didn't get commit access to the repo. My github id is: larsenfed
Thanks in advance for your help.
Kind regards.
Done: https://github.com/jenkinsci/copado-plugin
Beware to create the associated wiki page + update the pom.xml/url tag to
point to it.
Plugins without a wiki are very so