[JIRA] (JENKINS-43964) Two Build URLs appearing in JIRA comment
Title: Message Title SCM/JIRA link daemon commented on JENKINS-43964 Re: Two Build URLs appearing in JIRA comment Code changed in jenkins User: Wisen Tanasa Path: src/integrationTest/groovy/com/ceilfors/jenkins/plugins/jiratrigger/JiraTriggerAcceptanceTest.groovy src/main/groovy/com/ceilfors/jenkins/plugins/jiratrigger/JiraCommentReplier.groovy http://jenkins-ci.org/commit/jira-trigger-plugin/fed5539f3ba069c7096f1e82ff51252f2b3e427c Log: JENKINS-43964 Remove square brackets from Jenkins comment replier. The square brackets generated interfere with JIRA wiki syntax which causes multiple job URLs to be combined to one link. Before: Build is scheduled for: http://jenkins.url, http://jenkins.url After: Build is scheduled for: http://jenkins.url, http://jenkins.url 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-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title Christopher Unkel commented on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error Yup–that's it. Other discussion aside, I like the fix in PR313. It's a bit ugly to have to execute 'cp', but I think it will solve the problem completely and do so with a fix local to the git client. As far as the stack overflow article, I'm not sure either, but I have at least two theories: There's more than one JVM in the world: maybe openjdk doesn't set FD_CLOEXEC but other JVMs do. Even with FD_CLOEXEC there's still a short race window between fork() in the parent and the exec() in the child. On Linux this can be solved by using vfork() instead of fork(), but the POSIX semantics don't guarantee such. 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-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title Christopher Unkel commented on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error Mark Waite: this bug cannot be understood by thinking about the behavior of one git client thread in isolation. The straight-line code in the git client is correct and it does always close the unique temporary file before the call to command-line git. The problem is that there are other threads in the JVM and they may also run commands and make subprocesses. The mechanics of making subprocesses creates duplicates of open files. It is one of the duplicates that is open, not the version opened by the git client code. To be more explicit, imagine that I have two build jobs running: job 1 needs to do a git checkout, and job 2 needs to run make. Say that Jenkins is running as process ID 1000, thread 1 is running the git checkout, and thread 2 is running the make. Here's a thread/process execution interleaving in which the bug manifests: Process 1000, thread 1: open ssh123456.sh for writing, file descriptor 4 Process 1000, thread 2: fork in preparation to run make, creating process 1001. Inherits file descriptor 4 open for writing to ssh123456.sh. Process 1001: exec() make. Process 1000, thread 1: write contents of ssh123456.sh. Process 1000, thread 1: close ssh123456.sh. Process 1000 no longer has ssh123456.sh open for writing. However, this does not close file descriptor 4 in process 1001 (running make), hence ssh123456.sh is still open somewhere on the system for writing. Process 1000, thread 1: fork() in preparation to run git, creating process 1002. Process 1002: exec() git. Process 1002: fork in preparation to run SSH_AGENT script, creating process 1003. Process 1003: exec() ssh123456.sh --> ETXTBSY. ssh123456.sh is open for writing as file descriptor 4 in process 1001 (make). So the script file is not open in the Jenkins process, but nonetheless it is open somewhere on the system, hence ETXTBSY. And the fact that some other totally unrelated code can make a copy of the file descriptor and mess things up is why it's a Java runtime bug. A combination of vfork() and the close-on-exec flag would ensure that the file descriptor 4 in process 1001 in step 3, thus closing the copy. That's what's being contemplated as the fix in the JVM. One workaround is what's in PR313: copy the script using cp, which doesn't create children, so can't have stranded an open file descriptor to its destination. Another is what I proposed, which is to use a lock to ensure that steps 2 and 3 above cannot happen between steps 1 and 5.
[JIRA] (JENKINS-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title Mark Waite edited a comment on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error [~dscunkel] each invocation of command line git which needs a credentials file is allocated a unique temporary file by a call to Files.createTempFile(). The process which will consume that unique temporary file is not forked until after the JVM has been told to close the unique temporary file. I'm sure I must be missing something, but the sequence of calls tries very, very hard to assure that the unique temporary file is closed before the call to command line git.I think you're suggesting that the fork of a potentially unrelated process is holding file descriptors open which were opened by the git client plugin. If that's the case, then it will need someone with much better threading skills than mine to propose a change to the Jenkins core which does not damage process fork performance and still resolves this case. A [stackoverflow article|https://stackoverflow.com/questions/8997643/launch-a-child-process-from-java-that-doesnt-inherit-files-ports-on-unix] claims that Java on Unix sets the FD_CLOEXEC flag when it execs a process. I still don't have an explanation of the problem, just observations that seem to contradict the rational reasons this problem happens. 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
[JIRA] (JENKINS-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title Mark Waite edited a comment on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error [~dscunkel] each invocation of command line git which needs a credentials file is allocated a unique temporary file by a call to Files.createTempFile(). The process which will consume that unique temporary file is not forked until after the JVM has been told to close the unique temporary file. I'm sure I must be missing something, but the sequence of calls tries very, very hard to assure that the unique temporary file is closed before the call to command line git. I think you're suggesting that the fork of a potentially unrelated process is holding file descriptors open which were opened by the git client plugin. If that's the case, then it will need someone with much better threading skills than mine to propose a change to the Jenkins core which does not damage process fork performance and still resolves this case. 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-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title Mark Waite commented on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error Christopher Unkel each invocation of command line git which needs a credentials file is allocated a unique temporary file by a call to Files.createTempFile(). The process which will consume that unique temporary file is not forked until after the JVM has been told to close the unique temporary file. I'm sure I must be missing something, but the sequence of calls tries very, very hard to assure that the unique temporary file is closed before the call to command line git. 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-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title Christopher Unkel commented on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error Mark Waite: "thread 2" in the above could be any other thread in the Java virtual machine. From a Java language point of view, the PrintWriter object and the underlying FileOutputStream would seem to be local to the thread that is executing createUnixGitSSH() and subsequently asks for the git CLI process to be launched. However, on a Unix JVM implementation, underlying the FileOutputStream is an open file descriptor to the script. File descriptors always have process scope. They are not thread local. So when I see the bug I'm guessing that thread 2 is a different thread launching a shell build step from some unrelated job. On Unix Runtime.exec() is implemented with a fork(), producing a child process, followed by an exec() in the child process. The child process inherits all open file descriptors. If badly timed, this includes the open file descriptor for the SSH script, and that's how the script file is still open: it's open in a child process totally unrelated to what the git client plugin code is doing. By the time the git client code runs git, the script is closed in the Jenkins process itself. 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-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title Mark Waite commented on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error Christopher Unkel as far as I understand the git client plugin code, the temporary file is opened, written, and closed in the same thread that runs the command line git process. As far as I can tell, there is only a single thread which creates the script and then runs command line git in a subprocess. I can't explain why the temporary file is occasionally still open when the script is executed by command line git. 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-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title Christopher Unkel commented on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error Mark Waite: as I understand the issue as described in JDK-8068370, the issue isn't that the file descriptor for the fix isn't closed, but rather that the open file descriptor is inherited into a child process forked by another thread, so there's a race between writing the GIT_SSH file contents and launching processes: In thread 1: open GIT_SSH script file for writing. In thread 2: fork process; child inherits open file descriptor of GIT_SSH file. In thread 1: close GIT_SSH file. In thread 1: fork thread to run git. GIT_SSH file is still open in previous child, so ETXTBSY results. So if a lock can preclude step 2 from happening between step 1 and step 3, the race would be fixed That said, PR313 has a more local fix and would seem preferable if it works. I see this issue, but only intermittently, so it will probably take a month of testing to be confident the PR is a solution. 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
[JIRA] (JENKINS-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title Mark Waite commented on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error Christopher Unkel the git client plugin already asks the Java libraries to close the script before the process which will reference it is forked. Unfortunately, a bug in the Java libraries causes that request to close the file to sometimes be ignored. Refer to the earlier comment from Tomasz Śniatowski for more details. Refer to PR313 for the work-around as a pull request. Since I have never seen the problem, I can't reliably test that the patch fixes the problem. If you've seen the problerm, please download the pull request build, test it, and report your results on that pull request. 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-45230) Jenkins does not allow to install plugins
Title: Message Title olamy assigned an issue to Unassigned Jenkins / JENKINS-45230 Jenkins does not allow to install plugins Change By: olamy Assignee: olamy 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-15295) Maven Projects dont resolve dependencies correctly
Title: Message Title olamy assigned an issue to Unassigned Jenkins / JENKINS-15295 Maven Projects dont resolve dependencies correctly Change By: olamy Assignee: olamy 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-8711) Post build action deploy to maven repository does not honor the "private maven repository" setting
Title: Message Title olamy assigned an issue to Unassigned Jenkins / JENKINS-8711 Post build action deploy to maven repository does not honor the "private maven repository" setting Change By: olamy Assignee: olamy 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-14558) Not able to include and deploy a user defined/ external jar file.
Title: Message Title olamy assigned an issue to Unassigned Jenkins / JENKINS-14558 Not able to include and deploy a user defined/ external jar file. Change By: olamy Assignee: olamy 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-10700) Maven3 builder is swallowing exceptions in reporters
Title: Message Title olamy assigned an issue to Unassigned Jenkins / JENKINS-10700 Maven3 builder is swallowing exceptions in reporters Change By: olamy Assignee: olamy 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-11784) Build numbers not getting into manifest file
Title: Message Title olamy assigned an issue to Unassigned Jenkins / JENKINS-11784 Build numbers not getting into manifest file Change By: olamy Assignee: olamy 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-3122) auto build of downstream projects doesn't workfor m2 jobs in unstable state, when using surefire flag testFailureIgnore
Title: Message Title olamy assigned an issue to Unassigned Jenkins / JENKINS-3122 auto build of downstream projects doesn't workfor m2 jobs in unstable state, when using surefire flag testFailureIgnore Change By: olamy Assignee: olamy 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-7036) Modules of a Maven multimodule-build are not marked as FAILED/FAILURE in Hudson when dependencies cannot be resolved
Title: Message Title olamy assigned an issue to Unassigned Jenkins / JENKINS-7036 Modules of a Maven multimodule-build are not marked as FAILED/FAILURE in Hudson when dependencies cannot be resolved Change By: olamy Assignee: olamy 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-49034) pushToCloudFoundry does not clean up appDir* directories
Title: Message Title olamy assigned an issue to Unassigned Jenkins / JENKINS-49034 pushToCloudFoundry does not clean up appDir* directories Change By: olamy Assignee: olamy 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-21888) Upstream dependencies are incorrectly determined
Title: Message Title olamy assigned an issue to Unassigned Jenkins / JENKINS-21888 Upstream dependencies are incorrectly determined Change By: olamy Assignee: olamy 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-13962) Add exclusion list for which dependencies will trigger a build
Title: Message Title olamy assigned an issue to Unassigned Jenkins / JENKINS-13962 Add exclusion list for which dependencies will trigger a build Change By: olamy Assignee: olamy 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-50337) BlueOcean does not show steps after a parallel step inside a script block
Title: Message Title Denys Digtiar commented on JENKINS-50337 Re: BlueOcean does not show steps after a parallel step inside a script block Hi Moritz Baumann. I believe this is a duplicate of the JENKINS-35836 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-19871) Maven jobs see every env variable as java properties
Title: Message Title olamy assigned an issue to Unassigned Jenkins / JENKINS-19871 Maven jobs see every env variable as java properties Change By: olamy Assignee: olamy 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-31729) maven-dependency-update-trigger-plugin should be able to trigger for non-snapshot builds also
Title: Message Title olamy assigned an issue to Unassigned Jenkins / JENKINS-31729 maven-dependency-update-trigger-plugin should be able to trigger for non-snapshot builds also Change By: olamy Assignee: olamy 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-49257) Cloud Foundry Plugin error on a distributed system
Title: Message Title olamy assigned an issue to Unassigned Jenkins / JENKINS-49257 Cloud Foundry Plugin error on a distributed system Change By: olamy Assignee: olamy 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-26833) Downstream maven project not triggered on the right SCM branch
Title: Message Title olamy assigned an issue to Unassigned Jenkins / JENKINS-26833 Downstream maven project not triggered on the right SCM branch Change By: olamy Assignee: olamy 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-28373) apache maven 3.3.3 cannot be invoked anymore on windows
Title: Message Title olamy assigned an issue to Unassigned Jenkins / JENKINS-28373 apache maven 3.3.3 cannot be invoked anymore on windows Change By: olamy Assignee: olamy 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-19338) Cannot archive artifacts using Maven 3.1.0 on Windows slave
Title: Message Title olamy assigned an issue to Unassigned Jenkins / JENKINS-19338 Cannot archive artifacts using Maven 3.1.0 on Windows slave Change By: olamy Assignee: olamy 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-8396) POM validation errors are less detailled in Hudson than in M3
Title: Message Title olamy assigned an issue to Unassigned Jenkins / JENKINS-8396 POM validation errors are less detailled in Hudson than in M3 Change By: olamy Assignee: olamy 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-12259) NullPointerException in maven-plugin: Maven3Builder / ExecutedMojo (1.445)
Title: Message Title olamy assigned an issue to Unassigned Jenkins / JENKINS-12259 NullPointerException in maven-plugin: Maven3Builder / ExecutedMojo (1.445) Change By: olamy Assignee: olamy 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-12752) Checkbox 'Check Snapshot Plugins Update' does not remain checked after saving config changes.
Title: Message Title olamy assigned an issue to Unassigned Jenkins / JENKINS-12752 Checkbox 'Check Snapshot Plugins Update' does not remain checked after saving config changes. Change By: olamy Assignee: olamy 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-9068) Check non snapshot artifacts
Title: Message Title olamy assigned an issue to Unassigned Jenkins / JENKINS-9068 Check non snapshot artifacts Change By: olamy Assignee: olamy 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-9581) FATAL: null java.lang.NullPointerException if parent Project build is not hold until build start
Title: Message Title olamy assigned an issue to Unassigned Jenkins / JENKINS-9581 FATAL: null java.lang.NullPointerException if parent Project build is not hold until build start Change By: olamy Assignee: olamy 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-12196) [Publish JUnit test result report] not available for a Maven 2/3 job type
Title: Message Title olamy assigned an issue to Unassigned Jenkins / JENKINS-12196 [Publish JUnit test result report] not available for a Maven 2/3 job type Change By: olamy Assignee: olamy 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-10840) Maven "module" shows as running after build is aborted.
Title: Message Title olamy assigned an issue to Unassigned Jenkins / JENKINS-10840 Maven "module" shows as running after build is aborted. Change By: olamy Assignee: olamy 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-8428) Unable to copy site from xxxx to xxxxx hudson.util.IOException2: hudson.util.IOException2: Failed to extract ... (no idea which comp is responsible for this)
Title: Message Title olamy assigned an issue to Unassigned Jenkins / JENKINS-8428 Unable to copy site from to x hudson.util.IOException2: hudson.util.IOException2: Failed to extract ... (no idea which comp is responsible for this) Change By: olamy Assignee: olamy 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-6681) Maven-generated site link gives 404
Title: Message Title olamy assigned an issue to Unassigned Jenkins / JENKINS-6681 Maven-generated site link gives 404 Change By: olamy Assignee: olamy 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-49587) Cloud Foundry Plugins fails to connect Jenkins instance in PCF Dev
Title: Message Title olamy assigned an issue to Unassigned Jenkins / JENKINS-49587 Cloud Foundry Plugins fails to connect Jenkins instance in PCF Dev Change By: olamy Assignee: olamy 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-49493) CF push failing with Jenkins
Title: Message Title olamy assigned an issue to Unassigned Jenkins / JENKINS-49493 CF push failing with Jenkins Change By: olamy Assignee: olamy 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-43995) Individual Pipeline steps and stages/blocks should have Result statuses
Title: Message Title Jenn Briden updated an issue Jenkins / JENKINS-43995 Individual Pipeline steps and stages/blocks should have Result statuses Change By: Jenn Briden Labels: blueocean roadmap 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-50756) HTML and LRA folder not getting created after LR scenario execution with Jenkins
Title: Message Title Ashwin Unnikrishnan assigned an issue to Michael Seldin Jenkins / JENKINS-50756 HTML and LRA folder not getting created after LR scenario execution with Jenkins Change By: Ashwin Unnikrishnan Assignee: Ofir Shaked Michael Seldin 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-41894) deleteDir() for cwd removes workspace when run in docker.image('builder').inside
Title: Message Title
Jon B commented on JENKINS-41894
Re: deleteDir() for cwd removes workspace when run in docker.image('builder').inside
I found my way here after I noticed that declarative pipeline sh steps fail if you try to ensure the workspace is clear when using either deleteDir() or cleanWs() I have to do some really hacky workaround to make this work as desired. A reasonable person would assume that you can call deleteDir() anywhere to help ensure the WORKSPACE is empty. Unfortunately, deleteDir() physically blows away the WORKSPACE which screws up docker declarative agents.
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-48973) Add prev link to Blueocean API response
Title: Message Title Nicolae Pascu stopped work on JENKINS-48973 Change By: Nicolae Pascu Status: In Progress Open 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-48075) Show next/prev links in results screen
Title: Message Title Nicolae Pascu updated JENKINS-48075 Jenkins / JENKINS-48075 Show next/prev links in results screen Change By: Nicolae Pascu Status: In Review Closed Resolution: Fixed 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-50408) Highlight difficult to see after clicking on stage
Title: Message Title Nicolae Pascu assigned an issue to Nicolae Pascu Jenkins / JENKINS-50408 Highlight difficult to see after clicking on stage Change By: Nicolae Pascu Assignee: Nicolae Pascu 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-50408) Highlight difficult to see after clicking on stage
Title: Message Title Nicolae Pascu started work on JENKINS-50408 Change By: Nicolae Pascu Status: Open In Progress 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-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title Christopher Unkel commented on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error It seems like it should be possible to eliminate the race with the use of a lock to prevent processes from being forked while the GIT_SSH target script is open for writing. Roughly: In hudson.Launcher, add a static ReadWriteLock field using a ReentrantReadWriteLock. Hold the read lock in hudson.Launcher.ProcStarter.start() when calling launch(). Also hold the read lock in the various deprecated final hudson.Launcher.launch() overloads. Expose the (write) lock publicly for use in preventing launching. When writing files that will be executed, hold the write lock from when that file is created to when it is closed. Specifically, hold the lock for the lifetime of the PrintWriter in each of org.jenkinsci.plugins.gitclient.CliGitApiImpl.createUnixSshAskpass(), .createUnixStandardAskpass(), and .createUnixGitSSH(). Does this seem like a viable approach? Worth developing a patch? 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
[JIRA] (JENKINS-50825) Add editor ATH coverage for deleting steps and stages from a pipeline
Title: Message Title Karl Shultz stopped work on JENKINS-50825 Change By: Karl Shultz Status: In Progress Open 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-50825) Add editor ATH coverage for deleting steps and stages from a pipeline
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-50825 Add editor ATH coverage for deleting steps and stages from a pipeline Change By: Karl Shultz Sprint: Blue Ocean 1.6 - beta 2 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-50829) Automated test for stopping running jobs in Blue Ocean
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-50829 Automated test for stopping running jobs in Blue Ocean Change By: Karl Shultz Sprint: Blue Ocean 1.6 - beta 2 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-50956) Add parameter for using agent private address when connecting via SSH
Title: Message Title Vic Iglesias created an issue Jenkins / JENKINS-50956 Add parameter for using agent private address when connecting via SSH Issue Type: Task Assignee: Evan Brown Components: google-compute-engine-plugin Created: 2018-04-23 22:28 Priority: Minor Reporter: Vic Iglesias At the moment the Jenkins master will connect to the internal or external IP depending on whether there is an external IP attached to the agent. In some cases there will be an external IP attached to reach the internet but the master should still use the internal IP of its agents as to not have to haripin back from the internet. There should be an explicit setting for whether the master should reach out over the internal or external IP of an instance. Add Comment
[JIRA] (JENKINS-50829) Automated test for stopping running jobs in Blue Ocean
Title: Message Title Karl Shultz started work on JENKINS-50829 Change By: Karl Shultz Status: Open In Progress 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-25628) config.xml files do not end in newline
Title: Message Title Elliot Wolk commented on JENKINS-25628 Re: config.xml files do not end in newline i would like to point out, also, that editing config files without making changes is ALREADY allowed to produce a file with a difference checksum. it happens all the time, if you upgrade jenkins or any plugins. it would be unlikely for this to be the only change anyway. 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-43964) Two Build URLs appearing in JIRA comment
Title: Message Title Wisen Tanasa started work on JENKINS-43964 Change By: Wisen Tanasa Status: Open In Progress 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-50955) add ability to set "doNotScan" for the BFA plugin with Declarative Pipeline
Title: Message Title Ray Kivisto created an issue Jenkins / JENKINS-50955 add ability to set "doNotScan" for the BFA plugin with Declarative Pipeline Issue Type: Improvement Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 2018-04-23 21:23 Environment: build-failure-analyzer:1.19.2 'Build Failure Analyzer' pipeline-model-definition:1.2.9 'Pipeline: Declarative' CloudBees Jenkins Enterprise 2.107.2.1-rolling Priority: Minor Reporter: Ray Kivisto I'm able to disable the build failure analyzer plugin for my scripted Pipeline by using: properties([[$class: 'ScannerJobProperty', doNotScan: true]]) as per: https://github.com/rkivisto/buildFailureAnalyzer/blob/master/Jenkinsfile For declarative Pipeline: https://github.com/rkivisto/buildFailureAnalyzer/blob/declarative/Jenkinsfile the BFA plugin is working well, but when I searched the documentation for the BFA plugin, and also when I check the Declarative Directive Generator (https://jenkins.io/blog/2018/04/09/whats-in-declarative/#declarative-directive-generator) under the "Options" directive, I do not see any options related to disabling the BFA plugin for declarative pipeline.
[JIRA] (JENKINS-50176) Locked resources using the variable parameter do not get reset to the variable once released to another requester and only appear as null on subsequent locks
Title: Message Title Curt Coleman commented on JENKINS-50176 Re: Locked resources using the variable parameter do not get reset to the variable once released to another requester and only appear as null on subsequent locks Antonio Muñiz, is there anything you can do on your end to get this fix (PR-95) pushed through (assuming you agree with the changes)? 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-50954) Field references in CPS class methods fail in CPS subclasses
Title: Message Title
Andrew Bayer created an issue
Jenkins / JENKINS-50954
Field references in CPS class methods fail in CPS subclasses
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-cps-plugin
Created:
2018-04-23 20:28
Priority:
Major
Reporter:
Andrew Bayer
Still trying to figure out how to describe this exactly. =) There are two cases that are related that I can reproduce. First, in a single Jenkinsfile:
class C {
int x = 33
int getX() {
2 * this.@x
}
}
class D extends C {
int getY() {
2 * getX() }
}
new D().y
This results in groovy.lang.MissingFieldException: No such field: x for class: D, with the following stacktrace:
at groovy.lang.MetaClassImpl.getAttribute(MetaClassImpl.java:2823)
at groovy.lang.MetaClassImpl.getAttribute(MetaClassImpl.java:3759)
at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getGroovyObjectField(ScriptBytecodeAdapter.java:356)
at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.getAttribute(DefaultInvoker.java:53)
at com.cloudbees.groovy.cps.impl.AttributeAccessBlock.rawGet(AttributeAccessBlock.java:20)
at C.getX(Script1.groovy:1)
at D.getY(Script1.groovy:1)
at Script1.run(Script1.groovy:1)
The second I can't reproduce in a single Jenkinsfile - each of the inheriting classes need to be in a shared library, and it needs multiple levels of inheritance.
[JIRA] (JENKINS-38536) Execution time of parallel blocks of in-flight jobs wrong
Title: Message Title Damien Jiang reopened an issue See above comment; this issue is happening for us on the latest version of Blue Ocean. Jenkins / JENKINS-38536 Execution time of parallel blocks of in-flight jobs wrong Change By: Damien Jiang Resolution: Fixed Status: Closed Reopened 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
[JIRA] (JENKINS-42781) Load more than 100 steps in a node
Title: Message Title
Bimlendu Mishra edited a comment on JENKINS-42781
Re: Load more than 100 steps in a node
Is this something still looked into?I see the nodes api being called with a limit parameter of 1, the steps api does not have such parameter, and it maxes out at 100.\{code: title=test100StepsLimit.groovy|borderStyle=solid java } pipeline \{ agent \{ label any } stages \{ stage('200 Steps')\{ steps \{ script \{ def range = 1..200 range.each \{ n -> println n } } } } } } \{code}Call for nodes API: [http://localhost:8080/blue/rest/organizations/jenkins/pipelines/test100Limit/runs/4/nodes/?limit=1]Call for steps API: [http://localhost:8080/blue/rest/organizations/jenkins/pipelines/test100Limit/runs/4/nodes/6/steps/]Is there a way I can send the limits parameter to the steps API too. Or, I need to change here: [https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-dashboard/src/main/js/components/karaoke/services/Augmenter.js#L83]Also is there a reason why this limit is not being passed to steps/ endpoint ?
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-42781) Load more than 100 steps in a node
Title: Message Title
Bimlendu Mishra edited a comment on JENKINS-42781
Re: Load more than 100 steps in a node
Is this something still looked into?I see the nodes api being called with a limit parameter of 1, the steps api does not have such parameter, and it maxes out at 100.\{code:title=test100StepsLimit.groovy|borderStyle=solid}pipeline \{ agent \{ label any } stages \{ stage('200 Steps')\{ steps \{ script \{ def range = 1..200 range.each \{ n -> println n } } } } }}\{code}Call for nodes API: [ http://localhost:8080/blue/rest/organizations/jenkins/pipelines/test100Limit/runs/4/nodes/?limit=1 ] Call for steps API: [ http://localhost:8080/blue/rest/organizations/jenkins/pipelines/test100Limit/runs/4/nodes/6/steps/ ] Is there a way I can send the limits parameter to the steps API too. Or, I need to change here: [ https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-dashboard/src/main/js/components/karaoke/services/Augmenter.js#L83 ] Also is there a reason why this limit is not being passed to steps/ endpoint ?
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-42781) Load more than 100 steps in a node
Title: Message Title
Bimlendu Mishra commented on JENKINS-42781
Re: Load more than 100 steps in a node
Is this something still looked into? I see the nodes api being called with a limit parameter of 1, the steps api does not have such parameter, and it maxes out at 100. {code:title=test100StepsLimit.groovy|borderStyle=solid} pipeline { agent { label any } stages { stage('200 Steps'){ steps { script { def range = 1..200 range.each { n -> println n } } } } } } {code} Call for nodes API: http://localhost:8080/blue/rest/organizations/jenkins/pipelines/test100Limit/runs/4/nodes/?limit=1 Call for steps API: http://localhost:8080/blue/rest/organizations/jenkins/pipelines/test100Limit/runs/4/nodes/6/steps/ Is there a way I can send the limits parameter to the steps API too. Or, I need to change here: https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-dashboard/src/main/js/components/karaoke/services/Augmenter.js#L83 Also is there a reason why this limit is not being passed to steps/ endpoint ?
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-50887) Need a buildDiscarder in a pipeline, which deletes only failing jobs in master branch
Title: Message Title Oleg Nenashev commented on JENKINS-50887 Re: Need a buildDiscarder in a pipeline, which deletes only failing jobs in master branch Just to provide an update, unfortunately this project won't happen in GSoC this year 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-49823) Jacoco Plugin 3.0.1 fails build as basedir now incorrect
Title: Message Title Mor L edited a comment on JENKINS-49823 Re: Jacoco Plugin 3.0.1 fails build as basedir now incorrect Hi,For me this is actually a major problem - I have a generic flow which "suits-all" - some repositories produce jacoco reports while others don't - but I always call the jacoco step . In previous versions of the plugin this found nothing and the job continued properly. with the new plugin version my builds started to fail due to the above mentioned error - so I'm going to downgrade it.I would expect at least an option to not fail the build if classes/exec files are not found - same as exists for the Junit and TestNG plugins. If needed I can open a new ticket for this request. 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-49823) Jacoco Plugin 3.0.1 fails build as basedir now incorrect
Title: Message Title Mor L commented on JENKINS-49823 Re: Jacoco Plugin 3.0.1 fails build as basedir now incorrect Hi, For me this is actually a major problem - I have a generic flow which "suits-all" - some repositories produce jacoco reports while others don't - but I always call the jacoco step . In previous versions of the plugin this found nothing and the job continued properly. with the new plugin version my builds started to fail due to the above mentioned error - so I'm going to downgrade it. I would expect at least an option to not fail the build if classes/exec files are not found - same as exists for the Junit and TestNG plugins. 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-50740) gitlabCommitStatus clobbers Groovy compilation exceptions
Title: Message Title Andrew Bayer commented on JENKINS-50740 Re: gitlabCommitStatus clobbers Groovy compilation exceptions So I think the problem is in here. Though I may not be quite right. What's happening is that the compilation exception from load is getting serialized as part of the program state, but I'm not entirely sure how/why. 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-50884) Upgrade to 2.107.2 LTS breaks Jenkins home page
Title: Message Title Pranesh Ramakrishnan commented on JENKINS-50884 Re: Upgrade to 2.107.2 LTS breaks Jenkins home page Upgrading build-pipeline-plugin does not fix the bug. It only allows me to view the Jenkins home page but opening any Build Pipeline view crashes Jenkins with the same error. 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-50556) git polling succeeds even when origin/master has nothing new
Title: Message Title Jacob Keller commented on JENKINS-50556 Re: git polling succeeds even when origin/master has nothing new > Thanks Jacob, do you know how I could tell the git plugin to use the remote polling method instead of requiring a workspace? Make sure that you don't use any extensions which enable worktree polling. These include "author in change log", "change log to branch", "require workspace when polling", "Message exclusion", "User exclusion", or "Path restriction" I do not understand offhand why "author in change log" and "change log to branch" require this at the moment, but message exclusion, user exclusion, and path restriction require it because these features aren't implemented within the remote polling code. (I suspect it's possible to do so, but no one has done it). Additionally, remote polling is not setup to handle more than a single branch, so you need to make sure you only use one branch. It's in theory possible to fix these limitations, but I do not offhand know the work involved to do so. 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-37491) Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes
Title: Message Title Joshua Noble commented on JENKINS-37491 Re: Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes I can confirm that setting up the Basic Branch Build Strategies plugin and selecting Regular Branches and Change Requests (with Ignore rebuilding merge branches checked) indeed gives us exactly what we want. Thanks for the tip! 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-50953) Consider creating separate deployment repository for master commits
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-50953 Consider creating separate deployment repository for master commits Issue Type: Task Assignee: Jesse Glick Components: plugin-pom Created: 2018-04-23 16:42 Priority: Minor Reporter: Jesse Glick Would be useful for several reasons, for example versions:display-dependency-updates, to segregate artifacts built from master branch commits into their own repository. Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-50952) Broken link unsecure.key in ATH
Title: Message Title Raul Arabaolaza created an issue Jenkins / JENKINS-50952 Broken link unsecure.key in ATH Issue Type: Task Assignee: Oliver Gondža Components: acceptance-test-harness Created: 2018-04-23 16:34 Priority: Minor Reporter: Raul Arabaolaza See here Originally set as part o the DocdkerWinstoneController I believe now is broken as the fixture has been moved to jenkin/docker-fixtures and out of the ATH Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-45997) BitBucket PRs failing to checkout on initial run after PR updated with new commits
Title: Message Title Jakob Jarosch commented on JENKINS-45997 Re: BitBucket PRs failing to checkout on initial run after PR updated with new commits What is currently blocking the pull request from being merged? 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-37491) Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes
Title: Message Title Jesse Glick commented on JENKINS-37491 Re: Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes For safety, you may want to then configure GitHub to refuse to let PRs be merged unless they are up to date with the base branch—IOW to only permit fast-forward merges from the GUI. 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-50950) Updates service should compute and return deltas based on the instance's version
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-50950 Updates service should compute and return deltas based on the instance's version Issue Type: Task Assignee: R. Tyler Croy Components: essentials Created: 2018-04-23 16:07 Priority: Minor Reporter: R. Tyler Croy Basically the update service should have a full inventory of "everything" and then when the client phones home with its current level, it should be told about its level and given the delta of changes since the previous level to prevent re-downloads of existing artifact versions. Add Comment
[JIRA] (JENKINS-50951) evergreen-client should store its current update level
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-50951 evergreen-client should store its current update level Issue Type: Task Assignee: R. Tyler Croy Components: essentials Created: 2018-04-23 16:07 Priority: Minor Reporter: R. Tyler Croy 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
[JIRA] (JENKINS-50949) Track update levels properly in the backend datastore
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-50949 Track update levels properly in the backend datastore Issue Type: Task Assignee: R. Tyler Croy Components: essentials Created: 2018-04-23 16:03 Priority: Minor Reporter: R. Tyler Croy Per this discussion we need to keep track of update levels on the backend which requires a bit more machinery to get everything correct Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50948) Generate essentials.yaml with the appropriate dependencies
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-50948 Generate essentials.yaml with the appropriate dependencies Issue Type: Task Assignee: R. Tyler Croy Components: essentials Created: 2018-04-23 16:01 Priority: Minor Reporter: R. Tyler Croy Presently essentials.yaml includes a number of plugins which could be considered "top-level" dependencies for Jenkins Essentials such as workflow-aggregator. Some tooling needs to be in place to generate the appropriate essentials.yaml with all the dependencies within it. Jesse Glick suggested taking a look at some maven tooling he has used before: https://github.com/jenkinsci/workflow-aggregator-plugin/blob/2fd92539829c9b066ca4b4b65b50d6c4a403f9e1/demo/pom.xml#L5-L38 https://github.com/jenkinsci/workflow-aggregator-plugin/blob/2fd92539829c9b066ca4b4b65b50d6c4a403f9e1/demo/Makefile#L5-L12 Meanwhile Oleg Nenashev points out this issue for the custom-war-packager Add Comment
[JIRA] (JENKINS-48135) kubernetes-plugin should support multiple containers in declarative templates
Title: Message Title Carlos Sanchez updated JENKINS-48135 Jenkins / JENKINS-48135 kubernetes-plugin should support multiple containers in declarative templates Change By: Carlos Sanchez Status: In Review Resolved Resolution: Fixed 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-50207) Transient error "container [*] does not exist in pod"
Title: Message Title Carlos Sanchez closed an issue as Cannot Reproduce No feedback from reporter, closing Jenkins / JENKINS-50207 Transient error "container [*] does not exist in pod" Change By: Carlos Sanchez Status: Open Closed Resolution: Cannot Reproduce 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
[JIRA] (JENKINS-50302) Documentation for pulling docker images from AWS EC2 Container Registry
Title: Message Title Carlos Sanchez closed an issue as Won't Do Jenkins / JENKINS-50302 Documentation for pulling docker images from AWS EC2 Container Registry Change By: Carlos Sanchez Status: Open Closed Resolution: Won't Do 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-50533) YAML definition of jnlp container isn't updated with env variables and arguments
Title: Message Title Carlos Sanchez updated JENKINS-50533 Jenkins / JENKINS-50533 YAML definition of jnlp container isn't updated with env variables and arguments Change By: Carlos Sanchez Status: In Review Resolved Resolution: Fixed 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-49852) Collect Pipeline usage telemetry
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49852 Collect Pipeline usage telemetry Change By: R. Tyler Croy Sprint: Essentials - Milestone 1 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-49852) Collect Pipeline usage telemetry
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49852 Collect Pipeline usage telemetry Change By: R. Tyler Croy Sprint: Essentials - Milestone 2 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-50373) Design and implement the evergreen-client metrics system
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-50373 Design and implement the evergreen-client metrics system Change By: R. Tyler Croy Sprint: Essentials - Milestone 2 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-50373) Design and implement the evergreen-client metrics system
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-50373 Design and implement the evergreen-client metrics system Change By: R. Tyler Croy Sprint: Essentials - Milestone 1 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-50947) Could not attach 'nodes/master/pipeline-timings.txt' to support bundle
Title: Message Title David Aldrich created an issue Jenkins / JENKINS-50947 Could not attach 'nodes/master/pipeline-timings.txt' to support bundle Issue Type: Bug Assignee: Emilio Escobar Components: support-core-plugin Created: 2018-04-23 15:08 Environment: Jenkins 2.107.2 Priority: Minor Reporter: David Aldrich With Support Core plugin 2.47 I see exceptions: Apr 23, 2018 2:19:06 PM WARNING com.cloudbees.jenkins.support.SupportPlugin writeBundle Could not attach 'nodes/master/pipeline-timings.txt' to support bundle java.io.IOException: Zodiac_build_gcc_vstudio_TRY_TML_VS2017_18Apr2018 #9 did not yet start at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.get(WorkflowRun.java:1058) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$PipelineTimings$1.writeTo(CpsFlowExecution.java:1779) at com.cloudbees.jenkins.support.SupportPlugin.writeBundle(SupportPlugin.java:357) at com.cloudbees.jenkins.support.SupportPlugin.writeBundle(SupportPlugin.java:271) at com.cloudbees.jenkins.support.SupportPlugin$PeriodicWorkImpl$1.run(SupportPlugin.java:741) at java.lang.Thread.run(Thread.java:748)
[JIRA] (JENKINS-50616) JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50616 JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons Change By: Oleg Nenashev Labels: JEP-200 lts-candidate 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-50616) JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons
Title: Message Title Oleg Nenashev commented on JENKINS-50616 Re: JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons Created https://github.com/jenkinsci/jenkins/pull/3404. I do not believe it can be backported to 2.107.x, but CC Oliver Gondža just in case. It may need backporting to the next baseline anyway 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-50616) JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50616 JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons Change By: Oleg Nenashev Component/s: core 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-50616) JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons
Title: Message Title Oleg Nenashev commented on JENKINS-50616 Re: JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons OK, will create a PR in few minutes 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-50738) Instance versions information should be POSTable and history should be maintained
Title: Message Title R. Tyler Croy resolved as Fixed This has since been merged. Though the update levels are still giving me grief Jenkins / JENKINS-50738 Instance versions information should be POSTable and history should be maintained Change By: R. Tyler Croy Status: In Progress Resolved Resolution: Fixed 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
[JIRA] (JENKINS-50737) An admin should be able to POST essentials.yaml and create a new Update record
Title: Message Title R. Tyler Croy started work on JENKINS-50737 Change By: R. Tyler Croy Status: Open In Progress 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-50849) Define the versions manifest schema
Title: Message Title R. Tyler Croy started work on JENKINS-50849 Change By: R. Tyler Croy Status: Open In Progress 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-50616) JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons
Title: Message Title Jesse Glick commented on JENKINS-50616 Re: JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons Oleg Nenashev yes we should add RubyNil to the existing core whitelist—pending merge, release, and general adoption of the plugin fix. 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-50216) Google Auth Plugin is incompatible with Jenkins 2.102+
Title: Message Title Oleg Nenashev commented on JENKINS-50216 Re: Google Auth Plugin is incompatible with Jenkins 2.102+ According to https://issues.jenkins-ci.org/browse/JENKINS-50899?focusedCommentId=335821=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-335821, my fix likely does not work as expected 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-50294) Design (JEP) Essentials Instance Client Health Checking
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50294 Re: Design (JEP) Essentials Instance Client Health Checking Code changed in jenkins User: Baptiste Mathus Path: jep//README.adoc http://jenkins-ci.org/commit/jep/958d5d2d7f8f1842e0bf8a06141e164010a7c11a Log: JENKINS-50294 Essentials Instance Client Health Checking 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-50294) Design (JEP) Essentials Instance Client Health Checking
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50294 Re: Design (JEP) Essentials Instance Client Health Checking Code changed in jenkins User: R. Tyler Croy Path: jep/306/README.adoc jep/README.adoc http://jenkins-ci.org/commit/jep/d5c75cbae70a18055486f8550ec39cb9fa5cae4f Log: Merge pull request #91 from batmat/JENKINS-50294 JENKINS-50294 Essentials Instance Client Health Checking Compare: https://github.com/jenkinsci/jep/compare/b5d8196d8d9b...d5c75cbae70a 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-50602) Add documentation on how to access credentials from within Jenkins pipelines
Title: Message Title James Nord closed an issue as Fixed Jenkins / JENKINS-50602 Add documentation on how to access credentials from within Jenkins pipelines Change By: James Nord Status: Open Closed Resolution: Fixed 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-48945) wrong testreport, if testnames produce a hashcollision (because of temp. generated junit-files)
Title: Message Title Sascha Friederich assigned an issue to Nikolas Falco Jenkins / JENKINS-48945 wrong testreport, if testnames produce a hashcollision (because of temp. generated junit-files) Change By: Sascha Friederich Assignee: Gregory Boissinot Nikolas Falco 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-50767) Control initial crumb issuer proxy compatibility value
Title: Message Title Vincent Latombe updated JENKINS-50767 Jenkins / JENKINS-50767 Control initial crumb issuer proxy compatibility value Change By: Vincent Latombe Status: In Review Resolved Resolution: Fixed 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-50767) Control initial crumb issuer proxy compatibility value
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50767 Re: Control initial crumb issuer proxy compatibility value Code changed in jenkins User: Vincent Latombe Path: core/src/main/java/jenkins/install/SetupWizard.java http://jenkins-ci.org/commit/jenkins/909f55b77da1d4a0a16a818fe592504538e49430 Log: JENKINS-50767 Control crumb issuer proxy compatibility through system property (#3389) -Djenkins.model.Jenkins.crumbIssuerProxyCompatibility=true enables proxy compatibility on startup 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.
