[JIRA] (JENKINS-33632) docker.inside broken
Title: Message Title
Pierre Beitz commented on JENKINS-33632
Re: docker.inside broken
Hello Jesse Glick, I think I found a self-contained example showing that the issue is still around. Using the following versions of Docker
Docker 1.12.2, build bb80604 (on linux).
Docker 1.12.3, build 6b644ec, experimental (on windows).
And using this gist, I ended up with the following error on my two machines:
$ docker run -t -d -u 1000:1000 -w /var/jenkins_home/jobs/demo/workspace -v /var/jenkins_home/jobs/demo/workspace:/var/jenkins_home/jobs/demo/workspace:rw -v /var/jenkins_home/jobs/demo/workspace@tmp:/var/jenkins_home/jobs/demo/workspace@tmp:rw -e -e -e -e -e -e -e -e -e -e -e -e -e -e --entrypoint cat ubuntu
[Pipeline] {
[Pipeline] sh
[workspace] Running shell script
sh: 1: cannot create /var/jenkins_home/jobs/demo/workspace@tmp/durable-252b7e97/pid: Directory nonexistent
sh: 1: cannot create /var/jenkins_home/jobs/demo/workspace@tmp/durable-252b7e97/jenkins-log.txt: Directory nonexistent
sh: 1: cannot create /var/jenkins_home/jobs/demo/workspace@tmp/durable-252b7e97/jenkins-result.txt: Directory nonexistent
Version of the Docker pipeline is 1.9.1 at the time of this writing. Steps to reproduce
Copy this gist
Set the executable permissions on the scripts.
Run the build script and then the run script.
The Jenkins instance will be available on port 8080. There is one job in it running the following:
node ('master') {
sh 'pwd'
img = docker.image('ubuntu')
img.inside {
sh 'pwd'
}
}
Do you think there is enough to reopen this issue? Thanks
Add Comment
[JIRA] (JENKINS-33632) docker.inside broken
Title: Message Title
Pierre Beitz edited a comment on JENKINS-33632
Re: docker.inside broken
Hello [~jglick],I think I found a self-contained example showing that the issue is still around. Using the following versions of Docker* Docker 1.12.2, build bb80604 (on linux).* Docker 1.12.3, build 6b644ec, experimental (on windows).And using [this gist|https://gist.github.com/PierreBtz/9bf58de96fdf5f0b0f272cba850f1161], I ended up with the following error on my two machines:{noformat}$ docker run -t -d -u 1000:1000 -w /var/jenkins_home/jobs/demo/workspace -v /var/jenkins_home/jobs/demo/workspace:/var/jenkins_home/jobs/demo/workspace:rw -v /var/jenkins_home/jobs/demo/workspace@tmp:/var/jenkins_home/jobs/demo/workspace@tmp:rw -e -e -e -e -e -e -e -e -e -e -e -e -e -e --entrypoint cat ubuntu[Pipeline] {[Pipeline] sh[workspace] Running shell scriptsh: 1: cannot create /var/jenkins_home/jobs/demo/workspace@tmp/durable-252b7e97/pid: Directory nonexistentsh: 1: cannot create /var/jenkins_home/jobs/demo/workspace@tmp/durable-252b7e97/jenkins-log.txt: Directory nonexistentsh: 1: cannot create /var/jenkins_home/jobs/demo/workspace@tmp/durable-252b7e97/jenkins-result.txt: Directory nonexistent{noformat}Version of the Docker pipeline is 1.9.1 at the time of this writing , but as you can see in the console dump, the -v flag is used instead of the --volume-from, as if the plugin did not detect it was running inside a container . *Steps to reproduce** Copy [this gist|https://gist.github.com/PierreBtz/9bf58de96fdf5f0b0f272cba850f1161]* Set the executable permissions on the scripts.* Run the build script and then the run script.* The Jenkins instance will be available on port 8080. There is one job in it running the following:{noformat}node ('master') {sh 'pwd'img = docker.image('ubuntu')img.inside {sh 'pwd'}}{noformat}Do you think there is enough to reopen this issue?Thanks
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-33632) docker.inside broken
Title: Message Title
Pierre Beitz commented on JENKINS-33632
Re: docker.inside broken
Thank you for your answer. I had a quick look to the code, and wrote a failing unit test (that you can also find in the gist):
@Test
public void test_cgroup_string_matching_bug() {
final String[] possibleCgroupStrings = new String[] {
"14:name=systemd:/docker/45686cf8ff804c6250e87c02f768f44c63f4d25987e904189ea9156af9f63a11",
"13:pids:/docker/45686cf8ff804c6250e87c02f768f44c63f4d25987e904189ea9156af9f63a11",
"12:hugetlb:/docker/45686cf8ff804c6250e87c02f768f44c63f4d25987e904189ea9156af9f63a11",
"11:net_prio:/docker/45686cf8ff804c6250e87c02f768f44c63f4d25987e904189ea9156af9f63a11",
"10:perf_event:/docker/45686cf8ff804c6250e87c02f768f44c63f4d25987e904189ea9156af9f63a11",
"9:net_cls:/docker/45686cf8ff804c6250e87c02f768f44c63f4d25987e904189ea9156af9f63a11",
"8:freezer:/docker/45686cf8ff804c6250e87c02f768f44c63f4d25987e904189ea9156af9f63a11",
"7:devices:/docker/45686cf8ff804c6250e87c02f768f44c63f4d25987e904189ea9156af9f63a11",
"6:memory:/docker/45686cf8ff804c6250e87c02f768f44c63f4d25987e904189ea9156af9f63a11",
"5:blkio:/docker/45686cf8ff804c6250e87c02f768f44c63f4d25987e904189ea9156af9f63a11",
"4:cpuacct:/docker/45686cf8ff804c6250e87c02f768f44c63f4d25987e904189ea9156af9f63a11",
"3:cpu:/docker/45686cf8ff804c6250e87c02f768f44c63f4d25987e904189ea9156af9f63a11",
"2:cpuset:/docker/45686cf8ff804c6250e87c02f768f44c63f4d25987e904189ea9156af9f63a11",
"1:name=openrc:/docker"
};
for (final String possibleCgroupString : possibleCgroupStrings) {
final Pattern pattern = Pattern.compile(DockerClient.CGROUP_MATCHER_PATTERN);
Matcher matcher = pattern.matcher(possibleCgroupString);
Assert.assertTrue(matcher.find());
Assert.assertEquals("45686cf8ff804c6250e87c02f768f44c63f4d25987e904189ea9156af9f63a11", matcher.group(1));
}
}
As you can see, the pattern is not matching one of the known cgroup formats. I have no idea how to proceed from there. Note that I extracted this pattern from a docker running on top of windows 10. I also have the problem on Linux Mint, I can extract the content of the /proc/self/cgroup on it too if it can help.
Add Comment
[JIRA] (JENKINS-33632) docker.inside broken
Title: Message Title Pierre Beitz commented on JENKINS-33632 Re: docker.inside broken Hello again, You are absolutely right and I went debugging again to find out...that the issue was on my side To give more context for people coming here, it is in fact the docker that was inside my jenkins docker image that was not correct. I installed it using apt-get install from the official jenkins image which was a mistake as I ended up with a docker client version 1.6.2 (communicating with a docker deamon on my host running a version 12...). The problem finally came from the fact the docker inspect output format was changed for volumes in docker 1.8 (I'm pretty sure this comes from this PR). As a consequence, the plugin did not find any volumes, falling back to a --volume mount. Installing the latest version of docker using curl -sSL https://get.docker.com/ | sh solved the issue. I guess this means the issue can be closed. If you are interested, I made a pull request to add an error in the logs saying : "The docker version is less than v1.8. Running a 'docker.inside' from inside a container will not work." 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-33632) docker.inside broken
Title: Message Title Pierre Beitz commented on JENKINS-33632 Re: docker.inside broken I had a look at the non working and working environment and came up with the following: working Client: Version: 1.12.3 API version: 1.24 Server: Version: 1.12.3 API version: 1.24 non working Client version: 1.6.2 Client API version: 1.18 Server version: 1.12.3 Server API version: 1.24 I guess the client version is the one the plugin should look at then. 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-54166) Date parameter is lost upon restart
Title: Message Title Pierre Beitz created an issue Jenkins / JENKINS-54166 Date parameter is lost upon restart Issue Type: Bug Assignee: Pierre Beitz Components: date-parameter-plugin Created: 2018-10-19 14:31 Priority: Major Reporter: Pierre Beitz Upon restart, the date parameter plugin is losing the date value. Reproduction Scenario 1. Create a job with a date parameter and use it (for instance in a shell script). 2. Put Jenkins in quiet mode 3. Trigger a build of the job 4. Restart 5. After restart, the job will fail with: ERROR: Build step failed with exception java.lang.IllegalArgumentException: Null value not allowed as an environment variable: DATE at hudson.EnvVars.put(EnvVars.java:356) at hudson.model.StringParameterValue.buildEnvironment(StringParameterValue.java:56) at me.leejay.jenkins.dateparameter.DateParameterValue.buildEnvironment(DateParameterValue.java:81) at hudson.model.ParametersAction.buildEnvVars(ParametersAction.java:89) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:947) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:90) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.Build$BuildExecution.build(Build.java:205) at hudson.model.Build$BuildExecution.doRun(Build.java:162) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) at hudson.model.Run.execute(Run.java:1744) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374)
[JIRA] (JENKINS-54166) Date parameter is lost upon restart
Title: Message Title Pierre Beitz started work on JENKINS-54166 Change By: Pierre Beitz Status: Open In Progress 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-54166) Date parameter is lost upon restart
Title: Message Title Pierre Beitz updated JENKINS-54166 Jenkins / JENKINS-54166 Date parameter is lost upon restart Change By: Pierre Beitz Status: In Progress Review 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-54166) Date parameter is lost upon restart
Title: Message Title Pierre Beitz updated JENKINS-54166 Jenkins / JENKINS-54166 Date parameter is lost upon restart Change By: Pierre Beitz Status: In Review Progress 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-54166) Date parameter is lost upon restart
Title: Message Title Pierre Beitz updated JENKINS-54166 Jenkins / JENKINS-54166 Date parameter is lost upon restart Change By: Pierre Beitz Status: In Progress Fixed but Unreleased Resolution: Fixed 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-10986) Symlinks in a shelved project are archived as directories on Unix platforms
Title: Message Title Pierre Beitz commented on JENKINS-10986 Re: Symlinks in a shelved project are archived as directories on Unix platforms Valentin Baranov This issue is fixed in the plugin. There is however an issue in Jenkins core with the tar function breaking symlinks: https://issues.jenkins-ci.org/browse/JENKINS-52781 I made a fix for this, and there is a PR waiting for review here: https://github.com/jenkinsci/jenkins/pull/3569 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-26432) Allow shelving of Pipeline
Title: Message Title Pierre Beitz updated an issue Jenkins / JENKINS-26432 Allow shelving of Pipeline Change By: Pierre Beitz Labels: 2.2-fixed pipeline 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-26432) Allow shelving of Pipeline
Title: Message Title Pierre Beitz updated JENKINS-26432 Released in version 2.2 Jenkins / JENKINS-26432 Allow shelving of Pipeline Change By: Pierre Beitz Status: In Review Resolved Resolution: Fixed 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-54889) Blue Ocean is throwing an exception in case a Flownode displayname is null
Title: Message Title
Pierre Beitz created an issue
Jenkins / JENKINS-54889
Blue Ocean is throwing an exception in case a Flownode displayname is null
Issue Type:
Bug
Assignee:
Olivier Lamy
Components:
blueocean-plugin
Created:
2018-11-27 14:43
Priority:
Major
Reporter:
Pierre Beitz
From a 2.138.x, install the blue ocean plugin and use a plugin allowing a null display name. Eg:
pipeline {
agent none
stages {
stage("Checkpoint") {
steps {
checkpoint null
}
}
}
}
Note: the null is valid here and was supported in earlier versions. Build will fail with a stack in the listener:
java.lang.NullPointerException
at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:187)
at com.google.common.cache.LocalCache.put(LocalCache.java:4180)
at io.jenkins.blueocean.events.PipelineEventListener.onNewHead(PipelineEventListener.java:74)
at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.notifyListeners(CpsFlowExecution.java:1437)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$3.run(CpsThreadGroup.java:417)
at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(CpsVmExecutorService.java:35)
at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:131)
at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
at java.util.concurrent.Executors$Runnab
[JIRA] (JENKINS-54890) A Pipeline should be able to recover from an exception thrown in a GraphListener
Title: Message Title Pierre Beitz created an issue Jenkins / JENKINS-54890 A Pipeline should be able to recover from an exception thrown in a GraphListener Issue Type: Improvement Assignee: Olivier Lamy Components: workflow-cps-plugin Created: 2018-11-27 14:47 Priority: Major Reporter: Pierre Beitz As seen in JENKINS-54889, in case an exception is thrown in a GraphListener, a Pipeline will not recover. We should avoid breaking the build in this case. Add Comment This message was sent by Atlassi
[JIRA] (JENKINS-54890) A Pipeline should be able to recover from an exception thrown in a GraphListener
Title: Message Title Pierre Beitz updated JENKINS-54890 Jenkins / JENKINS-54890 A Pipeline should be able to recover from an exception thrown in a GraphListener Change By: Pierre Beitz Status: In Progress Review 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-54889) Blue Ocean is throwing an exception in case a Flownode displayname is null
Title: Message Title Pierre Beitz updated JENKINS-54889 Jenkins / JENKINS-54889 Blue Ocean is throwing an exception in case a Flownode displayname is null Change By: Pierre Beitz Status: In Progress Review 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-54889) Blue Ocean is throwing an exception in case a Flownode displayname is null
Title: Message Title Pierre Beitz started work on JENKINS-54889 Change By: Pierre Beitz Status: Open In Progress 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-10544) "shelve project" button missing on some projects
Title: Message Title Pierre Beitz commented on JENKINS-10544 Re: "shelve project" button missing on some projects Deepak Puligundla were you able to reproduce the issue on a Freestyle job? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52781) tar function is breaking symlinks
Title: Message Title Pierre Beitz updated JENKINS-52781 Jenkins / JENKINS-52781 tar function is breaking symlinks Change By: Pierre Beitz Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52781) tar function is breaking symlinks
Title: Message Title Pierre Beitz started work on JENKINS-52781 Change By: Pierre Beitz Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-10544) "shelve project" button missing on some projects
Title: Message Title Pierre Beitz updated JENKINS-10544 Jenkins / JENKINS-10544 "shelve project" button missing on some projects Change By: Pierre Beitz Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-10544) "shelve project" button missing on some projects
Title: Message Title Pierre Beitz updated JENKINS-10544 Jenkins / JENKINS-10544 "shelve project" button missing on some projects Change By: Pierre Beitz Status: Reopened Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-10544) "shelve project" button missing on some projects
Title: Message Title Pierre Beitz commented on JENKINS-10544 Re: "shelve project" button missing on some projects Deepak Puligundla I'll close as not reproduced, please reopen if you have a test case. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-10544) "shelve project" button missing on some projects
Title: Message Title Pierre Beitz assigned an issue to Pierre Beitz Jenkins / JENKINS-10544 "shelve project" button missing on some projects Change By: Pierre Beitz Assignee: Manivannan Selvaraj Pierre Beitz Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53158) Pipelines leak OneOffExecutors when triggered on a temporary offline master
Title: Message Title
Pierre Beitz created an issue
Jenkins / JENKINS-53158
Pipelines leak OneOffExecutors when triggered on a temporary offline master
Issue Type:
Bug
Assignee:
Unassigned
Components:
core, pipeline
Created:
2018-08-21 11:12
Environment:
* Version: 2.121.3 * workflow-aggregator:2.5 * workflow-cps:2.54 'Pipeline: Groovy'
Priority:
Major
Reporter:
Pierre Beitz
When a Pipeline is triggered while the master node has been put temporarily offline, a OneOff (flyweight) executor is leaked. As I'm unsure whether the issue lies in core or in the pipelines at put both components. Environment
Version: 2.121.3
workflow-aggregator:2.5
workflow-cps:2.54 'Pipeline: Groovy'
Steps to reproduce
Create a simple Pipeline Job, eg:
node('master') {
sh 'echo hello'
}
Put the master node temporary offline
Trigger the Pipelin
[JIRA] (JENKINS-53158) Pipelines leak OneOffExecutors when triggered on a temporary offline master
Title: Message Title Pierre Beitz updated an issue Jenkins / JENKINS-53158 Pipelines leak OneOffExecutors when triggered on a temporary offline master Change By: Pierre Beitz Environment: * Version: 2.121.3* workflow-aggregator:2.5* workflow-cps:2.54 'Pipeline: Groovy' Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53158) Pipelines leak OneOffExecutors when triggered on a temporary offline master
Title: Message Title
Pierre Beitz updated an issue
Jenkins / JENKINS-53158
Pipelines leak OneOffExecutors when triggered on a temporary offline master
Change By:
Pierre Beitz
When a Pipeline is triggered while the master node has been put temporarily offline, a OneOff (flyweight) executor is leaked.As I'm unsure whether the issue lies in core or in the pipelines at put both components. *Environment* * Version: 2.121.3 * workflow-aggregator:2.5 * workflow-cps:2.54 'Pipeline: Groovy' *Steps to reproduce* * Create a simple Pipeline Job, eg:{code:java}node('master') {sh 'echo hello'}{code} * Put the master node temporary offline * Trigger the Pipeline build * Put the master node back online * Observe the leaked executor *Observations*This executor has the following characteristics:{code:java}Executor #-1(-1) Active? false Likely Stuck? false Interrupted? false Busy? false Owner? hudson.model.Hudson$MasterComputer@228777fd Current Work Unit? null Causes Of Interruption? [] Idle Start Milliseconds? 1534847122799 Progress: -1 Asynchronous Execution: null Executable: null executorOwner: hudson.model.Hudson$MasterComputer@228777fd tiedJobs: []{code}Jenkins logs show:{noformat}Executor #-1 for master grabbed hudson.model.queue.WorkUnit@4891a81f[work=hello] from queue but master went off-line before the task's worker thread started. No termination trace available.{noformat}Pipeline logs show nothing:{noformat}Démarré par l'utilisateur adminRunning in Durability level: MAX_SURVIVABILITY[Pipeline] nodeRunning on Jenkins in /Users/pierrebeitz/cbsupporthome/jenkins-home/workspace/hello[Pipeline] {[Pipeline] sh[hello] Running shell script+ echo hellohello[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineFinished: SUCCESS{noformat}*Workaround*A restart of Jenkins will cleanup the executors.
Add Comment
[JIRA] (JENKINS-29903) Permission issue on
Title: Message Title Pierre Beitz commented on JENKINS-29903 Re: Permission issue on Looks like a duplicate of JENKINS-10544. Fixes made for shelve plugin version 2.1 should solve this. Closing, please reopen if you have a test case on this version. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-29903) Permission issue on
Title: Message Title Pierre Beitz closed an issue as Fixed Jenkins / JENKINS-29903 Permission issue on Change By: Pierre Beitz Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-23983) "shelve project" does not work for inheritance projects
Title: Message Title Pierre Beitz updated an issue Jenkins / JENKINS-23983 "shelve project" does not work for inheritance projects Change By: Pierre Beitz Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-18043) Shelve project - shelved project list empty
Title: Message Title Pierre Beitz assigned an issue to Pierre Beitz Jenkins / JENKINS-18043 Shelve project - shelved project list empty Change By: Pierre Beitz Assignee: ashlux Pierre Beitz Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-18043) Shelve project - shelved project list empty
Title: Message Title Pierre Beitz commented on JENKINS-18043 Re: Shelve project - shelved project list empty This bug report is very old, it shows an error in parsing, the parser was changed since then so I'll close the issue, Jan Seidel please reopen if you reproduce on the latest version of the plugin. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-18043) Shelve project - shelved project list empty
Title: Message Title Pierre Beitz closed an issue as Cannot Reproduce Jenkins / JENKINS-18043 Shelve project - shelved project list empty Change By: Pierre Beitz Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-17272) Shelve project requires an executor on the master
Title: Message Title Pierre Beitz commented on JENKINS-17272 Re: Shelve project requires an executor on the master Manivannan Selvaraj the shelving will take place on the master, using a flyweight executor (ie not using a standard executor). Leo Sager: as the shelving/unshelving is using flyweight executors now, I'll close this issue. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-17272) Shelve project requires an executor on the master
Title: Message Title Pierre Beitz closed an issue as Not A Defect Jenkins / JENKINS-17272 Shelve project requires an executor on the master Change By: Pierre Beitz Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-7923) Shelving a project which own a shared "Workspace" will cause Hudson to fail until restarted
Title: Message Title Pierre Beitz assigned an issue to Pierre Beitz Jenkins / JENKINS-7923 Shelving a project which own a shared "Workspace" will cause Hudson to fail until restarted Change By: Pierre Beitz Assignee: ashlux Pierre Beitz Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-7923) Shelving a project which own a shared "Workspace" will cause Hudson to fail until restarted
Title: Message Title Pierre Beitz closed an issue as Cannot Reproduce Jenkins / JENKINS-7923 Shelving a project which own a shared "Workspace" will cause Hudson to fail until restarted Change By: Pierre Beitz Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-7923) Shelving a project which own a shared "Workspace" will cause Hudson to fail until restarted
Title: Message Title Pierre Beitz commented on JENKINS-7923 Re: Shelving a project which own a shared "Workspace" will cause Hudson to fail until restarted efe4pj: Given all the changes made since Hudson-1.379 and the shelve plugin 0.3, I'll close this issue, please reopen if you reproduce on the latest (2.1) version of the plugin. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-26432) Allow shelving of Pipeline
Title: Message Title Pierre Beitz updated an issue Jenkins / JENKINS-26432 Allow shelving of Pipeline Change By: Pierre Beitz Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-26432) Allow shelving of Pipeline
Title: Message Title Pierre Beitz started work on JENKINS-26432 Change By: Pierre Beitz Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53238) After unshelving a build, symlinks are broken
Title: Message Title Pierre Beitz created an issue Jenkins / JENKINS-53238 After unshelving a build, symlinks are broken Issue Type: Bug Assignee: Pierre Beitz Components: shelve-project-plugin Created: 2018-08-25 17:48 Environment: Any shelve plugin version Jenkins version >= 2.91 Priority: Critical Reporter: Pierre Beitz After unshelving a project, the builds start with a stack for each symlink that are created by Jenkins eg: ln builds/lastSuccessfulBuild jenkins-home/jobs/freestyle/lastSuccessful failed java.nio.file.DirectoryNotEmptyException: jenkins-home/jobs/freestyle/lastSuccessful at sun.nio.fs.UnixFileSystemProvider.implDelete(UnixFileSystemProvider.java:242) at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(AbstractFileSystemProvider.java:108) at java.nio.file.Files.deleteIfExists(Files.java:1165) at hudson.Util.createSymlink(Util.java:1351) at hudson.model.Run.createSymlink(Run.java:1937) at hudson.model.Run.updateSymlinks(Run.java:1918) at hudson.model.Run.execute(Run.java:1796) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Or ln builds/lastStableBuild jenkins-home/jobs/freestyle/lastStable failed java.nio.file.DirectoryNotEmpty
[JIRA] (JENKINS-53238) After unshelving a build, symlinks are broken
Title: Message Title Pierre Beitz resolved as Won't Fix Issue is in core (JENKINS-52781), this issue is a placeholder for the workaround one can use. Jenkins / JENKINS-53238 After unshelving a build, symlinks are broken Change By: Pierre Beitz Status: Open Resolved Resolution: Won't Fix 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-26432) Allow shelving of Pipeline
Title: Message Title Pierre Beitz updated JENKINS-26432 Jenkins / JENKINS-26432 Allow shelving of Pipeline Change By: Pierre Beitz Status: In Progress Review 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-55244) Shelved projects footprint increased by factor 10
Title: Message Title Pierre Beitz started work on JENKINS-55244 Change By: Pierre Beitz Status: Open In Progress 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-55244) Shelved projects footprint increased by factor 10
Title: Message Title Pierre Beitz updated JENKINS-55244 Jenkins / JENKINS-55244 Shelved projects footprint increased by factor 10 Change By: Pierre Beitz Status: In Progress Review 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-55244) Shelved projects footprint increased by factor 10
Title: Message Title Pierre Beitz commented on JENKINS-55244 Re: Shelved projects footprint increased by factor 10 Jens Brejner: I made a fix, PR is available as well as the hpi (https://ci.jenkins.io/job/Plugins/job/shelve-project-plugin/job/PR-16/1/artifact/target/shelve-project-plugin.hpi) if you are interested. Before finally merging this, I'll need to make some more tests (especially on Windows...). 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-56181) Shelve project plugin broken backward compatibility
Title: Message Title Pierre Beitz commented on JENKINS-56181 Re: Shelve project plugin broken backward compatibility Sergey Ryazantsev API wasn't documented as an API...thus the changes. That being said it's a good point that one could want to use the plugin programatically (I'm thinking bulk update for instance...). I'll make a fix making sure to add Javadoc so that it doesn't happen again... 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-55462) "shelve project" button missing for all non-admin users
Title: Message Title Pierre Beitz commented on JENKINS-55462 Re: "shelve project" button missing for all non-admin users Roger Wang Sorry for the delay. No issue, I didn't have time to work on the plugin lately... Fix is straightforward, I just need to make some time to test it properly. 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-56181) Shelve project plugin broken backward compatibility
Title: Message Title Pierre Beitz commented on JENKINS-56181 Re: Shelve project plugin broken backward compatibility Sergey Ryazantsev I'll try to come up with something when I have some time, feel free to propose a PR if it's not fast enough, only thing I'll required in the PR is that you add a (minimal) javadoc on the methods you set back to public. Regarding your last remark, the project is not following semantic versioning (version numbers are in fact not following the major, minor patch pattern). And I didn't anticipate the usage of undocumented methods in the code (probably my fault here). Both reasons explain the aggressive refactoring that lead to this situation...but thanks for the semantic page, it's always good to re-read it from time to time 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-55462) "shelve project" button missing for all non-admin users
Title: Message Title Pierre Beitz started work on JENKINS-55462 Change By: Pierre Beitz Status: Open In Progress 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-55462) "shelve project" button missing for all non-admin users
Title: Message Title Pierre Beitz updated JENKINS-55462 Jenkins / JENKINS-55462 "shelve project" button missing for all non-admin users Change By: Pierre Beitz Status: In Progress Review 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-56181) Shelve project plugin broken backward compatibility
Title: Message Title Pierre Beitz started work on JENKINS-56181 Change By: Pierre Beitz Status: Open In Progress 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-56181) Shelve project plugin broken backward compatibility
Title: Message Title Pierre Beitz updated JENKINS-56181 Jenkins / JENKINS-56181 Shelve project plugin broken backward compatibility Change By: Pierre Beitz Status: In Progress Review 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-52781) tar function is breaking symlinks
Title: Message Title Pierre Beitz commented on JENKINS-52781 Re: tar function is breaking symlinks Brian J Murrell Review is stalled, the changes are a bit touchy and would need to be reviewed/discussed with more people. PR is linked to the ticket: https://github.com/jenkinsci/jenkins/pull/3569 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-55244) Shelved projects footprint increased by factor 10
Title: Message Title Pierre Beitz updated JENKINS-55244 Jenkins / JENKINS-55244 Shelved projects footprint increased by factor 10 Change By: Pierre Beitz Status: In Review Fixed but Unreleased Resolution: Fixed 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-55244) Shelved projects footprint increased by factor 10
Title: Message Title Pierre Beitz updated JENKINS-55244 Jenkins / JENKINS-55244 Shelved projects footprint increased by factor 10 Change By: Pierre Beitz Status: Fixed but Unreleased Resolved 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-55244) Shelved projects footprint increased by factor 10
Title: Message Title Pierre Beitz updated an issue Jenkins / JENKINS-55244 Shelved projects footprint increased by factor 10 Change By: Pierre Beitz Labels: 2.3-fixed 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-20922) Progress bar links to nonexistant console
Title: Message Title Pierre Beitz updated an issue Jenkins / JENKINS-20922 Progress bar links to nonexistant console Change By: Pierre Beitz Labels: 2.3-fixed 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-20922) Progress bar links to nonexistant console
Title: Message Title Pierre Beitz updated JENKINS-20922 Jenkins / JENKINS-20922 Progress bar links to nonexistant console Change By: Pierre Beitz Status: Fixed but Unreleased Resolved 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-55331) Shelving fails if the optional Folder plugin is absent
Title: Message Title Pierre Beitz updated JENKINS-55331 Jenkins / JENKINS-55331 Shelving fails if the optional Folder plugin is absent Change By: Pierre Beitz Status: Fixed but Unreleased Resolved 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-55331) Shelving fails if the optional Folder plugin is absent
Title: Message Title Pierre Beitz updated an issue Jenkins / JENKINS-55331 Shelving fails if the optional Folder plugin is absent Change By: Pierre Beitz Labels: 2.3-fixed 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-56181) Shelve project plugin broken backward compatibility
Title: Message Title Pierre Beitz updated JENKINS-56181 Jenkins / JENKINS-56181 Shelve project plugin broken backward compatibility Change By: Pierre Beitz Status: In Review Resolved Resolution: Fixed 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-56181) Shelve project plugin broken backward compatibility
Title: Message Title Pierre Beitz updated an issue Jenkins / JENKINS-56181 Shelve project plugin broken backward compatibility Change By: Pierre Beitz Labels: 2.4-fixed 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-55462) "shelve project" button missing for all non-admin users
Title: Message Title Pierre Beitz updated JENKINS-55462 Jenkins / JENKINS-55462 "shelve project" button missing for all non-admin users Change By: Pierre Beitz Status: In Review Resolved Resolution: Fixed 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-55462) "shelve project" button missing for all non-admin users
Title: Message Title Pierre Beitz updated an issue Jenkins / JENKINS-55462 "shelve project" button missing for all non-admin users Change By: Pierre Beitz Labels: 2.4-fixed 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-61230) Disconnecting a JNLP agent from the UI displays an exception
Title: Message Title Pierre Beitz created an issue Jenkins / JENKINS-61230 Disconnecting a JNLP agent from the UI displays an exception Issue Type: Bug Assignee: Unassigned Attachments: Screenshot 2020-02-25 at 11.35.24.png Components: core Created: 2020-02-26 09:50 Environment: Jenkins 2.176.3 (also visible in the latest weekly 2.222 and visible for as far as I can remember). Priority: Trivial Reporter: Pierre Beitz Reproduction Case create a JNLP agent connect it hit disconnect from the UI Notice the message in the UI shows the stack: Upon reconnection, the stack disappears. Note: in the logs only the disconnection appears (stack suppressed) with an INFO level message.
[JIRA] (JENKINS-61173) Audit trail plugin stop working unexpectedly
Title: Message Title Pierre Beitz closed an issue as Cannot Reproduce Jenkins / JENKINS-61173 Audit trail plugin stop working unexpectedly Change By: Pierre Beitz Status: Open Closed Resolution: Cannot Reproduce 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.204713.1582259655000.6469.1586017140230%40Atlassian.JIRA.
[JIRA] (JENKINS-61878) Improve the queue/cancelItem endpoint API documentation
Title: Message Title Pierre Beitz created an issue Jenkins / JENKINS-61878 Improve the queue/cancelItem endpoint API documentation Issue Type: Bug Assignee: Pierre Beitz Components: core Created: 2020-04-13 08:20 Priority: Trivial Reporter: Pierre Beitz As a follow up of JENKINS-21311, as discussed with Daniel, rephrase the documentation of the queue/cancelItem endpoint API. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61878) Improve the queue/cancelItem endpoint API documentation
Title: Message Title Pierre Beitz commented on JENKINS-61878 Re: Improve the queue/cancelItem endpoint API documentation See https://github.com/jenkinsci/jenkins/pull/4395#discussion_r387323817 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.205746.1586766048000.9522.1586766120047%40Atlassian.JIRA.
[JIRA] (JENKINS-61878) Improve the queue/cancelItem endpoint API documentation
Title: Message Title Pierre Beitz started work on JENKINS-61878 Change By: Pierre Beitz Status: Open In Progress 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.205746.1586766048000.9523.1586766480145%40Atlassian.JIRA.
[JIRA] (JENKINS-61878) Improve the queue/cancelItem endpoint API documentation
Title: Message Title Pierre Beitz updated JENKINS-61878 Jenkins / JENKINS-61878 Improve the queue/cancelItem endpoint API documentation Change By: Pierre Beitz Status: In Progress Review 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.205746.1586766048000.9524.1586766480210%40Atlassian.JIRA.
[JIRA] (JENKINS-61878) Improve the queue/cancelItem endpoint API documentation
Title: Message Title Pierre Beitz assigned an issue to Pierre Beitz Jenkins / JENKINS-61878 Improve the queue/cancelItem endpoint API documentation Change By: Pierre Beitz Assignee: prakash raj Pierre Beitz 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.205746.1586766048000.9544.1586770500141%40Atlassian.JIRA.
[JIRA] (JENKINS-61878) Improve the queue/cancelItem endpoint API documentation
Title: Message Title Pierre Beitz commented on JENKINS-61878 Re: Improve the queue/cancelItem endpoint API documentation prakash raj not sure if you assigned to yourself by mistake, but I took back the task as there is already a PR fixing it. 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.205746.1586766048000.9546.1586770560143%40Atlassian.JIRA.
[JIRA] (JENKINS-61878) Improve the queue/cancelItem endpoint API documentation
Title: Message Title Pierre Beitz assigned an issue to Pierre Beitz Jenkins / JENKINS-61878 Improve the queue/cancelItem endpoint API documentation Change By: Pierre Beitz Assignee: prakash raj Pierre Beitz 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.205746.1586766048000.9573.1586771460123%40Atlassian.JIRA.
[JIRA] (JENKINS-40517) Allow changing delimiter in log output
Title: Message Title Pierre Beitz updated JENKINS-40517 Jenkins / JENKINS-40517 Allow changing delimiter in log output Change By: Pierre Beitz Status: Fixed but Unreleased Closed 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.177193.1481911536000.9694.1586783161022%40Atlassian.JIRA.
[JIRA] (JENKINS-11048) Broken link in help text of Audit Trail plugin configuration
Title: Message Title Pierre Beitz updated an issue Jenkins / JENKINS-11048 Broken link in help text of Audit Trail plugin configuration Change By: Pierre Beitz Labels: 3.4-fixed 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.141258.1316451512000.9687.1586783160743%40Atlassian.JIRA.
[JIRA] (JENKINS-40517) Allow changing delimiter in log output
Title: Message Title Pierre Beitz updated an issue Jenkins / JENKINS-40517 Allow changing delimiter in log output Change By: Pierre Beitz Labels: 3.4-fixed 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.177193.1481911536000.9692.1586783160971%40Atlassian.JIRA.
[JIRA] (JENKINS-11048) Broken link in help text of Audit Trail plugin configuration
Title: Message Title Pierre Beitz updated JENKINS-11048 Jenkins / JENKINS-11048 Broken link in help text of Audit Trail plugin configuration Change By: Pierre Beitz Status: Fixed but Unreleased Closed 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.141258.1316451512000.9690.1586783160881%40Atlassian.JIRA.
[JIRA] (JENKINS-27975) Audit trail should log query string as well
Title: Message Title Pierre Beitz updated JENKINS-27975 Jenkins / JENKINS-27975 Audit trail should log query string as well Change By: Pierre Beitz Status: Fixed but Unreleased Closed 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.162172.1429183811000.9698.1586783220279%40Atlassian.JIRA.
[JIRA] (JENKINS-27975) Audit trail should log query string as well
Title: Message Title Pierre Beitz updated an issue Jenkins / JENKINS-27975 Audit trail should log query string as well Change By: Pierre Beitz Labels: 3.4-fixed 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.162172.1429183811000.9696.1586783220252%40Atlassian.JIRA.
[JIRA] (JENKINS-61960) Migrate the shelve project documentation
Title: Message Title Pierre Beitz created an issue Jenkins / JENKINS-61960 Migrate the shelve project documentation Issue Type: Task Assignee: Pierre Beitz Components: shelve-project-plugin Created: 2020-04-18 12:00 Priority: Minor Reporter: Pierre Beitz 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 "Jenki
[JIRA] (JENKINS-61960) Migrate the shelve project documentation
Title: Message Title Pierre Beitz updated JENKINS-61960 Jenkins / JENKINS-61960 Migrate the shelve project documentation Change By: Pierre Beitz Status: In Progress Review 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.205844.1587211241000.13538.1587211800218%40Atlassian.JIRA.
[JIRA] (JENKINS-61960) Migrate the shelve project documentation
Title: Message Title Pierre Beitz started work on JENKINS-61960 Change By: Pierre Beitz Status: Open In Progress 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.205844.1587211241000.13537.1587211800170%40Atlassian.JIRA.
[JIRA] (JENKINS-61919) Audit trail plugin shows anonymous user logged out
Title: Message Title Pierre Beitz commented on JENKINS-61919 Re: Audit trail plugin shows anonymous user logged out Ankur Could you please share: a sample of the entry you see the pattern you use 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.205793.1586970989000.13540.1587212160133%40Atlassian.JIRA.
[JIRA] (JENKINS-12848) Log parameters used for a build
Title: Message Title Pierre Beitz updated JENKINS-12848 Jenkins / JENKINS-12848 Log parameters used for a build Change By: Pierre Beitz Status: In Review Fixed but Unreleased Resolution: Fixed 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.143306.1329845988000.13542.1587212640215%40Atlassian.JIRA.
[JIRA] (JENKINS-60336) Add support for logging to Elastic Search
Title: Message Title Pierre Beitz updated JENKINS-60336 Jenkins / JENKINS-60336 Add support for logging to Elastic Search Change By: Pierre Beitz Status: In Review Fixed but Unreleased Resolution: Fixed 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.203348.1575231787000.13599.1587228600310%40Atlassian.JIRA.
[JIRA] (JENKINS-12848) Log parameters used for a build
Title: Message Title Pierre Beitz updated an issue Jenkins / JENKINS-12848 Log parameters used for a build Change By: Pierre Beitz Labels: 3.5-fixed 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.143306.1329845988000.13607.1587229440249%40Atlassian.JIRA.
[JIRA] (JENKINS-60336) Add support for logging to Elastic Search
Title: Message Title Pierre Beitz updated an issue Jenkins / JENKINS-60336 Add support for logging to Elastic Search Change By: Pierre Beitz Labels: 3.5-fixed 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.203348.1575231787000.13605.1587229440207%40Atlassian.JIRA.
[JIRA] (JENKINS-60336) Add support for logging to Elastic Search
Title: Message Title Pierre Beitz closed an issue as Fixed Jenkins / JENKINS-60336 Add support for logging to Elastic Search Change By: Pierre Beitz Status: Resolved Closed 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.203348.1575231787000.13611.1587229620377%40Atlassian.JIRA.
[JIRA] (JENKINS-60336) Add support for logging to Elastic Search
Title: Message Title Pierre Beitz updated JENKINS-60336 Jenkins / JENKINS-60336 Add support for logging to Elastic Search Change By: Pierre Beitz Status: Fixed but Unreleased Resolved 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.203348.1575231787000.13609.1587229620349%40Atlassian.JIRA.
[JIRA] (JENKINS-12848) Log parameters used for a build
Title: Message Title Pierre Beitz updated JENKINS-12848 Jenkins / JENKINS-12848 Log parameters used for a build Change By: Pierre Beitz Status: Fixed but Unreleased Closed 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.143306.1329845988000.13613.1587229620402%40Atlassian.JIRA.
[JIRA] (JENKINS-61960) Migrate the shelve project documentation
Title: Message Title Pierre Beitz updated JENKINS-61960 Jenkins / JENKINS-61960 Migrate the shelve project documentation Change By: Pierre Beitz Status: In Review Fixed but Unreleased Resolution: Fixed 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.205844.1587211241000.17705.1587820620469%40Atlassian.JIRA.
[JIRA] (JENKINS-62054) Support action is displayed even if the user does not have the rights
Title: Message Title Pierre Beitz created an issue Jenkins / JENKINS-62054 Support action is displayed even if the user does not have the rights Issue Type: Bug Assignee: Pierre Beitz Components: support-core-plugin Created: 2020-04-25 18:34 Environment: Any version of the plugin Any core version Priority: Major Reporter: Pierre Beitz Browse a Jenkins instance without admin rights (noticed with anonymous on the community Jenkins), and observe that you can see the Support link on the left of a Job. You can click on it and see the bundle generation screen. This is only a display issue, you cannot do more as the rest is protected. The screen itself doesn't show information you are not allowed to see. Same is also visible for the Computers. Add Comment
[JIRA] (JENKINS-62054) Support action is displayed even if the user does not have the rights
Title: Message Title Pierre Beitz started work on JENKINS-62054 Change By: Pierre Beitz Status: Open In Progress 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.205951.158783968.17802.1587839700186%40Atlassian.JIRA.
[JIRA] (JENKINS-62054) Support action is displayed even if the user does not have the rights
Title: Message Title Pierre Beitz updated JENKINS-62054 Jenkins / JENKINS-62054 Support action is displayed even if the user does not have the rights Change By: Pierre Beitz Status: In Progress Review 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.205951.158783968.17803.1587839820092%40Atlassian.JIRA.
[JIRA] (JENKINS-62054) Support action is displayed even if the user does not have the rights
Title: Message Title Pierre Beitz commented on JENKINS-62054 Re: Support action is displayed even if the user does not have the rights Arnaud Héritier here is the link where I detected this: https://ci.jenkins.io/job/Plugins/job/shelve-project-plugin/job/master/29/support/ I must admit I don't know how the management of permissions for an action in Jelly works. I have the same pattern in the shelve project plugin and I drive this with the java code (like I did in the PR for this task). 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.205951.158783968.17961.1587915540179%40Atlassian.JIRA.
[JIRA] (JENKINS-62083) The plugin does not use the standard release process
Title: Message Title Pierre Beitz created an issue Jenkins / JENKINS-62083 The plugin does not use the standard release process Issue Type: Bug Assignee: Assaf hefetz Components: snyk-security-plugin Created: 2020-04-28 15:57 Environment: Any version of the plugin in version 2.x Priority: Major Reporter: Pierre Beitz It appears that the snyk-security plugin does not follow the standard release process (as explained in https://www.jenkins.io/doc/developer/publishing/releasing/. As a consequence, the pom.xml inside the artifact is not properly formed. Especially the version field is not properly populated. See for instance the latest release 2.10.4 pom: https://github.com/jenkinsci/snyk-security-scanner-plugin/blob/a42a97bc8d2f47738bc4695d6b5934e4d131ae8f/pom.xml#L12. This does not seem to impact the Open Source Update Center, but it impacts other Update Centers. Would you mind reviewing the release process? Add Comment
[JIRA] (JENKINS-61919) Audit trail plugin shows anonymous user logged out
Title: Message Title Pierre Beitz commented on JENKINS-61919 Re: Audit trail plugin shows anonymous user logged out Ankur are you sure those logs are coming from the audit trail plugin? I would expect the plugin to log an url (path), I don't think "logged out" is an output coming from the audit trail plugin. Do you have evidence showing that those are logs coming from the Audit Trail plugin? Splunk is not natively supported by the plugin, could you please check the logs generated by the Audit Trail plugin and look for "logged out"? Maybe there is a transformation at Splunk level? Other hypothesis I have is that you are in fact looking at logs generated by Jenkins itself, namely this one: https://github.com/jenkinsci/jenkins/blob/fdb6faed00ef73c98e2f69c133d8c9a87a0ca9b0/core/src/main/java/jenkins/security/SecurityListener.java#L143 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.205793.1586970989000.20551.1588435740186%40Atlassian.JIRA.
[JIRA] (JENKINS-27734) Allow shelving of folder
Title: Message Title Pierre Beitz updated an issue Jenkins / JENKINS-27734 Allow shelving of folder Change By: Pierre Beitz Labels: 3.0-fixed 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.161724.1428050779000.20560.1588437060713%40Atlassian.JIRA.
