[JIRA] [radiatorview] (JENKINS-23096) radiatorviewplugin has incorrect links for jobs in folders
Baptiste Mathus updated JENKINS-23096 radiatorviewplugin has incorrect links for jobs in folders Change By: Baptiste Mathus (21/Sep/14 6:32 AM) Component/s: radiatorview This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24765) Jenkins doesn't escape commas when creating job URLs
Yaniv Kaul commented on JENKINS-24765 Jenkins doesnt escape commas when creating job URLs Create a matrix job, with these axis: axis 1: A B axis 2: -m rc,d -m e1,e2 This will result in the following link - which will not escape rc,d (the comma!) when trying to access the job URL. BTW, a similar issue we have just found is inability to create a workspace with the '@' character - although it's allowed in the matrix! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security] (JENKINS-15210) Add variable resolution to additional groovy class path
Sebastian Schuberth commented on JENKINS-15210 Add variable resolution to additional groovy class path @ikedam As outlined in the initial comment, this is not about adding libraries generated in builds to classpath. It's about storing (large) Groovy files for Jenkins in the VCS, along with the code that is supposed to be built. Basically, you just store the instructions how to build along with what to build, which IMHO makes very much sense. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [repository-connector] (JENKINS-24781) Repository Connector Plugin failed to resolve dependency after upgrade (0.8.2 - 1.0.1)
Dejan Stojadinovic updated JENKINS-24781 Repository Connector Plugin failed to resolve dependency after upgrade (0.8.2 - 1.0.1) Change By: Dejan Stojadinovic (21/Sep/14 7:07 AM) Environment: *JenkinsLTS1.565.2(deployedaswarinsideofTomcat)*SonatypeNexusOSS*2.8.1* This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [repository-connector] (JENKINS-24781) Repository Connector Plugin failed to resolve dependency after upgrade (0.8.2 - 1.0.1)
Dejan Stojadinovic
updated JENKINS-24781
Repository Connector Plugin failed to resolve dependency after upgrade (0.8.2 - 1.0.1)
Change By:
Dejan Stojadinovic
(21/Sep/14 7:11 AM)
Environment:
*JenkinsLTS1.565.2(deployedaswarinsideofTomcat)*SonatypeNexusOSS
*
2.8.1
*
Description:
[~imod]
JobfailsafterRepositoryConnectorPluginupgrade(*0.8.2*-*1.0.1*);pleasenotethatsameartifact(withsameartifactversion)isresolvedasexpectedwith*0.8.2*.Stacktrace:{noformat}2014-09-1912:25:54INFO[bio-8080-exec-7]-org.sonatype.security.model.source.FileModelConfigurationSource-Loadingsecurityconfigurationfrom:/home/TECH/tomcat/sonatype-work/nexus/conf/security.xml2014-09-1912:25:55INFO[bio-8080-exec-7]-org.sonatype.nexus.proxy.storage.remote.httpclient.HttpClientRemoteStorage-Initializingremotetransportforproxyrepositoryoss-snapshots[id=oss-snapshots]...2014-09-1912:25:55INFO[bio-8080-exec-7]-org.sonatype.nexus.proxy.storage.remote.httpclient.HttpClientRemoteStorage-InitializingremotetransportforproxyrepositoryApacheSnapshots[id=apache-snapshots]...2014-09-1912:25:55INFO[bio-8080-exec-7]-org.sonatype.nexus.proxy.storage.remote.httpclient.HttpClientRemoteStorage-InitializingremotetransportforproxyrepositoryCodehausSnapshots[id=codehaus-snapshots]...2014-09-1912:25:55INFO[bio-8080-exec-7]-org.sonatype.nexus.proxy.storage.remote.httpclient.HttpClientRemoteStorage-Initializingremotetransportforproxyrepositoryscct[id=scct]...2014-09-1912:25:56INFO[bio-8080-exec-7]-org.sonatype.nexus.velocity.VelocityEngineProvider-CreatingNexusVelocityEngineSep19,201412:25:56PMorg.jvnet.hudson.plugins.repositoryconnector.ArtifactResolverlogErrorSEVERE:failedtoresolvedependencyfor[Artifact}]org.sonatype.aether.resolution.DependencyResolutionException:Couldnotfindinnexus(/nexus/content/groups/public)atorg.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:375)atorg.jvnet.hudson.plugins.repositoryconnector.aether.Aether.resolve(Aether.java:157)atorg.jvnet.hudson.plugins.repositoryconnector.ArtifactResolver.download(ArtifactResolver.java:129)atorg.jvnet.hudson.plugins.repositoryconnector.ArtifactResolver.perform(ArtifactResolver.java:101)athudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)athudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:756)athudson.model.Build$BuildExecution.build(Build.java:198)athudson.model.Build$BuildExecution.doRun(Build.java:159)athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)athudson.model.Run.execute(Run.java:1706)athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)athudson.model.ResourceController.execute(ResourceController.java:88)athudson.model.Executor.run(Executor.java:232)Causedby:org.sonatype.aether.resolution.ArtifactResolutionException:Couldnotfindartifact*innexus(/nexus/content/groups/public)atorg.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:537)atorg.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216)atorg.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:358)...12moreCausedby:org.sonatype.aether.transfer.ArtifactNotFoundException:Couldnotfindartifact*innexus(/nexus/content/groups/public)atorg.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(WagonRepositoryConnector.java:971)atorg.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(WagonRepositoryConnector.java:966)atorg.sonatype.aether.connector.wagon.WagonRepositoryConnector$GetTask.flush(WagonRepositoryConnector.java:707)atorg.sonatype.aether.connector.wagon.WagonRepositoryConnector$GetTask.flush(WagonRepositoryConnector.java:701)atorg.sonatype.aether.connector.wagon.WagonRepositoryConnector.get(WagonRepositoryConnector.java:452)atorg.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:456)...14more{noformat}
[JIRA] [script-security] (JENKINS-24650) Add syntax highlighting like the Scriptler and Groovy plugins have
Sebastian Schuberth updated JENKINS-24650 Add syntax highlighting like the Scriptler and Groovy plugins have Change By: Sebastian Schuberth (21/Sep/14 7:24 AM) Summary: AddsyntaxhighlightingliketheScriptlerandGroovy plugin plugins have This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23868) Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported
sharon xia commented on JENKINS-23868 Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported I did another test on 1.532.3, not see this download issue with ab -n300 -c2 http://.EXE. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23868) Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported
sharon xia commented on JENKINS-23868 Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported However, we saw jenkins blue screen to death issue on 1.523.3, see https://issues.jenkins-ci.org/browse/JENKINS-24453?focusedCommentId=211164#comment-211164 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24453) Jenkins server got blue screen to death
sharon xia commented on JENKINS-24453 Jenkins server got blue screen to death This issue is not seen after upgrade jenkins to 1.565.1. But we are seeing download issue on 1.565.1. See https://issues.jenkins-ci.org/browse/JENKINS-23868?focusedCommentId=211163#comment-211163 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23868) Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported
sharon xia commented on JENKINS-23868 Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported Is there anything we can do to help debugging this issue? It is very easy for us to reproduce this download issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security] (JENKINS-15210) Add variable resolution to additional groovy class path
Daniel Beck commented on JENKINS-15210 Add variable resolution to additional groovy class path An alternative solution would be to extend script-security with a reusable scripts repository that way, it can be controlled by Jenkins admins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix] (JENKINS-24765) Jenkins doesn't escape commas when creating job URLs
Daniel Beck updated JENKINS-24765 Jenkins doesnt escape commas when creating job URLs Not a core issue, axis are handled by the matrix plugin. Change By: Daniel Beck (21/Sep/14 9:58 AM) Component/s: matrix Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project] (JENKINS-16055) Matrix project with comma in values
Daniel Beck resolved JENKINS-16055 as Duplicate Matrix project with comma in values Duplicates JENKINS-12439 Change By: Daniel Beck (21/Sep/14 10:02 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix] (JENKINS-24765) Jenkins doesn't escape commas when creating job URLs
Daniel Beck resolved JENKINS-24765 as Duplicate Jenkins doesnt escape commas when creating job URLs Duplicates JENKINS-16055, JENKINS-12439, JENKINS-16486. Please search first next time. Change By: Daniel Beck (21/Sep/14 10:02 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix] (JENKINS-16486) Links broken when user-defined axis values contain comma
Daniel Beck resolved JENKINS-16486 as Duplicate Links broken when user-defined axis values contain comma Duplicates JENKINS-12439. Change By: Daniel Beck (21/Sep/14 10:03 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix] (JENKINS-12439) Comma in configuration value causes 404 page
Daniel Beck updated JENKINS-12439 Comma in configuration value causes 404 page Still occurs on 1.580 with Matrix project 1.3. Change By: Daniel Beck (21/Sep/14 10:04 AM) Component/s: matrix-project This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix] (JENKINS-12439) Comma in configuration value causes 404 page
Daniel Beck commented on JENKINS-12439 Comma in configuration value causes 404 page Unrelated to JENKINS-1352 that one is about character set issues, this has the problem that the field separator used in the URL is also a valid field value, breaking the "URL decoder". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security] (JENKINS-15210) Add variable resolution to additional groovy class path
ikedam commented on JENKINS-15210 Add variable resolution to additional groovy class path Sorry, I misunderstood the problem. Anyway, it requires approaches other than using variables as jar files in workspaces shouldn't work correct in distributed builds. I agree with @danielbeck. It's often the case users want to reuse a script in multiple projects. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator] (JENKINS-24736) Android emulator plugin does not use all available executors on a slave
JY Hsu commented on JENKINS-24736 Android emulator plugin does not use all available executors on a slave The jobs are separate Jenkins jobs. The OS/density/resolution/locale/ABI are all the same, so I suspect the Android emulator plugin doesn't allow me to create and run two emulators of identical configuration at the same time? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24786) Since 2.2.6 ssh credentials on git push seems to have a problem.
Thomas Spalinger created JENKINS-24786 Since 2.2.6 ssh credentials on git push seems to have a problem. Issue Type: Bug Assignee: Nicolas De Loof Attachments: failing.txt, success.txt Components: git Created: 21/Sep/14 11:30 AM Description: Since 2.2.6 ssh credentials on git push seems to have a problem. When i revert back to 2.2.5 everything works as expected. I'm using jenkins credential with a ssh key. Don't know if that has something to say, but I'm using env var's to set the git url, and in the failing log it's not resolved. But I guess the error prints it before the resolution, because the connection itself seems to work, just not the authentication. I attached a log success.txt (with version 2.2.5) and a failing.txt (version 2.2.6). The only difference is that i reverted the plugin to 2.2.5 and everything worked again. let me know if you need more information. But maybe so find the problem due the recent changes. Environment: Jenkins: 1.580 Git Plugin 2.2.6 (before update 2.2.5) All plugins up to date (21. September) Project: Jenkins Priority: Major Reporter: Thomas Spalinger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23868) Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported
Daniel Beck commented on JENKINS-23868 Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported Log hudson.model.DirectoryBrowserSupport on FINE and report the output: https://wiki.jenkins-ci.org/display/JENKINS/Logging This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23868) Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported
Daniel Beck commented on JENKINS-23868 Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported Capture the HTTP request and response headers (there may be multiple). It may be related to partial downloads. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator] (JENKINS-24736) Android emulator plugin does not use all available executors on a slave
Christopher Orr resolved JENKINS-24736 as Not A Defect Android emulator plugin does not use all available executors on a slave Yes, if multiple jobs have the same emulator properties, they won't be able to build at the same time. You can set a unique "Emulator name suffix" per job which, as the documentation says, "allows you to run multiple emulators with the same configuration in parallel on the same build machine." Change By: Christopher Orr (21/Sep/14 12:28 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-24787) Exception when using Gerrit Trigger
Daniel Spilker
created JENKINS-24787
Exception when using Gerrit Trigger
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
21/Sep/14 1:19 PM
Description:
The following DSL script (which is an example from the docs) causes an exception.
job {
name('test')
triggers {
gerrit {
events {
ChangeMerged
DraftPublished
}
project('reg_exp:myProject', ['ant:feature-branch', 'plain:origin/refs/mybranch'])
project('test-project', '**')
buildSuccessful(10, null)
}
}
}
java.lang.NumberFormatException: For input string: "null"
at java_lang_Integer$parseInt$0.call(Unknown Source)
at javaposse.jobdsl.dsl.helpers.triggers.GerritContext.buildSuccessful(GerritContext.groovy:46)
at script1411305238047178367$_run_closure1_closure2_closure3.doCall(script1411305238047178367.groovy:10)
at script1411305238047178367$_run_closure1_closure2_closure3.doCall(script1411305238047178367.groovy)
at javaposse.jobdsl.dsl.helpers.AbstractContextHelper.executeInContext(AbstractContextHelper.groovy:21)
at javaposse.jobdsl.dsl.helpers.AbstractContextHelper$executeInContext$0.call(Unknown Source)
at javaposse.jobdsl.dsl.helpers.triggers.TriggerContext.gerrit(TriggerContext.groovy:201)
at script1411305238047178367$_run_closure1_closure2.doCall(script1411305238047178367.groovy:3)
at script1411305238047178367$_run_closure1_closure2.doCall(script1411305238047178367.groovy)
at javaposse.jobdsl.dsl.helpers.AbstractContextHelper.executeInContext(AbstractContextHelper.groovy:21)
at javaposse.jobdsl.dsl.helpers.AbstractContextHelper$executeInContext$0.callStatic(Unknown Source)
at javaposse.jobdsl.dsl.helpers.AbstractContextHelper.execute(AbstractContextHelper.groovy:32)
at javaposse.jobdsl.dsl.helpers.AbstractContextHelper$execute.callCurrent(Unknown Source)
at javaposse.jobdsl.dsl.helpers.triggers.TriggerContextHelper.triggers(TriggerContextHelper.groovy:21)
at javaposse.jobdsl.dsl.helpers.triggers.TriggerContextHelper$triggers.call(Unknown Source)
at javaposse.jobdsl.dsl.Job.triggers(Job.groovy)
at script1411305238047178367$_run_closure1.doCall(script1411305238047178367.groovy:2)
at javaposse.jobdsl.dsl.JobParent.job(JobParent.groovy:32)
at javaposse.jobdsl.dsl.JobParent.job(JobParent.groovy)
at javaposse.jobdsl.dsl.DslFactory$job.callCurrent(Unknown Source)
at script1411305238047178367.run(script1411305238047178367.groovy:1)
at javaposse.jobdsl.dsl.DslScriptLoader.runDslEngineForParent(DslScriptLoader.java:69)
at javaposse.jobdsl.dsl.DslScriptLoader$runDslEngineForParent.call(Unknown Source)
...
Environment:
Job DSL Plugin 1.25
Project:
Jenkins
Priority:
Major
Reporter:
Daniel Spilker
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-24787) Exception when using Gerrit Trigger
Daniel Spilker commented on JENKINS-24787 Exception when using Gerrit Trigger Pull request: https://github.com/jenkinsci/job-dsl-plugin/pull/284 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23868) Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported
sharon xia updated JENKINS-23868 Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported wireshark log Change By: sharon xia (21/Sep/14 1:53 PM) Attachment: resend.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23868) Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported
sharon xia commented on JENKINS-23868 Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported How to "Capture the HTTP request and response headers"? We did get below summary from our IT when asking them to investigating this issue(we thought it was about network before): Our networking team have run a few captures from the host you provided (10.62.34.216) using Wireshark while downloading the platypus.exe file. There seems to be duplicate requests where a packet is trying re-sending over and over (sometimes up to 120 times). This happens both when the file is loaded with a lower MB size and even when the file loads the entire 472MB. We also ran Wireshark captures from two separate desktops on our end and received no duplicate packet requests and a complete download. This is leading us to believe that there is isn’t a problem on the web server and that there may be a problem on the hosts in your network blocking traffic. Ronald took a look at the captures and does see a huge amount of duplicate ack packets. His report was these are requests from the receiver side towards the server asking for the server to resend a specific packet/frame that is missing. Normally, the server sees around 3 of these and immediately resends the packet the missing packet. This could point to packet loss problem but further captures and data would help us to verify this. Below is a image of the capture(see attachment wireshark log). As our network team see no abnormal in network, we did the experiments and found this issue is not exist on 1.532.3, but exist on 1.565.2. So we can say that it should be a jenkins issue, but this issue might be triggered by network that has a big latency. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23868) Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported
Daniel Beck commented on JENKINS-23868 Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported Which part of your comment is a quote? Because all the information in your comment points to OS or hardware level problem, which the last paragraph seems to contradict. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy] (JENKINS-17418) Enhancement to all Groovy Editing Interfaces to allow easy use of External Groovy Editors
ikedam updated JENKINS-17418 Enhancement to all Groovy Editing Interfaces to allow easy use of External Groovy Editors Groovy-postbuild delegates textareas for groovy script to script-security plugin since 2.0. I removed groovy-postbuild from components and added script-security instead. Change By: ikedam (21/Sep/14 2:09 PM) Component/s: script-security Component/s: groovy-postbuild This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-24163) Allow downstream jobs to push artifact updates to upstream jobs
ikedam commented on JENKINS-24163 Allow downstream jobs to push artifact updates to upstream jobs @jasonsmiley I think what you want is to rerun a multijob from the point it fails. You mean multijob M: Phase1: Run JobA Phase2: Run JobB-F Phase3: Run JobG (aggregates result of B-F) And you want to rerun only B and G if only B fails, don't you? Or, do you mean using "Trigger/call builds on other projects" of parameterized-trigger plugin? Anyway, I don't think they let you do what you want even if new features are added to copyartifact plugin. I recommend you try Promoted Builds plugin. It lets you do like this: Project A triggers project B-F. If all downstream of project A (that is, B-F) secceeds, a promotion of A triggers project G. If B failed, you can retrigger B with Rebuuld plugin, and a promotion can be activated if retriggered B succeeded. You need to understand Jenkins tracking files with fingerprinting. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-12618) Copy Artifact plugin - Access is denied to copy content
ikedam resolved JENKINS-12618 as Incomplete Copy Artifact plugin - Access is denied to copy content Sounds a problem of inproper permissions on file system. Change By: ikedam (21/Sep/14 2:40 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23868) Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported
Daniel Beck edited a comment on JENKINS-23868 Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported Which part of your comment is a quote? Because all the information in your comment points to OS/environment (e.g. JRE) or hardware level problem, which the last paragraph seems to contradict. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tasks-plugin] (JENKINS-24708) Message is missing from REST API
SCM/JIRA link daemon commented on JENKINS-24708 Message is missing from REST API Code changed in jenkins User: Ulli Hafner Path: analysis-core analysis-pom analysis-test dry findbugs pmd tasks http://jenkins-ci.org/commit/analysis-suite-plugin/281e9de549e0acebe8da9266e1dfec6de88deeac Log: FIXED JENKINS-24708 Also expose 'detailMessage property in remote API.' The message property is not used in the tasks plugin, detailMessage contains the actual message. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tasks-plugin] (JENKINS-24708) Message is missing from REST API
SCM/JIRA link daemon commented on JENKINS-24708 Message is missing from REST API Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/tasks/parser/Task.java http://jenkins-ci.org/commit/tasks-plugin/321bd840a71dea341923a9af0cf8461423152928 Log: FIXED JENKINS-24708 Also expose 'detailMessage property in remote API.' The message property is not used in the tasks plugin, detailMessage contains the actual message. Compare: https://github.com/jenkinsci/tasks-plugin/compare/40475e0ee9fc...321bd840a71d This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tasks-plugin] (JENKINS-24708) Message is missing from REST API
SCM/JIRA link daemon resolved JENKINS-24708 as Fixed Message is missing from REST API Change By: SCM/JIRA link daemon (21/Sep/14 6:56 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core] (JENKINS-13056) Obtain reference build from SCM/Trigger
Ulli Hafner updated JENKINS-13056 Obtain reference build from SCM/Trigger I don't see a chance to implement that in the near future. Interested in providing a pull request? Change By: Ulli Hafner (21/Sep/14 7:01 PM) Assignee: UlliHafner Component/s: warnings Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-9877) Static Code Analysis Plug-ins is updated between each plug-in update
Ulli Hafner updated JENKINS-9877 Static Code Analysis Plug-ins is updated between each plug-in update Change By: Ulli Hafner (21/Sep/14 7:03 PM) Component/s: core Component/s: analysis-core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-9877) Static Code Analysis Plug-ins is updated between each plug-in update
Ulli Hafner resolved JENKINS-9877 as Fixed Static Code Analysis Plug-ins is updated between each plug-in update I think this has been fixed quite some time ago. Or is this still valid for 1.457? Change By: Ulli Hafner (21/Sep/14 7:03 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [findbugs] (JENKINS-24289) Improve description of Only use stable builds as reference option
SCM/JIRA link daemon commented on JENKINS-24289 Improve description of Only use stable builds as reference option Code changed in jenkins User: Ulli Hafner Path: src/main/resources/util/thresholds.properties src/main/resources/util/thresholds_de.properties http://jenkins-ci.org/commit/analysis-core-plugin/c7d39361c6f38b4d93dbf502e616499cf942524b Log: FIXED JENKINS-24289 Improved doc of stableReferenceBuilds. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [findbugs] (JENKINS-24289) Improve description of Only use stable builds as reference option
SCM/JIRA link daemon resolved JENKINS-24289 as Fixed Improve description of Only use stable builds as reference option Change By: SCM/JIRA link daemon (21/Sep/14 7:13 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security] (JENKINS-15210) Add variable resolution to additional groovy class path
Sebastian Schuberth commented on JENKINS-15210 Add variable resolution to additional groovy class path @danielbeck A reusable scripts repository basically is what the Scriptler plugin already provides, no? In fact, that's exactly what we do as a work-around currently: We manually copy our private Groovy postbuild scripts to the Scriptler directory, which is in classpath, in order to share common code between postbuild steps. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security] (JENKINS-15210) Add variable resolution to additional groovy class path
Daniel Beck commented on JENKINS-15210 Add variable resolution to additional groovy class path Sebastian Schuberth It's only available to admins though (and users with Run Scripts permission, which as standalone permission is actually more powerful than Administer, but the Scriptler docs pretend it's not). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector] (JENKINS-24603) Bad URL encoding generated on redirection to warnings analysis reports
Ulli Hafner commented on JENKINS-24603 Bad URL encoding generated on redirection to warnings analysis reports Which Jenkins version are you using? Which browser on which OS? I tried to reproduce without success. I tried to click the link "http://localhost:8080/job/Montr%C3%A9al/warnings34", it is resolved to "http://localhost:8080/job/Montr%C3%A9al/6/warnings34Result/". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector] (JENKINS-24603) Bad URL encoding generated on redirection to warnings analysis reports
Daniel Beck commented on JENKINS-24603 Bad URL encoding generated on redirection to warnings analysis reports Which container is Jenkins running in? Is it running behind a reverse proxy? If so, which? Is there a reverse proxy warning shown in /manage ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings] (JENKINS-24011) Start filtering by exclude/include patterns AFTER absolute path expansion
SCM/JIRA link daemon commented on JENKINS-24011 Start filtering by exclude/include patterns AFTER absolute path expansion Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/warnings/WarningsPublisher.java src/main/java/hudson/plugins/warnings/parser/FileWarningsParser.java src/main/java/hudson/plugins/warnings/parser/ParserRegistry.java src/main/java/hudson/plugins/warnings/parser/WarningsFilter.java src/test/java/hudson/plugins/warnings/ConsoleParserTest.java src/test/java/hudson/plugins/warnings/ParserConfigurationTest.java src/test/java/hudson/plugins/warnings/WarningsPublisherTest.java src/test/java/hudson/plugins/warnings/parser/DynamicParserTest.java src/test/java/hudson/plugins/warnings/parser/ParserRegistryIntegrationTest.java src/test/java/hudson/plugins/warnings/parser/ParserRegistryTest.java src/test/java/hudson/plugins/warnings/parser/ParserSpeed.java http://jenkins-ci.org/commit/warnings-plugin/4f2bbc2f77b11159c87422e1c2ec5e65b974d07a Log: FIXED JENKINS-24011 Apply include/exclude filters after path expansion. Also use JenkinsRule for all integration tests. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings] (JENKINS-24011) Start filtering by exclude/include patterns AFTER absolute path expansion
SCM/JIRA link daemon resolved JENKINS-24011 as Fixed Start filtering by exclude/include patterns AFTER absolute path expansion Change By: SCM/JIRA link daemon (21/Sep/14 8:56 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24786) Since 2.2.6 ssh credentials on git push seems to have a problem.
Mark Waite
edited a comment on JENKINS-24786
Since 2.2.6 ssh credentials on git push seems to have a problem.
Thanks for the report. It appears that 2.2.5 was evaluating the ${TargetUrl} environment variable correctly, and 2.2.6 is not doing that any longer.
A change was introduced in 2.2.5 (change1 and change2) which broadened the evaluation of environment variables in order to fix JENKINS-22009. It seemed to be too broad and resulted in JENKINS-24467 and JENKINS-24516. A change was merged in 2.2.6 which narrowed the scope of the evaluation of environment variables, trying to bring it more into line with the evaluation that happened in 2.2.4 and prior.
Was the use case you're using working with plugin versions prior to 2.2.5?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24786) Since 2.2.6 ssh credentials on git push seems to have a problem.
Mark Waite assigned JENKINS-24786 to Mark Waite Since 2.2.6 ssh credentials on git push seems to have a problem. Change By: Mark Waite (21/Sep/14 10:02 PM) Assignee: NicolasDeLoof MarkWaite This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24786) Since 2.2.6 ssh credentials on git push seems to have a problem.
Mark Waite
commented on JENKINS-24786
Since 2.2.6 ssh credentials on git push seems to have a problem.
Thanks for the report. It appears that 2.2.5 was evaluating the ${TargetUrl} environment variable correctly, and 2.2.6 is not doing that any longer.
A change was introduced in 2.2.5 (change1 and change2) which broadened the evaluation of environment variables. It seemed to be too broad and resulted in JENKINS-24467 and JENKINS-24516. A change was merged in 2.2.6 which narrowed the scope of the evaluation of environment variables, trying to bring it more into line with the evaluation that happened in 2.2.4 and prior.
Was the use case you're using working with plugin versions prior to 2.2.5?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24467) ssh not found by git because PATH has been unexpectedly changed
Mark Waite commented on JENKINS-24467 ssh not found by git because PATH has been unexpectedly changed Refer to JENKINS-24786 for a possible unintended side effect of fixing this problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24786) Since 2.2.6 ssh credentials on git push seems to have a problem.
Mark Waite
commented on JENKINS-24786
Since 2.2.6 ssh credentials on git push seems to have a problem.
I'm not clear how to duplicate the bug. I need to understand where you're referencing ${TargetUrl} in the job definition.
Could you either post the job configuration file (config.xml) to the bug report, or mail it separately to me?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24552) Exception when use git plugin with ssh public key
Mark Waite resolved JENKINS-24552 as Cannot Reproduce Exception when use git plugin with ssh public key Since I can't duplicate the IllegalArgumentException and neither the submitter nor the one person commenting on the bug have offered steps which will duplicate the bug, I'm closing this as cannot reproduce. Change By: Mark Waite (21/Sep/14 10:58 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24552) Exception when use git plugin with ssh public key
Mark Waite closed JENKINS-24552 as Cannot Reproduce Exception when use git plugin with ssh public key Change By: Mark Waite (21/Sep/14 10:58 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22601) Provide option for -f / force in git push (after tagging)
Mark Waite closed JENKINS-22601 as Fixed Provide option for -f / force in git push (after tagging) Change By: Mark Waite (21/Sep/14 11:09 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22601) Provide option for -f / force in git push (after tagging)
Mark Waite resolved JENKINS-22601 as Fixed Provide option for -f / force in git push (after tagging) As far as I can tell, this now works if the "Force" checkbox is selected in the git publisher (as of git plugin 2.2.6). Change By: Mark Waite (21/Sep/14 11:09 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24786) Since 2.2.6, environment variables are noto expanded in git publisher
Mark Waite updated JENKINS-24786 Since 2.2.6, environment variables are noto expanded in git publisher Change By: Mark Waite (21/Sep/14 11:25 PM) Summary: Since2.2.6 sshcredentialson ,environmentvariablesarenotoexpandedin git pushseemstohaveaproblem. publisher This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24786) Since 2.2.6, environment variables are not expanded in git publisher
Mark Waite updated JENKINS-24786 Since 2.2.6, environment variables are not expanded in git publisher Change By: Mark Waite (21/Sep/14 11:25 PM) Summary: Since2.2.6,environmentvariablesare noto not expandedingitpublisher This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24786) Since 2.2.6, environment variables are not expanded in git publisher
Thomas Spalinger commented on JENKINS-24786 Since 2.2.6, environment variables are not expanded in git publisher Hi Mark I can't say if it would work prior 2.2.5, because I didn't use this job setup before as i can remember. Attached the config.xml of the job. TargetUrl is a job parameter of 3 with git url's I use. This is referenced for the fetch and then at the end for the push. Just to explain, the job fetches a repo from github (origin), my local gitlab mirror (target) and my gitlab mirror/fork from the origin (target2) and then I push the branch to target and target2 with git publisher to keep my mirrors (target/target2) in sync with the origin. To duplicate the bug, I think you could replace the default values of the origin parameters with some of your repos and maybe remove the target2 overall in the job for simplicity. Also just remove the "Docker plugin" stuff if you just want to use any other slave. The EnvInject can also be removed if you set the branch name without a variable. The result should be a job with just 2 or 3 repos in the SCM config and 1 or 2 push in the git publisher config. Nothing to do with this issue, but just a side question, as you see in the job, for such a simple (and in my eyes common job) i have to use EnvInject plugin to get the Branch name without the leading "origin" to use it in the git publisher for push. Because if I would directly use the GIT_BRANCH variable I get an error. I found many different approaches around how to handle that... but wouldn't it be easy to provide a GIT_BRANCH_NAME without the leading "origin" directly by the git plugin? I think would solve many ugly hacks out there This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24786) Since 2.2.6, environment variables are not expanded in git publisher
Thomas Spalinger updated JENKINS-24786 Since 2.2.6, environment variables are not expanded in git publisher Change By: Thomas Spalinger (22/Sep/14 12:04 AM) Attachment: config.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector] (JENKINS-24603) Bad URL encoding generated on redirection to warnings analysis reports
Francis Labrie commented on JENKINS-24603 Bad URL encoding generated on redirection to warnings analysis reports Our current Jenkins version is 1.580. It's running on Mac OS X 10.9.5 Server using the default container provided by the installer / JAR. This issue is reproductible in both environment: 1) using a direct access on the 8080 port; 2) using the nginx proxy host. There is no reverse proxy warning in the /manage page. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector] (JENKINS-24603) Bad URL encoding generated on redirection to warnings analysis reports
Francis Labrie commented on JENKINS-24603 Bad URL encoding generated on redirection to warnings analysis reports I don't know if it could be a factor: I don't think so. But for your information, on Mac OS X, the default UTF-8 encoding used on HFS+ filesystem uses NFD (Normalization Form D), and not NFC (Normalization Form C) like Windows and Linux. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23868) Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported
sharon xia commented on JENKINS-23868 Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported Hi Daniel: Previously we thought it was a network problem as our network team has using wireshark to monitor the download of artifact file. We found there were duplicate requests when a package is trying to re-sending over and over again(sometimes up to 120 times). his happens both when the file is loaded with a lower MB size and even when the file loads the entire 472MB. We also did experiments on another two desktop in United Stated where the server is placed, and see no duplicate issue and a complete download. This leading us to believe there is a network issue. However, then we did another experiment, to let the server in US, and use differnt version of jenkins to try to download. We found that in jenkins 1.532.2, we see no issue either from US or from China. For Jenkins 1.565.2, we saw issues in China very easily. So we believe this is a jenkins issue that could be triggered if we download from another contry for the artifacts. Since the network will have a network latency across country, it might trigger jenkins to resend the packages again and again which leads to the download issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23868) Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported
sharon xia commented on JENKINS-23868 Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported I did another experiments for 1.565.2, and saw 3 failed requests out of 300. Concurrency Level: 2 Time taken for tests: 10396.019 seconds Complete requests: 300 Failed requests:3 Here is the log. Sep 21, 2014 7:06:19 AM FINE hudson.model.DirectoryBrowserSupport Serving file:/C:/Program%20Files%20(x86)/Jenkins/jobs/pdk/builds/2014-09-11_20-03-08/archive/platypus.EXE with lastModified=1410491002000, length=162376398 Sep 21, 2014 7:06:37 AM FINE hudson.model.DirectoryBrowserSupport Serving file:/C:/Program%20Files%20(x86)/Jenkins/jobs/pdk/builds/2014-09-11_20-03-08/archive/platypus.EXE with lastModified=1410491002000, length=162376398 Sep 21, 2014 7:07:28 AM FINE hudson.model.DirectoryBrowserSupport Serving file:/C:/Program%20Files%20(x86)/Jenkins/jobs/pdk/builds/2014-09-11_20-03-08/archive/platypus.EXE with lastModified=1410491002000, length=162376398 Sep 21, 2014 7:07:46 AM FINE hudson.model.DirectoryBrowserSupport Serving file:/C:/Program%20Files%20(x86)/Jenkins/jobs/pdk/builds/2014-09-11_20-03-08/archive/platypus.EXE with lastModified=1410491002000, length=162376398 Sep 21, 2014 7:08:37 AM FINE hudson.model.DirectoryBrowserSupport Serving file:/C:/Program%20Files%20(x86)/Jenkins/jobs/pdk/builds/2014-09-11_20-03-08/archive/platypus.EXE with lastModified=1410491002000, length=162376398 Sep 21, 2014 7:08:54 AM FINE hudson.model.DirectoryBrowserSupport Serving file:/C:/Program%20Files%20(x86)/Jenkins/jobs/pdk/builds/2014-09-11_20-03-08/archive/platypus.EXE with lastModified=1410491002000, length=162376398 Sep 21, 2014 7:09:45 AM FINE hudson.model.DirectoryBrowserSupport Serving file:/C:/Program%20Files%20(x86)/Jenkins/jobs/pdk/builds/2014-09-11_20-03-08/archive/platypus.EXE with lastModified=1410491002000, length=162376398 Sep 21, 2014 7:10:03 AM FINE hudson.model.DirectoryBrowserSupport Serving file:/C:/Program%20Files%20(x86)/Jenkins/jobs/pdk/builds/2014-09-11_20-03-08/archive/platypus.EXE with lastModified=1410491002000, length=162376398 Sep 21, 2014 7:10:57 AM FINE hudson.model.DirectoryBrowserSupport Serving file:/C:/Program%20Files%20(x86)/Jenkins/jobs/pdk/builds/2014-09-11_20-03-08/archive/platypus.EXE with lastModified=1410491002000, length=162376398 Sep 21, 2014 7:11:11 AM FINE hudson.model.DirectoryBrowserSupport Serving file:/C:/Program%20Files%20(x86)/Jenkins/jobs/pdk/builds/2014-09-11_20-03-08/archive/platypus.EXE with lastModified=1410491002000, length=162376398 Sep 21, 2014 7:12:26 AM FINE hudson.model.DirectoryBrowserSupport Serving file:/C:/Program%20Files%20(x86)/Jenkins/jobs/pdk/builds/2014-09-11_20-03-08/archive/platypus.EXE with lastModified=1410491002000, length=162376398 Sep 21, 2014 7:12:33 AM FINE hudson.model.DirectoryBrowserSupport Serving file:/C:/Program%20Files%20(x86)/Jenkins/jobs/pdk/builds/2014-09-11_20-03-08/archive/platypus.EXE with lastModified=1410491002000, length=162376398 Sep 21, 2014 7:13:35 AM FINE hudson.model.DirectoryBrowserSupport Serving file:/C:/Program%20Files%20(x86)/Jenkins/jobs/pdk/builds/2014-09-11_20-03-08/archive/platypus.EXE with lastModified=1410491002000, length=162376398 Sep 21, 2014 7:13:42 AM FINE hudson.model.DirectoryBrowserSupport Serving file:/C:/Program%20Files%20(x86)/Jenkins/jobs/pdk/builds/2014-09-11_20-03-08/archive/platypus.EXE with lastModified=1410491002000, length=162376398 Sep 21, 2014 7:14:43 AM FINE hudson.model.DirectoryBrowserSupport Serving file:/C:/Program%20Files%20(x86)/Jenkins/jobs/pdk/builds/2014-09-11_20-03-08/archive/platypus.EXE with lastModified=1410491002000, length=162376398 Sep 21, 2014 7:14:51 AM FINE hudson.model.DirectoryBrowserSupport Serving file:/C:/Program%20Files%20(x86)/Jenkins/jobs/pdk/builds/2014-09-11_20-03-08/archive/platypus.EXE with lastModified=1410491002000, length=162376398 Sep 21, 2014 7:15:52 AM FINE hudson.model.DirectoryBrowserSupport Serving file:/C:/Program%20Files%20(x86)/Jenkins/jobs/pdk/builds/2014-09-11_20-03-08/archive/platypus.EXE with lastModified=1410491002000, length=162376398 Sep 21, 2014 7:15:59 AM FINE hudson.model.DirectoryBrowserSupport Serving file:/C:/Program%20Files%20(x86)/Jenkins/jobs/pdk/builds/2014-09-11_20-03-08/archive/platypus.EXE with lastModified=1410491002000, length=162376398 Sep 21, 2014 7:17:00 AM FINE hudson.model.DirectoryBrowserSupport Serving
[JIRA] [xshell] (JENKINS-20478) Some of the Environment Variables are not expanding properly
Mark Waite commented on JENKINS-20478 Some of the Environment Variables are not expanding properly I think I'm seeing the same issue with my XShell based jobs using a parameterized build. The wiki page suggests that the syntax for expansion is to precede the variable with a dollar sign as in $TARGET_URL. When I do that from a parameterized build which has a parameter TARGET_URL, the shell build step correctly expands the TARGET_URL reference, while the XShell build step emits a literal $TARGET_URL. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24786) Since 2.2.6, environment variables are not expanded in git publisher
Mark Waite
commented on JENKINS-24786
Since 2.2.6, environment variables are not expanded in git publisher
Thanks. I can duplicate the problem with a sample job. The steps I took:
Define a free-style project
Define a string parameter TARGET_URL for the project, default to ssh://mwaite@mark-pc1/var/lib/git/mwaite/JENKINS-12316.git
Use git as the SCM for the freestyle project
Configure git repo to user ${TARGET_URL} as repository URL
# Run the job, confirm it succeeds, confirm log does not contain literal string TARGET_URL
# Add git publisher post build action to push the master branch
# Run the job, confirm it now includes ${TARGET_URL} in the console log for git push (and only for git push)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24786) Since 2.2.6, environment variables are not expanded in git publisher
Mark Waite
edited a comment on JENKINS-24786
Since 2.2.6, environment variables are not expanded in git publisher
Thanks. I can duplicate the problem with a sample job. The steps I took:
Define a free-style project
Define a string parameter TARGET_URL for the project, default to ssh://mwaite@mark-pc1/var/lib/git/mwaite/JENKINS-12316.git
Use git as the SCM for the freestyle project
Configure git repo to use ${TARGET_URL} as repository URL
Run the job, confirm it succeeds, confirm log does not contain literal string TARGET_URL
Add git publisher post build action to push the master branch
Run the job, confirm it now includes ${TARGET_URL} in the console log for git push (and only for git push)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24786) Since 2.2.6, environment variables are not expanded in git publisher
Mark Waite
edited a comment on JENKINS-24786
Since 2.2.6, environment variables are not expanded in git publisher
Thanks. I can duplicate the problem with a sample job. The steps I took:
Define a free-style project
Define a string parameter TARGET_URL for the project, default to ssh://mwaite@mark-pc1/var/lib/git/mwaite/JENKINS-12316.git
Use git as the SCM for the freestyle project
Configure git repo to use ${TARGET_URL} as repository URL
Run the job, confirm it succeeds, confirm log does not contain literal string TARGET_URL, and does contain the value of the parameter TARGET_URL
Add git publisher post build action to push the master branch
Run the job, confirm it now includes ${TARGET_URL} in the console log for git push (and only for git push)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-22118) Unable to tag build due to lack of credentials
tigren zhang commented on JENKINS-22118 Unable to tag build due to lack of credentials same problem with Jenkins 1.577, Subversion plug-in 2.4.3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22855) SSH Credential's username isn't used.
Mark Waite commented on JENKINS-22855 SSH Credentials username isnt used. The work around for this is to include the user name in the ssh URL, as in ssh://mwaite@mark-pc1/var/lib/git/mwaite/bin.git This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
