Re: [GSoC2016] Interested in Test-Automation Project

Hi, We will definitely appreciate contributions in this area. I think it makes sense to sync-up with Tyler (in Cc), who is the INFRA officer right now. Best regards, Oleg Nenashev 2016-03-09 12:19 GMT+03:00 Krishna Gundala : > Ohh... i missed this. > I am not a student

Re: Updating from cloudbees docker build and publish v1.0.1 to v1.1 causes docker build failures.

A bulk-ish update could be scripted. On Thu, Mar 10, 2016 at 5:26 PM nicolas de loof wrote: > looks to me the plugin didn't correctly handle legacy data migration > > in 1.0 dockerfilePath was used to store the build context - as there was > only one possible

Re: Updating from cloudbees docker build and publish v1.0.1 to v1.1 causes docker build failures.

looks to me the plugin didn't correctly handle legacy data migration in 1.0 dockerfilePath was used to store the build context - as there was only one possible dockerfile the variable name looked good in 1.1, support for --file was introduced by changing the meaning of this field, and adding

Requesting commit access to ci-game-plugin

Hey, I submitted a pull request ( https://github.com/jenkinsci/ci-game-plugin/pull/18) to the ci-game-plugin project last week and haven't heard anything back. It looks like the project has been fairly stale so I'm also willing to be a maintainer for this project. My GitHub username is

[GSoC2016]- update plugin 2.0

Looking at the update center issue, I can figure out there is a lot of work to do. In nutshell, below tasks need to get done- 1-Switch from update fetching (from update-centre.json) technique to a technique which supports portability so that user can install other plugins that may not follow

[GSoC2016]-Update Center 2.0

Looking at the update center issue, I can figure out there is a lot of work to do. In nutshell, below tasks need to get done- 1-Switch from update fetching (from update-centre.json) technique to a technique which supports portability so that user can install other plugins that may doesn't

Re: Jenkins 2.0 initial setup plugin selection

On 23.02.2016, at 23:20, Daniel Beck wrote: > Hi everyone, > > I added two additional criteria to the wiki: The plugin shouldn't require a > restart to work (otherwise it's not exactly a great getting started > experience), and it shouldn't be just a UI/theming plugins that

Re: One-Shot Executors

" I do agree that certain issues should fail immediately (image not found). Certain other issues should perform exponential backoff (Cloud infrastructure down). Provisioning limits could be annoying though, would be interesting if they could be left in the queue until Jenkins side provisioning

Re: Updating from cloudbees docker build and publish v1.0.1 to v1.1 causes docker build failures.

OK, interested in how things are when you upgrade docker. I'll take a closer look at the confusion around Dockerfile name vs path. On Thursday, March 10, 2016 at 7:18:49 AM UTC+11, Liam wrote: > > So our Jenkins machine is running docker 1.7.1 atm. We're going to upgrade > to 1.10 shortly. >

Re: One-Shot Executors

On Wed, Mar 9, 2016 at 11:52 AM, Suckow, Thomas J wrote: > Certain other issues should perform exponential backoff (Cloud > infrastructure down). Or just fail the build and the next one should work. > It could also handle the logic of some users wanting to configure

Re: [GSoC2016] Jenkins WebUI

Oleg, thank you for today's office hours, that was very helpful! I am looking for the next meeting to discuss WebUI project in more details. I CCed orgs mailing list. Hopefully, there will be convenient time to gather and talk about the project. Here I also would like to update you on my

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

On Wed, Mar 9, 2016 at 12:11 PM, Rafael Rezende wrote: > is there any documentation > about the Jenkins release process behind the scenes? For example, when > someone wants to contribute with a new plugin, a whole environment is > created around it (github repo, confluence

Re: Updating from cloudbees docker build and publish v1.0.1 to v1.1 causes docker build failures.

So our Jenkins machine is running docker 1.7.1 atm. We're going to upgrade to 1.10 shortly. I don't think that we actually need to change anything, and it's not like we can rewrite past versions or anything, for me it's more about providing a working migration path forwards. Even if that

Re: Jenkins winstone-3.2 (embedded Jetty 9) integration into master (ref: JENKINS-33412)

Seems straightforward. https://github.com/jenkinsci/jenkins/pull/2108 On 08.03.2016, at 22:48, elijah.zupan...@joyent.com wrote: > I work for a public cloud provider (Joyent) and a number of our customers > have stumbled into a Jenkins issue when running in a containerized > environment or on

Re: Proposal: forbid direct commits to master for core

Personally the way I see it possibly the issue isn't really with having a PR or not - it seems to me that the issue was more with not having a discussion first somewhere prior to committing about the approach / issue. (Or maybe there was - in which case ignore my view :) ) Richard On Thu, 10 Mar

Re: Add and config UI for v2

Hey all, if you are at all interested in the Jenkins GUI for v2 I have a PR you might look at:https://github.com/jenkinsci/jenkins/pull/2106 At the moment, it is closed while I fix some tests, but open for comments. -- You received this message because you are subscribed to the Google Groups

[GSoC2016] - New generation of Fingerprinting engine for Jenkins - Draft project proposal for review

Hi all, Please help to comment on my draft proposal. https://docs.google.com/document/d/1WpGJ58ZconAUWZ2tUo3T8M-8xJustI9sEBn0tGVaYIY/edit?usp=sharing Regards, Mayuran -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from

XML comment removed after UI save

I have developed a client application that lets me edit the Jenkins job config XML file and push the change to the Jenkins server. It works great and I'm happy that Jenkins provides me with APIs that lets me do something like this. Now here is problem that I would like to solve. When I have

Re: Release not listed for download

I ran into a similar issue while releasing build-metrics-plugin which haven't been released for a long time. I fixed it by bumping maven-release-plugin dependency, in https://github.com/jenkinsci/build-metrics-plugin/commit/3c3a1b07f4ef8d61bd86c329f859e8769dcd23f9 You will need to delete

Re: One-Shot Executors

> On Mar 9, 2016, at 19:52, Suckow, Thomas J wrote: > > I like that this moves the provisioning to the build log. > > I do agree that certain issues should fail immediately (image not found). > Certain other issues should perform exponential backoff (Cloud

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

@Manfred, great hint about the maven site plugin. I remember using it for another format in the past, but just got to know that it actually supports Markdown since release 3.3. First I though about using jekyll, just like GitHub. But the maven site plugin would be better integrated. Thanks!

Re: Proposal: forbid direct commits to master for core

Not being an iCLA signer I have experienced the loop of death and that’s fine. I do not however wish it on iCLA signers. Would an acceptable compromise be that people with push access are allowed to optionally "skip" the human review portion of the PR? It would still require that Jenkins is

Re: One-Shot Executors

I like that this moves the provisioning to the build log. I do agree that certain issues should fail immediately (image not found). Certain other issues should perform exponential backoff (Cloud infrastructure down). Provisioning limits could be annoying though, would be interesting if they

Re: New SGE Cloud plugin

On Mon, Mar 7, 2016 at 12:44 PM, John McGehee wrote: > I have developed a Jenkins plugin that runs jobs on Sun Grid Engine (SGE). As an aside (not meaning to derail the hosting request!): it might be valuable to have a corresponding Pipeline step to submit the batch job and

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

On Wed, Mar 9, 2016 at 11:13 AM, Rafael Rezende wrote: > I was thinking about introducing the documentation in > markdown format directly from the Jenkins plugin itself. That is, an extra > doc folder in the plugin's source that will be part of the snapshot (tag, >

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

Suggestion: documentation as part of the plugin under SCM

We have a growing number of Jenkins plugins in our company's repository. They are all for specific purposes, reason why there is no plan to release them in public repository any time soon *(plus legal issues :-( shame)*. Anyway, we had plugin docs scattered all over our departments worldwide

Re: Proposal: forbid direct commits to master for core

On 08.03.2016, at 22:45, Stephen Connolly wrote: > So you are saying that somebody making fix-ups won't make mistakes and the > changes do not need re-review? > > It's hard enough in the current process to know at what point you have the OK > to merge...

Re: Maintenance of Global Build Stats Plugin

Spam-folder in my other mail-account...Sry for the trouble and thx for the quick reply! Am Mittwoch, 9. März 2016 12:35:45 UTC+1 schrieb Daniel Beck: > > > On 09.03.2016, at 11:14, 'David Hinske' via Jenkins Developers < > jenkin...@googlegroups.com > wrote: > > > I think im still missing

Re: Maintenance of Global Build Stats Plugin

On 09.03.2016, at 11:14, 'David Hinske' via Jenkins Developers wrote: > I think im still missing commit access in github. I am unable to push and do > not have the option to merge pull requests :-/. You have a pending invitation to the GitHub jenkinsci

Gsoc 16

Dear Sir, I am a first year student at Thapar University,Patiala,Punjab,India. - Area of study: I am doing my B.Tech in Electronics and Communications and I have a good programming experience in Java,C and C++,HTML,CSS,Javascript. - Interests:Android Application

Gsoc 16

Hello, I visited Jenkins Ideas Page and I am interested in the project titled :"Update Center 2.0". Please guide me on how to proceed as I am new to Gsoc. Thanks -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To

Re: New SGE Cloud plugin

Yes, it would be great to see this plugin merged and released. среда, 9 марта 2016 г., 12:54:24 UTC+3 пользователь susa...@gmail.com написал: > > Nice, this could be very useful to us! One question though: is there > anyway we can change/affect the command line parameters to qsub? > * We make

Re: [GSoC2016] - Jenkins Web Interface Improvements and Update Center 2.0

Sure. On Wednesday, March 9, 2016 at 4:43:09 AM UTC+5:30, Arshad Khan wrote: > > > Hello everyone, > > My name is Arshad Khan, I am a second year student > pursuing B.Tech. in Information Technology from Bharati Vidyapeeth College > of Engineering, New Delhi. I am

Re: minimal config.xml and strange behavior

The in-memory data model can be queried via http://jenkins/job/yourjob/api/xml while http://jenkins/job/yourjob/config.xml is the "on-disk" data model. /B On Wed, Mar 9, 2016 at 9:37 AM, Daniel Beck wrote: > > On 08.03.2016, at 23:31, memoe wrote: >

Re: Maintenance of Global Build Stats Plugin

I think im still missing commit access in github. I am unable to push and do not have the option to merge pull requests :-/. -- 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

Re: New SGE Cloud plugin

Nice, this could be very useful to us! One question though: is there anyway we can change/affect the command line parameters to qsub? * We make extensive use of complex variables to select what queues and servers to use. For instance, instead of "-q jenkins.q", we might use "-l

Re: [GSoC2016] Interested in Test-Automation Project

Ohh... i missed this. I am not a student anymore.Finished my graduation longback.. :( Please let me know any help needed regarding ruby stuff, Always ready to help. --- Mohan Krishna Gundala [image: https://]about.me/gmk.india

Re: minimal config.xml and strange behavior

On 08.03.2016, at 23:31, memoe wrote: > Very strange behavior. Jenkins generally only modifies configuration files when requested to do so (i.e. someone clicks 'Save'). There's no roundtrip when POSTing a config.xml, it simply gets loaded. It's often the case (e.g.