[JIRA] (JENKINS-60969) @libs pseudo-workspace collision due to branch name truncation
Title: Message Title Yves Schumann commented on JENKINS-60969 Re: @libs pseudo-workspace collision due to branch name truncation Jesse Glick: What functionality is enabled, if this option is used? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204432.1580891884000.17467.1587751980194%40Atlassian.JIRA.
[JIRA] (JENKINS-60969) Unwanted job interaction if using global pipeline libraries
Title: Message Title Yves Schumann commented on JENKINS-60969 Re: Unwanted job interaction if using global pipeline libraries Any news here? Spot the same issue again... Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204432.1580891884000.15950.1587560340200%40Atlassian.JIRA.
[JIRA] (JENKINS-60969) Unwanted job interaction if using global pipeline libraries
Title: Message Title Yves Schumann created an issue Jenkins / JENKINS-60969 Unwanted job interaction if using global pipeline libraries Issue Type: Bug Assignee: Unassigned Components: core, pipeline Created: 2020-02-05 08:38 Priority: Minor Reporter: Yves Schumann I've spot an issue with unwanted interaction between different, independent jobs. Here are the details: Our Jenkins instance (2.176.1 LTS) has some global pipeline libraries configured. My task was some kind of structural migration on a bunch of different projects. So I created a corresponding branch on each of these projects, did the change there and pushed it. So all the build jobs started at the same time and surprisingly most of them failed with a strange error during initial jobs steps like this: ... remote: Compressing objects: 100% (6/6), done. remote: Total 8 (delta 0), reused 0 (delta 0) error: cannot lock ref 'refs/remotes/origin/bugfix/ESTA-3146-yla': Unable to create '/var/jenkins_home/workspace/rate-build-description-to-json_5@libs/pipeline-helper/.git/refs/remotes/origin/bugfix/ESTA-3146-yla.lock': File exists. Another git process seems to be running in this repository, e.g. ... After digging around I figured out, that the pipeline helper libs are cloned on the Jenkins master using a folder named like the job a/o branch, which is suffixed with `_@libs`. Additionally the folder name is stripped to 37 characters by removing characters from the beginning of the name. This leads to the real cause: Because of the identical branch name on each Git repository, the unique part of the folder names got lost and so the jobs try to use the same folder during their initialization steps
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Yves Schumann commented on JENKINS-55287 Re: Pipeline: Failure to load flow node: FlowNode was not found in storage for head We've spot the same today, all our nightly pipelines break with this error: 04:02:41 04:02:40,990 INFO JettyHandler:43 - Got request: /status.xml. Sender is 10.1.53.1:40440 Creating placeholder flownodes because failed loading originals. java.io.IOException: Tried to load head FlowNodes for execution Owner[RT-Jobs/RT-Nightly/9:RT-Jobs/RT-Nightly #9] but FlowNode was not found in storage for head id:FlowNodeId 1:526 at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.initializeStorage(CpsFlowExecution.java:679) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad(CpsFlowExecution.java:716) at org.jenkinsci.plugins.workflow.job.WorkflowRun.getExecution(WorkflowRun.java:662) at org.jenkinsci.plugins.workflow.job.WorkflowRun.onLoad(WorkflowRun.java:526) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:57) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:501) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:483) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:381) at hudson.model.RunMap.getById(RunMap.java:205) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.run(WorkflowRun.java:899) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.get(WorkflowRun.java:910) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:65) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:57) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl.onLoaded(FlowExecutionList.java:178) at jenkins.model.Jenkins.(Jenkins.java:995) at hudson.model.Hudson.(Hudson.java:85) at hudson.model.Hudson.(Hudson.java:81) at hudson.WebAppMain$3.run(WebAppMain.java:233) Finished: UNSTABLE Quite annoying as it follows Murphy's Law: Occurs in the exact worst moment... :-/ Add Comment
[JIRA] (JENKINS-60150) "Each network interface requires either a subnet or a network interface ID" after update to 1.46.1
Title: Message Title Yves Schumann commented on JENKINS-60150 Re: "Each network interface requires either a subnet or a network interface ID" after update to 1.46.1 Ok, found it myself: It seems to be required to configure a subnet ID now. Never did this before... Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203015.1573600115000.2191.1573936560290%40Atlassian.JIRA.
[JIRA] (JENKINS-60150) "Each network interface requires either a subnet or a network interface ID" after update to 1.46.1
Title: Message Title Yves Schumann closed an issue as Not A Defect Jenkins / JENKINS-60150 "Each network interface requires either a subnet or a network interface ID" after update to 1.46.1 Change By: Yves Schumann Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203015.1573600115000.2193.1573936560319%40Atlassian.JIRA.
[JIRA] (JENKINS-60150) "Each network interface requires either a subnet or a network interface ID" after update to 1.46.1
Title: Message Title Yves Schumann commented on JENKINS-60150 Re: "Each network interface requires either a subnet or a network interface ID" after update to 1.46.1 Nobody else spotting this problem? Strange... Maybe a configuration issue? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203015.1573600115000.2189.1573935300263%40Atlassian.JIRA.
[JIRA] (JENKINS-60150) "Each network interface requires either a subnet or a network interface ID" after update to 1.46.1
Title: Message Title
Yves Schumann created an issue
Jenkins / JENKINS-60150
"Each network interface requires either a subnet or a network interface ID" after update to 1.46.1
Issue Type:
Bug
Assignee:
FABRIZIO MANFREDI
Components:
ec2-plugin
Created:
2019-11-12 23:08
Priority:
Major
Reporter:
Yves Schumann
After upgrading our installation including update of ec2-plugin to 1.46.1, we're unable to spawn ec2 slaves anymore. After starting such a job, I got this on the log:
2019-11-12 23:00:24.420+ [id=45]WARNING hudson.plugins.ec2.EC2Cloud#provision: SlaveTemplate{ami='ami-0188fdd719eed', labels='docker'}. Exception during provisioning
com.amazonaws.services.ec2.model.AmazonEC2Exception: Each network interface requires either a subnet or a network interface ID. (Service: AmazonEC2; Status Code: 400; Error Code: InvalidParameterValue; Request ID: 459d425f-56ac-4acf-857d-06a289f7ca6a)
I'm not sure if this is an error on our setup or a bug, as this was working this way for more than a year now. The option Associate Public IP is activated as noted on several other issues like JENKINS-59564 but the problem here seems to be different.
[JIRA] (JENKINS-58578) Public IP can still be assigned when Associate Public IP is disabled, depending on subnet(s)
Title: Message Title Yves Schumann commented on JENKINS-58578 Re: Public IP can still be assigned when Associate Public IP is disabled, depending on subnet(s) Same here. Need to revert to 1.45 to bring my EC2 builds back to green. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200731.1563593184000.12127.1573509960252%40Atlassian.JIRA.
[JIRA] (JENKINS-45716) Unable to connect to Jenkins when Security is based on OAuth2
Title: Message Title Yves Schumann commented on JENKINS-45716 Re: Unable to connect to Jenkins when Security is based on OAuth2 Seems I spot the same issue. Any news regarding this or is the plugin dead? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183915.1500631342000.7958.1566481200917%40Atlassian.JIRA.
[JIRA] (JENKINS-42609) Plugin should expose overview of it's env vars on an overview page
Title: Message Title Yves Schumann commented on JENKINS-42609 Re: Plugin should expose overview of it's env vars on an overview page Thx a lot! Nice to see something happen here after more than two years... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179547.1489052534000.10158.1563171300169%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Yves Schumann commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Can one please post a screenshot how this looks now on traditional view and on BlueOcean? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175630.1477271041000.1974.1558089963699%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13140) Disconnected slaves come back online within a few minutes
Title: Message Title Yves Schumann commented on JENKINS-13140 Re: Disconnected slaves come back online within a few minutes Running into the same issue. I need to set dedicated slaves offline for certain reasons and the should not come back online until an admin performs the corresponding action. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-44449) Provide GIT_COMMIT_SHORT environment variable
Title: Message Title
Yves Schumann commented on JENKINS-9
Re: Provide GIT_COMMIT_SHORT environment variable
On a declarative Pipeline, the following workaround could be used:
pipeline {
...
environment {
GIT_COMMIT_SHORT = sh(
script: "printf \$(git rev-parse --short ${GIT_COMMIT})",
returnStdout: true
)
}
...
Usage of printf is necessary to prevent trailing newline on the end of generated short Git hash.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-52397) Org Scan blows up when repository has no tags
Title: Message Title Yves Schumann commented on JENKINS-52397 Re: Org Scan blows up when repository has no tags I'm spotting this regardless if there are tags or not, which breaks a lot of stuff right now. We're running Jenkins 2.152 and GitHub-Branch-Source-Plugin 2.4.1. Any ideas how to fix or a workaround? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-52935) Git LFS failing clone
Title: Message Title Yves Schumann commented on JENKINS-52935 Re: Git LFS failing clone Any news on this issue? I've stumbled into the same problem but cannot switch to https. The failing job is part of a GitHub orga scanner and other jobs require ssh as they perform git push to publish changes/releases. So how can I fix git lfs clones using ssh? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-50595) build history disappeared after upgrade to 2.107.1
Title: Message Title Yves Schumann edited a comment on JENKINS-50595 Re: build history disappeared after upgrade to 2.107.1 OK, I digged a little bit deeper into this. I setup the same automatic job creation we use on another Jenkins instance using bleeding edge Jenkins release. So I have a job, which creates other Jenkinsfile-based pipeline jobs using job dsl. The created jobs have one difference: Some of them have a periodic trigger of an hour, some of them have no such trigger. So the first portion of the created jobs run every hour and the other ones must be triggered real manually.Now the first interesting part: The periodic triggered jobs have no problem with disappearing history. All fine here. But the manually triggered jobs loose their history on the UI at least on the next day. Actually I did not figured out when exactly the history disappears from the UI. And the 2nd interesting part is, that the whole _problem disappears after I uninstalled the JobConfigHistoryPlugin_! Can anybody verify this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-50595) build history disappeared after upgrade to 2.107.1
Title: Message Title Yves Schumann commented on JENKINS-50595 Re: build history disappeared after upgrade to 2.107.1 OK, I digged a little bit deeper into this. I setup the same automatic job creation we use on another Jenkins instance using bleeding edge Jenkins release. So I have a job, which creates other Jenkinsfile-based pipeline jobs using job dsl. The created jobs have one difference: Some of them have a periodic trigger of an hour, some of them have no such trigger. So the first portion of the created jobs run every hour and the other ones must be triggered real manually. Now the first interesting part: The periodic triggered jobs have no problem with disappearing history. All fine here. But the manually triggered jobs loose their history on the UI at least on the next day. Actually I did not figured out when exactly the history disappears from the UI. And the 2nd interesting part is, that the whole problem disappears after I uninstalled the JobConfigHistoryPlugin! Can anybody verify this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-50595) build history disappeared after upgrade to 2.107.1
Title: Message Title Yves Schumann commented on JENKINS-50595 Re: build history disappeared after upgrade to 2.107.1 Any news here? This is actually a show stopper... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-50595) build history disappeared after upgrade to 2.107.1
Title: Message Title Yves Schumann edited a comment on JENKINS-50595 Re: build history disappeared after upgrade to 2.107.1 We have the same issue with Jenkins 2.121.3.The visible history of all jobs which are created using Job-DSL disappear after some time (next day). The folders already exist on the master and each build folder has an contains a build.xml. Jobs created using the OrgaScanner did not have this problem.Please let me know if and which further details required to fix this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-50595) build history disappeared after upgrade to 2.107.1
Title: Message Title Yves Schumann commented on JENKINS-50595 Re: build history disappeared after upgrade to 2.107.1 We have the same issue with Jenkins 2.121.3. The visible history of all jobs which are created using Job-DSL disappear after some time (next day). The folders already exist on the master and each build folder has an build.xml. Jobs created using the OrgaScanner did not have this problem. Please let me know if and which further details required to fix this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-34617) Make extended-choice-parameter-plugin pipeline compatibility easier
Title: Message Title Yves Schumann commented on JENKINS-34617 Re: Make extended-choice-parameter-plugin pipeline compatibility easier Any progress here? The plugin is very important as we use it to reference generated properties files to select build parameters! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-42609) Plugin should expose overview of it's env vars on an overview page
Title: Message Title Yves Schumann created an issue Jenkins / JENKINS-42609 Plugin should expose overview of it's env vars on an overview page Issue Type: Improvement Assignee: Mark Waite Components: git-plugin Created: 2017/Mar/09 9:42 AM Priority: Minor Reporter: Yves Schumann The generated list of environment variables on http:///env-vars.html/ should contain the list of available Git-Env-Vars too. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42609) Plugin should expose overview of it's env vars on an overview page
Title: Message Title Yves Schumann updated an issue Jenkins / JENKINS-42609 Plugin should expose overview of it's env vars on an overview page Change By: Yves Schumann The generated list of environment variables on http:///env-vars.html/ should contain the list of available Git-Env-Vars too , if Git-plugin is installed . Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-26583) Env-inject plugin suppress variables contributed by extension points
Title: Message Title Yves Schumann commented on JENKINS-26583 Re: Env-inject plugin suppress variables contributed by extension points Any news on this issue? When will it be fixed? We are currently blocked on updating NodeJS plugin from 0.2.2 to 1.1.0 because it will no longer work together with EnvInject plugin. So right now we are stuck on NodeJS plugin 0.2.2. 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-38998) Cannot trigger pipeline job
Title: Message Title Yves Schumann commented on JENKINS-38998 Re: Cannot trigger pipeline job Any news here? It's currently some kind of a show stopper as we could not migrate to pipeline jobs... 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] [packaging] (JENKINS-23273) RPM post-install should not do a "chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}"
Title: Message Title
Yves Schumann commented on JENKINS-23273
Re: RPM post-install should not do a "chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}"
The NoGo-behaviour is still existing and as there seems to be no solution, we still use the hard workaround: If the update is running, open another console, find the chown process and kill it the hard way using kill -9 . The chown makes absolutely no sense on boxes, where jenkins is the one and only account.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [packaging] (JENKINS-23273) RPM post-install should not do a "chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}"
Title: Message Title
Yves Schumann commented on JENKINS-23273
Re: RPM post-install should not do a "chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}"
Hm, seems I missed this option completely! Will try this asap, thx for the hint.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [ircbot-plugin] (JENKINS-14921) Status Code: 500 If multiple channels should be used
Title: Message Title Yves Schumann closed an issue as Cannot Reproduce Jenkins / JENKINS-14921 Status Code: 500 If multiple channels should be used Change By: Yves Schumann Status: Resolved Closed Assignee: kutzi Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [nodejs-plugin] (JENKINS-28198) IllegalArgumentException after saving main configuration
Title: Message Title Yves Schumann closed an issue as Duplicate Jenkins / JENKINS-28198 IllegalArgumentException after saving main configuration Change By: Yves Schumann Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ssh-slaves-plugin] (JENKINS-22651) Could not copy slave.jar into ... on slave
Title: Message Title Yves Schumann closed an issue as Not A Defect Jenkins / JENKINS-22651 Could not copy slave.jar into ... on slave Change By: Yves Schumann Status: Resolved Closed Assignee: Kohsuke Kawaguchi Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [slave-utilization] (JENKINS-29412) Jenkins install jdk6 in node host. slave.jar cannot be executed.
Title: Message Title Yves Schumann commented on JENKINS-29412 Re: Jenkins install jdk6 in node host. slave.jar cannot be executed. Any news or ideas to solve this? I've spot exactly the same problem with another major impact: There is no Java 7 available for the buildnodes I must use. So actually I can't build packages of our software for the desired systems as their build nodes can't be used by Jenkins. That's a big blocker right now. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [nodejs-plugin] (JENKINS-28198) IllegalArgumentException after saving main configuration
Title: Message Title
Yves Schumann created an issue
Jenkins / JENKINS-28198
IllegalArgumentException after saving main configuration
Issue Type:
Bug
Assignee:
Unassigned
Components:
nodejs-plugin
Created:
04/May/15 8:11 AM
Priority:
Blocker
Reporter:
Yves Schumann
After updating Jenkins to 1.611 I'm unable to configure NodeJS. If I hit the save button on Jenkins main configuratino page, I got an IllegalArgumentException. See the following stacktrace:
javax.servlet.ServletException: java.lang.IllegalArgumentException: Failed to instantiate class jenkins.plugins.nodejs.tools.NodeJSInstallation from {name:0.10.x,home:,properties:{stapler-class-bag:true,hudson-tools-InstallSourceProperty:{installers:{id:0.10.31,npmPackages:bower@1.3.9 grunt-cli@0.1.13 karma@0.12.16 karma-cli@0.0.4,npmPackagesRefreshHours:72,kind:hudson.plugins.nodejs.tools.NodeJSInstaller
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123)
at com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(LessCSS.java:46)
at
[JIRA] [nodejs-plugin] (JENKINS-28198) IllegalArgumentException after saving main configuration
Title: Message Title Yves Schumann updated an issue Jenkins / JENKINS-28198 IllegalArgumentException after saving main configuration Change By: Yves Schumann Attachment: Stacktrace.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-23273) RPM post-install should not do a chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}
Yves Schumann
commented on JENKINS-23273
RPM post-install should not do a chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}
What's the state on this issue? It is still a pain to update Jenkins on CentOS as the whole System is down for more than a hour now!
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-plugin] (JENKINS-22457) Git push will trigger a build even though no path matches included regions
Yves Schumann commented on JENKINS-22457 Git push will trigger a build even though no path matches included regions Struggling with the same problem but found the solution on IRC help: Did you tried it with a leading "^"? On my setup included regions foo/.* did not work but with ^foo/.* it works as expected! 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-23273) RPM post-install should not do a chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}
Yves Schumann
commented on JENKINS-23273
RPM post-install should not do a chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}
As requested by Olaf Lenz:
# time find /var/lib/jenkins -not -user jenkins
real50m15.587s
user0m6.984s
sys 0m55.076s
So this is a NoGo!
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-23273) RPM post-install should not do a chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}
Yves Schumann
commented on JENKINS-23273
RPM post-install should not do a chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}
Updating jenkins on our environment took more than a hour because of this behaviour! This is very frustrating because everytime I need to explain the long downtime...
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] [subversion] (JENKINS-23146) StringIndexOutOfBoundsException on subversion checkout
Yves Schumann commented on JENKINS-23146 StringIndexOutOfBoundsException on subversion checkout Roger that! Same situation here. :-/ 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] [ssh-slaves] (JENKINS-22651) Could not copy slave.jar into ... on slave
Yves Schumann commented on JENKINS-22651 Could not copy slave.jar into ... on slave You made my day! That was the input which leads to the right direction. Did not even know that there is such a difference in between ssh and scp. You're completely right, plain ssh works but scp not: jenkins@flieger:~$ scp -i .ssh/builder07 tmp/foobar.txt alpine_2_7_x86:~/ Couldn't open /dev/null: Permission denied lost connection jenkins@flieger:~$ After setting proper permissions on /dev/null, jenkins is able to connect to the node again. Thank you very much for the push into the right directions. Have to investigate now, why the permission on /dev/null was set wrong. But that's a different story... 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] [ssh-slaves] (JENKINS-22651) Could not copy slave.jar into ... on slave
Yves Schumann edited a comment on JENKINS-22651 Could not copy slave.jar into ... on slave You made my day! That was the input which leads to the right direction. Did not even know that there is such a difference in between ssh and scp. You're completely right, plain ssh works but scp not: jenkins@flieger:~$ scp -i .ssh/builder07 tmp/foobar.txt alpine_2_7_x86:~/ Couldn't open /dev/null: Permission denied lost connection jenkins@flieger:~$ After setting proper permissions on /dev/null, jenkins is able to connect to the node again. Thank you very much for the push into the right direction. Have to investigate now, why the permission on /dev/null was set wrong. But that's a different story... 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] [ssh-slaves] (JENKINS-22651) Could not copy slave.jar into ... on slave
Yves Schumann commented on JENKINS-22651 Could not copy slave.jar into ... on slave Because there is no java7 available for AlpineLinux 2.7 which is running on these nodes. AlpineLinux up to 2.x is based on uCLibc and openjdk7 did not compile on these system and the version 2.7 ist the current LTS release. The current development line and next release (3.x) has switched from uCLibc to musl-libc and for these systems java7 is available. But as I said, v2.7 is the current stable release and I need to build packages for this release. 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] [ssh-slaves] (JENKINS-22651) Could not copy slave.jar into ... on slave
Yves Schumann commented on JENKINS-22651 Could not copy slave.jar into ... on slave Connecting to these nodes using SSH works as expected. I'm using this every day for administration a.s.o. Used SSH version is OpenSSH_6.4p1-hpn14v1, OpenSSL 1.0.1h 5 Jun 2014 As I wrote on the initial text: If I put slave.jar from another machine on the node by hand, it get's deleted during the copy step. So the SSH connection itself must work, otherwise the slave.jar which I copied by hand won't get removed!? 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] [ssh-slaves] (JENKINS-22651) Could not copy slave.jar into ... on slave
Yves Schumann commented on JENKINS-22651 Could not copy slave.jar into ... on slave I gave all required information but nothing happens. Is there something on schedule to fix this? Got a bunch of buildnodes which just wasting power and that's not what they should do all the 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] [ssh-slaves] (JENKINS-22651) Could not copy slave.jar into ... on slave
Yves Schumann commented on JENKINS-22651 Could not copy slave.jar into ... on slave Any news here? Still struggling with 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] [ssh-slaves] (JENKINS-22651) Could not copy slave.jar into ... on slave
Yves Schumann commented on JENKINS-22651 Could not copy slave.jar into ... on slave Current setup: Jenkins master (x86-64): 1.565 with Oracle-JDK 1.7.0_60-b19 Node1 (x86): OpenJDK 1.7.0_55 Node2 (x86): OpenJDK 1.6.0_27 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] [ssh-slaves] (JENKINS-22651) Could not copy slave.jar into ... on slave
Yves Schumann commented on JENKINS-22651 Could not copy slave.jar into ... on slave I'm using version 1.6 of ssh-slaves plugin. 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] [master-slave] (JENKINS-22651) Could not copy slave.jar into ... on slave
Yves Schumann created JENKINS-22651 Could not copy slave.jar into ... on slave Issue Type: Bug Assignee: Unassigned Components: master-slave Created: 17/Apr/14 7:57 AM Description: Since one of the last updates I cannot connect a slave, which is running a different java version. Jenkins is version 1.558 with Oracle Java 1.7.0_51 and the slave is an x86 box using OpenJDK 1.6.0_27. It is impossible to switch to another Java version on the node. If I try to establish the connection, it fails with this output: [04/17/14 09:46:48] [SSH] Opening SSH connection to alpine_2_7_x86:22. [04/17/14 09:46:48] [SSH] Authentication successful. [04/17/14 09:46:48] [SSH] The remote users environment is: HOME='/home/jenkins' IFS=' ' LOGNAME='jenkins' MAIL='/var/mail/jenkins' OPTIND='1' PATH='/usr/bin:/bin:/usr/sbin:/sbin' PPID='429' PS1='\w \$ ' PS2=' ' PS4='+ ' PWD='/home/jenkins' SHELL='/bin/ash' SSH_CLIENT='10.42.23.23 51323 22' SSH_CONNECTION='10.42.23.23 51323 10.42.23.192 22' USER='jenkins' [04/17/14 09:46:48] [SSH] Checking java version of java [04/17/14 09:46:48] [SSH] java -version returned 1.6.0_27. [04/17/14 09:46:48] [SSH] Starting sftp client. [04/17/14 09:46:48] [SSH] SFTP failed. Copying via SCP. [04/17/14 09:46:48] [SSH] Copying latest slave.jar... hudson.util.IOException2: Could not copy slave.jar into '/home/jenkins/ci' on slave at hudson.plugins.sshslaves.SSHLauncher.copySlaveJarUsingSCP(SSHLauncher.java:1056) at hudson.plugins.sshslaves.SSHLauncher.copySlaveJar(SSHLauncher.java:1015) at hudson.plugins.sshslaves.SSHLauncher.access$300(SSHLauncher.java:126) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:656) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:642) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: java.io.IOException: Error during SCP transfer. at com.trilead.ssh2.SCPClient.put(SCPClient.java:523) at hudson.plugins.sshslaves.SSHLauncher.copySlaveJarUsingSCP(SSHLauncher.java:1054) ... 8 more Caused by: java.io.IOException: Remote scp terminated unexpectedly. at com.trilead.ssh2.SCPClient.readResponse(SCPClient.java:50) at com.trilead.ssh2.SCPClient.sendBytes(SCPClient.java:140) at com.trilead.ssh2.SCPClient.put(SCPClient.java:519) ... 9 more [04/17/14 09:46:48] [SSH] Connection closed. [04/17/14 09:46:48] Launch failed - cleaning up connection The connection itself is opened successfully and if I put slave.jar from another node onto this one, it get's deleted during the above steps. But then scp fails!? Any ideas? The connection to another node with the same OpenJDK version but x86_64 architecture works without any problems. Project: Jenkins Priority: Major Reporter: Yves Schumann 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] [cli] (JENKINS-11024) Some commands don't work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others
Yves Schumann commented on JENKINS-11024 Some commands dont work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others Im Using Jenkins-CLI to setup jobs based on an deactivated job template and modify the activation state of the created jobs in a second step. It seems that I run into this issue as the creation of new jobs works as expected but the activation fails: Calling jenkins api to create job 'eisfair__bcstorage' hudson.security.AccessDeniedException2: anonymous fehlt das Recht 'Job/Configure' at hudson.security.ACL.checkPermission(ACL.java:54) at hudson.model.AbstractItem.checkPermission(AbstractItem.java:446) ... Sad story as there are more than 500 jobs handled this way and it is absolutely annoying to do this by hand... 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] [cli] (JENKINS-11024) Some commands don't work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others
Yves Schumann edited a comment on JENKINS-11024 Some commands dont work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others Im Using Jenkins-CLI to setup jobs based on an deactivated job template and modify the activation state of the created jobs in a second step. It seems that I run into this issue as the creation of new jobs works as expected but the activation fails: Calling jenkins api to create job 'eisfair__bcstorage' hudson.security.AccessDeniedException2: anonymous fehlt das Recht 'Job/Configure' at hudson.security.ACL.checkPermission(ACL.java:54) at hudson.model.AbstractItem.checkPermission(AbstractItem.java:446) ... Why is there "anonymous" used? Username and password is the same as for job creation some milliseconds before!? Sad story as there are more than 500 jobs handled this way and it is absolutely annoying to do this by hand... 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-20858) Images missing from Jenkins UI
Yves Schumann commented on JENKINS-20858 Images missing from Jenkins UI We're facing the same problem with 1.557. Any news here? 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] [maven] (JENKINS-19415) Jobs whose parent has downstream triggering disabled should be excluded from maven-generated dependency graph
Yves Schumann assigned JENKINS-19415 to Yves Schumann Jobs whose parent has downstream triggering disabled should be excluded from maven-generated dependency graph Change By: Yves Schumann (05/Feb/14 12:28 PM) Assignee: YvesSchumann 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/groups/opt_out.
[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Yves Schumann commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 Any news on this? 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/groups/opt_out.
[JIRA] [crowd2] (JENKINS-20871) Unable to login with plugin v1.6
Yves Schumann created JENKINS-20871 Unable to login with plugin v1.6 Issue Type: Bug Affects Versions: current Assignee: Thorsten Heit Components: crowd2 Created: 04/Dec/13 3:30 PM Description: After updating to version 1.6 of crowd2 plugin, I'm unable to login into our jenkins instance. The log constantly writes something like this: Dez 04, 2013 4:05:59 PM de.theit.jenkins.crowd.CrowdSecurityRealm loadGroupByGroupname Information: Die Gruppe 'jenkins' wurde nicht gefunden oder ist nicht aktiv. Dez 04, 2013 4:06:02 PM de.theit.jenkins.crowd.CrowdSecurityRealm loadGroupByGroupname Information: Die Gruppe 'kristov' wurde nicht gefunden oder ist nicht aktiv. Dez 04, 2013 4:06:02 PM de.theit.jenkins.crowd.CrowdSecurityRealm loadGroupByGroupname Information: Die Gruppe 'starwarsfan' wurde nicht gefunden oder ist nicht aktiv. Seems that there is a mismatch between groups and users because the mentioned names are users but not a groups! Rollback to 1.5 solves the problem. Project: Jenkins Priority: Critical Reporter: Yves Schumann 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/groups/opt_out.
[JIRA] [crowd2] (JENKINS-20871) Unable to login with plugin v1.6
Yves Schumann commented on JENKINS-20871 Unable to login with plugin v1.6 Sure, but this could be tricky. The snippet above is the log, so I have no idea how to switch to an english version!? Any ideas? And where can I see the group separator? 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/groups/opt_out.
[JIRA] [core] (JENKINS-18641) People View does Not Populate (makeStaplerProxy)
Yves Schumann commented on JENKINS-18641 People View does Not Populate (makeStaplerProxy) Right, still existing on 1.524 running on Ubuntu 12.04 and accessed with Chrome, FF and IE 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/groups/opt_out.
[JIRA] [core] (JENKINS-18641) People View does Not Populate (makeStaplerProxy)
Yves Schumann edited a comment on JENKINS-18641 People View does Not Populate (makeStaplerProxy) Right, still existing on 1.524 running on Ubuntu 12.04 and accessed with Chrome, FF, Safari and IE 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/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-17366) ssh slave login via keyfile not working in 0.23
Yves Schumann commented on JENKINS-17366 ssh slave login via keyfile not working in 0.23 Same here. Interaction with credential plugin seems to be wrong/broken. Rollback to 0.22 solved the 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/groups/opt_out.
[JIRA] (JENKINS-9142) Add Build Step button broken in job configure page
Yves Schumann commented on JENKINS-9142 Add Build Step button broken in job configure page Any news on this topic? We're still unable to configure jobs with additional build 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
[JIRA] (JENKINS-9142) Add Build Step button broken in job configure page
Yves Schumann commented on JENKINS-9142 Add Build Step button broken in job configure page We run into this issue with Jenkins 1.493 so we are unable to add build steps at the moment! Tested with Chrome 23, FF 16.01 and IE 8. Any ideas? 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
[JIRA] (JENKINS-14921) Status Code: 500 If multiple channels should be used
Yves Schumann commented on JENKINS-14921 Status Code: 500 If multiple channels should be used Can't reproduce this issue anymore, so it could be closed. Everything works as expected. Thx for the cool plugin! 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
[JIRA] (JENKINS-14936) UserNameResolver extension never invoked
Yves Schumann commented on JENKINS-14936 UserNameResolver extension never invoked Any news or plans on this? Would be great if this could be solved... 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
[JIRA] (JENKINS-14063) Images are broken when not logged in
Yves Schumann commented on JENKINS-14063 Images are broken when not logged in Same here, also behind apache with httpd proxy using https:// access. 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
