[JIRA] (JENKINS-49437) Impossible to specify user/uid to use inside container
Title: Message Title
Vi Pl edited a comment on JENKINS-49437
Re: Impossible to specify user/uid to use inside container
Seeing something similar:This: {code:java}docker.image(image).inside('-u 0:0') { sh "..."}{code}Results in:{code:java}[Pipeline] withDockerContainerJenkins seems to be running inside container e50594031f5a4017ed56c0842e4b546c8e1559caaf5c68549aeb541da3d70142$ docker run -t -d -u 1000:1000 -u 0:0 -w /var/jenkins_home/jobs/test/workspace --volumes-from e50594031f5a4017ed56c0842e4b546c8e1559caaf5c68549aeb541da3d70142 -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e image:0.1{code} I do not expect {{-u 1000:1000 -u 0:0}} ... - It full files my needs, but it seems wrong- The job will fail when writing inside /var/jenkins_home/jobs/test/workspace...
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.188322.1518018738000.755.1562148240120%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49437) Impossible to specify user/uid to use inside container
Title: Message Title
Vi Pl edited a comment on JENKINS-49437
Re: Impossible to specify user/uid to use inside container
Seeing something similar:This: {code:java}docker.image(image).inside('-u 0:0') { sh "..."}{code}Results in:{code:java}[Pipeline] withDockerContainerJenkins seems to be running inside container e50594031f5a4017ed56c0842e4b546c8e1559caaf5c68549aeb541da3d70142$ docker run -t -d -u 1000:1000 -u 0:0 -w /var/jenkins_home/jobs/test/workspace --volumes-from e50594031f5a4017ed56c0842e4b546c8e1559caaf5c68549aeb541da3d70142 -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e image:0.1{code} I do not expect {{-u 1000:1000 -u 0:0}} ... - It full files my needs, but it seems wrong - The job will fail when writing inside /var/jenkins_home/jobs/test/workspace...
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.188322.1518018738000.752.1562148180142%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49437) Impossible to specify user/uid to use inside container
Title: Message Title
Vi Pl commented on JENKINS-49437
Re: Impossible to specify user/uid to use inside container
Seeing something similar: This:
docker.image(image).inside('-u 0:0') {
sh "..."
}
Results in:
[Pipeline] withDockerContainer
Jenkins seems to be running inside container e50594031f5a4017ed56c0842e4b546c8e1559caaf5c68549aeb541da3d70142
$ docker run -t -d -u 1000:1000 -u 0:0 -w /var/jenkins_home/jobs/test/workspace --volumes-from e50594031f5a4017ed56c0842e4b546c8e1559caaf5c68549aeb541da3d70142 -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e image:0.1
I do not expect -u 1000:1000 -u 0:0 ... It full files my needs, but it seems wrong
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.188322.1518018738000.740.1562147400192%40Atlassian.JIRA.
For more options, visit https://g
[JIRA] (JENKINS-57580) Add support for JCasC xldeploy-plugin / deployitNotifier
Title: Message Title Vi Pl created an issue Jenkins / JENKINS-57580 Add support for JCasC xldeploy-plugin / deployitNotifier Issue Type: New Feature Assignee: Ewelina Wilkosz Components: configuration-as-code-plugin Created: 2019-05-21 11:08 Environment: Jenkins LTS 2.150.3 JCasC 1.15 Priority: Minor Reporter: Vi Pl Please add support for configuration-as-code for the xldeploy-plugin plugin. Currently, the following: unclassified: deployitNotifier: deployitServerUrl: "http://server:4516" gives: io.jenkins.plugins.casc.ConfiguratorException: Invalid configuration elements for type class com.xebialabs.deployit.ci.DeployitNotifier$DeployitDescriptor : deployitServerUrl. Available attributes : at io.jenkins.plugins.casc.BaseConfigurator.handleUnknown(BaseConfigurator.java:372) at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:361) at io.jenkins.plugins.casc.BaseConfigurator.check(BaseConfigurator.java:282) at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:347) at io.jenkins.plugins.casc.BaseConfigurator.check(BaseConfigurator.java:282) at io.jenkins.plugins.casc.ConfigurationAsCode.lambda$checkWith$6(ConfigurationAsCode.java:665) at io.jenkins.plugins.casc.ConfigurationAsCode.invokeWith(ConfigurationAsCode.java:627) Caused: io.
[JIRA] (JENKINS-57121) list view jobnames is missing getter and setter for jcasc compliance
Title: Message Title Vi Pl updated an issue Jenkins / JENKINS-57121 list view jobnames is missing getter and setter for jcasc compliance Change By: Vi Pl Attachment: image-2019-05-10-14-19-39-495.png 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.198871.1555696084000.23427.1557490800297%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57121) list view jobnames is missing getter and setter for jcasc compliance
Title: Message Title Vi Pl commented on JENKINS-57121 Re: list view jobnames is missing getter and setter for jcasc compliance @Joseph Petersen Are you sure this is a problem? I managed to create a new list view with: jenkins: primaryView: all: name: "all" views: - all: name: "all" - list: columns: - "status" - "weather" - "jobName" - "lastSuccess" - "lastFailure" - "lastDuration" - "buildButton" includeRegex: ".*" name: "test_view" Jenkins version: 2.150.3 configuration-as-code-plugin: version: 1.14 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.198871.1555696084000.23429.1557490860107%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
