Re: [DISCUSS] Time for Jenkins to require Java 8 to run

We recently did an upgrade to the latest 1.651.3 (latest 1.6 version) and had performance issues. When we switched to run it on Java 8 instead of Java 7 they all went away. We also had some plugin related problems. I am mentioning this because this shows that all developers are using 1.8 and most

Re: Build fauiler while plublishing the plugin

Then something with your git/ssh and auth setup is wrong. manfred On Thu, Oct 13, 2016 at 8:50 AM, wrote: > > scm:git:ssh://github.com/jenkinsci/catalogic-ecx-plugin.git > > scm:git:ssh://g...@github.com/ > jenkinsci/catalogic-ecx-plugin.git >

Re: Build fauiler while plublishing the plugin

You cant use https in the scm section. You ahve to use ssh as in the example I linked earleir On Wed, Oct 12, 2016 at 1:25 PM, wrote: > scm element in pom file has the following content > > > scm:git:https://github.com/jenkinsci/ > catalogic-ecx-plugin.git >

Re: Build fauiler while plublishing the plugin

What does the scm element in your pom look like? E.g. a correct setup can be seen here https://github.com/jenkinsci/tfs-plugin/blob/master/pom.xml#L42 On Wed, Oct 12, 2016 at 11:05 AM, wrote: > > Here is the output with -X option > > [INFO] Resuming release from phase

Re: Build fauiler while plublishing the plugin

Looks like your plugin github scm url is wrong. On Wed, Oct 12, 2016 at 10:23 AM, wrote: > I am trying to publish the plugin by running the maven command below: > > $ mvn -X -s settings.xml release:prepare release:perform -Dusername=... > -Dpassword=... > > > The build

Re: Interested in building your plugin on ci.jenkins.io?

es inline) > > On Mon, 08 Aug 2016, Manfred Moser wrote: > > > Hi Tyler, > > > > Can you point me to some docs on setting that up. I would like to create > > that setup for the tfs jenkins plugin. > > > Does the tfs plugin require Windows-based agents

Re: Interested in building your plugin on ci.jenkins.io?

Hi Tyler, Can you point me to some docs on setting that up. I would like to create that setup for the tfs jenkins plugin. Manfred On Mon, Aug 8, 2016 at 8:48 AM, R. Tyler Croy wrote: > Howdy there, your friendly project infrastructure dude here. I'm hoping to > get > more

Re: What NPM proxies do I need to build Blue Ocean

The Nexus issue you reference is NOT for 2.x... so it does not apply. On Fri, Jul 8, 2016 at 6:55 AM, Cliff Meyers wrote: > Would that be worth calling out in the README for the benefit of other > Nexus 2.x users? > > -Cliff > > > On Tue, Jul 5, 2016 at 4:16 AM, Stephen

Re: Automatic Plugin Documentation [GSOC 2016]

I certainly agree that pulling docs from master is the wrong approach. Just like pull the code from master and just building a plugin would be wrong. On Fri, May 20, 2016 at 3:07 AM, Cynthia Anyango wrote: > But I do not want to confuse users with documentation that

Re: Automatic Plugin Documentation [GSOC 2016]

I can migrate one > of them to Asciidoc. > If there are specific format requirements, let's try to prototype them. > > BR, Oleg > > понедельник, 9 мая 2016 г., 23:14:10 UTC+2 пользователь Manfred Moser > написал: >> >> I am all for asciidoc first, its the bette

Re: Automatic Plugin Documentation [GSOC 2016]

I am all for asciidoc first, its the better format after all ;-) On Mon, May 9, 2016 at 1:53 PM, Baptiste Mathus <m...@batmat.net> wrote: > +1 Manfred. > IMO, this could even be asciidoc first, and possibly some Markdown flavour > (prolly GH's) secondly. > > > 2016-05-09

Re: Automatic Plugin Documentation [GSOC 2016]

I sure hope this will work with asciidoc as well as markdown files ;-) On Mon, May 9, 2016 at 10:54 AM, Cynthia Anyango wrote: > > Hey Martinda , > > Thanks for your feedback . > > All that you have mentioned is within the scope of my project . > > As @Daniel

Re: I can't use archetype and set java.version to "8"

Nice ;-) On Tue, Apr 12, 2016 at 12:39 PM, Jesse Glick <jgl...@cloudbees.com> wrote: > On Fri, Apr 8, 2016 at 5:04 PM, Manfred Moser <mosa...@gmail.com> wrote: > > Yes there is. We got this published and done via mojohaus recently > > My apologies; looked for it i

Re: I can't use archetype and set java.version to "8"

/#artifactdetails%7Corg.codehaus.mojo.signature%7Cjava18%7C1.0%7Cpom On Fri, Apr 8, 2016 at 1:18 PM, Jesse Glick <jgl...@cloudbees.com> wrote: > On Fri, Apr 8, 2016 at 1:21 PM, Manfred Moser <mosa...@gmail.com> wrote: > > You probably have to override the animal sniffer co

Re: I can't use archetype and set java.version to "8"

You probably have to override the animal sniffer config with the correct signature file version. On Fri, Apr 8, 2016 at 10:19 AM, 'Dan Alvizu' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > I followed the instructions in the plugin tutorial to create a new plugin, > and I

Re: Suggestion: documentation as part of the plugin under SCM

On the TFS plugin we recently moved out docs to the github code repo as a readme . https://github.com/jenkinsci/tfs-plugin And if you want to get more fancy you could easily create a documentation site with the maven site plugin and writing the docs themselves in markdown or asciidoc. E.g. check

Re: Making a specific SCM Repository Browser the default

Yeah... I think we will look into this in the upcoming or following release. Manfred On Thu, Feb 25, 2016 at 12:45 PM, Jesse Glick <jgl...@cloudbees.com> wrote: > On Tue, Feb 23, 2016 at 5:05 PM, Manfred Moser <mosa...@gmail.com> wrote: > > From what I can tell if I return

Re: Jenkins 2.0 initial setup plugin selection

I would suggest to add the config file provider plugin in the recommended plugins. It seems to be the best way to provide Maven and other settings file to a cluster without having to provision them on the nodes directly. Unless there is some other preferred method I dont know about. On Wed, Feb

Re: Documentation review request: JenkinsBehindProxy

The wiki edits look good to me. If the proxy config is indeed global it seems to be located in the wrong spot in the UI. Probably a historic thing that should be fixed in 2.0. I would apply those changes and move on. Manfred On Wed, Feb 24, 2016 at 9:47 AM, Olivier Dagenais <

Re: Jenkins 2.0 initial setup plugin selection

Interesting.. that video reminded me of the email from Olivier about the proxy server config. How will a case be handled were the initial start up in a datacenter requires configuration of a proxy server to be able to get to the internet/update center? JVM proxy config or some UI? manfred On

Re: Release configuration issue (version conflicts during release step)

rs build artifacts and uploads them to Fortify on Demand > service with user-specified options. > > https://wiki.jenkins-ci.org/display/JENKINS/Fortify+On+Demand+Uploader+Plugin > > > 1.580.1 > > > > > > > > > On Wednesday, February 24, 20

Re: Release configuration issue (version conflicts during release step)

also use the parent pom version 2.3 ... On Wed, Feb 24, 2016 at 11:53 AM, Ryan Black wrote: > Try the specific Maven release plugin, I should say. > > > > > > On Wednesday, February 24, 2016 at 1:52:17 PM UTC-6, Ryan Black wrote: >> >> I can try the specific version. My

Re: Jenkins 2.0 initial setup plugin selection

At least it will easily be possible to have it NOT available so unknowing users dont get into trouble. I strongly believe that a lot of people only use this because they dont even know about the Maven build step. Maybe we should change the job type title to include something like "deprecated" or

Re: Making a specific SCM Repository Browser the default

ade the plugin to 1.568 or higher and trying to do that led me down into a rats nest of other changes and headaches. I would love some confirmation that this is the right approach before I pursue this more. Or are there any better approaches? thx Manfred On Tue, Feb 23, 2016 at 12:31 PM, Manfred Mo

Making a specific SCM Repository Browser the default

Hi all, I am working on the tfs-jenkins-plugin and I would like to make the default value for the Repository Browser to be NOT Auto but instead be the repository browser implemented by the plugin itself since there is only one. How can I set that default value? We have it implemented so that it

Re: Requesting tfs-plugin access

> > Confirmed! >> > >> > (sorry about the delay; I stopped following this list a while back) >> > >> > Cheers, >> > - Oli >> > >> > On Monday, January 25, 2016 at 1:28:17 PM UTC-5, Daniel Beck wrote: >> > >> > On

Re: Requesting tfs-plugin access

Can some JIRA admin please check my privileges. It seems that I can not e.g. close this issue https://issues.jenkins-ci.org/browse/JENKINS-30443 I dont have access to change any of the workflow stages. On Wed, Jan 27, 2016 at 10:48 AM, Manfred Moser <mosa...@gmail.com> wrote: >

Re: Requesting tfs-plugin access

://issues.jenkins-ci.org/browse/JENKINS-30445 https://issues.jenkins-ci.org/browse/JENKINS-30446 Thanks Manfred On Wed, Jan 27, 2016 at 11:33 AM, Daniel Beck <m...@beckweb.net> wrote: > > On 27.01.2016, at 20:27, Manfred Moser <mosa...@gmail.com> wrote: > > > I dont have access to

Re: Jenkins signup

https://wiki.jenkins-ci.org/display/JENKINS/Issue+Tracking https://jenkins-ci.org/account/ On Mon, Jan 25, 2016 at 9:39 AM, Bin Shi wrote: > > Hi there, > > Could you help me to set up Jenkins account so that I can log an issue? > > Thanks, > Bin > > -- > You received

Requesting tfs-plugin access

Hi everyone, I have been helping with PRs, reviews and JIRA cleanup on the tfs-plugin and been in contact with Olivier (https://github.com/olivierdagenais) regularly. I would like to have my privileges raised so I can commit pull requests to master and close and otherwise manage issues in

Status of TFS plugin / Commit access?

Hi everyone, I have a need for a few fixes on the TFS plugin for Jenkins. Looking at the project in github I see 9 open pull requests. The last release was in Feb 2014. Is there anybody maintaining the plugin and willing to cut a release in the near future. I am going to be working on some