[JIRA] (JENKINS-52816) scm poll triggers even there is no change in repository(bitbucket)
Title: Message Title Cenk Tosun edited a comment on JENKINS-52816 Re: scm poll triggers even there is no change in repository(bitbucket) For example, what is the final definition of the job as created by Job DSL? * declerative pipeline jobs using one checkout in job configuration for the jenkinsfile with branch */master and also multiple other git repos in the jenkinsfile with */masterIs there a webhook configured from Bitbucket to Jenkins? If not, why not (since polling is much less efficient than web hooks)? * Yes, with [http://Jenkinsurl/git/notifyCommit?url="" jobs are receiving the notification from bitbucketIf you use a web hook instead of polling, does that resolve the problem? * here it's the other way around, pure polling seems to work and scm poll but nevertheless both end up after certain build with no baseline for *** and starting multiple jobs Is the problem job a Pipeline (not multibranch) or a multibranch Pipeline? * yes, as already mentioned beforeWhat is the branch definition in the jobs? * */branchname, some other jobs contain slashes based on the gitflow patternI hope that is enough. 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-52090) Support arm64 architecture build of docker image
Title: Message Title Lee Jones commented on JENKINS-52090 Re: Support arm64 architecture build of docker image Are there any updates on this please? 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 Cenk Tosun commented on JENKINS-52816 Re: scm poll triggers even there is no change in repository(bitbucket) For example, what is the final definition of the job as created by Job DSL? declerative pipeline jobs using one checkout in job configuration for the jenkinsfile with branch */master and also multiple other git repos in the jenkinsfile with */master Is there a webhook configured from Bitbucket to Jenkins? If not, why not (since polling is much less efficient than web hooks)? Yes, with http://Jenkinsurl/git/notifyCommit?url=""> - jobs are receiving the notification from bitbucket If you use a web hook instead of polling, does that resolve the problem? here it's the other way around, pure polling seems to work and scm poll end up after certain build with no baseline for *** Is the problem job a Pipeline (not multibranch) or a multibranch Pipeline? yes, as already mentioned before What is the branch definition in the jobs? */branchname, some other jobs contain slashes based on the gitflow pattern I hope that is enough. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You
[JIRA] (JENKINS-54764) builds fail when using timeout step with the Pipeline Basic Steps Plugin
Title: Message Title Cenk Tosun created an issue Jenkins / JENKINS-54764 builds fail when using timeout step with the Pipeline Basic Steps Plugin Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2018-11-22 07:21 Environment: Jenkins ver. 2.138.3 Labels: pipeline plugins Priority: Critical Reporter: Cenk Tosun timeout is set up to 10 - 20 minutes since we upgraded to version 2.12 all pipeline builds fail after a certain time with the following error message: After 10s process did not stop After downgrading back to 2.11 builds are successful again Add Comment
[JIRA] (JENKINS-43758) Parameters disappear from pipeline job after running the job
Title: Message Title Khalil Jiries commented on JENKINS-43758 Re: Parameters disappear from pipeline job after running the job I'm having same issue, here is my use case: I have a seed job that loads all Jenkins declarative pipelines jobs to jenkins. These pipelines have job parameters defined in their Jenkinsfile. Each time the seed job runs, it overrides the job parameters and remove them all. Next trigger of the build will reflect the parameters back to the job. 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-48784) Workflow job doesn't update properly if you change a SCMStep polling from true to false
Title: Message Title Cenk Tosun commented on JENKINS-48784 Re: Workflow job doesn't update properly if you change a SCMStep polling from true to false I have the same problem here. Using pipeline jobs with multiple checkout of git repos. I am not sure what happens, but on every first build of the day and also in the course of the day, i get the message "no polling baseline in ***" on. as a result at least one new build although there have been no changes. that have led to an error so far: changing branch will end up with polling in the old branch (i guess until the first successful build) change/update of polling - end up with unnecessary builds workspace clean-up (assumption) - end up with unnecessary builds And Idea or additional experiences? 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-48489) ability to specify a path prefix to archiveArtifacts
Title: Message Title Craig Ringer commented on JENKINS-48489 Re: ability to specify a path prefix to archiveArtifacts I'm really surprised not to see more interest in this issue, I ran into it as soon as I started doing any archiving in parallel jobs. The shell workaround is ugly. I'll try to find time to patch this, but it looks like it requires changes to Jenkins and to pipeline, which is likely why it hasn't been picked up yet. 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-54763) Branch name disappear after plugin upgrade (>= 2.26)
Title: Message Title
Vern Sun updated an issue
Jenkins / JENKINS-54763
Branch name disappear after plugin upgrade (>= 2.26)
Change By:
Vern Sun
In my case, the IP address(ok.png) cannot be displayed after the upgrade(ng.png).I know this is a compatibility issue, after 2.26.I just hope that this problem can be solved in the future.*Jenkinsfile*{code:java}stage('Release') {def progress = [:];progress['___10.168.2.164 甲'] = {node("nj-mes-man-prod"){ do_offline(1); do_deploy(); do_online(1) }}progress['__10.1.2.65 乙'] = {node("nj-mes-man-2-pe"){ do_offline(2); do_deploy(); do_online(2) }}progress['_10.1.2.164 丙'] = {node("nj-mes-man-3-pe"){ do_offline(3); do_deploy(); do_online(3) }}progress['__10.1.2.69 丁'] = {node("nj-mes-man-4-pe"){ do_offline(4); do_deploy(); do_online(4) }}parallel progress}{code}*Diff*{code :diff }% git di workflow-job-2.25 workflow-job-2.26-beta-1...(略)-String prefix = getBranchName(node);-if (prefix != null) { @@ - logger = new LogLinePrefixOutputFilter(getListener().getLogger(), "[" + prefix + "] ");-} else {- logger = getListener().getLogger();-}...(略){code}
Add Comment
[JIRA] (JENKINS-54763) Branch name disappear after plugin upgrade (>= 2.26)
Title: Message Title
Vern Sun created an issue
Jenkins / JENKINS-54763
Branch name disappear after plugin upgrade (>= 2.26)
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
ng.png, ok.png
Components:
workflow-job-plugin
Created:
2018-11-22 06:17
Environment:
Jenkins ver. 2.138.3
Labels:
plugin pipeline
Priority:
Trivial
Reporter:
Vern Sun
In my case, the IP address(ok.png) cannot be displayed after the upgrade(ng.png). I know this is a compatibility issue, after 2.26. I just hope that this problem can be solved in the future. Jenkinsfile
stage('Release') {
def progress = [:];
progress['___10.168.2.164 甲'] = {
node("nj-mes-man-prod"){ do_offline(1); do_deploy(); do_online(1) }
}
progress['__10.1.2.65 乙'] = {
node("nj-mes-man-2-pe"){ do_offline(2); do_deploy(); do_online(2) }
}
progress['_10.1.2.164 丙'] = {
node("nj-mes-man-3-pe"){ do_offline(3); do_deploy(); do_online(3) }
}
progress['__10.1.2.69 丁'] = {
node("nj-mes-man-4-pe"){
[JIRA] (JENKINS-45479) API tokens and Job/Read permission issue
Title: Message Title Rakesh Nagarajan updated an issue Jenkins / JENKINS-45479 API tokens and Job/Read permission issue Change By: Rakesh Nagarajan Priority: Major Minor 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-54739) Accessing tests from BlueOcean UI results in http threads pegging cpu in TreeMap.java (put)
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54739 Accessing tests from BlueOcean UI results in http threads pegging cpu in TreeMap.java (put) Change By: Oleg Nenashev Component/s: blueocean-plugin Component/s: core 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-53398) cannot search for "master" branch in blue ocean page
Title: Message Title Tavis Deng updated an issue Jenkins / JENKINS-53398 cannot search for "master" branch in blue ocean page Change By: Tavis Deng Priority: Major Minor 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-53398) cannot search for "master" branch in blue ocean page
Title: Message Title Tavis Deng stopped work on JENKINS-53398 Change By: Tavis Deng Status: In Progress Open 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-53398) cannot search for "master" branch in blue ocean page
Title: Message Title Tavis Deng started work on JENKINS-53398 Change By: Tavis Deng 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-54762) Show output from reconcile -w -f step of Auto Cleanup and Sync
Title: Message Title Joel Brown updated an issue Jenkins / JENKINS-54762 Show output from reconcile -w -f step of Auto Cleanup and Sync Change By: Joel Brown If "QUIET Perforce messages" is unchecked, the job's console log should show the output from the "p4 reconcile -w -f" in the populate option Auto Cleanup and Sync. Even a simple: like: /jenkins/job/abc/workspace/path/to/modifed refreshed /jenkins/job/abc/workspace/path/to/newFile deleted 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-54762) Show output from reconcile -w -f step of Auto Cleanup and Sync
Title: Message Title Joel Brown updated an issue Jenkins / JENKINS-54762 Show output from reconcile -w -f step of Auto Cleanup and Sync Change By: Joel Brown Labels: P4_VERIFY 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-54762) Show output from reconcile -w -f step of Auto Cleanup and Sync
Title: Message Title Joel Brown created an issue Jenkins / JENKINS-54762 Show output from reconcile -w -f step of Auto Cleanup and Sync Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2018-11-21 23:49 Priority: Minor Reporter: Joel Brown If "QUIET Perforce messages" is unchecked, the job's console log should show the output from the "p4 reconcile -w -f" in the populate option Auto Cleanup and Sync. Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-54371) Monitoring plugin not pushing slave metrics to InfluxDB
Title: Message Title evernat updated JENKINS-54371 See https://github.com/javamelody/javamelody/issues/791 Jenkins / JENKINS-54371 Monitoring plugin not pushing slave metrics to InfluxDB Change By: evernat Status: Open Fixed but Unreleased Resolution: Done 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-54371) Monitoring plugin not pushing slave metrics to InfluxDB
Title: Message Title evernat updated JENKINS-54371 Jenkins / JENKINS-54371 Monitoring plugin not pushing slave metrics to InfluxDB Change By: evernat Status: Fixed but Unreleased Closed 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-48828) Bitbucket Team/Folder project: View Configuration pages shows Access Denied, Jenkins throws hudson.security.AccessDeniedException2
Title: Message Title Ronnie Zhou edited a comment on JENKINS-48828 Re: Bitbucket Team/Folder project: View Configuration pages shows Access Denied, Jenkins throws hudson.security.AccessDeniedException2 Bitbucket Team is creating jobs based on the Jenkinsfile in each branch. It kinda makes sense that Bitbucket Team doesn't have configure permission to change the Jenkinsfile dynamically.The error message is confusing but the issue shouldn't be a blocker. You just have to make change to the Jenkinsfile instead of changing the configuration from the UI . 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-48828) Bitbucket Team/Folder project: View Configuration pages shows Access Denied, Jenkins throws hudson.security.AccessDeniedException2
Title: Message Title Ronnie Zhou commented on JENKINS-48828 Re: Bitbucket Team/Folder project: View Configuration pages shows Access Denied, Jenkins throws hudson.security.AccessDeniedException2 Bitbucket Team is creating jobs based on the Jenkinsfile in each branch. It kinda makes sense that Bitbucket Team doesn't have configure permission to change the Jenkinsfile dynamically. The error message is confusing but the issue shouldn't be a blocker. You just have to make change to the Jenkinsfile instead of changing the configuration from the UI. 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-48828) Bitbucket Team/Folder project: View Configuration pages shows Access Denied, Jenkins throws hudson.security.AccessDeniedException2
Title: Message Title Brady Owens commented on JENKINS-48828 Re: Bitbucket Team/Folder project: View Configuration pages shows Access Denied, Jenkins throws hudson.security.AccessDeniedException2 Agreed. Another release of the module and still this problem exists. Setting this issue as a blocker so hopefully, it gets picked up before the next release. There is no workaround that I know of to get the module to operate 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-48828) Bitbucket Team/Folder project: View Configuration pages shows Access Denied, Jenkins throws hudson.security.AccessDeniedException2
Title: Message Title Brady Owens updated an issue Jenkins / JENKINS-48828 Bitbucket Team/Folder project: View Configuration pages shows Access Denied, Jenkins throws hudson.security.AccessDeniedException2 Change By: Brady Owens Priority: Critical Blocker 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-54087) Log an audit event for user login/logout actions
Title: Message Title Matt Sicker updated JENKINS-54087 Jenkins / JENKINS-54087 Log an audit event for user login/logout actions Change By: Matt Sicker Status: Open Fixed but Unreleased Resolution: Fixed Released As: https://github.com/jvz/audit-log-plugin/pull/4 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-54087) Log an audit event for user login/logout actions
Title: Message Title Matt Sicker assigned an issue to David Olorundare Jenkins / JENKINS-54087 Log an audit event for user login/logout actions Change By: Matt Sicker Assignee: David Olorundare 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-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title Gabriel Lavoie commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down I wouldn't think so, if I look at https://github.com/jenkinsci/trilead-api-plugin/blob/93ea25242fea336bd46f0356c7a1c5d61fe34f2b/pom.xml#L72 Should I understand that the switch from `trilead-ssh2` to `trilead-api` would be to make that an optional dependency of Jenkins? `ssh-slave-plugin` already depends on `trilead-api`. I had to bump the version in Jenkins core and rebuild `jenkins.war` to test the 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-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title Gabriel Lavoie edited a comment on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down I wouldn't think so, if I look at [https://github.com/jenkinsci/trilead-api-plugin/blob/93ea25242fea336bd46f0356c7a1c5d61fe34f2b/pom.xml#L72] `trilead-api` still depends on `trilead-ssh2`. Should I understand that the switch from `trilead-ssh2` to `trilead-api` would be to make that an optional dependency of Jenkins?`ssh-slave-plugin` already depends on `trilead-api`. I had to bump the version in Jenkins core and rebuild `jenkins.war` to test the 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-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title John Zila commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down Gabriel Lavoie it seems that they intend on switching from `trilead-ssh2` to `trilead-api`–will you need to implement this change there too? 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-54550) Add usage of new Error severity in Quality Gate Thresholds
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-54550 Add usage of new Error severity in Quality Gate Thresholds Change By: Ulli Hafner Component/s: warnings-ng-plugin Component/s: warnings-plugin 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-54759) Groovy Parsers
Title: Message Title Ulli Hafner commented on JENKINS-54759 Re: Groovy Parsers Can you please split this issue so that I can track the progress individually? The second point is related to JENKINS-52237. Scanning of the console log is done on the master currently, all other files are scanned on the agent. On the master a Groovy script could do harmful things. If I allow a parser script configuration in a job this might be too dangerous. So I thought it would be better to disable processing of Groovy scripts on the master. Do you have a better idea? Can’t you pipe your log output to a file on the agent? 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-38268) Parallel step and closure scope
Title: Message Title Kevin Phillips commented on JENKINS-38268 Re: Parallel step and closure scope So I guess the problem as described in my example above seems to be particular to the `git` and `checkout` build steps, however I have managed to reproduce the problem using the `sh` step as well - just in a more elaborate way. I haven't reduced that one to a minimal reproducible example yet so I left that part out of my reply. For now the only easy-to-reproduce example I have is with those 2 specific build steps. Also, the "trick" of renaming the variable names doesn't seem to work with either of those two build steps as I had originally thought. It does, however, seem to work around the problem wrt the `sh` build step that I have also encountered in some of my production builds. It's not a "fix" of course but it has temporarily worked around the problem for me in at least one use case. I have others I need to investigate further to see if / how they relate. Will post back as soon as I know more. Regardless, the example script I provided above should reproduce the problem in that one context at least. 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-54761) Downstream job not displaying in logs after upstream job is promoted
Title: Message Title Devin Nusbaum commented on JENKINS-54761 Re: Downstream job not displaying in logs after upstream job is promoted As far as I can tell, a line like you are requesting with a URL should be printed out by parameterized-trigger if the build really does get triggered by this code. However, given the weird job hierarchy used in the promoted-builds plugin it might be getting printed to a log of the promotion status or something strange that is hard to find. What is the URL for the log that says build hudson.plugins.parameterizedtrigger.BuildTrigger? That might help narrow down the classes that could be producing that message. I am happy to help review any changes to implement this improvement, but I do not plan to work on it myself. 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-54761) Downstream job not displaying in logs after upstream job is promoted
Title: Message Title Devin Nusbaum assigned an issue to Unassigned Jenkins / JENKINS-54761 Downstream job not displaying in logs after upstream job is promoted Change By: Devin Nusbaum Assignee: Devin Nusbaum 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-43814) Password parameters should be hidden in pipeline logs by default
Title: Message Title Cosmin Stroe edited a comment on JENKINS-43814 Re: Password parameters should be hidden in pipeline logs by default Any reason why the contents of a password parameter aren't automatically filtered out from console logs? That is, is there a technical reason? or is it just that noone's implemented the feature yet? 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-43814) Password parameters should be hidden in pipeline logs by default
Title: Message Title Cosmin Stroe commented on JENKINS-43814 Re: Password parameters should be hidden in pipeline logs by default Any reason why the contents of a password parameter aren't automatically filtered out from console logs? 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-54761) Downstream job not displaying in logs after upstream job is promoted
Title: Message Title Dylan Dewhurst created an issue Jenkins / JENKINS-54761 Downstream job not displaying in logs after upstream job is promoted Issue Type: Bug Assignee: Devin Nusbaum Components: parameterized-trigger-plugin, promoted-builds-plugin Created: 2018-11-21 19:32 Environment: promoted-builds 3.2 parameterized-trigger 2.35.2 Priority: Minor Reporter: Dylan Dewhurst When a downstream job is triggered from an upstream promotion via the `Promote builds when... -> Actions -> Trigger parameterized build on other projects`, the name of the triggered downstream job is not displayed in the logs or UI. This makes it hard for users to find the triggered job. Steps to reproduce: 1. Install `promoted-builds` and `parameterized-trigger` plugins 2. Create a freestyle project 3. Check `Promote builds when...` in the General section 4. Set any name, icon, criteria 5. Add action `Trigger parameterized build on other projects` and select an existing `Project to build` 6. Save and run the project 7. After the project is promoted, check the promotion logs under `Promotions Status -> log` 8. See that nothing is logged about what job was triggered. It only logs `build hudson.plugins.parameterizedtrigger.BuildTrigger` Expected Behavior: A line in the promotion logs saying what jobs were triggered. Ideally, each job name would be a clickable link that takes you to the job page. Something like: `scheduling build for ` Actual Behavior: Downstream job is successfully triggered, but there is no mention of what job was triggered in the logs or UI. All that is printed to the logs is `build hudson.plugins.parameterizedtrigger.BuildTrigger`. Workaround: The workaround I came up with is very manual and requires updates if the job name or URL changes:
[JIRA] (JENKINS-38664) bitbucket source plugin fails with bad URL
Title: Message Title Stephen Morley commented on JENKINS-38664 Re: bitbucket source plugin fails with bad URL Confirmed. After I changed the Jenkins URL to the IP address the problem went away. We're in a small shop so I don't have a domain name I can add to the normal URL. 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-38268) Parallel step and closure scope
Title: Message Title Jacob Keller commented on JENKINS-38268 Re: Parallel step and closure scope so you're using the git step, and expect its output to return something unique? Is it possible that after that runs once it always returns the first branch? I suspect maybe that step isn't actually returning the value you think it does? Hmm, but you said if you rename the variable it works fine?? that's odd. 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-54729) jenkins dashboard displays stacktrace
Title: Message Title Kurt Routley commented on JENKINS-54729 Re: jenkins dashboard displays stacktrace There is also this thread that discusses the issue: https://groups.google.com/forum/#!topic/jenkinsci-dev/Ba69w3M-jX0 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-38664) bitbucket source plugin fails with bad URL
Title: Message Title
Mark isert edited a comment on JENKINS-38664
Re: bitbucket source plugin fails with bad URL
I was getting this error as well. After adding some logging in the plugin I discovered here: if (cfg == null || cfg.getUrl() == null) { { LOGGER.fine(Level.INFO, "JenkinsLocationConfiguration empty"); throw new IllegalStateException("Could not determine Jenkins URL."); }That the server URL required a "." in it. In our case the Jenkins URL was a short name without a ".". So I changed it to use a long URL alias we have as well. This seems like a bug. At the least there could be more logging added to the code . I had to add more logging to figure this out for example and the original exception stack trace wasn't logged in this case.
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-38664) bitbucket source plugin fails with bad URL
Title: Message Title
Mark isert commented on JENKINS-38664
Re: bitbucket source plugin fails with bad URL
I was getting this error as well. After adding some logging in the plugin I discovered here: if (cfg == null || cfg.getUrl() == null) { LOGGER.fine(Level.INFO, "JenkinsLocationConfiguration empty"); throw new IllegalStateException("Could not determine Jenkins URL."); } That the server URL required a "." in it. In our case the Jenkins URL was a short name without a ".". So I changed it to use a long URL alias we have as well. This seems like a bug. At the least there could be more logging added to the code
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-54760) Allow the users to specify the test results path
Title: Message Title Tamas Florin updated an issue Jenkins / JENKINS-54760 Allow the users to specify the test results path Change By: Tamas Florin Allow the users to specify the test results path. Changes included:a. Able to dictate the result path.b. Will not overwrite the previous result. 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-54760) Allow the users to specify the test results path
Title: Message Title Tamas Florin created an issue Jenkins / JENKINS-54760 Allow the users to specify the test results path Issue Type: New Feature Assignee: Tamas Florin Components: hp-application-automation-tools-plugin Created: 2018-11-21 17:41 Priority: Minor Reporter: Tamas Florin Allow the users to specify the test results path. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54759) Groovy Parsers
Title: Message Title Norbert Lange created an issue Jenkins / JENKINS-54759 Groovy Parsers Issue Type: Bug Assignee: Ulli Hafner Components: warnings-plugin Created: 2018-11-21 17:35 Environment: Jenkins ver. 2.138.3 (Docker Hub) Wanings NG 1.0.0-beta5 Priority: Minor Reporter: Norbert Lange The configuration and functionality is currently lacking 1) The help text under the Static Analysis Tool configuration (Freestyle job), should add that the own configured Parser can be found if "Groovy Parser" is selected For each static analysis tool a dedicated parser will be used to read the report files. If your tool is not yet supported then you can create your own parser in the system configuration. 2) Groovy Parser cant scan console log output ?! Seems a bit weird to me that a single scanner has this limitation, is this getting fixed, or is there a recommendation to start writing logs to a file first? (As in best practices, generally for Jenkins or specific to this plugin). like using "2>&1 | tee some.log" on commands? FATAL: Static analysis tool Groovy Parser cannot scan console log output, please define a file pattern
[JIRA] (JENKINS-54640) Workspace folders are not unique
Title: Message Title Lars-Magnus Skog edited a comment on JENKINS-54640 Re: Workspace folders are not unique I've noticed that workspace names sometimes get cut off. Not sure if it's known issue or not, but this issue was the closest I could find. Example. Below is a list of workspaces for `deltachat/deltachat-desktop`. As you can see, one of the workspaces doesn't start with `deltachat-desktop`, but instead `hat-desktop` or `ltachat-desktop`: !Screenshot from 2018-11-21 18-31-31.png! Please advice if you want me to create a separate issue for this. 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-54640) Workspace folders are not unique
Title: Message Title Lars-Magnus Skog commented on JENKINS-54640 Re: Workspace folders are not unique I've noticed that workspace names sometimes get cut off. Not sure if it's known issue or not, but this issue was the closest I could find. Example. Below is a list of workspaces for `deltachat/deltachat-desktop`. As you can see, one of the workspaces doesn't start with `deltachat-desktop`, but instead `hat-desktop` or `ltachat-desktop`: 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-54640) Workspace folders are not unique
Title: Message Title Lars-Magnus Skog updated an issue Jenkins / JENKINS-54640 Workspace folders are not unique Change By: Lars-Magnus Skog Attachment: Screenshot from 2018-11-21 18-31-31.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54636) Configure default audit logging output configuration
Title: Message Title Matt Sicker commented on JENKINS-54636 Re: Configure default audit logging output configuration This is for a plugin, not core. The plugin hasn't been migrated to the jenkinsci GitHub organization yet, so there isn't an "audit-log-plugin" component in Jira yet. The plugin is currently located at https://github.com/jvz/audit-log-plugin 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-35708) EC2 Plugin: Ability to round robin EC2 availability zones
Title: Message Title Nicola Forbes commented on JENKINS-35708 Re: EC2 Plugin: Ability to round robin EC2 availability zones Hi Ed, Thanks for the suggestion. I've just tried it out but unfortunately still get the same error (various combos tried). I haven't had a chance to read through the source code, but it looks like az can only take one availability zone, not a list, and so all subnets must be part of the same az. Nicky 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-54686) Use trilead-api plugin instead trilead-ssh2 from core
Title: Message Title Ivan Fernandez Calvo edited a comment on JENKINS-54686 Re: Use trilead-api plugin instead trilead-ssh2 from core ssh-slaves 1.28.1 does not use trilead-api, it was introduced in 1.29.0.I have tested a few stuff * A fresh installation of Jenkins 2.152, I do not see the issue * A fresh installation of Jenkins 2.73.3(I choose this because you can not install 1.29.X), then upgrade to 2.152 and upgrade the plugins, I do not see the issueYou can test the same if you want: * Copy your JENKINS_HOME and your jenkins.war to a test machine * Go to the test machine * Go to the JENKINS_HOME folder * Remove the plugin from the plugins folder *rm -fr plugins/ssh-slaves* * (the asterisk matters) * * Start Jenkins 'JENKINS_HOME=$(pwd) java -jar jenkins.war' * Enter in the test instance on port 8080 'http://test.exampl.com:8080' * Upgrade the plugin * Restart 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-54686) Use trilead-api plugin instead trilead-ssh2 from core
Title: Message Title Ivan Fernandez Calvo edited a comment on JENKINS-54686 Re: Use trilead-api plugin instead trilead-ssh2 from core ssh-slaves 1.28.1 does not use trilead-api, it was introduced in 1.29.0.I have tested a few stuff* A fresh installation of Jenkins 2.152, I do not see the issue* A fresh installation of Jenkins 2.73.3(I choose this because you can not install 1.29.X), then upgrade to 2.152 and upgrade the plugins, I do not see the issue You can test the same if you want:* Copy your JENKINS_HOME and your jenkins.war to a test machine* Go to the test machine* Go to the JENKINS_HOME folder* Remove the plugin from the plugins folder *rm -fr plugins/ssh-slaves \ * (the asterisk matters) ** Start Jenkins 'JENKINS_HOME=$(pwd) java -jar jenkins.war'* Enter in the test instance on port 8080 'http://test.exampl.com:8080'* Upgrade the plugin* Restart 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-54686) Use trilead-api plugin instead trilead-ssh2 from core
Title: Message Title Ivan Fernandez Calvo edited a comment on JENKINS-54686 Re: Use trilead-api plugin instead trilead-ssh2 from core ssh-slaves 1.28.1 does not use trilead-api, it was introduced in 1.29.0.I have tested a few stuff* A fresh installation of Jenkins 2.152, I do not see the issue* A fresh installation of Jenkins 2.73.3(I choose this because you can not install 1.29.X), then upgrade to 2.152 and upgrade the plugins, I do not see the issueYou can test the same if you want:* Copy your JENKINS_HOME and your jenkins.war to a test machine* Go to the test machine* Go to the JENKINS_HOME folder* Remove the plugin from the plugins folder * *' rm -fr plugins/ssh-slaves \ * ' * * * Start Jenkins 'JENKINS_HOME=$(pwd) java -jar jenkins.war'* Enter in the test instance on port 8080 'http://test.exampl.com:8080'* Upgrade the plugin* Restart 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-54686) Use trilead-api plugin instead trilead-ssh2 from core
Title: Message Title Ivan Fernandez Calvo edited a comment on JENKINS-54686 Re: Use trilead-api plugin instead trilead-ssh2 from core ssh-slaves 1.28.1 does not use trilead-api, it was introduced in 1.29.0.I have tested a few stuff* A fresh installation of Jenkins 2.152, I do not see the issue* A fresh installation of Jenkins 2.73.3(I choose this because you can not install 1.29.X), then upgrade to 2.152 and upgrade the plugins, I do not see the issue You can test the same if you want:* Copy your JENKINS_HOME and your jenkins.war to a test machine* Go to the test machine* Go to the JENKINS_HOME folder* Remove the plugin from the plugins folder **'rm -fr plugins/ssh-slaves*'*** Start Jenkins 'JENKINS_HOME=$(pwd) java -jar jenkins.war'* Enter in the test instance on port 8080 'http://test.exampl.com:8080'* Upgrade the plugin* Restart 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-54636) Configure default audit logging output configuration
Title: Message Title C R commented on JENKINS-54636 Re: Configure default audit logging output configuration Matt Sicker I would like to do this. I checked and looks like the core uses log4j, not log4j 2. Am I missing something? 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-38268) Parallel step and closure scope
Title: Message Title
Kevin Phillips edited a comment on JENKINS-38268
Re: Parallel step and closure scope
Hmmm - I'm not sure if my case is exactly the same as this one, but it appears to me that this bug - or one similar to it - still exists. I'm running Jenkins v2.148 and Pipeline plugin v2.6 and can still break this parallel variable expansion problem, without using closures. Here's an example: {code:java}parallel ("thread1": {node() {def a = git(branch: 'BranchA', credentialsId: 'MyCreds', url: 'url/to/git/repo.git')def b = "1"def c = sh(returnStdout: true, script: 'echo 1').trim() echo "git commit " + a.GIT_COMMITecho "b is " + becho "c is " + c}},"thread2": {node() {def a = git(branch: 'BranchB', credentialsId: 'MyCreds', url: 'url/to/git/repo.git')def b = "2"def c = sh(returnStdout: true, script: 'echo 2').trim()echo "git commit " + a.GIT_COMMITecho "b is " + becho "c is " + c}}){code}In this example, I would expect the output to be something like{noformat}[thread1] git commit [thread1] b is 1[thread1] c is 1[thread2] git commit [thread2] b is 2[thread2] c is 2{noformat}What I actually get is this:{noformat}[thread1] git commit [thread1] b is 1[thread1] c is 1[thread2] git commit [thread2] b is 2[thread2] c is 2{noformat}While the 'b' and 'c' variables seem to get unique values for each of the parallel threads, the 'a' value becomes ambiguous, always returning a single Git commit hash.Further, I've confirmed that which Git commit hash that is shown represents the one that is executed "first" in the parallel stages. So, for example, if you put a small "sleep 5" at the top of thread1, then you get the Git commit has from BranchB in both echo statements, and if you move the sleep statement to the top of thread2 you get the has from BranchA.Also interesting is that although the 'a' variable seems to get confused based on the thread execution, the other variables do not. I thought at first that maybe assigning a static value to the variable may have explained the discrepancy like in the case of the 'b' variable so I added a dynamically executed shell step to the mix for variable 'c' and I get the same results as b... so I'm not sure how / why / what is going on here. Oh, and the other interesting thing I found as well is that if I rename the variables in the example code snippet so they are all unique names (ie: a,b,c in thread 1 and x,y,z in thread 2) the behavior results in the expected output as I mentioned above. So not only does this problem appear to be isolated to parallel threads, and to dynamic build steps, but also the variable names as well.
Add Comment
[JIRA] (JENKINS-54686) Use trilead-api plugin instead trilead-ssh2 from core
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-54686 Re: Use trilead-api plugin instead trilead-ssh2 from core ssh-slaves 1.28.1 does not use trilead-api, it was introduced in 1.29.0. I have tested a few stuff A fresh installation of Jenkins 2.152, I do not see the issue A fresh installation of Jenkins 2.73.3(I choose this because you can not install 1.29.X), then upgrade to 2.152 and upgrade the plugins, I do not see the issue 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-54686) Use trilead-api plugin instead trilead-ssh2 from core
Title: Message Title Csaba Sari commented on JENKINS-54686 Re: Use trilead-api plugin instead trilead-ssh2 from core Hi Ivan Fernandez Calvo, I can confirm Flemming Steffensen's report, exactly the same issue on CentOS 7, with Jenkins LTS 2.138.3. Only the 1.28.1 works for me. regards, Csaba 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-54729) jenkins dashboard displays stacktrace
Title: Message Title Mashrur mia commented on JENKINS-54729 Re: jenkins dashboard displays stacktrace I can confirm ssh-slave plugin 1.28.1 did the fix thanks Flemming Steffensen 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-22954) Setting Label String in Groovy Appears to only have a Delayed Effect.
Title: Message Title
Olivier Dagenais updated an issue
Jenkins / JENKINS-22954
Setting Label String in Groovy Appears to only have a Delayed Effect.
Change By:
Olivier Dagenais
equested Requested Feature: make Jenkins.labelTrim() a public method.I have a build task which runs a groovy script to change node labels from "operational" to "maintenance". I then launch a sub-project job which has a "restrict which nodes it can run on" set to "operational". It nevertheless runs on a node that was just labeled "maintenance".This is the code that sets the labels:{noformat}...slaves.each { slave -> out.println("Slave $slave.nodeName : Labels: $slave.labelString") def node_type switch(slave.nodeName) {case ~/^centos5-[^-]+-bld-slave-[0-9]+$/: node_type = "maintenance_centos" breakcase ~/^centos5-[^-]+-pipeline-slave-[0-9]+$/: node_type = "maintenance_pipeline" breakcase ~/^w2k8r2-bld-[0-9]+$/: node_type = "maintenance_win_bld" breakcase ~/^w2k8r2-test-[0-9]+$/: node_type = "maintenance_win_test" breakcase ~/^w2k8r2-sign-[0-9]+$/: node_type = "maintenance_win_sign" breakcase ~/^mac-.*$/: node_type = "maintenance_mac" breakcase ~/^cent-docsdemo-[0-9]+$/: node_type = "maintenance_docs" breakcase ['qa-master', 'qa-patch', 'qa-rc', 'qa-alto']: node_type = "maintenance_controller" breakdefault: node_type = "maintenance_unknown" break } def labelString = slave.labelString labelString = labelString.replaceAll(/ *operational/, '') labelString = labelString.replaceAll(/ *test-op/, '') labelString = labelString.replaceAll(/ *test-maint/, '') labelString = labelString.replaceAll(/ *maintenance[_a-z]*/, '') if (!dry_run) {slave.setLabelString(labelString+" maintenance "+node_type) } out.println(" --> New labels: $slave.labelString")}hudson.model.Hudson.instance.save()...{noformat}This is the log extract from the build, clearly showing that it selected a node labeled "maintenance":{noformat}04:59:48 Building remotely on centos5-x64-pipeline-slave-03 (maintenance btd-launchers maintenance_pipeline admin-pipeline) in workspace /build/jenkins/workspace/admin-slaves-root{noformat}Finally, attached is a screenshot showing the config, where the node restriction is defined.
[JIRA] (JENKINS-22954) Setting Label String in Groovy Appears to only have a Delayed Effect.
Title: Message Title
Olivier Dagenais updated an issue
Jenkins / JENKINS-22954
Setting Label String in Groovy Appears to only have a Delayed Effect.
Change By:
Olivier Dagenais
Requested equested Feature: make Jenkins.labelTrim() a public method.I have a build task which runs a groovy script to change node labels from "operational" to "maintenance". I then launch a sub-project job which has a "restrict which nodes it can run on" set to "operational". It nevertheless runs on a node that was just labeled "maintenance".This is the code that sets the labels:{noformat}...slaves.each { slave -> out.println("Slave $slave.nodeName : Labels: $slave.labelString") def node_type switch(slave.nodeName) {case ~/^centos5-[^-]+-bld-slave-[0-9]+$/: node_type = "maintenance_centos" breakcase ~/^centos5-[^-]+-pipeline-slave-[0-9]+$/: node_type = "maintenance_pipeline" breakcase ~/^w2k8r2-bld-[0-9]+$/: node_type = "maintenance_win_bld" breakcase ~/^w2k8r2-test-[0-9]+$/: node_type = "maintenance_win_test" breakcase ~/^w2k8r2-sign-[0-9]+$/: node_type = "maintenance_win_sign" breakcase ~/^mac-.*$/: node_type = "maintenance_mac" breakcase ~/^cent-docsdemo-[0-9]+$/: node_type = "maintenance_docs" breakcase ['qa-master', 'qa-patch', 'qa-rc', 'qa-alto']: node_type = "maintenance_controller" breakdefault: node_type = "maintenance_unknown" break } def labelString = slave.labelString labelString = labelString.replaceAll(/ *operational/, '') labelString = labelString.replaceAll(/ *test-op/, '') labelString = labelString.replaceAll(/ *test-maint/, '') labelString = labelString.replaceAll(/ *maintenance[_a-z]*/, '') if (!dry_run) {slave.setLabelString(labelString+" maintenance "+node_type) } out.println(" --> New labels: $slave.labelString")}hudson.model.Hudson.instance.save()...{noformat}This is the log extract from the build, clearly showing that it selected a node labeled "maintenance":{noformat}04:59:48 Building remotely on centos5-x64-pipeline-slave-03 (maintenance btd-launchers maintenance_pipeline admin-pipeline) in workspace /build/jenkins/workspace/admin-slaves-root{noformat}Finally, attached is a screenshot showing the config, where the node restriction is defined.
[JIRA] (JENKINS-54633) build dedicated VPC while installing evergreen on AWS
Title: Message Title Baptiste Mathus updated JENKINS-54633 Jenkins / JENKINS-54633 build dedicated VPC while installing evergreen on AWS Change By: Baptiste Mathus 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-52493) Declarative: Steps don't run inside container with "dockerfile true"
Title: Message Title
Reinout van Rees commented on JENKINS-52493
Re: Declarative: Steps don't run inside container with "dockerfile true"
Same here with a similar Jenkinsfile. I even tried placing the `agent { dockerfile true }` line inside the stage, but it still isn't getting used. To debug the issue, I placed a `sh pwd` in the stage, which prints the current working directory: `/var/lib/jenkins/jobs/nens/jobs/cookiecutter-staticsite-template/branches/master/workspace`, so it is indeed just running from the workspace, not from within the docker.
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-54708) org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/lib/layout/hasPermission.jelly:35:20:
Title: Message Title
Ivan Fernandez Calvo updated an issue
Jenkins / JENKINS-54708
org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/lib/layout/hasPermission.jelly:35:20: com/trilead/ssh2/crypto/Base64
Change By:
Ivan Fernandez Calvo
After updating jenkins to 2.152 I get the following error on all pages {code} org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/lib/layout/hasPermission.jelly:35:20: com/trilead/ssh2/crypto/Base64 at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:745) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:289) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.kohsuke.stapler.jelly.CompressTag.doTag(CompressTag.java:44) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) at
[JIRA] (JENKINS-54061) org.apache.commons.jelly.impl.TagScript.handleException
Title: Message Title
Ivan Fernandez Calvo updated an issue
Jenkins / JENKINS-54061
org.apache.commons.jelly.impl.TagScript.handleException
Change By:
Ivan Fernandez Calvo
A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened.Stack trace {code} org.apache.commons.jelly.JellyTagException: jar:file:/home/julian/.jenkins/war/WEB-INF/lib/jenkins-core-2.138.2.jar!/lib/hudson/actions.jelly:39:70: com/cloudbees/hudson/plugins/folder/properties/FolderCredentialsProvider at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:745) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:289) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at
[JIRA] (JENKINS-54758) Plugin Manager is available on AWS flavor
Title: Message Title Baptiste Mathus updated JENKINS-54758 Jenkins / JENKINS-54758 Plugin Manager is available on AWS flavor Change By: Baptiste Mathus 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-54758) Plugin Manager is available on AWS flavor
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-54758 Plugin Manager is available on AWS flavor Issue Type: Task Assignee: Baptiste Mathus Components: evergreen Created: 2018-11-21 15:36 Labels: aws Priority: Major Reporter: Baptiste Mathus Problem statement Accessing /pluginManager and easily installing plugins on AWS flavors is possible. It shouldn't. Also, no embeded docs available to explain why, etc. Expected These pages should be unreachable. Add Comment
[JIRA] (JENKINS-54758) Plugin Manager is available on AWS flavor
Title: Message Title Baptiste Mathus started work on JENKINS-54758 Change By: Baptiste Mathus 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-53815) several threads looping in TreeMap.put()
Title: Message Title Davide Angelocola closed an issue as Cannot Reproduce Jenkins / JENKINS-53815 several threads looping in TreeMap.put() Change By: Davide Angelocola Status: Open Closed Resolution: Cannot Reproduce 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-54686) Use trilead-api plugin instead trilead-ssh2 from core
Title: Message Title Flemming Steffensen commented on JENKINS-54686 Re: Use trilead-api plugin instead trilead-ssh2 from core Ivan Fernandez Calvo I were manually installing the plugins, and stopping the Jenkins service before each installation. The only two plugins changed on my system were ssh-slave and trilead-api. I manually tried these combinations (in this order), before I wrote here: 1.29.1 + 1.0.1 = Stacktrace on boot 1.29.1 + 1.0.0 = Stacktrace on boot 1.29.0 + 1.0.0 = Stacktrace on boot 1.28.1 + 1.0.0 = Works 1.28.1 + 1.0.1 = Works 1.29.0 + 1.0.1 = Stacktrace on boot Ended up using this combination: 1.28.1 + 1.0.1 = Works 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-54708) org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/lib/layout/hasPermission.jelly:35:20:
Title: Message Title Reinhold Füreder commented on JENKINS-54708 Re: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/lib/layout/hasPermission.jelly:35:20: com/trilead/ssh2/crypto/Base64 Ivan Fernandez Calvo Thanks for the confirmation! I'll therefore update tomorrow morning... 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-54686) Use trilead-api plugin instead trilead-ssh2 from core
Title: Message Title
Ivan Fernandez Calvo edited a comment on JENKINS-54686
Re: Use trilead-api plugin instead trilead-ssh2 from core
I have confirmation on a few issues that the upgrade to 1.29.1 fix the issue, it required a restart if not yo do not change the plugin, check that you are using the right version of the plugin by executing the following script in the Jenkins script console{code}result = ''for (plugin in Jenkins.instance.pluginManager.plugins) { result = result + "${plugin.displayName}" + ',' + "${plugin.version}\n"}return result{code} JENKINS-54061JENKINS-54713
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-54708) org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/lib/layout/hasPermission.jelly:35:20:
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-54708 Re: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/lib/layout/hasPermission.jelly:35:20: com/trilead/ssh2/crypto/Base64 Reinhold Füreder see my las comment on https://issues.jenkins-ci.org/browse/JENKINS-54686?focusedCommentId=354378=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-354378 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-54708) org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/lib/layout/hasPermission.jelly:35:20:
Title: Message Title Ivan Fernandez Calvo edited a comment on JENKINS-54708 Re: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/lib/layout/hasPermission.jelly:35:20: com/trilead/ssh2/crypto/Base64 [~reinholdfuereder] see my las latest comment on https://issues.jenkins-ci.org/browse/JENKINS-54686?focusedCommentId=354378=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-354378 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-54686) Use trilead-api plugin instead trilead-ssh2 from core
Title: Message Title
Ivan Fernandez Calvo commented on JENKINS-54686
Re: Use trilead-api plugin instead trilead-ssh2 from core
I have confirmation on a few issues that the upgrade to 1.29.1 fix the issue, it required a restart if not yo do not change the plugin, check that you are using the right version of the plugin by executing the following script in the Jenkins script console
result = ''
for (plugin in Jenkins.instance.pluginManager.plugins) {
result = result + "${plugin.displayName}" + ',' + "${plugin.version}\n"
}
return result
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-54699) Durable Task Version 1.28 break jenkins pipeline
Title: Message Title Devin Nusbaum commented on JENKINS-54699 Re: Durable Task Version 1.28 break jenkins pipeline laurent gil You can see the only change from Durable Task 1.27 to 1.28 here, and given the stack trace you posted I just don't see how it could be related to that change. Maybe there is an bug in Script Security that shows up rarely after a restart or something, although reading the error again it actually looks like it might be an internal issue in Guava's LocalCache itself (hence the AssertionError without a useful error message). Do you have a minimal Pipeline that can reproduce the error? Did you see any additional stack traces in your logs that might be relevant? 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-38268) Parallel step and closure scope
Title: Message Title
Kevin Phillips commented on JENKINS-38268
Re: Parallel step and closure scope
Hmmm - I'm not sure if my case is exactly the same as this one, but it appears to me that this bug - or one similar to it - still exists. I'm running Jenkins v2.148 and Pipeline plugin v2.6 and can still break this parallel variable expansion problem, without using closures. Here's an example:
parallel (
"thread1": {
node() {
def a = git(branch: 'BranchA', credentialsId: 'MyCreds', url: 'url/to/git/repo.git')
def b = "1"
def c = sh(returnStdout: true, script: 'echo 1').trim()
echo "git commit " + a.GIT_COMMIT
echo "b is " + b
echo "c is " + c
}
},
"thread2": {
node() {
def a = git(branch: 'BranchB', credentialsId: 'MyCreds', url: 'url/to/git/repo.git')
def b = "2"
def c = sh(returnStdout: true, script: 'echo 2').trim()
echo "git commit " + a.GIT_COMMIT
echo "b is " + b
echo "c is " + c
}
}
)
In this example, I would expect the output to be something like
[thread1] git commit
[thread1] b is 1
[thread1] c is 1
[thread2] git commit
[thread2] b is 2
[thread2] c is 2
What I actually get is this:
[thread1] git commit
[thread1] b is 1
[thread1] c is 1
[thread2] git commit
[thread2] b is 2
[thread2] c is 2
While the 'b' and 'c' variables seem to get unique values for each of the parallel threads, the 'a' value becomes ambiguous, always returning a single Git commit hash. Further, I've confirmed that which Git commit hash that is shown represents the one that is executed "first" in the parallel stages. So, for example, if you put a small "sleep 5" at the top of thread1, then you get the Git commit has from BranchB in both echo statements, and if you move the sleep statement to the top of thread2 you get the has from BranchA. Also interesting is that although the 'a' variable seems to get confused based on the thread execution, the other variables do not. I thought at first that maybe assigning a static value to the variable may have explained the discrepancy like in the case of the 'b' variable so I added a dynamically executed shell step to the mix for variable 'c' and I get the same results as b... so I'm not sure how / why / what is going on here. Oh, and the other interesting thing I found as well is that if I rename the variables in the example code snippet so they are all unique names (ie: a,b,c in thread 1 and x,y,z in thread 2) the behavior results in the expected output as I mentioned above. So not only does this problem appear to be isolated to parallel threads, and to dynamic build steps, but also the
[JIRA] (JENKINS-54678) Logs are lost in Multibranch Pipleline after the build has finished
Title: Message Title Thomas Vuillaume commented on JENKINS-54678 Re: Logs are lost in Multibranch Pipleline after the build has finished Same problem spotted on 2.138.2 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-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title Gabriel Lavoie edited a comment on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down The connection timeout error seen here has been a recurrent issue with the ec2-fleet plugin for us: https://issues.jenkins-ci.org/browse/JENKINS-53468?focusedCommentId=354028=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-354028Some debugging details are explained here: [https://github.com/jenkinsci/ec2-fleet-plugin/issues/41]I tracked this down to the Connection.connect() method of _trilead_ that doesn't clear up correctly the timeout handler, when the `kex` timeout is enabled and an exception occurs during the connection attempt. Created a PR about this: [ https://github.com/jenkinsci/trilead-ssh2/pull/36 ]Should I create a separate ticket for this? 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-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title Gabriel Lavoie commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down The connection timeout error seen here has been a recurrent issue with the ec2-fleet plugin for us: https://issues.jenkins-ci.org/browse/JENKINS-53468?focusedCommentId=354028=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-354028 Some debugging details are explained here: https://github.com/jenkinsci/ec2-fleet-plugin/issues/41 I tracked this down to the Connection.connect() method of trilead that doesn't clear up correctly the timeout handler, when the `kex` timeout is enabled and an exception occurs during the connection attempt. Created a PR about this: https://github.com/jenkinsci/trilead-ssh2/pull/36 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-54753) SV 5.00 is not supported
Title: Message Title Pavel Chuchma commented on JENKINS-54753 Re: SV 5.00 is not supported Fixed in my fork, PR created: https://github.com/jenkinsci/hpe-application-automation-tools-plugin/pull/198 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-54753) SV 5.00 is not supported
Title: Message Title Pavel Chuchma started work on JENKINS-54753 Change By: Pavel Chuchma 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-54753) SV 5.00 is not supported
Title: Message Title Pavel Chuchma assigned an issue to Pavel Chuchma Jenkins / JENKINS-54753 SV 5.00 is not supported Change By: Pavel Chuchma Assignee: Daniel Gront Pavel Chuchma 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-54757) High CPU caused by dumping the classloader in CpsFlowExecution
Title: Message Title Grigor Lechev created an issue Jenkins / JENKINS-54757 High CPU caused by dumping the classloader in CpsFlowExecution Issue Type: Bug Assignee: Unassigned Components: workflow-cps-plugin Created: 2018-11-21 13:58 Environment: Jenkins 2.144, Workflow CPS Plugin 2.60, Job DSL Plugin 1.70 Priority: Major Reporter: Grigor Lechev I have a pretty big system, 1000+ Jenkins items (mostly pipelines), 50+ slaves at all times.I'm investigating some high CPU issues after the upgrade to 2.144 (I've upgraded the plugins as well, so I doubt it's really Jenkins core). What caught my eye is the following stacktrace (a few variations of it): java.lang.Thread.State: RUNNABLE at java.lang.String.valueOf(String.java:2994) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.cleanUpGlobalClassValue(CpsFlowExecution.java:1345) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.cleanUpLoader(CpsFlowExecution.java:1291) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.cleanUpHeap(CpsFlowExecution.java:1265) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:375) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$200(CpsThreadGroup.java:83) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:244) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:232) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64) at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[JIRA] (JENKINS-39143) Stage view disappears after restarting jenkins
Title: Message Title Omar Malik commented on JENKINS-39143 Re: Stage view disappears after restarting jenkins I have the same issue and get this error. java.lang.IllegalStateException: Matching start node 3 lost from deserialization at org.jenkinsci.plugins.workflow.graph.BlockEndNode.getStartNode(BlockEndNode.java:65) I am fairly new to Jenkins though. 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-54754) JellyTestSuiteBuilder complains about escape-by-default
Title: Message Title Oleg Nenashev commented on JENKINS-54754 Re: JellyTestSuiteBuilder complains about escape-by-default CC Daniel Beck Wadeck Follonier 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-54700) Findbugs SAXParser not found
Title: Message Title Christian Asselmeyer commented on JENKINS-54700 Re: Findbugs SAXParser not found I think I ran into the same issue in the 1.0.0-beta5 when collecting SpotBugs results: [SpotBugs] Using default pattern '**/target/spotbugsXml.xml' since user defined pattern is not set [SpotBugs] [ERROR] Parsing of file '/target/spotbugsXml.xml' failed due to an exception: org.dom4j.DocumentException: Sax error Nested exception: SAX2 driver class org.apache.xerces.parsers.SAXParser not found at edu.umd.cs.findbugs.SortedBugCollection.doReadXML(SortedBugCollection.java:391) at edu.umd.cs.findbugs.SortedBugCollection.doReadXML(SortedBugCollection.java:368) at edu.umd.cs.findbugs.SortedBugCollection.readXML(SortedBugCollection.java:355) at edu.hm.hafner.analysis.parser.FindBugsParser.readXml(FindBugsParser.java:230) at edu.hm.hafner.analysis.parser.FindBugsParser.parse(FindBugsParser.java:175) at edu.hm.hafner.analysis.parser.FindBugsParser.parse(FindBugsParser.java:111) at edu.hm.hafner.analysis.parser.FindBugsParser.parse(FindBugsParser.java:97) at edu.hm.hafner.analysis.IssueParser.parse(IssueParser.java:70) at io.jenkins.plugins.analysis.core.util.FilesScanner.aggregateIssuesOfFile(FilesScanner.java:101) at io.jenkins.plugins.analysis.core.util.FilesScanner.scanFiles(FilesScanner.java:85) at io.jenkins.plugins.analysis.core.util.FilesScanner.invoke(FilesScanner.java:68) at io.jenkins.plugins.analysis.core.util.FilesScanner.invoke(FilesScanner.java:29) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3084) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: org.xml.sax.SAXException: SAX2 driver class org.apache.xerces.parsers.SAXParser not found java.lang.ClassNotFoundException: org.apache.xerces.parsers.SAXParser at org.xml.sax.helpers.XMLReaderFactory.loadClass(XMLReaderFactory.java:230) at org.xml.sax.helpers.XMLReaderFactory.createXMLReader(XMLReaderFactory.java:191) at edu.umd.cs.findbugs.SortedBugCollection.doReadXML(SortedBugCollection.java:388) ... 20 more Caused by: java.lang.ClassNotFoundException: org.apache.xerces.parsers.SAXParser at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1374) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1327) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1080) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch4(RemoteClassLoader.java:845) at hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch3(RemoteClassLoader.java:889) at sun.reflect.GeneratedMethodAccessor5348.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:929) at hudson.remoting.Request$2.run(Request.java:369) at
[JIRA] (JENKINS-54724) ssh-credentials-plugin broken when using ssh-slaves-plugin 1.29.0
Title: Message Title Ivan Fernandez Calvo resolved as Fixed Jenkins / JENKINS-54724 ssh-credentials-plugin broken when using ssh-slaves-plugin 1.29.0 Change By: Ivan Fernandez Calvo Status: Reopened Resolved Resolution: Fixed Released As: ssh-slaves-1.29.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54755) Disable "Require branches to be up to date before merging" on Evergreen repo
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-54755
Disable "Require branches to be up to date before merging" on Evergreen repo
Change By:
Baptiste Mathus
h3. Problem statementWe enabled some time ago the fact that reviews were required.In the go, we also enabled the fact that the branch **must** be up-to-date.This makes sense in general, but is mostly a waste of time in our time, given we use the merge strategy, i.e. Jenkins will first merge the PR against master, then build it (showing up as {{pr-merge}} on the PR status check).I assume this GitHub settings makes sense for other CI systems or when Jenkins is only configured to build the so-called {{pr-head}}.h3. ExpectedWe should only require reviews.We can allow not being up to date with master branch given we build {{pr-merge}}. to clarify, we need to uncheck the bolded line: !to be unchecked.png!
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54755) Disable "Require branches to be up to date before merging" on Evergreen repo
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-54755 Disable "Require branches to be up to date before merging" on Evergreen repo Change By: Baptiste Mathus Attachment: to be unchecked.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54756) No page found 'config.jelly' for class org.jenkinsci.plugins.configfiles.GlobalConfigFiles
Title: Message Title xiao baozi created an issue Jenkins / JENKINS-54756 No page found 'config.jelly' for class org.jenkinsci.plugins.configfiles.GlobalConfigFiles Issue Type: Bug Assignee: xiao baozi Components: config-file-provider-plugin Created: 2018-11-21 13:14 Environment: Jenkins ver. 2.138.2 jdk8 centos6.x Priority: Blocker Reporter: xiao baozi org.apache.commons.jelly.JellyTagException: jar:file:/root/.jenkins/war/WEB-INF/lib/jenkins-core-2.138.2.jar!/jenkins/model/Jenkins/configure.jelly:51:84: No page found 'config.jelly' for class org.jenkinsci.plugins.configfiles.GlobalConfigFiles at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:124) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at
[JIRA] (JENKINS-54755) Disable "Require branches to be up to date before merging" on Evergreen repo
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-54755 Disable "Require branches to be up to date before merging" on Evergreen repo Change By: Baptiste Mathus Sprint: Evergreen - Milestone 2 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-54755) Disable "Require branches to be up to date before merging" on Evergreen repo
Title: Message Title Baptiste Mathus commented on JENKINS-54755 Re: Disable "Require branches to be up to date before merging" on Evergreen repo I will proceed about this later today or tomorrow I think. Cc R. Tyler Croy in case you think this should be preserved for a good reason and you possibly actually configured it this way on purpose. Thanks 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-54755) Disable "Require branches to be up to date before merging" on Evergreen repo
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-54755 Disable "Require branches to be up to date before merging" on Evergreen repo Issue Type: Task Assignee: Baptiste Mathus Components: evergreen Created: 2018-11-21 13:02 Priority: Minor Reporter: Baptiste Mathus Problem statement We enabled some time ago the fact that reviews were required. In the go, we also enabled the fact that the branch *must* be up-to-date. This makes sense in general, but is mostly a waste of time in our time, given we use the merge strategy, i.e. Jenkins will first merge the PR against master, then build it (showing up as pr-merge on the PR status check). I assume this GitHub settings makes sense for other CI systems or when Jenkins is only configured to build the so-called pr-head. Expected We should only require reviews. We can allow not being up to date with master branch given we build pr-merge. Add Comment
[JIRA] (JENKINS-54680) Compressed build logs not rendering with update to workflow-job plugin >= 2.26
Title: Message Title Daniel Beck assigned an issue to Unassigned Jenkins / JENKINS-54680 Compressed build logs not rendering with update to workflow-job plugin >= 2.26 Change By: Daniel Beck Assignee: Daniel Beck 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-54754) JellyTestSuiteBuilder complains about escape-by-default
Title: Message Title Valentin Titov created an issue Jenkins / JENKINS-54754 JellyTestSuiteBuilder complains about escape-by-default Issue Type: Bug Assignee: Unassigned Components: ui-samples-plugin Created: 2018-11-21 12:51 Environment: current version on github Priority: Minor Reporter: Valentin Titov When running mvn test for ui-samples-plugin I get an error: [ERROR] Tests run: 29, Failures: 1, Errors: 4, Skipped: 0, Time elapsed: 17.758 s <<< FAILURE! - in InjectedTest [ERROR] index.jelly(org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyCheck) Time elapsed: 0.009 s <<< FAILURE! java.lang.AssertionError: is missing in file:/E:/Users/Public/vititov/build/github/ui-samples-plugin/target/classes/index.jelly at org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyCheck.runTest(JellyTestSuiteBuilder.java:108) Please, check PR with a fix: https://github.com/jenkinsci/ui-samples-plugin/pull/6
[JIRA] (JENKINS-44670) Pipeline integration for Mantis Plugin
Title: Message Title Steffen Wilke edited a comment on JENKINS-44670 Re: Pipeline integration for Mantis Plugin We're also struggling with this. [~sogabe] is there any plan to implement this functionality (or even update the plugin in general)?Particularly, we're interested in providing the hyperlinks to the mantis system from the commit message. According to this commit on a fork of the plugin: [https://github.com/chrismathis/mantis-plugin/commit/cb2330a80ce202e34fc7381a8f1a63008606dbfc] it is possible to trigger an issue update but I don't see a solution for enabling hyperlinks to the mantis system for a pipeline job. 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-44670) Pipeline integration for Mantis Plugin
Title: Message Title Steffen Wilke edited a comment on JENKINS-44670 Re: Pipeline integration for Mantis Plugin We're also struggling with this. [~sogabe] is there any plan to implement this functionality (or even update the plugin in general)?Particularly, we're interested in providing the hyperlinks to the mantis system from the commit message. According to [This this commit on a fork of the plugin | : [https://github.com/chrismathis/mantis-plugin/commit/cb2330a80ce202e34fc7381a8f1a63008606dbfc] ] it is possible to trigger an issue update but I don't see a solution for enabling hyperlinks to the mantis system for a pipeline job. 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-44670) Pipeline integration for Mantis Plugin
Title: Message Title Steffen Wilke edited a comment on JENKINS-44670 Re: Pipeline integration for Mantis Plugin We're also struggling with this. [~sogabe] is there any plan to implement this functionality (or even update the plugin in general)?Particularly, we're interested in providing the hyperlinks to the mantis system from the commit message. According to [This commit on a fork of the plugin|[https://github.com/chrismathis/mantis-plugin/commit/cb2330a80ce202e34fc7381a8f1a63008606dbfc] , ] it is possible to trigger an issue update but I don't see a solution for enabling hyperlinks to the mantis system for a pipeline job. 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-44670) Pipeline integration for Mantis Plugin
Title: Message Title Steffen Wilke commented on JENKINS-44670 Re: Pipeline integration for Mantis Plugin We're also struggling with this. sogabe is there any plan to implement this functionality (or even update the plugin in general)? Particularly, we're interested in providing the hyperlinks to the mantis system from the commit message. According to [This commit on a fork of the plugin|https://github.com/chrismathis/mantis-plugin/commit/cb2330a80ce202e34fc7381a8f1a63008606dbfc,] it is possible to trigger an issue update but I don't see a solution for enabling hyperlinks to the mantis system for a pipeline job. 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-54752) Ansi plugin fails to render formatted console output
Title: Message Title
Michal Kruzik updated an issue
Jenkins / JENKINS-54752
Ansi plugin fails to render formatted console output
Change By:
Michal Kruzik
Ansicolor plugin throws error when formatted string appears in console output. Archived console logs are rendered just fine.Expected output: [exec] *Api Tests (300)* [exec] Testing api [exec] {color:#00cd00}*✔*{color} {color:#cd00cd}*SomeTest:*{color} Test {color:#00cd00}(0.28s){color} Rendered output:[exec] *Api Tests (329)* [exec] Testing api Followed by Stack trace exception:{code:java}java.lang.IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276) at hudson.MarkupText.addMarkup(MarkupText.java:270) at hudson.plugins.ansicolor.ColorConsoleAnnotator$1EmitterImpl.emitHtml(ColorConsoleAnnotator.java:74) at hudson.plugins.ansicolor.AnsiAttributeElement.emitClose(AnsiAttributeElement.java:42) at hudson.plugins.ansicolor.AnsiHtmlOutputStream.closeTagOfType(AnsiHtmlOutputStream.java:150) at hudson.plugins.ansicolor.AnsiHtmlOutputStream.setForegroundColor(AnsiHtmlOutputStream.java:335) at hudson.plugins.ansicolor.AnsiHtmlOutputStream.processDefaultTextColor(AnsiHtmlOutputStream.java:589) at hudson.plugins.ansicolor.AnsiOutputStream.processEscapeCommand(AnsiOutputStream.java:352) at hudson.plugins.ansicolor.AnsiOutputStream.write(AnsiOutputStream.java:138) at hudson.plugins.ansicolor.AnsiHtmlOutputStream.write(AnsiHtmlOutputStream.java:220){code}Whole stack trace in attachment. Example text that causes issue with disabled plugin: [32;1m✔ [39;22m [35;SomeTest: [39;22m Test [32m(11.15s) [39m
Add Comment
