[JIRA] (JENKINS-55139) ansicolor 0.6.0 shows terminal escape sequences in console log
Title: Message Title
Thomas M commented on JENKINS-55139
Re: ansicolor 0.6.0 shows terminal escape sequences in console log
I can confirm this bug and also that downgrading to 0.5.3 (from http://updates.jenkins-ci.org/download/plugins/ansicolor/) helps. My sh commands use double quotes (but only single-line, as in sh "bash path/to/script ${arg1} ${arg2}") already so I cannot confirm Dennis Hoer workaround. With the 0.6.2 I get output similar to Marc Benstein comment.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196206.1544605559000.11017.1575362882892%40Atlassian.JIRA.
[JIRA] (JENKINS-50429) Shell command are really slower than before
Title: Message Title Thomas M commented on JENKINS-50429 Re: Shell command are really slower than before The PR applies to a specific plugin. I can't pin it down to a specific plugin. https://github.com/jenkinsci/kubernetes-plugin/pull/425/files seems to use reflection to make a general change to the java runtime. I would like to try that, but I don't know how to apply it. Do I have to develop a dummy plugin or can I otherwise hook into the runtime? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189484.1522154059000.3154.1574157120598%40Atlassian.JIRA.
[JIRA] (JENKINS-50429) Shell command are really slower than before
Title: Message Title Thomas M commented on JENKINS-50429 Re: Shell command are really slower than before Pascal Laporte Carlos Sanchez This issue is marked as resolved, but your last comments don't look like it? I'm facing a similar problem, but I'm not using any kubernetes related plugin. Carlos Sanchez can you please suggest how I could quickly check if the workaround helps in my case as well (don't know how I could apply a hotfix in java code in an existing Jenkins installation). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189484.1522154059000.895.1573745401026%40Atlassian.JIRA.
[JIRA] (JENKINS-52816) scm poll triggers even there is no change in repository(bitbucket)
Title: Message Title Thomas M commented on JENKINS-52816 Re: scm poll triggers even there is no change in repository(bitbucket) Cenk Tosun your workaround (changing to legacy scm and effectively ignoring all commits there) seems effective, thanks! It means that we cannot trigger on pipeline library changes but that's good enough for now. Now, does that point to a defect in the modern scm method? That ought to be fixed, right? I got the feeling that "legacy scm" is somewhat half-deprecated and might be removed in the future. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192737.1533040103000.1340.1571999820350%40Atlassian.JIRA.
[JIRA] (JENKINS-52816) scm poll triggers even there is no change in repository(bitbucket)
Title: Message Title Thomas M commented on JENKINS-52816 Re: scm poll triggers even there is no change in repository(bitbucket) Mark Waite We found that most proably shared pipeline libraries cause the rebuilds. Can you rule this out? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192737.1533040103000.9270.1571262480448%40Atlassian.JIRA.
[JIRA] (JENKINS-52816) scm poll triggers even there is no change in repository(bitbucket)
Title: Message Title Thomas M commented on JENKINS-52816 Re: scm poll triggers even there is no change in repository(bitbucket) Do you also use pipeline libraries? I tried your workaround on the job for the repo that pulls the Jenkinsfile, but the parent project (and the Jenkinsfile) specifies a pipeline library. For that library I cannot specifiy ignore patterns in the same way as for the Jenkinsfile itself. 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-52816) scm poll triggers even there is no change in repository(bitbucket)
Title: Message Title
Thomas M commented on JENKINS-52816
Re: scm poll triggers even there is no change in repository(bitbucket)
I have the same problem. Cenk Tosun It sounds exactly as you describe. Do you have a solution or at least a workaround? In fact, I believe the causing SCM is not the one providing the Jenkins file but the one that provides the pipeline library ("@Library") that the Jenkinsfile uses (in thise case both branches are on the same repository). But I may be wrong. But the polling protocol does say "already built by XX" for scm polls that are explicitely mentioned in the groovy code so I don't think these are causing the rebuilds.
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.
