Re: Jenkins 2.0 initial setup plugin selection

On 24.02.2016, at 13:05, Victor Martinez wrote: > Mercurial and Perforce are not part of that list, although their usage are > not massive compare to Git or SVN, but might be also important to have them > as part of the SCM category. That's my point of view and

Re: 2.0-alpha-1 as a trial

*New version of Jenkins (2.0-alpha-1) is available for download (changelog ).* Showed up on my manage Jenkins page today, but the download link is 404 (I have the experimental update center

Re: Jenkins 2.0 initial setup plugin selection

On 24.02.2016, at 13:05, Victor Martinez wrote: > And I believe docker-commons is just an API plugin. My apologies for the spreadsheet not being clear enough -- Plugins to be part of the initial setup are those with "YES" in the Inclusion column. I stopped

Re: Jenkins 2.0 initial setup plugin selection

On 24.02.2016, at 13:05, Victor Martinez wrote: > What about docker plugin? It might be a good candidate as part of the plugin > selection as it's widely used and might alienate the concept of > reproducibility and configuration, which are nowadays quite trendy,

Re: Release appeared to work, but wiki not updated

Well-appreciated, thanks! On Wed, Feb 24, 2016 at 8:01 AM Daniel Beck wrote: > The wiki is fed from the update site metadata, and that is updated only > every four hours (plus, some caching which may delay things a few hours on > top of that). Since you published the plugin

New Plugin initial pushed on GitHub

Hi, I have created a Plugin to support the gitflow branching model and I convinced my boss tot o allow me to open source it. It is hosted on GitHub: https://github.com/OSTHUS/jenkins-gitflow-plugin The plugin works successfully for our setup, but not a lot of thought/effort has been put into

Re: Jenkins 2.0 initial setup plugin selection

What about docker plugin? It might be a good candidate as part of the plugin selection as it's widely used and might alienate the concept of reproducibility and configuration, which are nowadays quite trendy, with Jenkins. Mercurial and Perforce are not part of that list, although their usage

Re: 2.0-alpha-1 as a trial

On 24.02.2016, at 12:09, Robert Sandell wrote: > New version of Jenkins (2.0-alpha-1) is available for download (changelog). > > Showed up on my manage Jenkins page today, but the download link is 404 (I > have the experimental update center enabled). I fixed the

Re: Jenkins 2.0 initial setup plugin selection

If GitLab and GitHub triggers are on the list because of their SCM affiliation then Gerrit Trigger should be on the list as well. If the neighbour’s kids gets to go to the Prom then my baby should also go to the Prom! :-p /B On Wed, Feb 24, 2016 at 2:05 PM, Daniel Beck wrote:

Re: Jenkins 2.0 initial setup plugin selection

So what defines UI/Theme plugins? I see for example that extra-columns and sidebar-link made the cut? /B On Wed, Feb 24, 2016 at 8:08 AM, Oliver Gondža wrote: > On 02/23/2016 07:08 PM, Daniel Beck wrote: > >> >> On 22.01.2016, at 14:14, ogondza wrote: >>

Re: Jenkins 2.0 initial setup plugin selection

... and gravatar. And I believe docker-commons is just an API plugin. /B On Wed, Feb 24, 2016 at 11:44 AM, Robert Sandell wrote: > So what defines UI/Theme plugins? > > I see for example that extra-columns and sidebar-link made the cut? > > /B > > On Wed, Feb 24, 2016

Release configuration issue (version conflicts during release step)

All, I am attempting to release a newer version of my plugin but notice the final upload step appears to be uploading an old, existing, version of it. Consequently it fails. In my POM (attached) I have a newer version number that supersedes the existing. Would someone mind giving me a few

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

All, To add, I have already reviewed the HTTP 401 Unauthorized section of the Wiki post re: plugins: https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues

Update of crawler scripts for SonarQube Scanners

Hi guys, I have submitted a P/R to update some crawlers: https://github.com/jenkinsci/backend-crawler/pull/49 Could someone have a look and merge if everything is ok? Many thanks Julien -- You received this message because you are subscribed to the Google Groups "Jenkins Developers"

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

The version in the POM should always be a snapshot, e.g., `1.1-SNAPSHOT`, except during tagged release commits made by `mvn release: prepare release:perform`. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group

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

Jesse, All, Thanks for that. I did notice this discrepancy when looking into this further. I should have updated my email more promptly. I have managed to release, but I think I am running into a known issue: https://issues.apache.org/jira/browse/SCM-740 As it stands I now have a successful

(MultiJob) MultiJobAction serialization issue

Hi folks, I noticed a strange thing about the Multijob Plugin[1]. The MultiJobAction class (com.tikal.jenkins.plugins.multijob.MultiJobBuilder_- MultiJobAction, a private class) has a field 'build' of AbstractBuild type, which gets serialized not by reference, as other similar fields in other

Documentation review request: JenkinsBehindProxy

Hi, I'm nearing the end of verifying proxy support for the Jenkins TFS plugin and I thought I would update the proxy documentation in the Jenkins wiki , so I could point my users to it.

Re: new hadoop-plugin

I don't think its really a good idea to blow away the old version of the plugin - there may be users out there who rely on the functionality and changing it completely with no kind of upgrade path seems a little off to me (users might see the update, install it, and then find it completely breaks

Re: Adopt a plugin: job-import-plugin

Thanks Michael, i would also be willing to help out as a developer if you give me the rights. I am using this plugin also. -- 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,

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

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 plugin version is 1.580.1 > > org.jenkins-ci.plugins > plugin > > 1.580.1 > > To be certain, the 1.580.1 key is > appended

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

I can try the specific version. My plugin version is 1.580.1 org.jenkins-ci.plugins plugin 1.580.1 To be certain, the 1.580.1 key is appended where in the POM? Aside these two changes I have removed the release file and POM backup as to reset the prepare step. If this looks like all I

dashboard-view-plugin review request

https://github.com/jenkinsci/dashboard-view-plugin/pull/38 Polite week-later bump per PR instructions. In particular I think this change requires little specific knowledge of the plugin itself, and is more generally about pulling jenkins.forward and XSS protection. -- You received this

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

On Wed, Feb 24, 2016 at 1:44 PM, Ryan Black wrote: > Before I continue to iterate releases, perhaps in error, to have my > release version not include -SNAPSHOT, would you have any advice on this > scenario? Possibly you are accidentally using an old, and buggy, version of

Advice on plugin patch for Pipeline support

I'm working on a patch for a plugin to implement the SimpleBuildStep interface and I could use some advice. I've fixed up the simple issues, the areas I could do with a hand on are highlighted here: https://github.com/leth/cobertura-plugin/commit/52a2ce9b2ec9dde01ff9054e1184c2e833e00a60 The

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

Well.. by moving to 1.580.1 you are essentially forcing users to use at least that version of Jenkins. Given that there were numerous security issues and LTS releases since that release I would not worry too much. Cut a release when you have some bug fixes or further improvements. More releases

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: Jenkins 2.0 initial setup plugin selection

There's a demo video linked from the "Jenkins 2.0" wiki page: https://www.youtube.com/watch?v=kzRR8XR8hu4 Though I have a feeling a saw a newer version at FOSDEM; not sure where the code can be found (not that I've looked). Regards, Chris On 24/02/16 22:14, Ullrich Hafner wrote: > How is the

Re: Jenkins 2.0 initial setup plugin selection

Why BitBucket, GitLab, GitHub and not Gerrit? Gerrit is 100% OpenSource, whilst the same cannot be said about the others ;-) Luca. > On 24 Feb 2016, at 12:51, Daniel Beck wrote: > > > On 24.02.2016, at 13:05, Victor Martinez > wrote: > >>

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: Advice on plugin patch for Pipeline support

On Wed, Feb 24, 2016 at 5:16 PM, Marcus Cobden wrote: > https://github.com/leth/cobertura-plugin/commit/52a2ce9b2ec9dde01ff9054e1184c2e833e00a60 I added a couple of tips. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers"

Re: Jenkins 2.0 initial setup plugin selection

The Configuration Slicing plugin is also a must have from my POV On Thu, Feb 25, 2016 at 12:49 AM, Manfred Moser wrote: > 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 >

Re: Documentation review request: JenkinsBehindProxy

If there are no objections to these modifications, I'll save the new content tomorrow (Thursday) at 14:00 EST (19:00 UTC). If it will help, here's a preview of the proposed changes:

Re: [update] SimpleBuild DSL for pipeline (now a plugin)

But it's such sweet pain ;) OK I have released this for now: https://wiki.jenkins-ci.org/display/JENKINS/Simple+Build+For+Pipeline+Plugin On Wednesday, February 24, 2016 at 1:33:27 PM UTC+11, Jesse Glick wrote: > > On Sun, Feb 21, 2016 at 5:23 PM, Michael Neale >

Question About Documentation

Hey, I was working on a plugin and ran into two roadblocks. I need to do the following but there seems to be nothing that I can find on the wiki about these: 1. Store a variable, with a default value, for every project I am building with Jenkins 2. Make a file that can be downloaded

Re: Pull request to fix JENKINS-26318

Hi, Any response from the maintainer? Cheers On Thu, Feb 4, 2016 at 2:46 PM, Baptiste Mathus wrote: > Hi, > > Though this plugin is not (yet?) marked as "to be adopted", I feel like we > would actually need to check how the current maintainer feels about. > > @Slawomir: in

Re: [Google Summer of Code 2016] - We're looking for mentors

The today's Office Hours are in Jeopardy. I need to go to another city (urgent need), Baptiste and Tyler are on their vacations/project meetings. We're looking for the alternative 2016-02-23 13:52 GMT+03:00 Arnaud Héritier : > > > On Tue, Feb 23, 2016 at 10:32 AM, Oleg

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

Thanks Manfred! It looks like I should be good to go. Given the dated versions I use would you advise I submit a subsequent release using the new versions? This is really intended to be our initial release of this plugin. org.jenkins-ci.plugins plugin 2.3 fortify-on-demand-uploader

Re: Proposal: forbid direct commits to master for core

Is it weird only for me https://github.com/jenkinsci/jenkins/pull/1301 ? Could somebody describe? -- 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

Re: new hadoop-plugin

Hi Richard, The main reason is note I pasted from Jenkins wiki. Another reason is the old plugin has been inactive for 4 years and, as Andew's commented above, it's not useful and should just be retried. Do we have a process to sunset a plugin? Thanks, -Peter On Wednesday, February 24, 2016

Re: [Google Summer of Code 2016] - We're looking for mentors

I'm available to discuss the proposals, so if anyone's interested, join me in the Hangout! On 24.02.2016, at 10:45, Oleg Nenashev wrote: > The today's Office Hours are in Jeopardy. > I need to go to another city (urgent need), Baptiste and Tyler are on their >

Re: Jenkins 2.0 initial setup plugin selection

Are we talking in this thread about the left or right selection in this demo (or both)? I.e. "Recommended plugins“ or "Customize your Plugins“? > Am 24.02.2016 um 22:30 schrieb Christopher Orr : > > There's a demo video linked from the "Jenkins 2.0" wiki page: >

Re: Jenkins 2.0 initial setup plugin selection

Nice work! I'm not sure whether `javadoc` (row 17, YES) is a useful suggestion; it's seemingly only high on the list because it used to be part of core. Having set up some jobs last week for various types of software projects, the Javadoc- and Doxygen-specific plugins don't seem to offer any

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

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