[JIRA] (JENKINS-38721) Viewing canceled pipeline jobs can raise exception.
Title: Message Title Nick Sonneveld created an issue Jenkins / JENKINS-38721 Viewing canceled pipeline jobs can raise exception. Issue Type: Bug Assignee: Unassigned Attachments: jenkins_view_job_error.log Components: core, pipeline, workflow-job-plugin Created: 2016/Oct/05 5:43 AM Environment: Jenkins 2.24, workflow-job 2.7, Linux vmkvmx02 3.10.0-327.el7.x86_64 #1 SMP Thu Oct 29 17:29:29 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux Labels: exception pipeline Priority: Critical Reporter: Nick Sonneveld Sometimes when viewing cancelled pipeline jobs, an exception is shown. I'm not sure if it's all cancelled jobs or just particular ones. Can still view console logs by entering url in manually. javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/home/jenkins/plugins/workflow-job/WEB-INF/lib/workflow-job.jar!/org/jenkinsci/plugins/workflow/job/WorkflowRun/index.jelly:63:93: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.24.jar!/lib/hudson/summary.jelly:105:31: Cannot get property 'fullName' on null object
[JIRA] (JENKINS-38720) 500 Server Error when notifying master of new mercurial commit
Title: Message Title Nick Sonneveld updated an issue Jenkins / JENKINS-38720 500 Server Error when notifying master of new mercurial commit Change By: Nick Sonneveld Labels: exception mercurial scm Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38720) 500 Server Error when notifying master of new mercurial commit
Title: Message Title Nick Sonneveld updated an issue Jenkins / JENKINS-38720 500 Server Error when notifying master of new mercurial commit Change By: Nick Sonneveld Summary: 500 Server Error when notifying Jenkins master of new mercurial commit Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38720) 500 Server Error when notifying Jenkins of new mercurial commit
Title: Message Title Nick Sonneveld created an issue Jenkins / JENKINS-38720 500 Server Error when notifying Jenkins of new mercurial commit Issue Type: Bug Assignee: Unassigned Attachments: jenkins_notify.log Components: core, mercurial-plugin Created: 2016/Oct/05 5:33 AM Environment: Jenkins 2.24, Linux vmkvmx01 2.6.32-431.29.2.el6.x86_64 #1 SMP Sun Jul 27 15:55:46 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux Priority: Major Reporter: Nick Sonneveld Notifying Jenkins of a new mercurial commit via /mercurial/notifyCommit responds with a '500 Server Error'. It looks like the notification is accepted in the Jenkins logs but an exception is also raised. The logs also show all the job polling that is triggered, perhaps related to the issue? curl -v http://jenkins.bld.cbr.internal.example.com:8080/mercurial/notifyCommit?url="" * Trying 192.168.12.1... * Connected to jenkins.bld.cbr.internal.example.com (192.168.12.1) port 8080 (#0) > GET /mercurial/notifyCommit?url="" HTTP/1.1 > Host: jenkins.bld.cbr.internal.example.com:8080 > User-Agent: curl/7.43.0 > Accept: */* > < HTTP/1.1 500 Server Error < Connection: close < Server: Jetty(9.2.z-SNAPSHOT) < * Closing connection 0 Log snippet:
[JIRA] (JENKINS-38717) EC2 slave goes offline
Title: Message Title deepanshu madan commented on JENKINS-38717 Re: EC2 slave goes offline Francis Upton it still happens with v 1.36 The gradle build stops in between with "Agent went offline during the build" and with the error above. That error is too generic, I am not able to figure what's the root cause of it. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38085) Settings not appearing in the sidebar
Title: Message Title
Steven G Brown edited a comment on JENKINS-38085
Re: Settings not appearing in the sidebar
Jenkins serves the script with this URL:{noformat}https://my.jenkins.host/extensionList/hudson.console.ConsoleAnnotatorFactory/hudson.plugins.timestamper.annotator.TimestampAnnotatorFactory2/script.js{noformat}and it expires after a day. This is a problem for plugins because the script from the previous version might still be cached.The only way this URL can be changed within the plugin is to rename the {{TimestampAnnotatorFactory2}} class to something else. That's what I plan to do the next time the script changes.Other options:* Redirect to another URL using a relative path. This is what Timestamper 1.8.5 does, and the new URL includes the plugin version so that upgrading or downgrading the plugin causes the script to be re-downloaded. Now we know that it doesn't work on your system.* Redirect to another URL using an absolute path. However, if using a reverse proxy, it must be configured properly or the settings will not appear. (See [Jenkins.getRootUrlFromRequest|http://javadoc.jenkins-ci.org/jenkins/model/Jenkins.html#getRootUrlFromRequest()].) I'd rather pick another option that is not sensitive to how the proxy is configured.* Turn off the caching altogether by overridding [ConsoleAnnotatorFactory.doScriptJs|http://javadoc.jenkins-ci.org/hudson/console/ConsoleAnnotatorFactory.html#doScriptJs(org.kohsuke.stapler.StaplerRequest, org.kohsuke.stapler.StaplerResponse)]. I considered this, but it seems unfortunate to have the script downloaded every time.Ultimately, the best solution would be to have Jenkins include the plugin version or a timestamp in the URL. I've raised JENKINS-38719 to do this.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38719) ConsoleAnnotatorFactory serves stale JavaScript and CSS when a plugin is upgraded/downgraded
Title: Message Title Steven G Brown created an issue Jenkins / JENKINS-38719 ConsoleAnnotatorFactory serves stale _javascript_ and CSS when a plugin is upgraded/downgraded Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Oct/05 3:55 AM Environment: Latest Jenkins as of 2016-08-05 Priority: Minor Reporter: Steven G Brown When a plugin extends ConsoleAnnotatorFactory, it can serve a _javascript_ file and a CSS file. These resources expire after a day, which means that after upgrading or downgrading the plugin, they remain out of date for a while. This is most likely the cause of JENKINS-31213. It is possible to work around this within the plugins by renaming the ConsoleAnnotatorFactory subclass every time the _javascript_ or CSS files are changed. I wasn't able to find a better workaround - see this comment. This could be fixed within Jenkins by including the plugin version or the SESSION_HASH in the URL. The plugin version would allow the resources to be cached for longer, but the SESSION_HASH is probably easier to implement.
[JIRA] (JENKINS-36118) console output for a job run reports error
Title: Message Title Steven G Brown resolved as Cannot Reproduce Jenkins / JENKINS-36118 console output for a job run reports error Change By: Steven G Brown Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34019) ANSIColor plugin leaks format onto next line's timestamp
Title: Message Title Steven G Brown reopened an issue Changes were reverted for Timestamper 1.8.7. Overriding the style works fine for the default Jenkins theme, but clashes with custom themes. This can be fixed instead within the AnsiColor plugin by: Using a ConsoleAnnotatorFactory instead of inserting console notes into the log file. When a style continues to the next line, the ConsoleAnnotatorFactory can insert a closing tag at the end of the line and an opening tag at the beginning of the next line. This prevents the timestamps from being affected. Jenkins / JENKINS-34019 ANSIColor plugin leaks format onto next line's timestamp Change By: Steven G Brown Resolution: Fixed Status: Resolved Reopened Assignee: Steven G Brown Add Comment
[JIRA] (JENKINS-38390) Timestamp background color white
Title: Message Title Steven G Brown resolved as Fixed All changes made under JENKINS-34019 have been reverted. I have an idea about how it can be fixed within the AnsiColor plugin instead. Custom themes should look normal again. Fix released with Timestamper 1.8.7. Jenkins / JENKINS-38390 Timestamp background color white Change By: Steven G Brown Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-38717) EC2 slave goes offline
Title: Message Title Francis Upton commented on JENKINS-38717 Re: EC2 slave goes offline Please try plugin version 1.36 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38718) Add an extension point so github et al can expose their default branches via scm api
Title: Message Title Michael Neale edited a comment on JENKINS-38718 Re: Add an extension point so github et al can expose their default branches via scm api [~vivek] https://github.com/jenkinsci/scm-api-plugin/pull/15 - not sure if that is the best approach or best place, but is a stab in the dark..obviously to make it useful, one of the github plugins will need to implement this extension point (up to you how this is called, may affect where we put extension point) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38718) Add an extension point so github et al can expose their default branches via scm api
Title: Message Title Michael Neale commented on JENKINS-38718 Re: Add an extension point so github et al can expose their default branches via scm api Vivek Pandey https://github.com/jenkinsci/scm-api-plugin/pull/15 - not sure if that is the best approach or best place, but is a stab in the dark.. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38718) Add an extension point so github et al can expose their default branches via scm api
Title: Message Title Michael Neale assigned an issue to Vivek Pandey Jenkins / JENKINS-38718 Add an extension point so github et al can expose their default branches via scm api Change By: Michael Neale Assignee: Vivek Pandey Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38718) Add an extension point so github et al can expose their default branches via scm api
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-38718 Add an extension point so github et al can expose their default branches via scm api Issue Type: Task Assignee: Unassigned Components: blueocean-plugin, scm-api-plugin Created: 2016/Oct/05 2:35 AM Priority: Minor Reporter: Michael Neale Github and bitbucket (and likely others) have the concept of a default branch. This nominally is "master" by convention with git, but it is common enough for people to make up their own convention. With github you can tell github what the master branch is, and this changes the behavior of the UI somewhat. This is also exposed via the api. Given the importance of main/master/default branches in UI, it would be nice to be able to expose this via the respective plugins. The common dependency I believe is scm-api (even though the git implementation won't implement this extension, one of the github ones can, as it depends on git, which depends on scm-api) Add Comment
[JIRA] (JENKINS-38390) Timestamp background color white
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38390 Re: Timestamp background color white Code changed in jenkins User: Steven Brown Path: src/main/resources/hudson/plugins/timestamper/annotator/TimestampAnnotatorFactory2/style.css http://jenkins-ci.org/commit/timestamper-plugin/6b763a9b72afa21d7f3fe3a8e850612029bac335 Log: JENKINS-38390 JENKINS-34019 Revert timestamps style added by c31dc95 The style matched the default Jenkins theme, but clashed with custom themes. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34019) ANSIColor plugin leaks format onto next line's timestamp
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34019 Re: ANSIColor plugin leaks format onto next line's timestamp Code changed in jenkins User: Steven Brown Path: src/main/resources/hudson/plugins/timestamper/annotator/TimestampAnnotatorFactory2/style.css http://jenkins-ci.org/commit/timestamper-plugin/6b763a9b72afa21d7f3fe3a8e850612029bac335 Log: JENKINS-38390 JENKINS-34019 Revert timestamps style added by c31dc95 The style matched the default Jenkins theme, but clashed with custom themes. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34019) ANSIColor plugin leaks format onto next line's timestamp
Title: Message Title Steven G Brown updated an issue Jenkins / JENKINS-34019 ANSIColor plugin leaks format onto next line's timestamp Change By: Steven G Brown Comment: Seems to work with IE and Edge. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38390) Timestamp background color white
Title: Message Title Steven G Brown commented on JENKINS-38390 Re: Timestamp background color white That would fix this issue, but reintroduce JENKINS-34019. (The white background for the timestamps overrides the styling applied by the AnsiColor plugin.) I'd like to have a plan for dealing with both. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34019) ANSIColor plugin leaks format onto next line's timestamp
Title: Message Title Steven G Brown updated an issue Jenkins / JENKINS-34019 ANSIColor plugin leaks format onto next line's timestamp Change By: Steven G Brown Comment: Pushed fix for Chrome and Firefox. Not yet tested in Internet Explorer. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38717) EC2 slave goes offline
Title: Message Title
deepanshu madan updated an issue
Jenkins / JENKINS-38717
EC2 slave goes offline
Change By:
deepanshu madan
EC2 slaves are created and connected through ssh when a build is started but it goes offline after every 9-10 minutes with this error log.Jenkins - 2.7.4 EC2 plugin 1.35 *E2 slave machine system*: Groovy: 2.4.4Ant: Apache Ant(TM) version 1.9.6 compiled on June 29 2015JVM: 1.8.0_60 (Oracle Corporation 25.60-b23)OS: Linux 4.4.11-23.53.amzn1.x86_64 amd64{code:java}SEVERE: I/O error in channel jenkins-roadrunner-linux-builder-slave (i-9fc2c187)java.io.IOException: Unexpected termination of the channelat hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:73)Caused by: java.io.EOFExceptionat java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2335)at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2804)at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:802)at java.io.ObjectInputStream.(ObjectInputStream.java:299)at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48)at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:59){code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38717) EC2 slave goes offline
Title: Message Title
deepanshu madan updated an issue
Jenkins / JENKINS-38717
EC2 slave goes offline
Change By:
deepanshu madan
EC2 slaves are created and connected through ssh when a build is started but it goes offline after every 9-10 minutes with this error log. Jenkins - 2.7.4 *E2 slave system*: Groovy: 2.4.4Ant: Apache Ant(TM) version 1.9.6 compiled on June 29 2015JVM: 1.8.0_60 (Oracle Corporation 25.60-b23)OS: Linux 4.4.11-23.53.amzn1.x86_64 amd64 {code:java}SEVERE: I/O error in channel jenkins-roadrunner-linux-builder-slave (i-9fc2c187)java.io.IOException: Unexpected termination of the channelat hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:73)Caused by: java.io.EOFExceptionat java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2335)at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2804)at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:802)at java.io.ObjectInputStream.(ObjectInputStream.java:299)at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48)at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:59){code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38363) Investigate slow loading experience
Title: Message Title Michael Neale commented on JENKINS-38363 Re: Investigate slow loading experience Here are some gifs I made to get a baseline against the roughly equivalent "classic" screen, where blue ocean isn't as snappy as it needs to be: 1) main dashboard: http://www.giphy.com/gifs/26ufkjzMWkd09D4hW 2) Activity screen: http://www.giphy.com/gifs/l3vR23VQ30SGdeDAc (this isn't exactly one to one, as blue ocean is showing across branches). 3) showing pipeline results: http://www.giphy.com/gifs/l0MYNT0wNlpnRmNUI (once again, not quite the same, but a fair comparison I think). The most prominent bad UX is on cold cache load of course, but I thought I should point out these others. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38717) EC2 slave goes offline
Title: Message Title deepanshu madan created an issue Jenkins / JENKINS-38717 EC2 slave goes offline Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 2016/Oct/05 1:49 AM Labels: plugin jenkins ec2 ec2-plugin connection ssh-slave Priority: Critical Reporter: deepanshu madan EC2 slaves are created and connected through ssh when a build is started but it goes offline after every 9-10 minutes with this error log. SEVERE: I/O error in channel jenkins-roadrunner-linux-builder-slave (i-9fc2c187) java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:73) Caused by: java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2335) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2804) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:802) at java.io.ObjectInputStream.(ObjectInputStream.java:299) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:59)
[JIRA] (JENKINS-35776) Bundle all licenses in the license directory and display them on /legal
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-35776 Bundle all licenses in the license directory and display them on /legal Change By: Michael Neale Sprint: 1.0-m7 , indian Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35776) Bundle all licenses in the license directory and display them on /legal
Title: Message Title Michael Neale commented on JENKINS-35776 Re: Bundle all licenses in the license directory and display them on /legal I used npm-license-crawler and it was able to dig up the licences for all the libraries - is this what is needed? It is fairly simple to use. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38675) gerrit trigger git summary show refspec instead of branch
Title: Message Title Jacob Keller commented on JENKINS-38675 Re: gerrit trigger git summary show refspec instead of branch I disagree with the removal of git-plugin and git-client-plugin as I believe that it probably requires a change in more than just the gerrit-trigger-plugin.. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38655) org.jvnet.winp.WinpException: Failed to read RT_USER_PROCESS_PARAMETERS
Title: Message Title Mark Waite commented on JENKINS-38655 Re: org.jvnet.winp.WinpException: Failed to read RT_USER_PROCESS_PARAMETERS Can you further clarify which (if any) of the scenarios described in my first comment apply in your case? Are you using TFS? Are _ and ! the only special characters in the password? Any other hints that would allow someone else to duplicate the problem (and thus be sure it is fixed in some future release)? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38675) gerrit trigger git summary show refspec instead of branch
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-38675 gerrit trigger git summary show refspec instead of branch Change By: Mark Waite Component/s: git-client-plugin Component/s: git-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28178) Option to disable sandbox in CpsScmFlowDefinition
Title: Message Title
Patrick Wolf edited a comment on JENKINS-28178
Re: Option to disable sandbox in CpsScmFlowDefinition
Regarding the sandbox there are a few things I wanted to point out:* The built in whitelist (and blacklist) for Script Security is available in GitHub and can be updated via a Pull Request to add more signatures. This is a great way to add common, safe functions to the sandbox that benefits everyone:** [Whitelists| https://github.com/jenkinsci/script-security-plugin/tree/master/src/main/resources/org/jenkinsci/plugins/scriptsecurity/sandbox/whitelists ] ** [Ticket on how to update whitelist| https://issues.jenkins-ci.org/browse/JENKINS-25804 ] * If you create a Shared library at the Jenkins master level all functions in this library are assumed to be safe (users must have run_script access to create add these libraries) and will bypass the sandbox.** [Shared Libraries| https://github.com/jenkinsci/workflow-cps-global-lib-plugin ] * As I mentioned in a previous comment above it is possible to append or override the Sandbox with a plugin. It would be possible to create a plugin that whitelisted everything automatically. It would not disable the sandbox but would make it allow everything. Creating this functionality as a separate plugin would be preferable to having it as part of the core functionality. This way users who want to disable the sandbox can actively do so but others aren't exposed to large security holes through misconfigurations. Can we get someone to volunteer to create such a plugin?** [Comment| https://issues.jenkins-ci.org/browse/JENKINS-28178?focusedCommentId=255040=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-255040 ] * Lastly, Andrew Bayer ([~abayer]) presented the new Declarative Pipeline syntax at Jenkins World. This is installed with the {{pipeline-model-definition}} plugin. This plugin extends Pipeline to include a declarative syntax that does not allow imperative scripting but simplifies the construction of pipeline stages, notifications, docker images, etc to execute pipeline steps. Having end users build their Pipelines using the declarative model with no scripting also allows any syntax errors to be found during compilation, instead of runtime, and should not trigger any script security errors, any Groovy methods would be built into the step definitions themselves.
Add Comment
[JIRA] (JENKINS-38363) Investigate slow loading experience
Title: Message Title Michael Neale commented on JENKINS-38363 Re: Investigate slow loading experience Keith Zantow right - https://github.com/jenkinsci/blueocean-plugin/pull/551 is a PR by tom that sets the cache headers. Will give it a try. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28178) Option to disable sandbox in CpsScmFlowDefinition
Title: Message Title
Patrick Wolf edited a comment on JENKINS-28178
Re: Option to disable sandbox in CpsScmFlowDefinition
Regarding the sandbox there are a few things I wanted to point out:* The built in whitelist (and blacklist) for Script Security is available in GitHub and can be updated via a Pull Request to add more signatures. This is a great way to add common, safe functions to the sandbox that benefits everyone:** https://github.com/jenkinsci/script-security-plugin/tree/master/src/main/resources/org/jenkinsci/plugins/scriptsecurity/sandbox/whitelists** https://issues.jenkins-ci.org/browse/JENKINS-25804* If you create a Shared library at the Jenkins master level all functions in this library are assumed to be safe (users must have run_script access to create add these libraries) and will bypass the sandbox.** https://github.com/jenkinsci/workflow-cps-global-lib-plugin*As I mentioned in a previous comment above it is possible to append or override the Sandbox with a plugin. It would be possible to create a plugin that whitelisted everything automatically. It would not disable the sandbox but would make it allow everything. Creating this functionality as a separate plugin would be preferable to having it as part of the core functionality. This way users who want to disable the sandbox can actively do so but others aren't exposed to large security holes through misconfigurations. Can we get someone to volunteer to create such a plugin?** https://issues.jenkins-ci.org/browse/JENKINS-28178?focusedCommentId=255040=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-255040* Lastly, Andrew Bayer ([~abayer]) presented the new Declarative Pipeline syntax at Jenkins World. This is installed with the {{pipeline-model-definition}} plugin. This plugin extends Pipeline to include a declarative syntax that does not allow imperative scripting but simplifies the construction of pipeline stages, notifications, docker images, etc to execute pipeline steps. Having end users build their Pipelines using the declarative model with no scripting also allows any syntax errors to be found during compilation, instead of runtime, and should not trigger any script security errors, any Groovy methods would be built into the step definitions themselves.
Add Comment
[JIRA] (JENKINS-28178) Option to disable sandbox in CpsScmFlowDefinition
Title: Message Title Patrick Wolf commented on JENKINS-28178 Re: Option to disable sandbox in CpsScmFlowDefinition Regarding the sandbox there are a few things I wanted to point out: The built in whitelist (and blacklist) for Script Security is available in GitHub and can be updated via a Pull Request to add more signatures. This is a great way to add common, safe functions to the sandbox that benefits everyone: https://github.com/jenkinsci/script-security-plugin/tree/master/src/main/resources/org/jenkinsci/plugins/scriptsecurity/sandbox/whitelists https://issues.jenkins-ci.org/browse/JENKINS-25804 If you create a Shared library at the Jenkins master level all functions in this library are assumed to be safe (users must have run_script access to create add these libraries) and will bypass the sandbox. https://github.com/jenkinsci/workflow-cps-global-lib-plugin *As I mentioned in a previous comment above it is possible to append or override the Sandbox with a plugin. It would be possible to create a plugin that whitelisted everything automatically. It would not disable the sandbox but would make it allow everything. Creating this functionality as a separate plugin would be preferable to having it as part of the core functionality. This way users who want to disable the sandbox can actively do so but others aren't exposed to large security holes through misconfigurations. Can we get someone to volunteer to create such a plugin? https://issues.jenkins-ci.org/browse/JENKINS-28178?focusedCommentId=255040=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-255040 Lastly, Andrew Bayer (Andrew Bayer) presented the new Declarative Pipeline syntax at Jenkins World. This is installed with the pipeline-model-definition plugin. This plugin extends Pipeline to include a declarative syntax that does not allow imperative scripting but simplifies the construction of pipeline stages, notifications, docker images, etc to execute pipeline steps. Having end users build their Pipelines using the declarative model with no scripting also allows any syntax errors to be found during compilation, instead of runtime, and should not trigger any script security errors, any Groovy methods would be built into the step definitions themselves.
[JIRA] (JENKINS-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Mark Waite resolved as Not A Defect Unfortunately, I'm unwilling to change the default behavior because that would change the default behavior for the 80 000+ installations of the git plugin. Some portion of those installations are predictably dependent on the (strange) default behavior of showing the committer name rather than the author name. It was considered to change that default behavior as part of the switch from git plugin 1 to git plugin 2, but then was decided to instead retain compatibility. I kept with that same decision in the switch from git plugin 2 to git plugin 3. Jenkins / JENKINS-38698 SCM Changelog: Commits, made via github, displayed with "noreply" user Change By: Mark Waite Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Tyrel Haveman edited a comment on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
Indeed, this was done to fix JENKINS-30744. Encoding the name gets rid of {{%2F}} which was there before in place of {{/}} in a branch name. Personally For our organization, {{%2F}} wasn't causing any problems (Maven doesn't seem to care) and I prefer it to this crap messy situation .
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38592) pipelines data for json is getting a bit too crazy (for dashboard)
Title: Message Title Michael Neale commented on JENKINS-38592 Re: pipelines data for json is getting a bit too crazy (for dashboard) Cliff Meyers yes I don't think the size, compressed, is a problem per se - its more the calculation of things like latestRun and perhaps some of the other things that may trip things up. It is a pain when diagnosing to look at the json as you can't see the wood for the trees. Good suggestions. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30744) multibranch issues if branch contains /
Title: Message Title Tyrel Haveman commented on JENKINS-30744 Re: multibranch issues if branch contains / Changing my workspace name from workspace/foo/bar%2Fstuff to workspace/foo_bar-stuff-ISUDFHISDHFG345934SDHFSDYG82734SDFH has created a lot of problems because it's much longer. I don't find this to be an acceptable solution. %2F wasn't causing any problems for our org. Why not actually use a / so we can have the workspaces organized with subdirectories? workspace/foo/bar/stuff would be great. Or, alternately, workspace/foo/bar_stuff would be fine. But workspace/foo_bar-stuff-ISUDFHISDHFG345934SDHFSDYG82734SDFH is not. As noted in JENKINS-38706, this is causing files within them to have extremely long paths such that Windows won't actually let us delete them (Jenkins, CMD, and Windows Explorer all fail to delete them. We have to rename them to shorter names first), which ends up causing us to run out of disk space because our branch builds never get deleted. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Tyrel Haveman commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline Indeed, this was done to fix JENKINS-30744. Encoding the name gets rid of %2F which was there before in place of / in a branch name. Personally %2F wasn't causing any problems and I prefer it to this crap. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38710) jira-ext plugin is not adding comment as expected
Title: Message Title Dan Alvizu commented on JENKINS-38710 Re: jira-ext plugin is not adding comment as expected This is an open source project, please be respectful of that. You are asking unrelated questions in a bug report about basic functionality. Please read this: http://www.catb.org/~esr/faqs/smart-questions.html > When you ask your question, display the fact that you have done these things first; this will help establish that you're not being a lazy sponge and wasting people's time. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Tyrel Haveman commented on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
I was looking a bit and Jenkins source trying to find out where this bug might be, and now I'm getting a terrible feeling that this might actually be intentional. Check out this chunk of a unit test in WorkflowBranchProjectFactoryTest.java:
story.j.assertLogContains("branch=dev/main", b1);
story.j.assertLogContains("workspace=dev_main-ZFNHWJSHKH4HUVOQUPOQV6WFX7XUPIKIAQAQ3DV7CCAGIXQW7YSA", b1);
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38710) jira-ext plugin is not adding comment as expected
Title: Message Title Basma Shahadat commented on JENKINS-38710 Re: jira-ext plugin is not adding comment as expected It is working smoothly. Can I pass any value generated by build in that field update? How? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Greg Smith commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline I would even vote for raising this to severe. I don't know what is worse – giant long workspace names, or randomly removing characters from the workspace names. I did go through and try to downlevel all of the plugins I had just updated – the problem never went away (I did it one by one – unfortunately, I was a couple of weeks behind, so there were a lot of updates) I just reached a point where my Jenkins install wouldn't start (too many cross dependencies), and I had to move back up to latest to get it started again. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title Sam Van Oort commented on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage Indeed – the branch name is the identifier in this case, it's up in the air if stages inside parallels will be supported in the UI or not. The syntax allows it, but just because you can doesn't mean you should! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38710) jira-ext plugin is not adding comment as expected
Title: Message Title Basma Shahadat commented on JENKINS-38710 Re: jira-ext plugin is not adding comment as expected Thanks. It is working now. We are testing field update now. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title Michael Neale commented on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage The name of the parallel "branches" do indeed look like stages, and provide and identifier (this shows up int he log as a prefix, and also in blue ocean visualisation as branches of execution). Sam Van Oort I wouldn't recomment putting stages inside of things until we decide how we want to visualise it. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38710) jira-ext plugin is not adding comment as expected
Title: Message Title Dan Alvizu commented on JENKINS-38710 Re: jira-ext plugin is not adding comment as expected You need to tell jira-ext that your tickets begin with `BUILDREL-` – you will need to set this in your JIRA ticket pattern in global configuration. Please read the configuration and the help there. It defaults to `FOO-,BAR` https://github.com/jenkinsci/jira-ext-plugin/blob/master/src/main/resources/org/jenkinsci/plugins/jiraext/Config/global.jelly#L20 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38710) jira-ext plugin is not adding comment as expected
Title: Message Title Basma Shahadat commented on JENKINS-38710 Re: jira-ext plugin is not adding comment as expected Thanks. Got it. It is working for single issue update. If i choose the option mentioned somewhere in commit message, it does not update. Here is my changes: Changes BUILDREL-3205: Testing JIRA ext plugins (detail) The Console log says: Updating JIRA tickets ChangeLogSet class: class hudson.plugins.git.GitChangeSetList Operation: Add a comment Finish updating JIRA tickets In JIRA ticket, i dont see any update. It works if i mention the same JIRA ticket# explicitly in single issue update. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Kseniia Nenasheva commented on JENKINS-38698 Re: SCM Changelog: Commits, made via github, displayed with "noreply" user Thanks Mark Waite, it's works. I had to replace git step in my pipeline, by the generic checkout step. IMHO, it would be great to have this behavior by default. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38677) Failure to create label in TFS
Title: Message Title Andrew Gray updated an issue Jenkins / JENKINS-38677 Failure to create label in TFS Change By: Andrew Gray Since upgrading to 5.2.1 of the TFS plugin bad things have started happening: Last step in job is to apply label to TFS if all unit tests pass. Instead I get this more often than not:Creating label 'TPS_1927' on '$/PSD Team/TPS/TPS App' as of the current version in workspace 'Hudson-TPS-MASTER'...ERROR: Build step failed with exceptionjava.lang.RuntimeException: java.lang.RuntimeException: Label creation failed. at hudson.plugins.tfs.model.Server.execute(Server.java:226) at hudson.plugins.tfs.TFSLabeler.perform(TFSLabeler.java:86) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665) at hudson.model.Run.execute(Run.java:1745) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404)Caused by: java.lang.RuntimeException: Label creation failed. at hudson.plugins.tfs.commands.LabelCommand.call(LabelCommand.java:70) at hudson.plugins.tfs.commands.LabelCommand.call(LabelCommand.java:22) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) at hudson.plugins.tfs.model.Server.execute(Server.java:222) ... 10 moreThis is REALLY BAD as we rely on labels to deploy by label via Web Deploy . Add Comment
[JIRA] (JENKINS-38710) jira-ext plugin is not adding comment as expected
Title: Message Title Dan Alvizu commented on JENKINS-38710 Re: jira-ext plugin is not adding comment as expected That is not the jira-ext plugin config. That is the JIRA plugin config Please look for jira-ext config. > Target host is null You have not set your host in global config. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38710) jira-ext plugin is not adding comment as expected
Title: Message Title Dan Alvizu resolved as Won't Fix Jenkins / JENKINS-38710 jira-ext plugin is not adding comment as expected Change By: Dan Alvizu Status: Reopened Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38710) jira-ext plugin is not adding comment as expected
Title: Message Title Basma Shahadat reopened an issue Jenkins / JENKINS-38710 jira-ext plugin is not adding comment as expected Change By: Basma Shahadat Resolution: Won't Fix Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38710) jira-ext plugin is not adding comment as expected
Title: Message Title Basma Shahadat commented on JENKINS-38710 Re: jira-ext plugin is not adding comment as expected Please find Global Configuration as attached. Here is full stack trace .. ERROR Updating jira notifications net.rcarz.jiraclient.JiraException: Failed to retrieve issue BUILDREL-3205 at net.rcarz.jiraclient.Issue.realGet(Issue.java:700) at net.rcarz.jiraclient.Issue.get(Issue.java:723) at net.rcarz.jiraclient.JiraClient.getIssue(JiraClient.java:90) at org.jenkinsci.plugins.jiraext.svc.impl.JiraClientSvcImpl.addCommentToTicket(JiraClientSvcImpl.java:78) at org.jenkinsci.plugins.jiraext.view.AddComment.perform(AddComment.java:78) at org.jenkinsci.plugins.jiraext.view.JiraExtBuildStep.perform(JiraExtBuildStep.java:63) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) at hudson.model.Build$BuildExecution.build(Build.java:205) at hudson.model.Build$BuildExecution.doRun(Build.java:162) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Caused by: java.lang.IllegalStateException: Target host is null at org.apache.http.util.Asserts.notNull(Asserts.java:52) at org.apache.http.impl.conn.DefaultHttpRoutePlanner.determineRoute(DefaultHttpRoutePlanner.java:98) at org.apache.http.impl.client.DefaultRequestDirector.determineRoute(DefaultRequestDirector.java:762) at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:381) at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:882) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55) at net.rcarz.jiraclient.RestClient.request(RestClient.java:126) at net.rcarz.jiraclient.RestClient.get(RestClient.java:243) at net.rcarz.jiraclient.Issue.realGet(Issue.java:698) ... 14 more Add Comment
[JIRA] (JENKINS-38710) jira-ext plugin is not adding comment as expected
Title: Message Title Basma Shahadat updated an issue Jenkins / JENKINS-38710 jira-ext plugin is not adding comment as expected Change By: Basma Shahadat Attachment: GlobalConfiguration.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32551) Pipeline script from SCM: ClearCase not available
Title: Message Title
George Bell commented on JENKINS-32551
Re: Pipeline script from SCM: ClearCase not available
When using the UCM Clearcase Plugin (not the Clearcase UCM plugin). When saving the job we get the following error: Caused by: java.lang.IllegalArgumentException: Caused by: java.lang.IllegalArgumentException: Failed to instantiate class hudson.scm.SCM from {"viewname":"Jenkins_$ {USER_NAME} _$ {NODE_NAME} _$ {JOB_NAME} $ {DASH_WORKSPACE_NUMBER} ","viewpath":"view","stream":"OLBB6.9.2_Int@/vobs/CTP_Proj","useupdate":true,"changeset": {"value":"branch"} ,"buildFoundationBaseline":false,"excludedRegions":"","mkviewoptionalparam":"","rmviewonrename":true,"multiSitePollBuffer":"","filterOutDestroySubBranchEvent":false,"overrideBranchName":"","stapler-class":"hudson.plugins.clearcase.ClearCaseUcmSCM","$class":"hudson.plugins.clearcase.ClearCaseUcmSCM"} at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:676) at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:478) at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:771) ... 81 more Caused by: java.lang.IllegalArgumentException: Failed to convert the changeset parameter of the constructor public hudson.plugins.clearcase.ClearCaseUcmSCM(java.lang.String,java.lang.String,java.lang.String,boolean,java.lang.String,java.lang.String,boolean,boolean,boolean,java.lang.String,java.lang.String,java.lang.String,boolean,boolean,boolean,boolean,java.lang.String,boolean,hudson.plugins.clearcase.AbstractClearCaseScm$ChangeSetLevel,hudson.plugins.clearcase.viewstorage.ViewStorage,boolean) at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:773) at org.kohsuke.stapler.RequestImpl.access$200(RequestImpl.java:83) at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:674) ... 83 more Caused by: java.lang.IllegalArgumentException: Failed to instantiate class hudson.plugins.clearcase.AbstractClearCaseScm$ChangeSetLevel from {"value":"branch"} at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:676) at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:478) at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:771) ... 85 more Caused by: org.kohsuke.stapler.NoStaplerConstructorException: There's no @DataBoundConstructor on any constructor of class hudson.plugins.clearcase.AbstractClearCaseScm$ChangeSetLevel at org.kohsuke.stapler.ClassDescriptor.loadConstructorParamNames(ClassDescriptor.java:247) at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:758) at org.kohsuke.stapler.RequestImpl.access$200(RequestImpl.java:83) at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:674) ... 87 more This seems to work if you change the {value:"no"} to just "no"...something about the way that enums are serialized from JSON I guess...adding the DataBoundConstructor to the enum doesn't work since it's a private constructor (and can't be made public)...how do we get the form to submit the JSON as a "no" instead of {value:"no"} ? My guess is it's something to do with https://github.com/jenkinsci/clearcase-plugin/blob/d27f8ec2ed99001b5d0ffb80dbbde045b4262c3a/src/main/resources/hudson/plugins/clearcase/ClearCaseUcmSCM/config.jelly Changeset section...maybe shouldn't be radio? But not sure if changing it will cause other problems (I don't have a good understanding of stapler).
[JIRA] (JENKINS-38313) External Build Log storage for Jenkins
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-38313 External Build Log storage for Jenkins Change By: Oleg Nenashev Jenkins' logging system is one of potential scalability bottlenecks on big Jenkins instances. System logging can be redirected via JUL log appenders (or other such solutions), but there is no OOTB solution for build logs.It would be great to have such solution . Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38381) Optimize log handling in Pipeline and Durable Task
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-38381 Optimize log handling in Pipeline and Durable Task Change By: Oleg Nenashev Summary: Optimize log handling in Pipeline and Durable Task Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-38698 SCM Changelog: Commits, made via github, displayed with "noreply" user Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Mark Waite commented on JENKINS-38698 Re: SCM Changelog: Commits, made via github, displayed with "noreply" user There is a setting in the git plugin which will change from showing the committer (likely the noreply in this case) to showing the author. The job definition likely is configured to the default which is to show the committer. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38281) Global variables starting with capital letter regression
Title: Message Title Phil Grayson commented on JENKINS-38281 Re: Global variables starting with capital letter regression Thank you for the update. I've migrated my affected code since. I'm happy for this ticket to be closed and I can raise a low priority feature request if you like. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25130) f:dropdownDescriptorSelector ignores help.html for the selected descriptor
Title: Message Title Jesse Glick commented on JENKINS-25130 Re: f:dropdownDescriptorSelector ignores help.html for the selected descriptor Seems that f:property has the same problem. rsandell seems to be working around this by preceding it with an empty f:entry. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38702) AccuRev for Jenkins Plugin does not display Depots
Title: Message Title Joseph Petersen commented on JENKINS-38702 Re: AccuRev for Jenkins Plugin does not display Depots Peter, by any chance would your H:\ drive also be your user's home location (usually default is C:\users\myuser)? If so this would actually conflict with accurev's behaviour using the C:\users\myuser\.accurev to put the folder. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34958) Getting "Your Authorization Token has expired" when using ECR credentials
Title: Message Title Javier Martínez commented on JENKINS-34958 Re: Getting "Your Authorization Token has expired" when using ECR credentials When this patch is going to be released? This is a blocking issue for our company. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38712) Pipeline Library - A large amount of indentation exists when setting up a library
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-38712 Pipeline Library - A large amount of indentation exists when setting up a library Change By: Daniel Beck Summary: Pipeline Library - A large amount of indentation exists when setting up a libraryA large amount of indentation exists when setting up a library Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Tyrel Haveman edited a comment on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
[~gregcovertsmith] Yeah, characters are being removed from the beginning of the name. It's not always just the first character, though; it seems to depend on the length of the build name. Longer names have more characters removed.We do have a workaround, but it's annoying: Inside the {{node}} element of our Jenkinsfile we wrap the entire build also with : { { code:java} ws("workspace/${env.JOB_NAME}") { // ... } {code } }
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Tyrel Haveman commented on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
Greg Smith Yeah, characters are being removed from the beginning of the name. It's not always just the first character, though; it seems to depend on the length of the build name. Longer names have more characters removed. We do have a workaround, but it's annoying: Inside the node element of our Jenkinsfile we wrap the entire build also with {{ws("workspace/$ {env.JOB_NAME} ") { ... } }}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38712) Pipeline Library - A large amount of indentation exists when setting up a libraryA large amount of indentation exists when setting up a library
Title: Message Title Jesse Glick updated JENKINS-38712 Jenkins / JENKINS-38712 Pipeline Library - A large amount of indentation exists when setting up a libraryA large amount of indentation exists when setting up a library Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38517) “Local module directory” not supported for external libraries
Title: Message Title Brian Ray commented on JENKINS-38517 Re: “Local module directory” not supported for external libraries This makes sense Jesse Glick. If I restructure the directory tree for these libraries in our SVN repo, I might be able to get what I am after. Thanks. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Greg Smith commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline This just happened to us as well. Not only are the names super long with that UUID like value on them, but the first character of the branch name is missing too. If you look at Tyrel's example, his directory name is "ine-job_my-branch" – that was probably supposed to be "line" or something else. We are also seeing the first character removed. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38716) editor not accessible to screenreader
Title: Message Title Michał Zegan created an issue Jenkins / JENKINS-38716 editor not accessible to screenreader Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Oct/04 8:54 PM Labels: accessibility Priority: Minor Reporter: Michał Zegan Although most/all of jenkins is usable by users using a screenreaders like me, it seems that the editor is not. I mean at least some places where I can enter multiline data, and that is for example editor of configuration files when using config file plugin, editor where you can enter shell scripts to execute for a build step, or anything that you can enter when your markup formatter is switched from plain to any other. Accessibility events are not reported when moving through the editor, so I do not know anything when I arrow through the text, there is just no feedback as it goes for normal html fields, so I cannot review what I type and read anything from the field, by any means. Add Comment
[JIRA] (JENKINS-38712) Pipeline Library - A large amount of indentation exists when setting up a libraryA large amount of indentation exists when setting up a library
Title: Message Title Jesse Glick commented on JENKINS-38712 Re: Pipeline Library - A large amount of indentation exists when setting up a libraryA large amount of indentation exists when setting up a library f:dropdownDescriptorSelector actually works much better—faster, safer, more convenient—except for the indentation issue, which is caused by this code. Ideally there would be some mode in which you could avoid creating the nested table. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-8942) Change configuration for Multiple jobs
Title: Message Title guy levy commented on JENKINS-8942 Re: Change configuration for Multiple jobs This works for me, you will need to write a script that will loop through your Jenkins jobs and SED the value with a new one then use POST https://support.cloudbees.com/hc/en-us/articles/218353308-How-to-update-job-config-files-using-the-REST-API-and-cURL Get current config curl -X GET http://developer:developer@localhost:8080/job/test/config.xml -o mylocalconfig.xml Post updated config curl -X POST http://developer:developer@localhost:8080/job/test/config.xml --data-binary "@mymodifiedlocalconfig.xml" Obviously, replace: developer:developer with your username:password localhost:8080 with your Jenkins URL test with your job name Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38712) Pipeline Library - A large amount of indentation exists when setting up a libraryA large amount of indentation exists when setting up a library
Title: Message Title Jesse Glick commented on JENKINS-38712 Re: Pipeline Library - A large amount of indentation exists when setting up a libraryA large amount of indentation exists when setting up a library A radio list gives a better appearance (at least with respect to indentation), but worse performance and robustness, which is why I did not use it to begin with. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16327) Pages with CodeMirror editors are impossibly wide
Title: Message Title Ollie ! commented on JENKINS-16327 Re: Pages with CodeMirror editors are impossibly wide As noted in the PR, this is a very good solution that works well in my testing. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38712) Pipeline Library - A large amount of indentation exists when setting up a libraryA large amount of indentation exists when setting up a library
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-38712 Pipeline Library - A large amount of indentation exists when setting up a libraryA large amount of indentation exists when setting up a library Change By: Jesse Glick Labels: ui Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38712) Pipeline Library - A large amount of indentation exists when setting up a libraryA large amount of indentation exists when setting up a library
Title: Message Title Jesse Glick started work on JENKINS-38712 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38712) Pipeline Library - A large amount of indentation exists when setting up a libraryA large amount of indentation exists when setting up a library
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-38712 Pipeline Library - A large amount of indentation exists when setting up a libraryA large amount of indentation exists when setting up a library Change By: Jesse Glick Component/s: workflow-cps-global-lib-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38550) "Pipeline Libraries" shouldn't show "Modern SCM" if no implementations exist
Title: Message Title Jesse Glick updated JENKINS-38550 Jenkins / JENKINS-38550 "Pipeline Libraries" shouldn't show "Modern SCM" if no implementations exist Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38715) Container instance cannot be empty error
Title: Message Title Jae Gangemi created an issue Jenkins / JENKINS-38715 Container instance cannot be empty error Issue Type: Bug Assignee: Jan Roehrich Components: amazon-ecs-plugin Created: 2016/Oct/04 8:21 PM Priority: Minor Reporter: Jae Gangemi i am getting the following error when trying to launch a build into ecs: com.amazonaws.services.ecs.model.InvalidParameterException: Container instance cannot be empty. (Service: AmazonECS; Status Code: 400; Error Code: InvalidParameterException; Request ID: 0c26d03e-8a6c-11e6-be2f-71463a1d5d9f) at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1307) at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:894) at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:597) at com.amazonaws.http.AmazonHttpClient.doExecute(AmazonHttpClient.java:363) at com.amazonaws.http.AmazonHttpClient.executeWithTimer(AmazonHttpClient.java:329) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:308) at com.amazonaws.services.ecs.AmazonECSClient.invoke(AmazonECSClient.java:) at com.amazonaws.services.ecs.AmazonECSClient.describeContainerInstances(AmazonECSClient.java:876) at com.cloudbees.jenkins.plugins.amazonecs.ECSService.waitForSufficientClusterResources(ECSService.java:180) at com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback.call(ECSCloud.java:255) at com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback.call(ECSCloud.java:237) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at
[JIRA] (JENKINS-37183) Pipeline text area doesn't have a horizontal scrollbar when long lines are long
Title: Message Title Jesse Glick commented on JENKINS-37183 Re: Pipeline text area doesn't have a horizontal scrollbar when long lines are long ACE editor issue. Need someone besides Tom FENNELLY to own this code. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37183) Pipeline text area doesn't have a horizontal scrollbar when long lines are long
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-37183 Pipeline text area doesn't have a horizontal scrollbar when long lines are long Change By: Jesse Glick Component/s: workflow-cps-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38710) jira-ext plugin is not adding comment as expected
Title: Message Title Dan Alvizu resolved as Won't Fix Please look at your global configuration. You're almost certainly missing stuff there, such as what jenkins server to use, how to authenticate, and what ticket prefixes you care about. If you're still seeing issues please paste your global configuration and the full stack trace. The stuff you've posted above is missing key information (the 'caused by' clause). Jenkins / JENKINS-38710 jira-ext plugin is not adding comment as expected Change By: Dan Alvizu Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Kseniia Nenasheva assigned an issue to Mark Waite Jenkins / JENKINS-38698 SCM Changelog: Commits, made via github, displayed with "noreply" user Change By: Kseniia Nenasheva Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Kseniia Nenasheva updated an issue Jenkins / JENKINS-38698 SCM Changelog: Commits, made via github, displayed with "noreply" user Change By: Kseniia Nenasheva Component/s: git-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Kseniia Nenasheva updated an issue Jenkins / JENKINS-38698 SCM Changelog: Commits, made via github, displayed with "noreply" user Change By: Kseniia Nenasheva Labels: changes git github pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Kseniia Nenasheva updated an issue Jenkins / JENKINS-38698 SCM Changelog: Commits, made via github, displayed with "noreply" user Change By: Kseniia Nenasheva Summary: SCM Changelog: Commits, made via github, displayed with "noreply" user Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16327) Pages with CodeMirror editors are impossibly wide
Title: Message Title Daniel Beck commented on JENKINS-16327 Re: Pages with CodeMirror editors are impossibly wide Ollie ! I asked someone else to take care of this, PR is at https://github.com/jenkinsci/jenkins/pull/2575 – if you have the time, test it to make sure it works as expected. There's a PR build you can download and try. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38517) “Local module directory” not supported for external libraries
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-38517 “Local module directory” not supported for external libraries Really I think Local module directory should be hidden in an Advanced block so that people are not tempted to use it. Not possible for workflow-cps-global-lib to even detect that it is in use, since SCM.getModuleRoots is limited to AbstractBuild. In principle the core API could be extended, but I think it is not worth the effort for a legacy feature like this. Change By: Jesse Glick Summary: Multiple shared libs throw "ERROR: Library expected to contain at least one of src or vars directories" when ... “Local module directory” not supported for external libraries Component/s: workflow-cps-global-lib-plugin Labels: pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38702) AccuRev for Jenkins Plugin does not display Depots
Title: Message Title Joseph Petersen commented on JENKINS-38702 Re: AccuRev for Jenkins Plugin does not display Depots Let me actually fix it. Before you wrote I had already thought it of a point of failure due to it just starting a process without any proper setup like where to execute command from. I will be back with a code change tomorrow that would make it a release tomorrow or the day after tomorrow. You shouldn't have to change your jenkins home. Clearly the plugin is doing something odd. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38517) “Local module directory” not supported for external libraries
Title: Message Title
Jesse Glick edited a comment on JENKINS-38517
Re: “Local module directory” not supported for external libraries
External libraries mandate that {{src/}} etc. be at the root of a “repository”, which in the case of Subversion would be a “version” folder such as { { …/trunk/}}, so it is correct to fail. Possibly it could fail with a more helpful error message, though I am not sure that is feasible—would have to look at what the API offers in this case.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38517) Multiple shared libs throw "ERROR: Library expected to contain at least one of src or vars directories" when ...
Title: Message Title
Jesse Glick updated an issue
Jenkins / JENKINS-38517
Multiple shared libs throw "ERROR: Library expected to contain at least one of src or vars directories" when ...
Change By:
Jesse Glick
... Multiple shared libs throw "ERROR: Library expected to contain at least one of src or vars directories" when multiple external SVN Legacy SCM libs are loaded by the Jenkinsfile *and* the *Local module directory* indicates preservation/overriding of the parent directory. (Ie, when the dot default is not used and a working copy root directory for each lib is created under the {{@libs}} directory.Configuration of global and folder specific libraries as shown in the attachments. The Jenkinsfile script begins{ quote code } @Library('pipeline_global_helpers') _@Library('pipeline_branch_build')import com.foo.bar.Application{ quote code }Running the pipeline makes it as far as checking out or updating the local working copies in the {{@libs/pipeline_global_helpers}} and {{@libs/pipeline_branch_build}} in the pipeline workspace on the master, but execution aborts thereafter with the stack trace{ quote code:none } ERROR: Library pipeline_branch_build expected to contain at least one of src or vars directoriesorg.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:WorkflowScript: Loading libraries failed1 error at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310) at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1073) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:591) at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:569) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:546) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268) at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688) at groovy.lang.GroovyShell.parse(GroovyShell.java:700) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:67) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:410) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:373) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:213) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Finished: FAILURE { quote code }The libraries both have {{src}} and {{vars}} subdirectories and cause no error if used individually if checked out with *Local module directory* set to the default dot (no working copy root directory). I have also avoided the error once or twice when overriding/preserving the working copy root directory when loading a single external library, but not reliably. Ultimately the above error recurs.Checking out straight into the {{@libs}} directory is good for the single-library
[JIRA] (JENKINS-38710) jira-ext plugin is not adding comment as expected
Title: Message Title Basma Shahadat commented on JENKINS-38710 Re: jira-ext plugin is not adding comment as expected When I am trying to update a single issue, I am getting the following error: Operation: Add a comment Updating ticket: BUILDREL-3205 ERROR Updating jira notifications net.rcarz.jiraclient.JiraException: Failed to retrieve issue BUILDREL-3205 at net.rcarz.jiraclient.Issue.realGet(Issue.java:700) at net.rcarz.jiraclient.Issue.get(Issue.java:723) at net.rcarz.jiraclient.JiraClient.getIssue(JiraClient.java:90) at org.jenkinsci.plugins.jiraext.svc.impl.JiraClientSvcImpl.addCommentToTicket(JiraClientSvcImpl.java:78) Is it because of connectivity issue? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38698) Commits, made via github, displayed with "noreply" user
Title: Message Title
Kseniia Nenasheva updated an issue
Jenkins / JENKINS-38698
Commits, made via github, displayed with "noreply" user
Change By:
Kseniia Nenasheva
+Steps:+# Create Pipeline job for any project on github. {code}node { def mvnHome stage('Preparation') { git 'https://github.com/user-github/project.git' mvnHome = tool 'M3' } stage('Build') { if (isUnix()) { sh "'${mvnHome}/bin/mvn' -Dmaven.test.failure.ignore clean package" } else { bat(/"${mvnHome}\bin\mvn" -Dmaven.test.failure.ignore clean package/) } stage('Results') { junit '**/target/surefire-reports/TEST-*.xml' archive 'target/*.jar' }}{code} # Open this project on github.# Edit any files via the web interface. Commit.# Run this job.# Check Recent Changes:*Expected Result:* Recent changes have been made the correct user from github.*Actual Result:* Recent changes have been made the "noreply" user. # Correct git log:{noformat}commit 497fb99ae5c481f72ea34fa2e190afa908660798Author: ksenia-nenasheva Date: Tue Oct 4 14:46:24 2016 +0200Update Jenkinsfilecommit bbf860b9a6c7a28208b717d42e6f8665b21063a8Author: ksenia-nenasheva Date: Tue Oct 4 14:18:41 2016 +0200Update Jenkinsfilecommit 7312064526032f050b04335b4676b27b48a698f0Author: ksenia-nenasheva Date: Tue Oct 4 13:56:31 2016 +0200Update Jenkinsfile{noformat}Please see the attached screenshots.
Add Comment
This message was sent by
[JIRA] (JENKINS-38714) Jenkins should delete queued item if a project is deleted
Title: Message Title Xing Yan created an issue Jenkins / JENKINS-38714 Jenkins should delete queued item if a project is deleted Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Oct/04 7:42 PM Priority: Minor Reporter: Xing Yan Currently in AbstractProject, when performDelete is called, it will call makeDisabled first, and makeDisabled will check if supportsMakeDisabled is true, if supportsMakeDisabled is true, all queued items will be canceled. What performDelete should really do is regardless supportsMakeDisabled is true or false, all queued items for the project needed to be canceled. Currently behavior will cause all jobs stuck in the queue. If a project got deleted, but it has job in the queue, and queued job is not canceled, all job after that will be queued and won't be run unless manually cancel the deleted job. Add Comment
[JIRA] (JENKINS-38550) "Pipeline Libraries" shouldn't show "Modern SCM" if no implementations exist
Title: Message Title Jesse Glick commented on JENKINS-38550 Re: "Pipeline Libraries" shouldn't show "Modern SCM" if no implementations exist I already updated the docs BTW. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38550) "Pipeline Libraries" shouldn't show "Modern SCM" if no implementations exist
Title: Message Title Jesse Glick started work on JENKINS-38550 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38381) Optimize log handling
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-38381 Optimize log handling Change By: Jesse Glick Component/s: workflow-api-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38021) Accessing unset global variable cause master to hang
Title: Message Title Jesse Glick commented on JENKINS-38021 Re: Accessing unset global variable cause master to hang you confirm that this is current and intended behavior? No, I was just offering a suggestion to fix your issue. Probably there is a StackOverflowError that some code TBD could defend against. Have you reproduced this? I have not yet tried. Even more strange behavior found Offhand this looks unrelated, please keep it to a separate issue (with steps to reproduce from scratch as usual). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38672) Git Organization plugin bug
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-38672 Git Organization plugin bug Change By: Arnaud Héritier Component/s: github-organization-folder-plugin Component/s: build-pipeline-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38679) Polling using legacy SCM fails: “Workspace doesn't contain https://svn/global-library-repo${library.myib.version}”
Title: Message Title
Jesse Glick commented on JENKINS-38679
Re: Polling using legacy SCM fails: “Workspace doesn't contain https://svn/global-library-repo${library.myib.version}”
the modern scm dropdown is empty
I know, I am trying to find someone to cut releases of the Subversion plugin; currently it is abandoned.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
