New plugin repository hosting and Jira module request (TestFairy)
Hi, We would like repository hosting for a new plugin: TestFairy It performs Android apk uploads to https://www.testfairy.com/ as a post build step. *Jenkins Plugin Name:* TestFairy *Current Location:* private github repository containing multiple projects. We would like to commit only plugin code to the new repo. *Our GitHub Users:* cmester, icotora, io3pg *Our JenkinsCI User:* jenkins3pillar Thank you! Ciprian -- 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-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Debugging JSON construction logic
Hi. I'm trying to fix this issue:
https://github.com/jenkinsci/docker-plugin/issues/5
In my jelly, I have a repeatable section:
f:repeatable field=templates
// ... config stuff here
/f:repeatable
From an interaction POV, this works fine. But it bombs out trying to
construct the JSON to return to Jenkins, and I don't really understand why.
What seems to be happening is that the first child gets added to the parent
as an object, not an array.
hudson-behaviour.js:1768 does this:
function addProperty(parent,name,value) {
name = shortenName(name);
if(parent[name]!=null) {
if(parent[name].push==null) // is this array?
parent[name] = [ parent[name] ];
parent[name].push(value);
} else {
parent[name] = value;
}
}
The first time through, parent['templates'] == null, so an empty object is
assigned.
The second time through, parent['templates'] != null, so it attempts to
push the value onto an object, not an array (and so bombs out).
The template is pretty simple, and copied from a separate plugin. What's
going wrong?
--
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-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Debugging JSON construction logic
On Wed, Apr 16, 2014 at 8:38 AM, Nigel Magnay nigel.mag...@gmail.com wrote: In my jelly, I have a repeatable section: f:repeatable field=templates Did you mean to use f:repeatableProperty? Not necessarily the solution to your problem but just noting that it is preferable to use full databinding when you can. -- 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-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Debugging JSON construction logic
The repeatable thing is itself an object :- I.E: template is defined as public final ListDockerTemplate templates; (it also has an accessor). I just copied what I saw in the EC2 plugin (which I was trying just now to try to get running to try to figure out if it's a bug there too, but some dependency isn't downloading thru maven) I'm sure it's something really stupid! (Parent) https://github.com/jenkinsci/docker-plugin/blob/master/src/main/java/com/nirima/jenkins/plugins/docker/DockerCloud.java (Template) https://github.com/jenkinsci/docker-plugin/blob/master/src/main/java/com/nirima/jenkins/plugins/docker/DockerTemplate.java (Parent jelly) https://github.com/jenkinsci/docker-plugin/blob/master/src/main/resources/com/nirima/jenkins/plugins/docker/DockerCloud/config.jelly (Template jelly) https://github.com/jenkinsci/docker-plugin/blob/master/src/main/resources/com/nirima/jenkins/plugins/docker/DockerTemplate/config.jelly On Wed, Apr 16, 2014 at 2:02 PM, Jesse Glick jgl...@cloudbees.com wrote: On Wed, Apr 16, 2014 at 8:38 AM, Nigel Magnay nigel.mag...@gmail.com wrote: In my jelly, I have a repeatable section: f:repeatable field=templates Did you mean to use f:repeatableProperty? Not necessarily the solution to your problem but just noting that it is preferable to use full databinding when you can. -- 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-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Debugging JSON construction logic
On Wed, Apr 16, 2014 at 9:10 AM, Nigel Magnay nigel.mag...@gmail.com wrote: The repeatable thing is itself an object A Describable I guess you mean. Good; and that is what repeatableProperty is for. From its documentation: Data-bound only version of f:repeatable that assumes the type pointed by the property is data-bound as well. The nested property type must be Describable and it needs to have config.jelly. I doubt that would fix your JavaScript problem (whatever it is), but it is the right Jelly API to call and should at least provide the proper layout. -- 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-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Debugging JSON construction logic
Found it.
In case anyone else googles in this direction:
The child page had this:
f:entry title=${%Push on successful build} field=push
f:checkbox/
/f:entry
Evidently push conflicts somehow (possibly with array push), and caused
all the failures. Simply renaming it to
f:entry title=${%Push on successful build} field=pushOnSuccess
f:checkbox/
/f:entry
Fixed it. It'd be nice if there were a test list of invalid field names the
testsuite could check against, but I guess it's a reasonably unusual case.
On Wed, Apr 16, 2014 at 3:21 PM, Nigel Magnay nigel.mag...@gmail.comwrote:
Hmm. Switching to repeatableProperty makes the page not even load
correctly (it sticks at the greyed-out 'Loading' point).
On Wed, Apr 16, 2014 at 2:26 PM, Jesse Glick jgl...@cloudbees.com wrote:
On Wed, Apr 16, 2014 at 9:10 AM, Nigel Magnay nigel.mag...@gmail.com
wrote:
The repeatable thing is itself an object
A Describable I guess you mean. Good; and that is what
repeatableProperty is for. From its documentation:
Data-bound only version of f:repeatable that assumes the type pointed
by the property is data-bound as well.
The nested property type must be Describable and it needs to have
config.jelly.
I doubt that would fix your JavaScript problem (whatever it is), but
it is the right Jelly API to call and should at least provide the
proper layout.
--
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-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Debugging JSON construction logic
On Wed, Apr 16, 2014 at 11:17 AM, Nigel Magnay nigel.mag...@gmail.com wrote: It'd be nice if there were a test list of invalid field names the testsuite could check against Sounds like a core bug; it should check not only for ['push'] being defined, but a function. Please file it, with a pull request if you can manage it. -- 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-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: maven-hpi-plugin 1.107 partial deployment
This is because the username has to be set in ~/.m2/settings.xml. I've
added a comment to explain this.
On 04/15/2014 07:32 AM, Jesse Glick wrote:
Mainly for @Kohsuke.
I ran release:{prepare,perform} on this. I think the actual plugin
release was fine:
http://repo.jenkins-ci.org/public/org/jenkins-ci/tools/maven-hpi-plugin/1.107/
But the last step failed (Linux, mvn 3.1.0, JDK 7u51, Git 1.8.3.2):
[INFO] [INFO] --- maven-site-plugin:3.3:deploy (default-deploy) @
maven-hpi-plugin ---
[INFO] [INFO] Parent project loaded from repository:
org.jenkins-ci:jenkins:pom:1.32
[INFO] scm:git:ssh://github.com/jenkinsci/maven-hpi-plugin.git/ -
Session: Opened
[INFO] [INFO] Pushing
/space/src/jenkinsci/maven-hpi-plugin/target/checkout/target/site
[INFO] [INFO] to
scm:git:ssh://github.com/jenkinsci/maven-hpi-plugin.git/./
[INFO] Uploading: ./ to scm:git:ssh://github.com/jenkinsci/maven-hpi-plugin.git/
[INFO]
[INFO] [INFO] Executing: /bin/sh -c cd
/space/src/jenkinsci/maven-hpi-plugin/target/checkout/. git
ls-files
[INFO] [INFO] Working directory:
/space/src/jenkinsci/maven-hpi-plugin/target/checkout/.
[INFO] [INFO] Executing: /bin/sh -c cd
/tmp/wagon-scm1270777913.checkout git init
[INFO] [INFO] Working directory: /tmp/wagon-scm1270777913.checkout
[INFO] [INFO] Executing: /bin/sh -c cd
/tmp/wagon-scm1270777913.checkout git remote add origin
ssh://github.com/jenkinsci/maven-hpi-plugin.git
[INFO] [INFO] Working directory: /tmp/wagon-scm1270777913.checkout
[INFO] [INFO] Executing: /bin/sh -c cd
/tmp/wagon-scm1270777913.checkout git pull origin
refs/heads/gh-pages
[INFO] [INFO] Working directory: /tmp/wagon-scm1270777913.checkout
[INFO] Transfer error: org.apache.maven.scm.ScmException: Unable to
commit file. The git-pull command failed. Permission denied
(publickey).
[INFO] fatal: Could not read from remote repository.
[INFO]
[INFO] Please make sure you have the correct access rights
[INFO] and the repository exists.
[INFO]
[INFO] scm:git:ssh://github.com/jenkinsci/maven-hpi-plugin.git/ -
Session: Disconnecting
[INFO] scm:git:ssh://github.com/jenkinsci/maven-hpi-plugin.git/ -
Session: Disconnected
[INFO] [INFO]
[INFO] [INFO] BUILD FAILURE
[INFO] [INFO]
[INFO] [INFO] Total time: 1:07.205s
[INFO] [INFO] Finished at: Tue Apr 15 10:20:22 EDT 2014
[INFO] [INFO] Final Memory: 46M/620M
[INFO] [INFO]
[INFO] [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.3:deploy (default-deploy)
on project maven-hpi-plugin: Error uploading site: Error checking out:
Unable to commit file. The git-pull command failed. Permission denied
(publickey).
[INFO] [ERROR] fatal: Could not read from remote repository.
[INFO] [ERROR]
[INFO] [ERROR] Please make sure you have the correct access rights
[INFO] [ERROR] and the repository exists.
It is odd that I would be getting a permission problem on the repo
when I can clearly push code changes to it.
I would suggest just getting rid of
distributionManagement
site
idgithub.com/id
urlgitsite:g...@github.com/jenkinsci/maven-hpi-plugin.git/url
/site
/distributionManagement
plugin
artifactIdmaven-site-plugin/artifactId
version3.3/version
dependencies
dependency
groupIdcom.github.stephenc.wagon/groupId
artifactIdwagon-gitsite/artifactId
version0.4.1/version
/dependency
/dependencies
/plugin
extensions
extension
groupIdorg.apache.maven.wagon/groupId
artifactIdwagon-ssh/artifactId
version1.0-beta-7/version
/extension
/extensions
on the grounds that site deployment is more trouble than it is worth.
If anyone really uses the Maven generated sites, it would be better to
have a CI job which runs mvn site and publishes the result somewhere
using stored credentials, so regular folks just trying to cut a
release are not stymied by it—making the Maven release plugin work
even in the simplest cases is enough trouble.
--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Jenkins Enterprise, our professional version of Jenkins
--
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-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: New JIRA component
Done On Wed, Apr 16, 2014 at 10:01 AM, Tomáš Bambas tomas.bam...@gmail.comwrote: Hi, may I ask somebody to create a new JIRA component installshield for the installshield-plugin and set a lead to bambas? could you also set a lead of the python-wrapper component to bambas? Kind Regards Tomáš Bambas -- 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-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Website: http://earl-of-code.com -- 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-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Jira component for vault plugin.
Hi Michael, Can you get me the Vault plugin to Jira? Thanks, Gail On Sunday, March 10, 2013 11:26:10 AM UTC-7, Michael Clarke wrote: Done [1]. Thanks Michael [1] https://issues.jenkins-ci.org/browse/JENKINS/component/17333 On 10 Mar 2013, at 18:19, Stuart Whelan stu...@somepointinthefuture.co.nz javascript: wrote: Hi Michael, My Jira id is: StuartWhelan The vault plugin id is: vault-scm-plugin Thanks! On Mon, Mar 11, 2013 at 7:18 AM, Michael Clarke michael@gmail.com javascript: wrote: Stuart, What's your Jira ID? Thanks Michael On 10 Mar 2013, at 18:15, Stuart Whelan stu...@somepointinthefuture.co.nz javascript: wrote: Hello, Could someone please create a Jira component for the vault plugin: https://wiki.jenkins-ci.org/display/JENKINS/Vault+Plugin so issues can be logged against it please? Thanks! Stuart. -- 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 javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- 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 javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- 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 javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- 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-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Backporting for 1.554.1 started
See backported fixes: https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+10172+AND+labels+%3D+%221.554.1-fixed%22 Tests are passing[1], acceptance test are in a good shape[2]. Thanks marco-miller for testing and backporting https://issues.jenkins-ci.org/browse/JENKINS-21579. [1] https://jenkins.ci.cloudbees.com/job/core/job/jenkins_lts_branch/ [2] https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness/ -- 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-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Request for contributor access to jenkinsci/windows-azure-storage-plugin repository
Hi I am hereby requesting contributor access to jenkinsci/windows-azure-storage-plugin repository for my github id *snallami* I was one of the contributor for this project but now i am not able to push changes to repo. (I recently renamed my github userid , that might have revoked permissions) Thanks, Suresh Nallamilli. -- 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-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Request for Jenkins login reset on Wiki/Confluence (infra not updating again)
Ping? Jan On Apr 2, 2014, at 15:00, Jan Ruzicka wrote: Hi Can anybody reset/enable the jenkins login on Wiki/Confluence? The Unreleased Plugin Changes report is getting stale again. I'm not sure what other reports are affected. Thanks Jan error message: Fault 0: java.lang.Exception: com.atlassian.confluence.rpc.AuthenticationFailedException: Attempt to log in user 'jenkins' failed. The maximum number of failed login attempts has been reached. Please log into the web application through the web interface to reset the number of failed login attempts. -- 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-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: New JIRA component
Thank You. TB Dne středa, 16. dubna 2014 19:12:46 UTC+2 slide napsal(a): Done On Wed, Apr 16, 2014 at 10:01 AM, Tomáš Bambas tomas@gmail.comjavascript: wrote: Hi, may I ask somebody to create a new JIRA component installshield for the installshield-plugin and set a lead to bambas? could you also set a lead of the python-wrapper component to bambas? Kind Regards Tomáš Bambas -- 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 javascript:. For more options, visit https://groups.google.com/d/optout. -- Website: http://earl-of-code.com -- 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-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Violation plugin unresolved for almost 2 years - fix already available
I verified Roger's fix works in our deployment. and I even have a fix on top of that to get it showing the jslint errors inside the code (the current plugin expects absolute paths reported by jslint, but jshint reports relative paths, and thus can't find the corresponding code). It's been 2 years since there was a release of jenkins-violations-plugin, and it's starting to look abandoned. Roger are you going to request commit access? Or should I? I'm willing to work through the backlog of pull requests. On Sunday, March 2, 2014 11:58:57 AM UTC-8, Daniel Beck wrote: If nobody responds, you can just request commit access and merge it yourself: http://jenkins-ci.org/pull-request-greeting On 02.03.2014, at 18:33, Roger Hu roge...@gmail.com javascript: wrote: Can someone review this PR and consider merging it into the branch? -- 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-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: acceptance tests harness: students projects
Ulli, just in case you didn't know yet, some of us will participate to this upcoming event: http://jenkins-ci.org/content/upcoming-jenkins-office-hours-acceptance-test-harness -which agenda has a bit of something to do with parts of yours below.. Feel free to jump in then, /Marco. Le mardi 15 avril 2014 18:07:31 UTC-4, Ullrich Hafner a écrit : I’m currently working with 12 master students in the area of the acceptance test harness“ project. Currently we are still in the planning and knowledge building phase but we are planning to work in the following areas soon: Docker improvements for other Unix derivates (and OS X) as well as additional docker fixtures and test cases for: - Git, Subversion, LDAP, SCP, SSH*, Instant Messenger Additional test cases for: - Analysis Suite (Checkstyle, FindBugs, PMD), NodeLabel Parameter In case you are also planning to add some new tests in that area it would be good if we could coordinate our efforts so that things will not be implement twice. Ulli -- 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-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: acceptance tests harness: students projects
On Wed, 16 Apr 2014 00:07:31 +0200, Ulli Hafner ullrich.haf...@gmail.com wrote: I'm currently working with 12 master students in the area of the acceptance test harness project. Currently we are still in the planning and knowledge building phase but we are planning to work in the following areas soon: Docker improvements for other Unix derivates (and OS X) as well as additional docker fixtures and test cases for: - Git, Subversion, LDAP, SCP, SSH*, Instant Messenger Additional test cases for: - Analysis Suite (Checkstyle, FindBugs, PMD), NodeLabel Parameter Those are great news! In case you are also planning to add some new tests in that area it would be good if we could coordinate our efforts so that things will not be implement twice. Agree, I suggest using GitHub issues to do so. -- oliver -- 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-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
JUnit NUnit test results in same job; possible to keep separated?
Hello, I have a job that runs both JUnit and NUnit tests. Jenkins displays two Test Result Trend charts, but they are both identical. The results are consolidated. Is there a way to keep them separate? Thanks in advance. Steve K. -- 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-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: JUnit NUnit test results in same job; possible to keep separated?
When I was running both JUnit and NUnit in the same job, I saw the same behavior and never found a solution for it. Mark Waite On Wed, Apr 16, 2014 at 2:27 PM, SteveK steve.kerxha...@carestream.comwrote: Hello, I have a job that runs both JUnit and NUnit tests. Jenkins displays two Test Result Trend charts, but they are both identical. The results are consolidated. Is there a way to keep them separate? Thanks in advance. Steve K. -- 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-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Thanks! Mark Waite -- 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-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: much belated 1.532.3 RC posted
Was released on Friday. As usual the changelog is wrong, missing most of the fixes that went in, and mentioning one fix that did not go in (was backed out). I have manually created a corrected changelog here: http://release-notes.cloudbees.com/release/Jenkins+OSS+LTS/1.532.3 -- 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-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
