[JIRA] (JENKINS-41804) Jenkins.instance.getItem does not find jobs, in a Thread launched from a systemGroovyScript
Title: Message Title
Jon Alberdi created an issue
Jenkins / JENKINS-41804
Jenkins.instance.getItem does not find jobs, in a Thread launched from a systemGroovyScript
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2017/Feb/07 1:13 PM
Environment:
java: openjdk version "1.8.0_121" jenkins: org.jenkins-ci.main:jenkins-war:2.32.2
Priority:
Minor
Reporter:
Jon Alberdi
Create a job, with the following system groovy script.
import jenkins.model.Jenkins
def run() {
out.printf("Instance = %s\n", Jenkins.instance)
out.println(Jenkins.instance.getItem("test-job"))
Thread.start {
out.printf("TTT Instance = %s\n", Jenkins.instance)
out.println(Jenkins.instance.getItem("test-job"))
}.join()
}
run()
``` outputs
Instance = hudson.model.Hudson@6fd641a0
hudson.model.FreeStyleProject@4e6be3ed[test-job]
TTT Instance = hudson.model.Hudson@6fd641a0
null
The issue is not reproduced in
org.jenkins-ci.main:jenkins-war:2.19.4
when using getItemMap()['test-job'] instead of getI
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title
philippe lançon edited a comment on JENKINS-37984
Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
problem seems to be linked with the size all the script but I remarked it's linked also according number and size of stages.A workaround consists to declare a function called in some big stages.before :stage ('build') {if ( . ) { } else { } .}workaround def build() {if ( . ) { } else { } .}stage ('build') { build()}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title
philippe lançon commented on JENKINS-37984
Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
problem seems to be linked with the size all the script but I remarked it's linked also according number and size of stages. A workaround consists to declare a function called in some big stages. before : stage ('build') { if . } else { } . } workaround def build() { if . } else { } . } stage ('build') { build() }
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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] (JENKINS-41758) Add a Declarative Agent extension to the Kubernetes plugin
Title: Message Title Andrew Bayer started work on JENKINS-41758 Change By: Andrew Bayer Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41758) Add a Declarative Agent extension to the Kubernetes plugin
Title: Message Title Andrew Bayer commented on JENKINS-41758 Re: Add a Declarative Agent extension to the Kubernetes plugin Initial very much still work in progress PR up at https://github.com/jenkinsci/kubernetes-plugin/pull/127 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-28335) Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Title: Message Title
James Hogarth commented on JENKINS-28335
Re: Step to run Git commands w/ credentials & tool (was: GitPublisher support)
I like the files idea but we needed a user/pass version. My contribution and modification to this is:
Our ansible deployment configures:
- name: configure git username
become_user: jenkins
git_config:
scope: global
name: user.name
value: "{{ lookup('env','USER') }}"
- name: configure git email
become_user: jenkins
git_config:
scope: global
name: user.email
value: "{{ lookup('env','USER') }}@{{ ansible_hostname }}"
- name: enable git cache credential storage
become_user: jenkins
git_config:
scope: global
name: credential.helper
value: cache
The jenkins pipeline contains:
stage("tag the commit with datetime") {
withCredentials([usernamePassword(credentialsId: 'my_cred_id' usernameVariable: 'GIT_USERNAME', passwordVariable: 'GIT_PASSWORD')]) {
// use date for tag
def tag = new Date().format("MMddHHmm")
// configure the git credentials, these are cached in RAM for several minutes to use
// this is required until https://issues.jenkins-ci.org/browse/JENKINS-28335 is resolved upstream
sh "echo 'protocol=https\nhost=\nusername=${GIT_USERNAME}\npassword=${GIT_PASSWORD}\n\n' | git credential approve "
sh "git tag -a ${tag} -m '${USER} tagging'"
sh "git push --tags"
}
}
This example uses new Date() which needs whitelisting right now but could easily be BUILD_ID if you were sure that you'd never need to rebuild, and lose an incrementing BUILD_ID, or whatever other metric/value was preferred.
Add Comment
[JIRA] (JENKINS-41803) httpRequest step called outside node causes exception
Title: Message Title Dmitry Salashnik updated an issue Jenkins / JENKINS-41803 httpRequest step called outside node causes exception Change By: Dmitry Salashnik Summary: httpRequest sep step called outside node causes exception Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41803) httpRequest sep called outside node causes exception
Title: Message Title Dmitry Salashnik created an issue Jenkins / JENKINS-41803 httpRequest sep called outside node causes exception Issue Type: Bug Assignee: Janario Oliveira Components: http-request-plugin Created: 2017/Feb/07 12:45 PM Environment: Jenkins ver. 2.44 HTTP Request Plugin ver. 1.8.13 Labels: plugin pipeline exception Priority: Minor Reporter: Dmitry Salashnik httpRequest step called outside node causes exception "Required context class hudson.FilePath is missing" as i think, this is because logResponseToFile(build.getWorkspace(), logger, responseContentSupplier); is called in HttpRequest.perform
[JIRA] (JENKINS-30206) Multibranch plugin: Modified properties do not propagate to existing branches
Title: Message Title Roman Baeriswyl commented on JENKINS-30206 Re: Multibranch plugin: Modified properties do not propagate to existing branches Any news on this? How can this be resolved while the problem is not fixed in the plugin? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41802) Inconsistent case for DisplayURLProvider.getTestUrl() method name
Title: Message Title Reinhold Füreder created an issue Jenkins / JENKINS-41802 Inconsistent case for DisplayURLProvider.getTestUrl() method name Issue Type: Bug Assignee: James Dumay Components: display-url-api-plugin Created: 2017/Feb/07 12:25 PM Environment: Display URL API plug-in 1.1.1 Priority: Minor Reporter: Reinhold Füreder I stumbled over this in groovy email templates: getTestUrl(...) vs. getRunURL(...) and getChangesURL(...) and getJobURL(...). (Not sure about getRoot(), that also returns an URL.) Not sure about backwards compatibility etc... Add Comment
[JIRA] (JENKINS-41175) BlueOcean display URL is not working
Title: Message Title
Alex Radinsky commented on JENKINS-41175
Re: BlueOcean display URL is not working
Restarted after install, that's not the issue. How do you call the job url to point to blue ocean? something like $ {env.BUILD_URL} ?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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] (JENKINS-41767) Exception in jenkins log: class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method
Title: Message Title
Nikolas Falco edited a comment on JENKINS-41767
Re: Exception in jenkins log: class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method
This happens because I'm the only plugin in your job configuration page that calls GlobalConfigFiles.getConfigs(Class) to populate the combobox filtering by configuration kind.There are other plugin the invoke config-file-provider API in the job configuration page* the config-file-provider itself, where it populate a similar combobox BUT with all kinds of configuration. It calls a different API GlobalConfigFiles.getConfigs() where descriptor {noformat}at org.jenkinsci.lib.configprovider.model.Config.getDescriptor(Config.java:108){noformat} is not used* maven plugin where you can choose "Maven Settings" configuration file BUT has a totally different way to provide themTo discover other extension point of config-file-provider please try to go on "Manage Jenkins"->"Managed files"->"Add a new Config"Follow default kind:* Global Maven settings.xml* Maven settings.xml* Json file* Maven toolchains.xml* Simple XML file* Groovy file* Custom file* Ivy configurationAll others entries are extension point (mine is "_Npm config file_").Other good tentative is delete one by one defined configuration file and at the same time reload job configuration page. When the page works the latest deleted configuration has the problem.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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,
[JIRA] (JENKINS-41767) Exception in jenkins log: class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method
Title: Message Title Nikolas Falco commented on JENKINS-41767 Re: Exception in jenkins log: class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method This happens because I'm the only plugin in your job configuration page that calls GlobalConfigFiles.getConfigs(Class) to populate the combobox filtering by configuration kind. There are other plugin the invoke config-file-provider API in the job configuration page the config-file-provider itself, where it populate a similar combobox BUT with all kinds of configuration. It calls a different API GlobalConfigFiles.getConfigs() where descriptor at org.jenkinsci.lib.configprovider.model.Config.getDescriptor(Config.java:108) is not used maven plugin where you can choose "Maven Settings" configuration file BUT has a totally different way to provide them To discover other extension point of config-file-provider please try to go on "Manage Jenkins">"Managed files">"Add a new Config" Follow default kind: Global Maven settings.xml Maven settings.xml Json file Maven toolchains.xml Simple XML file Groovy file Custom file Ivy configuration All others entries are extension point (mine is "Npm config file"). Other good tentative is delete one by one defined configuration file and at the same time reload job configuration page. When the page works the latest deleted configuration has the problem. Add Comment
[JIRA] (JENKINS-34437) Enable amazon-ecr-plugin behind proxy
Title: Message Title Markus Pöschl commented on JENKINS-34437 Re: Enable amazon-ecr-plugin behind proxy PR is through Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41801) Ant plugin does not correctly resolve and property resolving empty build parameter
Title: Message Title Matt Doran created an issue Jenkins / JENKINS-41801 Ant plugin does not correctly resolve and property resolving empty build parameter Issue Type: Bug Assignee: Armando Fernandez Components: ant-plugin Created: 2017/Feb/07 12:02 PM Environment: Jenkins: 2.43 Ant Plugin: 1.4 OS: Mac/Linux/Windows - though problems most pronounced on windows Priority: Major Reporter: Matt Doran If an ant build passes through a parameter referencing a "build parameter", the replacement will not occur if the build parameter is an empty string. e.g. if properties on Ant build step are: myprop=$buildVariable The resulting ant command line will look like: ant -Dmyprop=$buildVariable instead of ant -Dmyprop= The reason is that the EnvVars jenkins class, will remove properties when they are empty. This odd behaviour is also discussed in JENKINS-15146 ... it would seem that empty string is valid and only null should be removed. This issue is particularly tricky as things will mostly work as expected on Unix operating systems because the $buildVariable will be replaced by the shell with the build variable in the environment. If fails completely on Windows because no variable expansion occurs. Also note that the same behaviour is not seen by the gradle plugin, as does these replacements slightly differently (replacing build parameters without putting them into EnvVars). I'm preparing a pull request to resolve this.
[JIRA] (JENKINS-41800) BitBucket organization folder not displaying after SCM 2.0
Title: Message Title Mike Delaney created an issue Jenkins / JENKINS-41800 BitBucket organization folder not displaying after SCM 2.0 Issue Type: Bug Assignee: Antonio Muñiz Attachments: Screen Shot 2017-02-07 at 6.51.56 AM.png Components: bitbucket-branch-source-plugin Created: 2017/Feb/07 11:54 AM Environment: Ubuntu, v14.04 (amd64) Java, v1.8 Jenkins, v2.43 BItbucket Branch Source, v2.0.2 Priority: Minor Reporter: Mike Delaney After the upgrade to SCM API 2.0, the folder icon for BitBucket Team project type is missing. It just dispays the text "Organization Folder". See as an example. Add Comment
[JIRA] (JENKINS-40624) nodejs installer not compatible with declarative pipeline definition
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40624 Re: nodejs installer not compatible with declarative pipeline definition Code changed in jenkins User: Nikolas Falco Path: src/main/java/jenkins/plugins/nodejs/tools/NodeJSInstallation.java src/test/java/jenkins/plugins/nodejs/NpmrcFileSupplyTest.java http://jenkins-ci.org/commit/nodejs-plugin/15db7f5faf3a6fbb3a558f0150684b88654eb6e1 Log: JENKINS-40624 Fix test case, miss to remove assert on environment Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41794) Groovy pipeline: Git command didn't checkout the last commit
Title: Message Title
Mark Waite edited a comment on JENKINS-41794
Re: Groovy pipeline: Git command didn't checkout the last commit
There is a surprising line in the git output where it says:{code}> git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10{code}That might indicate that someone created a branch named "origin/master" in your repository. If so, that tends to confuse the git plugin. Most users don't need a branch named "origin/master", so if one exists, you should probably delete it.Other than that, I don't have suggestions to offer.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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] (JENKINS-41794) Groovy pipeline: Git command didn't checkout the last commit
Title: Message Title
Mark Waite edited a comment on JENKINS-41794
Re: Groovy pipeline: Git command didn't checkout the last commit
There is a surprising line in the git output where it says:{ quote code }> git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10{ quote code }That might indicate that someone created a branch named "origin/master" in your repository. If so, that tends to confuse the git plugin.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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] (JENKINS-41794) Groovy pipeline: Git command didn't checkout the last commit
Title: Message Title
Mark Waite commented on JENKINS-41794
Re: Groovy pipeline: Git command didn't checkout the last commit
There is a surprising line in the git output where it says:
> git rev-parse refs/remotes/origin/origin/master^
Unknown macro: {commit}
# timeout=10
That might indicate that someone created a branch named "origin/master" in your repository. If so, that tends to confuse the git plugin.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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] (JENKINS-41799) Automatic token renewal for HashiCorp Vault plugin
Title: Message Title Brian Lycett created an issue Jenkins / JENKINS-41799 Automatic token renewal for HashiCorp Vault plugin Issue Type: New Feature Assignee: Peter Tierno Components: hashicorp-vault-plugin Created: 2017/Feb/07 11:47 AM Priority: Minor Reporter: Brian Lycett Would it be possible add an option to automatically renew the Vault token each time it's used? Or periodically? At the moment we need to keep generating new tokens if the current one expires. Using the `/auth/token/renew-self` API feature would be ideal (https://www.vaultproject.io/docs/auth/token.html). Add Comment
[JIRA] (JENKINS-41794) Groovy pipeline: Git command didn't checkout the last commit
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-41794 Groovy pipeline: Git command didn't checkout the last commit Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41767) Exception in jenkins log: class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method
Title: Message Title Petr H commented on JENKINS-41767 Re: Exception in jenkins log: class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method It might be possible that it isn't being caused by the NodeJS plugin itself, but then: 1. Why it started to occur after updating only this single plugin (and nothing else)? 2. Why it's the only plugin appearing in the stack trace: Caused by: java.lang.IllegalStateException: class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method! at org.jenkinsci.lib.configprovider.model.Config.getDescriptor(Config.java:108) at org.jenkinsci.plugins.configfiles.GlobalConfigFiles.getConfigs(GlobalConfigFiles.java:91) at jenkins.plugins.nodejs.NodeJSBuildWrapper$DescriptorImpl.getConfigs(NodeJSBuildWrapper.java:137) ... 189 more With the above 2 points - how are we supposed to find out the other plugin that's the cause is it isn't the NodeJS one? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41797) Jenkins jobs loading stuck resetting ProxyWhitelist
Title: Message Title Oliver Gondža started work on JENKINS-41797 Change By: Oliver Gondža Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41797) Jenkins jobs loading stuck resetting ProxyWhitelist
Title: Message Title Oliver Gondža commented on JENKINS-41797 Re: Jenkins jobs loading stuck resetting ProxyWhitelist Fix proposed. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41797) Jenkins jobs loading stuck resetting ProxyWhitelist
Title: Message Title Oliver Gondža assigned an issue to Oliver Gondža Jenkins / JENKINS-41797 Jenkins jobs loading stuck resetting ProxyWhitelist Change By: Oliver Gondža Assignee: Oliver Gondža Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-25324) SymLinks are not maintained
Title: Message Title Erik Sørnes commented on JENKINS-25324 Re: SymLinks are not maintained Hi, i'm using version 0.33, latest, version of this plugin, and the issue is stil there. Folder symlinks are not copied as symlinks. I'm also copying artifact from workspace to a directory in the same filesystem. regards Erik Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41797) Jenkins jobs loading stuck resetting ProxyWhitelist
Title: Message Title
Oliver Gondža updated an issue
Jenkins / JENKINS-41797
Jenkins jobs loading stuck resetting ProxyWhitelist
Change By:
Oliver Gondža
All 32 of my loading thrreads threads got stuck there never seem to resume again.{noformat}"Loading job my-task" #51 daemon prio=5 os_prio=0 tid=0x7efeb011e800 nid=0x32c66 runnable [0x7eff48245000] java.lang.Thread.State: RUNNABLE at java.util.WeakHashMap.put(WeakHashMap.java:453) at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.ProxyWhitelist.reset(ProxyWhitelist.java:95) at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.ProxyWhitelist.(ProxyWhitelist.java:54) at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.ProxyWhitelist.(ProxyWhitelist.java:117) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.run(GroovySandbox.java:136) at hudson.matrix.FilterScript.evaluate(FilterScript.java:45) at hudson.matrix.FilterScript.apply(FilterScript.java:85) at hudson.matrix.Combination.evalGroovyExpression(Combination.java:101) at hudson.matrix.Combination.evalGroovyExpression(Combination.java:91) at hudson.matrix.MatrixProject.rebuildConfigurations(MatrixProject.java:641) at hudson.matrix.MatrixProject.onLoad(MatrixProject.java:508) at hudson.model.Items.load(Items.java:320) at jenkins.model.Jenkins$17.run(Jenkins.java:2651) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:904) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745){noformat}
Add Comment
[JIRA] (JENKINS-41798) Duration of running jobs on BO activity page resets to 0 on reload
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-41798 Duration of running jobs on BO activity page resets to 0 on reload Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2017/Feb/07 10:39 AM Environment: Blue Ocean 1.0.0-b21 Priority: Minor Reporter: Andrew Bayer Could be this has been fixed since, but just in case, thought I'd report it - when I go to, say, https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fpipeline-model-definition-plugin/activity/, the duration for any currently running build starts at 0 seconds and counts forward. Then, if I reload the page, the duration resets back to 0 again. This isn't the case for completed builds, just running builds. Add Comment
[JIRA] (JENKINS-41797) Jenkins jobs loading stuck resetting ProxyWhitelist
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-41797 Jenkins jobs loading stuck resetting ProxyWhitelist Change By: Oliver Gondža Environment: Script Security Plugin 1.19Permissive Script Security Plugin 0.1 (does not seem to be related) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41797) Jenkins jobs loading stuck resetting ProxyWhitelist
Title: Message Title
Oliver Gondža updated an issue
Jenkins / JENKINS-41797
Jenkins jobs loading stuck resetting ProxyWhitelist
Change By:
Oliver Gondža
All 32 of my loading thrreads got stuck there never seem to resume again. {noformat}"Loading job my-task" #51 daemon prio=5 os_prio=0 tid=0x7efeb011e800 nid=0x32c66 runnable [0x7eff48245000] java.lang.Thread.State: RUNNABLE at java.util.WeakHashMap.put(WeakHashMap.java:453) at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.ProxyWhitelist.reset(ProxyWhitelist.java:95) at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.ProxyWhitelist.(ProxyWhitelist.java:54) at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.ProxyWhitelist.(ProxyWhitelist.java:117) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.run(GroovySandbox.java:136) at hudson.matrix.FilterScript.evaluate(FilterScript.java:45) at hudson.matrix.FilterScript.apply(FilterScript.java:85) at hudson.matrix.Combination.evalGroovyExpression(Combination.java:101) at hudson.matrix.Combination.evalGroovyExpression(Combination.java:91) at hudson.matrix.MatrixProject.rebuildConfigurations(MatrixProject.java:641) at hudson.matrix.MatrixProject.onLoad(MatrixProject.java:508) at hudson.model.Items.load(Items.java:320) at jenkins.model.Jenkins$17.run(Jenkins.java:2651) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:904) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745){noformat}
Add Comment
[JIRA] (JENKINS-41797) Jenkins jobs loading stuck resetting ProxyWhitelist
Title: Message Title Oliver Gondža created an issue Jenkins / JENKINS-41797 Jenkins jobs loading stuck resetting ProxyWhitelist Issue Type: Bug Assignee: Unassigned Components: script-security-plugin Created: 2017/Feb/07 10:35 AM Priority: Major Reporter: Oliver Gondža "Loading job my-task" #51 daemon prio=5 os_prio=0 tid=0x7efeb011e800 nid=0x32c66 runnable [0x7eff48245000] java.lang.Thread.State: RUNNABLE at java.util.WeakHashMap.put(WeakHashMap.java:453) at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.ProxyWhitelist.reset(ProxyWhitelist.java:95) at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.ProxyWhitelist.(ProxyWhitelist.java:54) at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.ProxyWhitelist.(ProxyWhitelist.java:117) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.run(GroovySandbox.java:136) at hudson.matrix.FilterScript.evaluate(FilterScript.java:45) at hudson.matrix.FilterScript.apply(FilterScript.java:85) at hudson.matrix.Combination.evalGroovyExpression(Combination.java:101) at hudson.matrix.Combination.evalGroovyExpression(Combination.java:91) at hudson.matrix.MatrixProject.rebuildConfigurations(MatrixProject.java:641) at hudson.matrix.MatrixProject.onLoad(MatrixProject.java:508) at hudson.model.Items.load(Items.java:320) at jenkins.model.Jenkins$17.run(Jenkins.java:2651) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:904) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.Thre
[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials
Title: Message Title
Sebastian Lange edited a comment on JENKINS-32167
Re: ISVNAuthentication provider did not provide credentials
I can confirm this. We encounter the same problems. All externals are on the same SVN-server. Nevertheless it breaks on first revision-check initialted build, but succeeds with the next build. Do not mind the binary stores on the SVN, just a convenience thing{code:java}...A N\libs\mysql\docs\INFO_BINA N\libs\mysql\docs\ChangeLogA N\libs\mysql\READMEAt revision 5113Hole 'http://10.*.*.*/svn/unit/path/RL-32' aus Revision -1 in Datei 'C:\Jenkins\N\libs\RL' AUN\libs\RL\RLn1.dllAUN\libs\RL\RLn2.dllAt revision 5113At revision 10752 5113 No changes for http://10.*.*.*/svn/unit/path/project since the previous buildorg.tmatesoft.svn.core.SVNCancelException: svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:723)Caused: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled.svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. at org.tmatesoft.svn.core.internal.wc.SVNError{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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,
[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials
Title: Message Title Sebastian Lange commented on JENKINS-32167 Re: ISVNAuthentication provider did not provide credentials I can confirm this. We encounter the same problems. All externals are on the same SVN-server. Nevertheless it breaks on first revision-check initialted build, but succeeds with the next build. Do not mind the binary stores on the SVN, just a convenience thing ... A N\libs\mysql\docs\INFO_BIN A N\libs\mysql\docs\ChangeLog A N\libs\mysql\README At revision 5113 Hole 'http://10.*.*.*/svn/unit/path/RL-32' aus Revision -1 in Datei 'C:\Jenkins\N\libs\RL' AUN\libs\RL\RLn1.dll AUN\libs\RL\RLn2.dll At revision 5113 At revision 10752 No changes for http://10.*.*.*/svn/unit/path/project since the previous build org.tmatesoft.svn.core.SVNCancelException: svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:723) Caused: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. at org.tmatesoft.svn.core.internal.wc.SVNError Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41796) Create acceptance test for git-userContent
Title: Message Title Evaristo Gutierrez updated JENKINS-41796 Jenkins / JENKINS-41796 Create acceptance test for git-userContent Change By: Evaristo Gutierrez Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41796) Create acceptance test for git-userContent
Title: Message Title Evaristo Gutierrez started work on JENKINS-41796 Change By: Evaristo Gutierrez Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41796) Create acceptance test for git-userContent
Title: Message Title Evaristo Gutierrez created an issue Jenkins / JENKINS-41796 Create acceptance test for git-userContent Issue Type: Task Assignee: Evaristo Gutierrez Components: acceptance-test-harness Created: 2017/Feb/07 10:20 AM Priority: Minor Reporter: Evaristo Gutierrez Create acceptance test for git-userContent plugin that verifies that at least basic operations are working properly. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41795) Add field to track event sources
Title: Message Title Stephen Connolly created an issue Jenkins / JENKINS-41795 Add field to track event sources Issue Type: Improvement Assignee: Stephen Connolly Components: scm-api-plugin Created: 2017/Feb/07 10:10 AM Priority: Minor Reporter: Stephen Connolly Need a way to see where events are originating from. May not be available for all event sources. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41722) Job folder loading performance is worse when folder contains fewer items
Title: Message Title Daniel Beck commented on JENKINS-41722 Re: Job folder loading performance is worse when folder contains fewer items If this is supposed to be bug, please provide references to relevant source code, for example from repeated thread dumps taking during page load. (I'd rather not start investigating just to find out after several hours that my previous comment was right and there's no bug here.) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41768) testlink status not run with TAP
Title: Message Title
Mark Crusher updated an issue
Jenkins / JENKINS-41768
testlink status not run with TAP
Change By:
Mark Crusher
when trying to execute test case job in Jenkins using TAP I will always see Testlink result as 'Not run' but build number variable is sent to testlink to create a new build there, so they know about each other and communicate on every buildcolored textperhaps my implementation of TAP file format/name is wrong?file name: gui_argumentscontent:{noformat}1..2not ok 1 - gui_argumentsnot ok 2 - gui_arguments{noformat}then the result shows this{noformat}Executing iterative Build Steps.Looking for the test results of TestLink test cases.Found 1 test result(s).Archiving artifactsFinished: SUCCESS{noformat} but status results are always like this: TestLink build ID: 3TestLink build name: 0.10Total of 1 tests. Where 0 passed, 0 failed, 0 were blocked and 1 were not executed.List of test cases and execution result status||Test case ID||Test case external ID||Version||Name||Test project ID||Execution status|||1113|OTC-31|1|automatic test test|1|Not Run| any ideas? I spent few days and 32 runs of the job to get here and running out of ideas.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41167) credential is not saving the credentials (iframe cross origin policy issue)
Title: Message Title Stephen Connolly commented on JENKINS-41167 Re: credential is not saving the credentials (iframe cross origin policy issue) IM PSYCHIC!!! Also unread / ignored by original poster Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41768) testlink status not run with TAP
Title: Message Title
Mark Crusher updated an issue
Jenkins / JENKINS-41768
testlink status not run with TAP
Change By:
Mark Crusher
when trying to execute test case job in Jenkins using TAP I will always see Testlink result as 'Not run' but build number variable is sent to testlink to create a new build there, so they know about each other and communicate on every build colored text perhaps my implementation of TAP file format/name is wrong?file name: gui_argumentscontent:{ { noformat} 1..2not ok 1 - gui_argumentsnot ok 2 - gui_arguments {noformat } } then the result shows this{ { noformat} Executing iterative Build Steps.Looking for the test results of TestLink test cases.Found 1 test result(s).Archiving artifactsFinished: SUCCESS {noformat } } any ideas? I spent few days and 32 runs of the job to get here and running out of ideas.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
T
[JIRA] (JENKINS-35143) Delete Pipeline Multibranch sub projects
Title: Message Title Stephen Connolly updated an issue Jenkins / JENKINS-35143 Delete Pipeline Multibranch sub projects Change By: Stephen Connolly Attachment: Screen Shot 2017-02-07 at 09.49.43.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-35143) Delete Pipeline Multibranch sub projects
Title: Message Title Stephen Connolly commented on JENKINS-35143 Re: Delete Pipeline Multibranch sub projects Andrew Hill When the branch is excluded it is then eligible for the Orphaned Item Strategy, e.g. for this screenshotI started off with the source configured for all branches, with a retention strategy of keep up to 1 branch. Then after all branches had been indexed I reconfigured the source to exclude the throw-away branch, on the subsequent index the branch becomes a "dead branch" and is now disabled. Once the orphaned item strategy is able to remove it, it will be automatically removed. Or I can preemptively delete it manually: Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41768) testlink status not run with TAP
Title: Message Title Mark Crusher updated an issue Jenkins / JENKINS-41768 testlink status not run with TAP Change By: Mark Crusher Attachment: JENKINS-41768.jpg Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41768) testlink status not run with TAP
Title: Message Title Mark Crusher updated an issue Jenkins / JENKINS-41768 testlink status not run with TAP Change By: Mark Crusher Attachment: JENKINS-41768.jpg Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41167) credential is not saving the credentials (iframe cross origin policy issue)
Title: Message Title Daniel Beck commented on JENKINS-41167 Re: credential is not saving the credentials (iframe cross origin policy issue) My guess would be that Jenkins is accessed from a different URL that the one configured in the system configuration. That messes up all kinds of things. IM PSYCHIC!!! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (TEST-100) How to Launch a openstack windows instance from Jenkins
Title: Message Title Shimith Menon updated an issue test / TEST-100 How to Launch a openstack windows instance from Jenkins Change By: Shimith Menon Hi All,I have installed latest Jenkins for windows and I was trying to Integrate openstack windows images with Jenkins. For that I have installed all openstack Plugins and Now I can see an option "*Openstack Instance Creation* " ! and I have filled all details as cloud name , template name etc. But when I build the Job I am getting below error FATAL: No such template sysprep_bare_win2012_v25java.lang.IllegalArgumentException: No such template sysprep_bare_win2012_v25 at jenkins.plugins.openstack.compute.JCloudsBuildWrapper$1.apply(JCloudsBuildWrapper.java:66) at jenkins.plugins.openstack.compute.JCloudsBuildWrapper$1.apply(JCloudsBuildWrapper.java:58) at com.google.common.collect.Iterators$8.transform(Iterators.java:794) at com.google.common.collect.TransformedIterator.next(TransformedIterator.java:48) at jenkins.plugins.openstack.compute.internal.ProvisionPlannedInstancesAndDestroyAllOnError.apply(ProvisionPlannedInstancesAndDestroyAllOnError.java:36) at jenkins.plugins.openstack.compute.JCloudsBuildWrapper.setUp(JCloudsBuildWrapper.java:77) at hudson.model.Build$BuildExecution.doRun(Build.java:156) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1728) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404)Finished: FAILURE Can anyone tell help me the steps find and fix this error to add *Cloud Name, template Name in Jenkins that also Please let me know how that can be properly configured , so that I can launch a windows openstack windows instance from Jenkins successfully. Any help is much appreciated. Add Comment
[JIRA] (JENKINS-41638) "Open Blue Ocean" button doesn't work unless the server URL is set correctly
Title: Message Title Tom FENNELLY commented on JENKINS-41638 Re: "Open Blue Ocean" button doesn't work unless the server URL is set correctly I really do not like apps that just start doing something different to what you expect. If you've been using Blue Ocean and know how this button works then you're going to expect certain behaviours. If that behaviour changes for some unknown reason (unknown to the user - even if there's warning about it somewhere else) then that can be quite annoying. Personally I much prefer an app to tell me something is not right and not do unexpected things. Anyway ... I'll have a look and see can I hack it to "just work", as is often said Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-35143) Delete Pipeline Multibranch sub projects
Title: Message Title Stephen Connolly updated an issue Jenkins / JENKINS-35143 Delete Pipeline Multibranch sub projects Change By: Stephen Connolly Attachment: Screen Shot 2017-02-07 at 09.46.57.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41768) testlink status not run with TAP
Title: Message Title Mark Crusher updated an issue Jenkins / JENKINS-41768 testlink status not run with TAP Change By: Mark Crusher Attachment: JENKINS-41768.jpg Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41768) testlink status not run with TAP
Title: Message Title Mark Crusher updated an issue Jenkins / JENKINS-41768 testlink status not run with TAP Change By: Mark Crusher Attachment: JENKINS-41768.jpg Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41768) testlink status not run with TAP
Title: Message Title Mark Crusher updated an issue Jenkins / JENKINS-41768 testlink status not run with TAP Change By: Mark Crusher Attachment: JENKINS-41768.jpg Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-38418) Failed to load persisted workflow state (remote-loader)
Title: Message Title Emilio Escobar started work on JENKINS-38418 Change By: Emilio Escobar Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41794) Groovy pipeline: Git command didn't checkout the last commit
Title: Message Title
Mikhail Chinkov updated an issue
Jenkins / JENKINS-41794
Groovy pipeline: Git command didn't checkout the last commit
Change By:
Mikhail Chinkov
The problem: once, when I've run in Groovy pipeline [multibranch mode] git command to fetch the latest codebase to the slave workspace. The command:{code :groovy }git([url: 'https://github.com/myorg/myrepo.git', branch: "${env.BRANCH_NAME}", credentialsId: "${env.CREDENTIALS_ID}"]){code}Command output:{code:shell} > git init /home/jenkins/workspace/myjob_master-U53VEN73XGVKUQMHQMUNYUI3M2EMMZ6IAKD7LIC32FLG7MMBHHIQ # timeout=10 > git --version # timeout=10 > git fetch --tags --progress https://github.com/myorg/myrepot.git +refs/heads/*:refs/remotes/origin/* > git config remote.origin.url https://github.com/myorg/myrepo.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://github.com/myorg/myrepo.git # timeout=10 > git fetch --tags --progress https://github.com/myorg/myrepo.git +refs/heads/*:refs/remotes/origin/* > git rev-parse refs/remotes/origin/master^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10 > git config core.sparsecheckout # timeout=10 > git checkout -f 950c0037ee3d2b2803380baa5c0d7812a47dd6b9 > git branch -a -v --no-abbrev # timeout=10 > git checkout -b master 950c0037ee3d2b2803380baa5c0d7812a47dd6b9{code}Although it has to checkout the latest version - it didn't. And there was no error in the build workflow. So, I've got the obsolete repo state, built to Docker image and finally got some sort of troubleshooting because the problem was not so obvious. When I connected to the troubled slave and check the git - the commit wasn't there. I just made a git pull into the workspace, rebuilt the Docker image and got the latest application version.I tried to reproduce the possible bug, but I couldn't. I rebuilt the pipeline at the clean workspace, later trying to roll out the commit with changes. And commit came! So, I still confused what kind of bug it was.So, please, help me to understand where is the problem might be. If you have to know additional details - please, write, what kind of.Thanks in advance.
Add Comment
[JIRA] (JENKINS-41794) Groovy pipeline: Git command didn't checkout the last commit
Title: Message Title
Mikhail Chinkov updated an issue
Jenkins / JENKINS-41794
Groovy pipeline: Git command didn't checkout the last commit
Change By:
Mikhail Chinkov
The problem: once, when I've run in Groovy pipeline [multibranch mode] git command to fetch the latest codebase to the slave workspace. The command:{code}git([url: 'https://github.com/myorg/myrepo.git', branch: "${env.BRANCH_NAME}", credentialsId: "${env.CREDENTIALS_ID}"]){code}Command output:{code :shell } > git init /home/jenkins/workspace/myjob_master-U53VEN73XGVKUQMHQMUNYUI3M2EMMZ6IAKD7LIC32FLG7MMBHHIQ # timeout=10 > git --version # timeout=10 > git fetch --tags --progress https://github.com/myorg/myrepot.git +refs/heads/*:refs/remotes/origin/* > git config remote.origin.url https://github.com/myorg/myrepo.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://github.com/myorg/myrepo.git # timeout=10 > git fetch --tags --progress https://github.com/myorg/myrepo.git +refs/heads/*:refs/remotes/origin/* > git rev-parse refs/remotes/origin/master^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10 > git config core.sparsecheckout # timeout=10 > git checkout -f 950c0037ee3d2b2803380baa5c0d7812a47dd6b9 > git branch -a -v --no-abbrev # timeout=10 > git checkout -b master 950c0037ee3d2b2803380baa5c0d7812a47dd6b9{code}Although it has to checkout the latest version - it didn't. And there was no error in the build workflow. So, I've got the obsolete repo state, built to Docker image and finally got some sort of troubleshooting because the problem was not so obvious. When I connected to the troubled slave and check the git - the commit wasn't there. I just made a git pull into the workspace, rebuilt the Docker image and got the latest application version.I tried to reproduce the possible bug, but I couldn't. I rebuilt the pipeline at the clean workspace, later trying to roll out the commit with changes. And commit came! So, I still confused what kind of bug it was.So, please, help me to understand where is the problem might be. If you have to know additional details - please, write, what kind of.Thanks in advance.
Add Comment
[JIRA] (JENKINS-41794) Groovy pipeline: Git command didn't checkout the last commit
Title: Message Title Mikhail Chinkov created an issue Jenkins / JENKINS-41794 Groovy pipeline: Git command didn't checkout the last commit Issue Type: Bug Assignee: Mark Waite Attachments: VPk8wS4Pnqw.jpg Components: git-client-plugin, groovy-plugin, multi-branch-project-plugin, pipeline-stage-step-plugin Created: 2017/Feb/07 9:18 AM Environment: Operating System: Ubuntu 16.04 Xenial Kernel: 4.4.0-53-generic Java: OpenJDK Runtime Environment (build 1.8.0_121-8u121-b13-0ubuntu1.16.04.2-b13) Jenkins version: 2.32.1 Jenkins plugins versions: at the attached screenshot Jenkins run: directly How you installed Jenkins: apt-get from official repo Slave nodes: 1 affected node on the same OS/kernel and Java, connected by SSH, built from EC2 plugin. Labels: git pipeline groovy multibranch Priority: Trivial Reporter: Mikhail Chinkov The problem: once, when I've run in Groovy pipeline [multibranch mode] git command to fetch the latest codebase to the slave workspace. The command: Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xht
[JIRA] (JENKINS-22088) Disk space leak with multiple copies of winstone-XXXX.jar in TEMP folder
Title: Message Title Erwin Müller commented on JENKINS-22088 Re: Disk space leak with multiple copies of winstone-.jar in TEMP folder Hello. Just run in this issue on our build server. Jenkins ver. 2.32.1. Windows Server 2008 R2 Standard 64 Bit. winstone-.jar was created and filled up disk space on C:. Solution was to kill all Jenkins/Java processes and restart Jenkins. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41590) Mercurial plugin 1.58 doesnt appear at the update center
Title: Message Title Javier Delgado resolved as Fixed Version released after the SCM API 2.0 Upgrade Fallout Jenkins / JENKINS-41590 Mercurial plugin 1.58 doesnt appear at the update center Change By: Javier Delgado Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.googl
[JIRA] (JENKINS-35096) Add support for Jenkins Pipeline to the cppcheck-plugin
Title: Message Title Marten Lootsma commented on JENKINS-35096 Re: Add support for Jenkins Pipeline to the cppcheck-plugin Marco Steffan thanks for the pointer. That solved it for me. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41792) NeoLoad plugin attempts to parse archived XML files
Title: Message Title
Tuukka Mustonen updated an issue
Jenkins / JENKINS-41792
NeoLoad plugin attempts to parse archived XML files
Change By:
Tuukka Mustonen
I am not sure when exactly this happens, but my jenkins.log gets pretty much flooded by something like this:{code}[Fatal Error] dashBoard_*.xml:9:12: Attribute name "_ping" associated with an element type "GET" must be followed by the ' = ' character.Feb 07, 2017 7:55:15 AM com.neotys.nl.controller.report.transform.NeoLoadReportDoc WARNING: Error reading xml file. Attribute name "_ping" associated with an element type "GET" must be followed by the ' = ' character.org.xml.sax.SAXParseException; systemId: file:///var/lib/jenkins/jobs/COSMOS-CI-PERF-ew1-perftest-ping/builds/5/archive/dashBoard_*.xml; lineNumber: 9; columnNumber: 12; Attribute name "_ping" associated with an element type "GET" must be followed by the ' = ' character.at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:257)at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:339)at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:177)at org.jenkinsci.plugins.neoload.integration.supporting.XMLUtilities.readXmlFile(XMLUtilities.java:226)at com.neotys.nl.controller.report.transform.NeoLoadReportDoc.(NeoLoadReportDoc.java:102)at org.jenkinsci.plugins.neoload.integration.ProjectSpecificAction.findXMLResultsFile(ProjectSpecificAction.java:428)at org.jenkinsci.plugins.neoload.integration.ProjectSpecificAction.refreshGraphData(ProjectSpecificAction.java:171)at org.jenkinsci.plugins.neoload.integration.ProjectSpecificAction.(ProjectSpecificAction.java:109)at org.jenkinsci.plugins.neoload.integration.ProjectSpecificActionFactory.createFor(ProjectSpecificActionFactory.java:53)at hudson.model.AbstractProject.createTransientActions(AbstractProject.java:766)at hudson.model.Project.createTransientActions(Project.java:241)at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:755)at hudson.model.AbstractProject.addProperty(AbstractProject.java:786)at hudson.plugins.disk_usage.DiskUsageUtil.addProperty(DiskUsageUtil.java:58)at hudson.plugins.disk_usage.BuildDiskUsageAction.(BuildDiskUsageAction.java:38)at hudson.plugins.disk_usage.DiskUsageBuildActionFactory.createFor(DiskUsageBuildActionFactory.java:31)at hudson.plugins.disk_usage.DiskUsageBuildActionFactory.createFor(DiskUsageBuildActionFactory.java:21)at hudson.model.Actionable.createFor(Actionable.java:107)at hudson.model.Actionable.getAllActions(Actionable.java:98)at hudson.model.Run.onLoad(Run.java:346)at hudson.model.RunMap.retrieve(RunMap.java:224)at hudson.model.RunMap.retrieve(RunMap.java:56)at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:487)at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:
[JIRA] (JENKINS-40523) Include Jenkins Project Name in Log message
Title: Message Title Boguslaw Klimas resolved as Fixed Release 0.8.0 Jenkins / JENKINS-40523 Include Jenkins Project Name in Log message Change By: Boguslaw Klimas Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-40232) Git Parameter Plugin doesn't need to clone
Title: Message Title Boguslaw Klimas updated JENKINS-40232 Release 0.8.0 Jenkins / JENKINS-40232 Git Parameter Plugin doesn't need to clone Change By: Boguslaw Klimas Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41638) "Open Blue Ocean" button doesn't work unless the server URL is set correctly
Title: Message Title Michael Neale started work on JENKINS-41638 Change By: Michael Neale Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41659) Stabilise ATH
Title: Message Title Michael Neale commented on JENKINS-41659 Re: Stabilise ATH So spent way to long mucking around with things, and settled on this: https://github.com/jenkinsci/blueocean-acceptance-test/pull/117 This works around the missing events (by just waiting for result - optional but it means it doens't hang) And also, nightwatch has a retry option that is not the suite retry: http://nightwatchjs.org/guide#command-line-options this allows the flaky ones to be retried without the whole thing being retried. Thoughts? This has passed a few times in a row now. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-39176) Project-based security configuration doesn't work for folders and subfolders
Title: Message Title Roman Stepanchuk commented on JENKINS-39176 Re: Project-based security configuration doesn't work for folders and subfolders I updated my setup to Folders Plugin 5.17. You can look on screenshot, here what I got. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-39176) Project-based security configuration doesn't work for folders and subfolders
Title: Message Title Roman Stepanchuk updated an issue Jenkins / JENKINS-39176 Project-based security configuration doesn't work for folders and subfolders Change By: Roman Stepanchuk Attachment: Screen Shot 2017-02-07 at 10.06.15.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41793) No changes from last build though my work-space has changes
Title: Message Title khushal jajpura created an issue Jenkins / JENKINS-41793 No changes from last build though my work-space has changes Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2017/Feb/07 8:02 AM Environment: Window 7, Jenkins 2.19.1 Priority: Critical Reporter: khushal jajpura I have configured jenkins to build my workspace. According to build history which has 12 builds. First 6 were failing , from build 7 onward it is stable. But from build 8 on wards I didn't see any changes in my changelist. It has changes till my first successful build. Why jenkins not showing changes to my changelist ? Add Comment
