[JIRA] (JENKINS-56617) Node-based security is ignored with pipelines
Title: Message Title Christian Gredig commented on JENKINS-56617 Re: Node-based security is ignored with pipelines Ah, now I see the entry for the security project! Thanks for the explanation and sorry for disregarding it in the first place. I am also looking forward to the admin UI enhancements. And yes, maybe the security hint might make the "bold red" list. 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-56617) Node-based security is ignored with pipelines
Title: Message Title Christian Gredig commented on JENKINS-56617 Re: Node-based security is ignored with pipelines Oleg Nenashev How could I have known this? Jesse Glick I read the reporting guidelines one is linked to when opening an issue, the vulnerability guidelines are not linked there (they should, propably). Also, this kind of actually is a security issue, isn't it? Even if it can be fixed by installing the plugin you mentioned - I can confirm it worked. Thanks for your answers though. My problem is solved, I just wonder how we can protect other users from running into the same problems. 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-56618) Build slaves do not start when requested by pipeline
Title: Message Title
Christian Gredig updated an issue
Jenkins / JENKINS-56618
Build slaves do not start when requested by pipeline
Change By:
Christian Gredig
Having a job of type pipeline with a code like this:{code:java}node("my-node") { sh 'ls -la' } {code}does not spin up a node "my-node" with a configuration of "start agent on request and go offline on inactivity". Wait time for starting is 0. Wait time for offline is 1.
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-56618) Build slaves do not start when requested by pipeline
Title: Message Title
Christian Gredig updated an issue
Jenkins / JENKINS-56618
Build slaves do not start when requested by pipeline
Change By:
Christian Gredig
Labels:
node pipeline slave
Having a job of type pipeline with a code like this:{code:java}node("my-node") { sh 'ls -la' } {code} does not spin up a node "my-node" with a configuration of "start agent on request and go offline on inactivity".
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-56618) Build slaves do not start when requested by pipeline
Title: Message Title
Christian Gredig created an issue
Jenkins / JENKINS-56618
Build slaves do not start when requested by pipeline
Issue Type:
Bug
Assignee:
Unassigned
Components:
core, pipeline
Created:
2019-03-19 12:01
Environment:
Jenkins ver. 2.164.1 LTS java version "1.8.0_131"
Priority:
Major
Reporter:
Christian Gredig
Having a job of type pipeline with a code like this:
node("my-node") { sh 'ls -la' }
Add Comment
[JIRA] (JENKINS-56617) Node-based security is ignored with pipelines
Title: Message Title
Christian Gredig created an issue
Jenkins / JENKINS-56617
Node-based security is ignored with pipelines
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2019-03-19 12:00
Environment:
Jenkins ver. 2.164.1 LTS java version "1.8.0_131"
Labels:
Security pipeline node slave
Priority:
Major
Reporter:
Christian Gredig
Node-based security is ignored in Pipelines. Restricting "build" on a node to specific users has no effect. Reproduction:
Create a node, let's say "test-node"
Use restrictions to end up with a user that has access to Jenkins and can create pipelines but does not have "build" permission on that node
Create a new job of type pipeline and add this code to it:
node('test-node') { sh 'ls -la ..' }
No matter which user will start this job, he will be allowed to do it and be able to read files on that node. I
[JIRA] (JENKINS-48094) image.push throws HTTP 404 response body: invalid character
Title: Message Title Christian Gredig commented on JENKINS-48094 Re: image.push throws HTTP 404 response body: invalid character This error appears when you connect to your registry on the wrong URL or port, for example when you try to connect to the UI (usually you will have a different port for the backend) or when you use a proxy / reverse proxy. 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.
